How On-request works in ESP Workload Automation
search cancel

How On-request works in ESP Workload Automation

book

Article ID: 224213

calendar_today

Updated On:

Products

ESP Workload Automation

Issue/Introduction

Need to know REQUEST and UNREQUEST job work.

LINUX_JOB TEST1 REQUEST
   RUN daily
   AGENT <agent>
   SCRIPTNAME /<path>/xx.sh
   EARLYSUB 11:30
   RELEASE (TEST2)
ENDJOB
                       

Environment

Release : 12.0
Component : ESP WORKLOAD AUTOMATION

Cause

When the job submits to the queue, ESP bypasses the job (when the submit time is ready) unless you "Mark as Request".

Resolution

Identify On-Request Job:

With applications, you can identify certain jobs as on-request and define their relationships to other jobs. The on-request jobs take their place in the schedule when they are selected. From the time you generate the application up to the time of job submission, you can use CSF or the APPLJOB command to request the job. If you have not explicitly requested the job, ESP bypasses the job and treats it as a normal completion, releasing its successor jobs. To mark a job as on-request, use the REQUEST operand of the JOB statement.

By marking a job as on-request, you are not requesting the job, you are only making it eligible for explicit request through CSF or the APPLJOB command. You must first generate the application before you can request any of the application's on-request jobs. To allow users to request jobs, you can generate the application containing these jobs early in the morning and can use submit time dependencies (for example, DELAYSUB statements) on the jobs with no predecessors so they are not submitted at the time ESP generates the application.

Using LIM on Director:

1. AJ RQ1 APPL(TSTREQ.Gen#) REQUEST   (In Workstation Directory Right-Mouse click on Job and select "Request") This will set the job to Request and run.

See output after you Request:

APPL TSTREQ   GEN 10                                            
  CREATED AT 13.31 ON FRIDAY SEPTEMBER 17TH, 2021               
           BY EVENT <event>.UNREQEST                           
  RQ1, HC=0                                                     
   ON REQUEST (REQUESTED)                                       
   SUBMISSION AT 01.15 ON SATURDAY SEPTEMBER 18TH, 2021         
   ANTICIPATED END TIME: 01.15 ON SATURDAY SEPTEMBER 18TH, 2021 
   PREDECESSORS: (NONE)                                         
   SUCCESSORS: RQ2                                    

Example:

APPL TSTREQ                    
NT_JOB RQ1 REQUEST             
RUN DAILY                      
AGENT <agent>                 
CMDNAME <path>\<script> 
EARLYSUB 01:15                 
RELEASE RQ2                    
ENDJOB                         


2,  The job is now "Requested" and will run on its normal scheduled or submit time.  (By default if you do not request, the job will be bypassed after its submit time)