search cancel

CA OPS/MVS OPSCMD batch job shows multiple signons and signoffs within the same job

book

Article ID: 252987

calendar_today

Updated On:

Products

OPS/MVS Event Management & Automation

Issue/Introduction

CA OPS/MVS batch job using TSO's prgoram IKJEFT01 to issue the  OPSCMDs:

Example

  OPSCMD COMMAND('RO *ALL,D T')

  OPSCMD COMMAND('RO *ALL,D A')

  OPSCMD COMMAND('RO *ALL,D R')

prouduce a signon and signoff audit entry in Top Secret Audit Tracking File.

 

Environment

Release : 14.0

Cause

This is normal for TSO's IKJEFT01 program issuing OPSCMD from a batch job.

Using CA OPS/MVS OPS/REXX exec as an alternative will produce only one signon with multiple OPSCMDs.

Sample JCL statements to run an OPS/REXX exec from a batch job: 

//[email protected]  EXEC PGM=OI,PARM=rexx_exec_name

//STEPLIB  DD  DISP=SHR,DSN=OPSDIST.MSPS.OPS140.DEV.CCLXLOAD
//SYSPROC  DD  DISP=SHR,DSN=OPSDIST.MSPS.OPS140.DEV.CCLXCLS0
//SYSEXEC  DD  DISP=SHR,DSN=OPSDIST.MSPS.OPS140.DEV.CCLXEXEC

//SYSTCPD  DD  DISP=SHR,DSN=VTAM.TCPIP.TCPIP.DATA
//SYSTSPRT DD  SYSOUT=*                          
//SYSPRINT DD  SYSOUT=* 

With PGM=OI, the OPS/REXX exec will need to reside in a dataset referred to by the SYSEXEC DD. 

OR use this: 

//[email protected]  EXEC PGM=IKJEFT01,REGION=0M,DYNAMNBR=100,TIME=1439

//STEPLIB  DD  DISP=SHR,DSN=OPSDIST.MSPS.OPS140.DEV.CCLXLOAD

//SYSEXEC  DD  DISP=SHR,DSN=LASMT01.OPS.REXX

//SYSTSPRT DD  SYSOUT=*        
//SYSPRINT DD  SYSOUT=*        
//SYSTSIN  DD  *               
OI MYEXEC

The OPS/REXX exec called in either method should use ADDRESS OPER "Command('the_1st_MVS_cmd')" Command('the_2nd_MVS_cmd')" etc....

Resolution

Working as designed. To avoid this behavior, a REXX program can be created and the ADDRESS OPER host environment can be used instead of OPSCMD.