search cancel

OPSINFO Function Now Supports Cross-system Scope (LU04902)

book

Article ID: 244324

calendar_today

Updated On:

Products

OPS/MVS Event Management & Automation

Issue/Introduction

OPS/MVS users want to create automation that references information about the operating environment of OPS/MVS running on other systems in the OPSplex. To that end, the enhancement PTF LU04902 provides a new OPS/REXX OPSINFO function that now accepts a second positional argument to route execution of the function to a remote, MSF-connected system in the OPSplex.

 

Environment

Release : 14.0

Component : OPS/MVS

Resolution

To correctly implement and test this enhancement, it is necessary to take into consideration the Description section reported into the PTF :

ENHANCEMENT DESCRIPTION:
 
This enhancement adds the ability to issue the OPSINFO function
in cross-system mode. The function now accepts a second operand, which
specifies the MSF system id of the remote target system. For example,
OPSINFO("EXECPGM","SYSV") where "SYSV" is the MSF System id of the
target system.
 
Note:
 
This PTF must be applied to any LPAR that is targeted by the OPSINFO
function in cross-system mode. If the PTF is not applied to the
cross-system targeted LPAR, the request will fail and the following
messages will be issued.
 
On the local system where the PTF is applied, the new argument is recognized.
The function is routed to the remote system, but it times out waiting for a
response:
 
  WAIT TIME EXCEEDED BEFORE ALL OUTPUT RECEIVED FROM MVS31K. DETECTED BY
  OPRFSYFU.
 
On the targeted remote system where the PTF is not applied, the new argument
on the routed function is not recognized. WTO OPS3860I is issued with RC=70,
meaning too many arguments were specified:
 
  OPS3860I MRT cross system execute of OPSINFO failed, RC=70

 

So it is important to install the PTF in all the involved Lpars of the OPSplex where the tests will be done in order to avoid any error situation.