After performing the upgrade, CAS9192 messages appeared constantly in the syslog.
Performing the Common Services 15.0 upgrade without IPL:
1) Removing the Common Services LOADLIB from LINKLIST, updating the Common Services loadlib. Adding the Common Services LOADLIB to the LINKLIST again and issuing the LPA commands.
2) Starting CAS9 with following options:
PRODUCT(CAIRIM) VERSION(CAS9) INIT(CAS9INIT) -
3) Restarting CA Healtchecker with the following commands:
1. F CAHC,SHUTDOWN
F CAMASTER,START COMPONENT=CAHCHECK
To get rid of the CAS9192 messages, performing all the upgrade steps again but choosing to run CAS9 with the Common Services LOADLIB defined as STEPLIB.
After running the CAS9 procedure, the CAS9192 messages stopped appearing.
However as soon as the CAS9192 messages appeared, starting seeing S0C4 abends in the jobs, first not in all jobs/tasks.
Seeing now S0C4 abends in all jobs, the jobs themselves complete normally however. Running a test job with EXEC PGM=IEFBR14, which produces a S0C4 abend.
CA Common Services 14.1 & 15.0 - z/OS supported releases -
It was found that the CAS9ATRT module attempted to run the LMP Violation table and abends because it runs beyond its original allocation.
This occurs because the new Common Services 15.0 environment is running with PTF SO07952, but the original Common Services 14.1 environment did not have on the equivalent 14.1 PTF: SO08031.
These PTFs change the expected length of the violation table. When Common Services 14.1 came up it allocated the file with a length of x'1000', with Common Services 15.0 PTF SO07952, the expected length is x'2000'.
These abends will occur until next IPL.