Issue with QMSG Processing in New REXX Code

Products

• OPS/MVS Event Management & Automation

Issue/Introduction

Issue with QMSG Processing in New REXX Code causing an abend System abend code 0C3, reason code 00000003

Cause

Rexx is triggering through TSO, but customer was using the OPS Rexx command which is ADDRESS WTO which is causing the RC(-3) and following by System abend 0C3.

 

Resolution

Option 1 : 

 Invoking the Rexx through TSO and using the *-* ADDRESS WTO which you can't use directly as a built-in command. 

TSO/e function will cause S0C3 abends because of functions like OPSVALUE will not be known. 

OPS/REXX provides equivalent commands that will work under TSO/e

ADDRESS WTO - OPSWTO
ADDRESS OPER - OPSCMD
OPSVALUE - OPSSET and OPSGET.

Option 2 : 

Rexx is executing from this Rule - MONITOR.NSY3166I, so you have below options - 

1) Change from EX to OI CPSYSINC
2)  If you don't have that dataset in the OSF SYSEXEC DD, then you will need to use OX 'I09131.OPS.REXX.CHANGE(CPSYSINC)'

OI and OX invoke the REXX code to execute under the OPS/REXX compiler

In this case, you don't need to change any of the commands (ADDRESS WTO).