Upgrading operating system from z/OS 2.2 to z/OS 2.3 and receiving CAT9015I & CAT9010I error messages and S0C4.
Article ID: 197745
Updated On:
Products
Issue/Introduction
I am in the process of upgrading our operating system from z/OS 2.2 to z/OS 2.3 and when I start CAS9 for the first time I am receiving a CAT9015I and CAT9010I error message along with an S0C4 DUMP:
SYSTEM COMPLETION CODE=0C4 REASON CODE=00000010
TIME=08.50.40 SEQ=00008 CPU=0000 ASID=002B
PSW AT TIME OF ERROR 070C1000 80025F04 ILC 6 INTC 10
ACTIVE MODULE ADDRESS=00000000_000252D8 OFFSET=00000C2C
NAME=G8UTY
DATA AT PSW 00025EFE - ABE74420 CD28D50B AC482000
AR/GR 0: 00000003/00000000 1: 00000000/08AFC348
2: 00000000/A4A28540 3: 00000000/00000050
4: 00000000/89BA0ED0 5: 00000000/09BA0F0C
6: 00000000/00CC3610 7: 00000000/00CC3158
8: 00000000/0006B002 9: 00000000/00CC1110
A: 00000000/000272D8 B: 00000000/000262D8
C: 00000000/000252D8 D: 00000000/000282B8
E: 00000000/80025BCC F: 00000000/00000000
END OF SYMPTOM DUMP
CAS9140E - INIT ERROR: CA-TLMS/MVS VER TLE0, INIT ROUTINE
RC=S0C4
Cause
TLMS FAILSAFE module still has z/OS 2.2 code inside the usermod. When copied to a z/OS 2.3, the offsets of the modules do not match causing an S0C4.
Environment
Release : 14.0
Component : CA TLMS Tape Management
Resolution
1). Check SYS1.PARMLIB(PROGxx) member. Are there any SYSLIB LPALIB(oldzOS22libs.LPALIB) statements?
2). Check the library in question and see if the following modules are there:
IFG0KLCM, IFG019RB, IFG055ZZ. Alias of IFG019RB.
3). The modules are used for the TLMS FAILSAFE feature. When the old library was copied from z/OS 2.2 to 2.3 system, you still have IBM 2.2 code in those usemods.
4). Remove the SYSLIB LPALIB(oldzOS22libs.LPALIB) from the SYS1.PARMLIB(PROGxx) and IPL out this library. This will let you start CAS9/CTS without the S0C4.
5). Restore off the TLMS FAILSAFE usermod and re-apply on the z/OS 2.3 using the 2.3 libraries.
Feedback
