OPSVASRV failing after application of CARS2306
Article ID: 270591
Updated On:
Products
Issue/Introduction
After applying CARS2306 to our lab systems, we started to receive errors with the OPSVASRV function.
The errors happen when we make a call to this function via a CMD rule, which we have had no issue prior to installing CARS2306, but now complains about not being allowed to execute in an AOF rule that isn't a TOD or REQ rule.
The following error message is produced:
OPS1000H OPS9537E OPSVASRV MAY NOT BE EXECUTED IN AN AOF RULE TYPE THAT PROHIBITS WAITS
Environment
Release : 14.0
Cause
The PTF LU09173 closed a 'loophole' where a CALLed external subroutine with OPSVASRV() from any AOF rule would work by mistake. See the description of this PTF:
https://support.broadcom.com/web/ecx/solutiondetails?aparNo=LU09173&os=z/OS
PROBLEM DESCRIPTION:
The OPSVASRV OPS/REXX function is erroneously allowed to execute
in an external subroutine that is called by an AOF rule type other
than REQ, API or ARM. The OPSVASRV function can cause a wait condition
and should not be allowed to execute within rule types other than
REQ, API or ARM
SYMPTOMS:
The OPSVASRV function is successful when run in a rule type other than an
REQ, API or ARM rule.
IMPACT:
The OPSVASRV function was running in an environment that should be
restricted to commands that cannot cause a wait.
CIRCUMVENTION:
Run the OPSVASRV code in an OPSOSF server.
The documentation of the OPSVASRV function always had this note in the Supported Environments section:
Resolution
When using other types of rules, the solution is to dispatch a REXX program to run on the OSF servers to be able to use the OPSVASRV function.
ADDRESS OSF 'OI P(rexx-pgm-name) ARG(arguments)'
Feedback
