The OSF uses OPSOSF address spaces as servers that handle asynchronous action requests from various CA OPS/MVS facilities.
OPSOSF address spaces have the following characteristics:
1. They include the following facilities:
– Automated Operations Facility (AOF)
– Enhanced Console Facility (ECF)
– IMS Operations Facility (IOF)
– Multi-system Facility (MSF).
2. They use z/OS cross-memory services to handle action requests.
3. They may be swappable or non-swappable, as determined by the value of OSFSWAPPABLE parameter.
4. They are started and stopped by CA OPS/MVS as necessary, although the number of active servers must fall within the bounds set by the following parameters:
– OSFMIN and OSFMAX
– OSFTSLMIN and OSFTSLMAX
– OSFTSPMIN and OSFTSPMAX
– USSMIN and USSMAX
It can happen that these OPSOSF dynamic tasks abend S013 with the below messages:
*OPS2023S NO CONSOLE OR SERVER BLOCK FOUND FOR USERID=OPSOSF
IEF196I OPS2023S NO CONSOLE OR SERVER BLOCK FOUND FOR USERID=OPSOSF
IEF196I IEC141I 013-C0,IGG0199G,OPSOSF,OPSOSF,SYSTSIN
IEC141I 013-C0,IGG0199G,OPSOSF,OPSOSF,SYSTSIN 614
IEF196I IEA995I SYMPTOM DUMP OUTPUT
IEF196I SYSTEM COMPLETION CODE=013 REASON CODE=000000C0
IEF196I TIME=16.25.00 SEQ=05716 CPU=0000 ASID=00BC
IEF196I PSW AT TIME OF ERROR 075C1000 80DD291E ILC 2 INTC 0D
IEF196I NO ACTIVE MODULE FOUND
IEF196I DATA AT PSW 00DD2918 - 41003038 0A0DB20A 00509808
IEF196I AR/GR 0: 009FF260/00DD2B2C 1: 00000000/A4013000
IEF196I 2: 00000000/009D20D8 3: 00000000/00DD2AF4
IEF196I 4: 00000000/009DB410 5: 00000000/009DB7A4
IEF196I 6: 00000000/009DB74C 7: 00000000/009DB7A4
IEF196I 8: 00000000/009DB76C 9: 00000000/009CDEC0
IEF196I A: 00000000/00000000 B: 00000000/00DD25AA
IEF196I C: 00000000/80DD2806 D: 00000000/7F6E3D20
IEF196I E: 00000000/00DD25AA F: 00000000/000000C0
IEF196I END OF SYMPTOM DUMP
IEA995I SYMPTOM DUMP OUTPUT 616
What is the cause of this kind of abend and how to prevent it from happening?
CA OPSMVS - OPSOSF Component
The OPS2023S message and the subsequent S013 ABEND will be issued any time an OPSOSF server attempts to do I/O to SYSTSPRT or SYSTSIN subsystem datasets and OPSMAIN (the central address space for CA OPS/MVS) has not created a control block for that ASID yet.
This can mostly happen if:
1) An MVS START OPSOSF command is issued manually.
2) OPSOSF has a higher WLM class than that of OPSMAIN.
OPSMAIN issues an ASCRE (address space create request) Z/OS service call.
The return code from the call includes the ASID of the newly created OPSOSF address space.
If OPSMAIN is suspended by WLM after the ASCRE completes but before OPSMAIN creates the server control block and the OPSOSF server reaches the point of asking for data via the SYSTSIN / SYSTSPRT DD subsys datasets, the OPS2023S message is issued when OPS sees the server request.
This is usually a temporary error situation which can be prevented increasing the Z/OS WLM Service Class for OPSMAIN so that it could not be suspended by WLM during the ASCRE/SCB creation for OPSOSF.