From: John McKown <[email protected]> Date: 06/25/2013 09:17 AM -------------------------------------------------------------------------------------------------------------------------------------
IMO, this is a rather involved problem. <SNIPPAGE> Cutting to the chase: If you can make the alc module in question know if it is called inside of CICS, or outside of CICS, then you can build a SAVEAREA either via the EXEC CICS ... for the type of storage you need, or via GETMAIN, and then chain it. OTH - if this module makes no system calls or other subroutine calls, then it does not need a save area of its own, so it can use the caller's provided area (as the protocol requires). In these two cases, the REUSE issue is gone, the program is RENT as long as it otherwise does not modify its storage. If you don't do this, then the module *MAY* cause a performance problem for CICS if you make this code dynamically callable. Depending on how things are set up in CICS (for the transactions in question), this module may be requiring CICS to change TCBs just to execute this one module (threadsafe vs. non-threadsafe). This becomes a $$$ problem depending on the MSUs used by CICS for the transactions involved. Regards, Steve Thompson ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
