Actually not true. I have done it frequently when it made sense to do so. COBOL dynamic CALL in CICS has been supported for quite some time now. The trick is to limit the use to subprograms that don't need to use CICS calls, but even that is possible if you pass the EIB along.
Of course, you do NOT want a QSAM I/O module being invoked under CICS, that would be quite bad. Nor do you want any subprogram that invokes any z/OS services directly to be called, but that has always been true. Nonetheless, dynamic COBOL calls are supported and useful in CICS. What you lose is debugging information from CICS in the event of any abend or failure in the subprogram, because CICS thinks that the calling program is the one in control and not the dynamically called subprogram, since CICS LINK was not used to invoke it. HTH Peter > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Chase, John > Sent: Thursday, July 14, 2011 10:39 AM > To: [email protected] > Subject: Re: running Assembler I/O macro code as AMODE 31, RMODE ANY > > How would TCB switching occur at all? Are these programs running in > CICS? If so, you cannot use the DYNAM compiler option for COBOL. -- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
