Shortly after upgrading to z/OS 1.10 a customer noticed that their CMN ZMF 5.6.1 package audit jobs started abending sporadically in both the AD 000/CMNAD000 and AD 500/CMNAD500 steps with S378 completion codes. The output showed the following type of symptom dump:
A customer upgraded to ChangeMan ZMF 8.2 Patch 2. When they now run audit with autoresolve enabled to fix, for example, any SYNCH5! errors that exist within the package, the AD 500 step often submits multiple recompile requests for the same SRC component. This should not occur and only one recompile request should be submitted for each SRC component, regardless of the number of errors that require the recompile to be executed to resolve them.
The X21£STAT (X21$STAT) value passed to CMNEX021 can be set incorrectly in the AD 500 step when the autoresolve option has been enabled on a package audit. This can lead to various problems in customer audits depending on exactly how the customer is using this field in their exit 21 processing.
A user submitted an audit job for a relatively large, old package where the staging datasets had all been migrated to HSM level 2. The audit job ended with a RC=20 in the AD 000/ AD 500 steps and the following messages in the AD 000 SYSPRINT file: ... CMN7801A - Audit discovered too many integrity errors in the package to continue.
A customer who has recently upgraded a DP system to ZMF 8.1 reports that they are now receiving audit RC=20 in the AD 000 and AD 500 steps along with the following message when audits of packages in certain applications are run: CMN2624A - There are no XAP=appl sysin parms OR the application specified is not in the I/A table; Audit cannot continue. CMN7540I - End of job; RC = 20
A customer recently upgraded from ZMF 7.1.2 to 8.1. After doing so, audits of one of their larger complex packages appears to loop and/or send the started task into a loop in the AD 000/CMNAD000 step. They have applied the 8.1.0.01 patch in the hope of resolving the issue.
ZMF Db2 option customers upgrading to ZMF 8.2 Patch 4+ must run the DB2ALTER job as a part of their upgrade, prior to re-binding CMNDB2 AD . This job is missing from early versions of the 8.2 Patch 4 documentation (e.g. Readme and/or Migration Guide). Failure to run this job will result in the bind of CMNDB2AD failing with a RC=12 and the following type of errors:
