Getting the OPS3162W message during system startup of OPS/MVS

Products

• OPS/MVS Event Management & Automation

Issue/Introduction

The OPSMAIN program is issuing the message OPS3162W and referencing the address space of an OSF server. This is occurring during system startup after upgrading the release of z/OS. There were a cluster of messages issued during both system startups.

Example:
22MAR 20:12:16 OPS3162W MESSAGE SEND TO ASID X'0000002A' FAILED; REASON IS TAG CHECK FAILED, DETECTED AT OPSNMG+X'00000A9E'

We want to remove the messages. How?

Environment

OPS/MVS Event Management and Automation, all releases
Multi-System Facility (MSF)
z/OS , all releases
JES2, all releases
 

Cause

The problem was that the REXX program was issuing a command and waiting for the response. The response was taking too long to return.
 

Resolution

Using the NOOUTPUT allows the program to continue without the need to wait for a response from the EDQ (External Data Queue).

Add the NOOUTPUT option to the MSG statements, for example: 
 

ADDRESS 'OPSCTL' "MSF DEFINE MSFID("sys_id") APPLID("applid") RETRY(30,120) APPC NOOUTPUT"
"MSF START NOOUTPUT"
"MSF ACTIVATE MSFID(ALL) NOOUTPUT"

Results:
No OPS3162W errors.

 

Additional Information

ADDRESS OPSCTL Commands for the MSF