Templib member not deleted when job is submitted

Products

• ESP Workload Automation

Issue/Introduction

The JCL member in the ESP TEMPLIB data set is not deleted automatically when the job is submitted.
USERMOD 198 JCLSCAN exit module CYBJSDLT has been enabled using the command  "EXIT FUNCTION(JCLSCAN) MODULE(CYBJSDLT)".

               

Environment

Component: ESP WORKLOAD AUTOMATION
Release:   12.0

Resolution

The TEMPLIB member will not be deleted under the following circumstances: 

1) If there is no COPYJCL statement in the application. In this case exit module CYBJSDLT is not invoked.
2) The TEMPLIB dataset is the same as the COPYJCL dataset.
3) The job was submitted from a library that is not TEMPLIB, and the job in TEMPLIB does not include a //* UNTIL statement.
4) The job was submitted from a library that is not TEMPLIB, and the job in TEMPLIB includes a //* UNTIL statement but the date has not yet passed.
5) There was an outstanding RESERVE on the TEMPLIB dataset.  Check for data set contention messages in the system log.
6) A failure was detected when ESP attempted to delete the TEMPLIB member. Failure messages are found in the system log.
7) The TEMPLIB member was not found.
8) Usermod 198 is active which means that the CYBJSDLT module does not delete the jCL member from the TEMPLIB that ESP selects based on //* FROM or //* UNTIL statements.