OPS9999T OPAOEV RC= 46 FOR ENVIRONMENTAL VARIABLE SEC.AUGLRQTY
search cancel

OPS9999T OPAOEV RC= 46 FOR ENVIRONMENTAL VARIABLE SEC.AUGLRQTY

book

Article ID: 139651

calendar_today

Updated On:

Products

OPS/MVS Event Management & Automation

Issue/Introduction

In coming up after an IPL, the client received the following messages:


Date  CN Time     Job Name User ID  ----+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8
03NOV 00 04:13:41 OPSOSF   OPSOSF   OPS9999T OPAOEV RC= 46 FOR ENVIRONMENTAL VARIABLE SEC.AUGLRQTY                 
03NOV 00 04:13:41 OPSS0032 OPSOSF   OPS3092O ERROR 46 RUNNING SECURITY.ALLOWOPS, LINE 16: INVALID VARIABLE REFERENCE
03NOV 00 04:13:41 OPSOSF   OPSOSF   OPS9999T OPAOEV RC= 46 FOR ENVIRONMENTAL VARIABLE SEC.AUGLRQTY                 
03NOV 00 04:13:41 OPSS0032 OPSOSF   OPS3092O ERROR 46 RUNNING SECURITY.ALLOWOPS, LINE 16: INVALID VARIABLE REFERENCE
03NOV 00 04:13:41 OPSOSF   OPSOSF   OPS9999T OPAOEV RC= 46 FOR ENVIRONMENTAL VARIABLE SEC.AUGLRQTY                 
03NOV 00 04:13:41 OPSS0032 OPSOSF   OPS3092O ERROR 46 RUNNING SECURITY.ALLOWOPS, LINE 16: INVALID VARIABLE REFERENCE
03NOV 00 04:13:41 OPSOSF   OPSOSF   OPS9999T OPAOEV RC= 46 FOR ENVIRONMENTAL VARIABLE SEC.AUGLRQTY                 
03NOV 00 04:13:41 OPSS0032 OPSOSF   OPS3092O ERROR 46 RUNNING SECURITY.ALLOWOPS, LINE 16: INVALID VARIABLE REFERENCE

 

What is causing the problem?

 

Environment

OPS/MVS Event Management & Automation

Resolution

The problem was a coding error in the client's ALLOWOPS security rule, as it was referencing an event variable, SEC.AUGLRQTY, which is only available for OPSGLOBAL SECurity events.

The client changed their IF with an AND, to be embedded IFs instead, and that solved the problem.