CA OPS/MVS TSL SERVER OPSOSF FAILED - ABEND S0C1 IKJRBBMC

Document ID : KB000107793
Last Modified Date : 03/08/2018
Show Technical Document Details
Issue:
In CA OPSMVS, the OPSOSF Server (Operator Server Facility) allows users to schedule work in the form of OPS/REXX programs or commands to an OPSOSF server address space.
Various components of CA OPS/MVS utilize this facility including AOF for asynchronous automation tasks when needed.

Sometimes it can happen that this task abnormally terminates with messages like the following:

DUMPID=001 REQUESTED BY JOB (OPSOSF ) 
DUMP TITLE=COMPID=5665-28502,ISSUER=IGX00027. SDUMP FROM THE T 
SO I/O SERVICE SVC 
OPS3092J IKJ56600I UNRECOVERABLE COMMAND SYSTEM ERROR 
IEC214I 614-10,IGG0201W,OPSOSF,OPSOSF,SYSTSIN 

IEF404I CAIVTAM - ENDED - TIME=11.15.29 
$HASP395 CAIVTAM ENDED - RC=0000 
OPS3092J READY 
OPS3092J READY 
OPS3092J READY 
IEF404I OPSOSF - ENDED - TIME=11.15.29 
IEA989I SLIP TRAP ID=X33E MATCHED. JOBNAME=*UNAVAIL, ASID=01AC. 
OPS2083J CA OPS/MVS TSL SERVER OPSOSF,ASID=X'01AC' FAILED 

and it generates an SVCDUMP containing references to :
... 
RIDS/IKJRBBMC Csect name: IKJRBBMC 
AB/S00C1 System abend code: 00C1 
...

What is the reason of this abend and how to recover it? 
 
Environment:
Z/OS - OPSMVS - OPSOSF 
Resolution:
A possible cause of this abend is that the OPSOSF server has a WLM Class higher than the OPSMAIN address space WLM Class.

OPSMAIN task priority should be comparable to JES. At least it should be set to SRMGOOD. If it runs at the lower priority, there is a small window where OPSMAIN task can be suspended after starting a server and when this occurs the ACBINRTN field is not filled in for the server subsystem dataset. 
The problem is a timing problem introduced by local settings for the OPSMAIN address space in WLM. Since it is a low priority when it issues the ASCRE to create the OSF server, it is suspended by WLM, and the OSF server attempts to open its subsystem datasets, but OPSMAIN did not fill in the ASCB address of the server because of the suspension. So when the OPSS10 exit is driven, it cannot identify the address space trying to open the subsystem dataset.

The documentation reports that OPSMAIN should run at the same priority as JES2, and normally OPSMAIN should be set to 

SERVICE CLASS = SYSSTC 
WORKLOAD = SYSTEM 
INTERNAL CLASS= $SRMGOOD 

Anything lower could result in the abend described before.

The OPSOSF/TSF Servers can remain lower, unless they will start having performances issues. 
.