Connect CDC SQData

2021/04/27

•IMS z/OS TM Exit Capture: SQD0526I - IMS CDC exit globally disabled messages. GENCDC must be run again for all exits using JCL similar to sample member GENICDCL included in the distribution. See Generate IMS TM EXIT Capture Agent for more details. It is critical that the XPARM is loaded into ESCA when an exit is disabled to prevent the SQD0526I message from being issued each time the Exit is called. Precisely highly recommends loading the XPARM into ECSA as noted regardless of whether the capture is disabled or not. Finally, ALL of the ESS modules must be re-linked and updated in the IMS RESLIB or JOBLIB/STEPLIB before IMS is brought up.

•IMS Log Capture (SQDIMSC): Fix invalid safe-restart LSN, that existed under obscure conditions at normal termination, to prevent IMSC_BAD_RECORD error during capture restart.

Note, some comments repeated from the Installation Guide about applying product maintenance on z/OS.

While maintenance releases generally involve only a subset of Connect CDC SQData modules, updates are packaged as a full installation. Migration of an installation from one environment to the next, development to production for example may involve little more than copying the LOADLIB members to the production libraries. There is nothing that ties the linked modules directly to the LOADLIB.

If however, your environments have different version of Db2 or IMS, then the safest course is to re-link in the the upper environments. This is because we include certain IMS, Db2, CICS and MQ modules. If you are using the product with those modules in lower environments and they are compatible with those in upper environments, then no re-link on upper environments is needed.  If they are not compatible, then you have to re-link.

Important: It is highly recommended that you back up your current object and load module libraries before applying any maintenance release. This allows you to quickly back out the maintenance if any problems arise.