Undocumented OPS Error Messages such as OPX8510E

Products

• OPS/MVS Event Management & Automation

Issue/Introduction

How do I look up the cause of an undocumented error?  Below is an example:

15:35:45 ---- IAT6853 THE CURRENT DATE IS MONDAY,    22 AUG 2022 ----                                           

15:35:45 IAT4221 SYSTEM SYMBOLS SELECTED FROM AAA1                                                              

 15:35:45  IAT2000 JOB MYJOB (JOB10207) SELECTED AAA1    SRVCLASS=srvclass                                      

15:35:45  ACF9CCCD USERID xxxxxx   IS ASSIGNED TO THIS JOB - MYJOB                                              

15:35:45  IEF196I ACF9CCCD USERID xxxxxx   IS ASSIGNED TO THIS JOB - MYJOB                                      

15:35:45  IEF403I MYJOB - STARTED - TIME=15.35.45                                                               

15:35:45  OPX8500I Global variable backup for subsystem OPSX has started                                         

15:35:45  OPX8510E Dynamic allocation failed, RC=X'0000000C', error code=X'0000000C'                             

15:35:45  OPX8512I Global variable backup ended RC = 52, number of global variables backed up = 0               

15:35:45  08/22/22 MYJOB  1 OPSSGVBK          COND=   52 ELAPSED=00:00:00 CPU=    0.01 EXCPS=        0 T-MOUNTS= 

15:35:45  IEF404I MYJOB - ENDED - TIME=15.35.45                                                                                     

 

 

Environment

OPS/MVS

Resolution

Since a subsystem name other than the default OPSS was used, the S in the message was replaced with the subsystem identifier.   In the example above it was with X to show that it occurred on OPSX as evidenced in the message, OPX8500I Global variable backup for subsystem OPSX has started.   

For more information on the messaging formats used by OPS/MVS Performance Manager, review the section of documentation titled "Understanding OPS/MVS Messages". 

Documentation:  Message Format

 

Please Note: For the particular error message the customer saw above, there was an incorrect GLOBALBACKUP parameter specified.