Error After AJ command to complete application that's already completed thru OPSMVS
search cancel

Error After AJ command to complete application that's already completed thru OPSMVS

book

Article ID: 225741

calendar_today

Updated On:

Products

ESP Workload Automation

Issue/Introduction

We have an automated process in OPS/MVS to issues the AJ Complete command.   Occasionally the 0 version of the application has already been marked complete.  When this happens, the ESP command requests more input, this causes the OPSOSF task to abend.   Is there a parm that can be added to the AJ command to request that no additional command response be required?

 

Good run:

ESPHTTPWRN - JOB=jobname JOBNO=0 CODE=1 APPL=applname AGENT=agentname STAT=CONNECTION RESET AUTH= 
OPS3724T TSO eventname Sent CMD=ESP SUB(ESPP) MASTER; AJ jobname COMPLETE APPL(applname.0);END  
OPS3092O ESP SUB(ESPP) MASTER; AJ jobname COMPLETE APPL(applname.0);
OPS3092O JOB jobname MARKED COMPLETE                                
OPS3092O READY  

 

Failed run:

ESPHTTPWRN - JOB=jobname JOBNO=0 CODE=1 APPL=applname  AGENT=agentname STAT=CONNECTION RESET AUTH=
OPS3724T TSO eventname Sent CMD=ESP SUB(ESPP) MASTER; AJ jobname COMPLETE APPL(applname.0);END 
OPS3092O ESP SUB(ESPP) MASTER; AJ jobname COMPLETE APPL(applname.0);
ESPAGINACT - AGENT=agentname IS NOW INACTIVE                                
OPS3092O APPL ALREADY MARKED COMPLETE                                          
OPS3092O -->                                                                   
OPS3083S COMMAND REQUESTED MORE INPUT - COMMAND ABORTED                        
OPS3092O END        

mm/dd/yy hh:mm:ss PROD OPS3083S COMMAND REQUESTED MORE INPUT - COMMAND ABORTED
mm/dd/yy hh:mm:ss PROD OPS2083W CA OPS/MVS TSO SERVER OPSOSF,ASID=X'01A9' FAILED

 

Environment

Release : 11.4 & 12.0

 

Resolution

When ESP is processing a line with a list of commands separated by the semicolon and one of the commands fails, it ignores the rest of the line and asks for a next line.

The behaviour depends on whether ESP thinks it runs in interactive/non-interactive mode. In a non-interactive mode, if there is nothing to do, it ends. In the interactive mode it waits for the next input from a terminal.

Whether it runs in interactive/non-interactive mode, ESP decides from the environment (JOB/TSO/...).

There are two workarounds: 

1. Issue the MVS modify command against the ESP STC: 
         F esp_stc,AJ .....

    Note: user mode 35 needs to be turned on.

2. Set up an event: 
       EVENT ID(ESP.CMD) ...
       Proc                    
         ESPNOMSG AJ %USER1           
      EndProc                 
      ENDDEF        

And in OPS/MVS, use command: 
      F esp_stc,TRIGGER ESP.CMD USER1(....)