What is new with ESP R11.4 and OPS/MVS R12.3

Document ID : KB000046178
Last Modified Date : 14/02/2018
Show Technical Document Details

 

Question:  

 

What is new with ESP R11.4 and OPS/MVS R12.3

 

Answer: 

 

++PTF (RO78156)
/***************************************************************************

NEW COMMAND, CALLOPS, FOR INTERFACE WITH OPS/MVS

New command, CALLOPS, for interface with OPS/MVS
PROBLEM DESCRIPTION:
The new command, CALLOPS, creates an API event in OPS/MVS with a
user-defined event id suffix. It is available for use in ESP procedures.

CALLOPS MESSAGE('message text') [RULESUF(suffix)]
'message text' is the message that will be sent to OPS/MVS. It will be
available to OPS/MVS API rules as the value of API.TEXT variable. This
operand is required. The maximum length is 4096 bytes. Quotes that are
part of the text must be doubled.

suffix is a string of up to 4 alphanumeric characters that will replace
the rightmost portion of the default id string CAESP00000 to form an
OPS/MVS API event id.
command. The default event id for this command is CAESP00000. This
operand is optional.

This command is similar in function to SEND2OPS, with the following
differences.
1. CALLOPS allows a selectable API event id. SEND2OPS uses a fixed id of
CAESP00001.
2. CALLOPS sets two variables: API.ESPUSER and API.ESPEVENT to the values of
ESP variables ESPUSER and ESPEVENT.
CALLOPS also sets API.LEVEL variable to the name of the current ESP
subsystem. This is in common with SEND2OPS.

Example:
CALLOPS RULE(ALRT) MESSAGE('ESP alert: job %MNJOB.(%MNJOBNO) %MNHICMPC')

 

 

 

Additional Information:

 

 ESPWA Release notes explains new features.

https://support.ca.com/cadocs/7/CA%20Workload%20Automation%20ESP%20Edition%2011%204-ENU/Bookshelf_Files/PDF/WA_EE_Release_zOS_ENU.pdf