“Managing Multi-version Applications in CICS” | SHARE 2014 in Pittsburgh, PA
MatthewWebster 060000AMGC Visits (1473)
Thanks to everyone who came to my Wednesday session “Man
Question 1: Very interesting concept however in my organization COBOL calls are used not EXEC CICS LINKS.
Answer: To use application multi-versioning with COBOL you need to declare one or more entry points using either a PROGRAM or a URIMAP. That first program must be called with an EXEC CICS LINK so we can set up the application context but all the rest of the programs in you application can continue to use COBOL dynamic calls.
Question 2: There was some confusion between programs and tran codes that invoke those programs. It is entirely possible to not only have duplicate program names, but to also have duplicate transaction codes.
Answer: In V5.2 we only support private LIBRARY, POLICY and PROGRAM resources. We know that TRANSCATION, FILE and other resources are important as well as appl
Question 3: Hope you are able to implement an easier way to detect AMODE 31 load modules so as to set DATALOCATION=ANY in program autoinstall.
Answer: You cannot use the BLDL macro for load modules associated with private PROGRAM resources as the user exit does not identify which library and dataset or dataset is being used. However, RFE
For more information please see my previous articles on this blog starting with What