The OPSINFO built-in function returns information about CA OPS/MVS or about the environment where the issuing OPS/REXX program is running, or both.
It is possible to use the OPSINFO function in OPS/REXX or AOF rules.
It can happen that, executing an OPSINFO external function, the following Abend occurs :
IDI0123S Processing of abend S0C3 terminated due to unsupported execution environment: SUB=MSTR
IEF196I IDI0123S Processing of abend S0C3 terminated due to unsupported
IEF196I execution environment: SUB=MSTR address space
IEA995I SYMPTOM DUMP OUTPUT
SYSTEM COMPLETION CODE=0C3 REASON CODE=00000003
TIME=23.17.03 SEQ=48902 CPU=0000 ASID=024C
PSW AT TIME OF ERROR 078D1000 B25C5A12 ILC 4 INTC 03
ACTIVE LOAD MODULE ADDRESS=325C59A8 OFFSET=0000006A
DATA AT PSW 325C5A0C - 00044410 C06650B0 D00850D0
AR/GR 0: 008C2380/32342C90 1: 00000000/323D14B8
2: 00000000/00000000 3: 00000000/325C1EFC
4: 00000000/323D1190 5: 00000000/0A0CA207
6: 00000000/00000000 7: 00000000/00000003
8: 00000000/8A0C1868 9: 00000000/325C1237
A: 00000000/325C1C78 B: 00000000/0A0C8DF8
C: 00000000/B25C59A8 D: 00000000/323D1190
E: 00000000/8A0CA0EA F: 00000000/B25C59A8
END OF SYMPTOM DUMP
Is it possible to identify the cause of this abend and how to bypass it?
In general the Abend S0C3 in OPSINFO with OFFSET=0000006A is caused by the fact that OPSINFO is a OPS/REXX function call, which means that the REXX containing the OPSINFO built-in function should be executed with the OI command processor.
If the REXX is not invoked with OI this results in the S0C3 abend in OPSINFO at OFFSET 0000006A.
If this suggestion doesn't solve the Abend, Please open a case to Technical Support.