OPSCMD abends with S0C3 after upgrade

Products

• OPS/MVS Event Management & Automation

Issue/Introduction

After having upgraded OPS/MVS abends S0C3 are occurring when issuing z/OS consoles commands from OPSLOG.

ESTAE LEVEL 1 TAG CHECK FAILED, CODE=0C3 TIME=06:33:23 SEQ=0 CPU=00 ASID=0185 (0185 0185) 
PSW AT TIME OF ERROR 078C2000 989A731E ILC 4 INTC 03 RSCD 00000003 
CURRENT ROUTINE NAME=OPSMMG ADDRESS=189A71F0 OFFSET=0000012A 
GPR 0-3 00000000 18CC3538 18CC3538 00000000 
GPR 4-7 065B9000 98CC353C 80EC604E 00EC704D 
GPR 8-11 00994AB8 000CB7E0 18C09000 18CC2C10 
GPR 12-15 189A71F0 18CC2C10 989A72AA 189A71F0 
AR 0-3 00000000 00000000 00000000 00000000 
AR 4-7 00000000 00000000 00000000 00000000 
AR 8-11 00000000 00000000 00000000 00000000 
AR 12-15 00000000 00000000 00000000 00000000 
ABENDING LOCATION OPSMMG+X'12E' 
UNKNOWN CALLED BY OPSMMG+UNKNOWN 
OPSMMG CALLED BY OPOCCP+X'174' 
OPOCCP CALLED BY OPSAMD+X'9B4' 
OPOCCP CALLED BY SYSTEM+UNKNOWN 

Environment

OPSMVS, all releases 

Resolution

This error indicates that load modules from mixed releases are being used. Check the allocations of the TSO userid and make sure no modules from the previous release are being referenced. Also check the LNKLST and LPALST.
The command TSO ISRDDN can be used to check the TSO allocations.

To use ISRDDN, log into the OPSMVS region having the issue, then enter TSO ISRDDN followed by M OPSAEX.  This will show the library that the OPSAEX module was being referenced from.   This command could be issued against any module from the **.CCLXLOAD library, but this example uses module OPSAEX.   

If it is discovered that a previous release of the CCLXLOAD was referenced, then it confirms that that library exists in the LNKLST or LPALST.   

Until the above steps are completed, a work around would be to add the correct version of the CCLXLOAD to the STEPLIB DD in the CLIST used to access TSO.  The USER will need to log out of TSO and back in for it to be picked up.