There are several lines written to the CICS log for each transaction that executes in CICS that references IDMS:
TERM=SA01 IDMSINTC AlocTemp Stg=002510B8 Opts=00000000 Tran=BIRL Task=0000272C
TERM=SA01 IDMSTRUE Func=APPLCALL EI-Stg=002510B8 Tran=BIRL TIND=40QR Task=000027
The CICS person said these messages are written in CICS, but he thinks the "command" to write the message is coming from somewhere in IDMS. He also said CICS will crash because it exceeds the maximum number of line of output that JES has specified.
How are these messages produced and how to suppress them?
This problem occurs when Trace Entries have been turned on in the CICSOPTS CA IDMS CICS interface option source module. Check your IDMS 18.5 source library IDMS185.CUSTOM.SRCLIB(CICSOPTS) and see if you have DEBUG=YES. It should be DEBUG=NO.
Normally, the install defaults to DEBUG=NO. Reassemble and link it with DEBUG=NO
or verify that you are using the correct CICSOPTS module in your CICS region.
JOB03 in the IDMS 185.CAISAG.CONFIG library contains JCL for the CICSOPTS assemble and link with IDMSINTC.
CA IDMS System Operations Guide, Chapter 7: CICS Considerations