How to setup autoreply so the CAWTOR does not "get stuck" waiting for a reply.

Products

• CIS
• COMMON SERVICES FOR Z/OS
• 90S SERVICES
• DATABASE MANAGEMENT SOLUTIONS FOR DB2 FOR Z/OS
• COMMON PRODUCT SERVICES COMPONENT
• Common Services
• Datacom/AD
• CA ECOMETER SERVER COMPONENT FOC
• Easytrieve Report Generator for Common Services
• INFOCAI MAINTENANCE
• IPC
• UNICENTER JCLCHECK COMMON COMPONENT
• Mainframe VM Product Manager
• CHORUS SOFTWARE MANAGER
• CA ON DEMAND PORTAL
• CA Service Desk Manager - Unified Self Service
• PAM CLIENT FOR LINUX ON MAINFRAME
• MAINFRAME CONNECTOR FOR LINUX ON MAINFRAME
• GRAPHICAL MANAGEMENT INTERFACE
• WEB ADMINISTRATOR FOR TOP SECRET
• Xpertware
• Compress Data Compression for MVS
• Compress Data Compression for Fujitsu

Issue/Introduction

Summary:

We have a mainframe started task (STC) that uses the Event Management cawtor command to send messages between our mainframe systems. The task has 4 steps that send messages to both our MAINFRAME and DISTRIBUTED platforms. The first 2 steps that are sending messages to the distributed platforms work very well, but the task remains "stuck" at the step where it is setup to send a message to another MAINFRAME system.

Here is a sample of the step that executes BPXBATCH to send a message using the cawtor command to a remote mainframe system named "sysb"

//SYSB     EXEC PGM=BPXBATCH,REGION=0M,TIME=(,01),

//   PARM='PGM  usr/nsmem/bin/cawtor -n sysb Test inter machine NSM'

//SYSIN    DD DUMMY

//SYSPRINT DD SYSOUT=*

//SYSERR   DD SYSOUT=*

//STDENV   DD PATH='/usr/nsmem/browser/httpd.envvars',

//            PATHOPTS=(ORDONLY)             

//STDOUT   DD  PATH='/usr/nsmem/sysbwtor.out',

//         PATHOPTS=(OWRONLY,OCREAT,OTRUNC),

//         PATHMODE=(SIRUSR,SIWUSR,SIRGRP,SIWGRP,SIROTH)

//STDERR   DD  PATH='/usr/nsmem/sysbwtor.err',

//         PATHOPTS=(OWRONLY,OCREAT,OTRUNC),

//         PATHMODE=(SIRUSR,SIWUSR,SIRGRP,SIWGRP,SIROTH)

//*

 

When using the cawtor command, the command will wait for a reply. To automatically reply to a cawtor message, an AUTOREPLY message action must be created.

 

Instructions:

Here is a way to set up an AUTOREPLY to cawtor: 

1)  Log on to Event Management on the "sysb" mainframe system using the CA NSM Browser Interface. In the GUI, you will find a tree in the left panel called "Enterprise Management". 

2)  Expand the tree and click "Messages". In the right panel, click on the blank paper icon to create a new message record. A window titled "Message Record - Detail" will appear.

In "Message id", enter the text: 

* Test inter machine NSM 

The asterisk is the wildcard for the reply ID of the cawtor.

3)  Click on the diskette icon to save the Message Record, which will now detect the cawtor message sent from the batch job.

4)  In the "Message Record - Detail" window, click on the Actions tab. Then click "new". A new window "Message Record Action - Detail" appears.

Enter 1 for Sequence number. In "Text:", enter the text: 

&1 <Your reply message> 

Then in the drop down next to "Action:", select AUTORPLY.

5)  Click the OK icon to save and close.

6)  Click the OK button again in the Message Record window. 

7)  Finally, in the main Browser window, select Console Logs in the tree. In the Console Log window that appears, enter the following command on the bottom to reload the Event Management policies database: 

opreload 

 

After completing the above steps, AUTOREPLY will now respond to the cawtor on sysb.

Environment

Release: CA90SV00200-14-Common Services-for z/OS
Component: