I have a fairly remedial CICS question. Due to recent cutbacks in our company we have lost all in-house CICS expertise. I am wanting to know if there is a way for a CICS program to start another CICS task and continue on with it's logic without waiting for a return from the newly started task. We have a suite of CICS programs that are experiencing performance problems in QA due to some significant logging and housekeeping that was added to the programs that is not critical to the primary function of the program. If we could split that logic off to different "background" processes, I think it could help our problems.
I am open to any suggestions that any of you may have.
Thanks for your time.
Brent
I am open to any suggestions that any of you may have.
Thanks for your time.
Brent