Convert DJCNET script into a native Broadcom ESP Application
search cancel

Convert DJCNET script into a native Broadcom ESP Application

book

Article ID: 449269

calendar_today

Updated On:

Products

ESP Workload Automation

Issue/Introduction

In the process of jes3 to jes2 migration, our production system is on the z/os 2.5 as in migration process, we are checking the system Proc libs to make compatibility for JES2. We could see that our LOGREC proc is using few statement related to the ESP and JES3 related DJCNET.

Environment

Component: ESP Workload Automation

Release: All Releases

Resolution

In native ESP, the SELECT card is no longer needed because any job defined inside an active APPL block is automatically selected for execution based on its dependencies.
Here is the converted, native ESP Application syntax:
 
text
EREPREPT:ESPPROC                        
JCLLIB 'ESP.CNTL'               
APPL MDSEREP1
/* Native ESP replaces DJCNET with the APPL statement */

GENTIME ERP1 TODAY AT 06.00 LESS 1 DAY  
GENTIME ERP2 TODAY AT 06.00             
JYESTERDAY = '%ERP1YY%ERP1DDD'          
JTODAY = '%ERP2YY%ERP2DDD'              

JOB EREPDUMP
RUN DAILY RELEASE (EREPHWD, EREPSFT) ENDJOB JOB EREPHWD
RUN DAILY ENDJOB JOB EREPSFT
RUN DAILY ENDJOB /* The SELECT statement is removed. ESP tracks these jobs natively via APPL */
Key Changes Made
  • APPL MDSEREP1: Replaced the DJCNET MDSEREP1 statement. This registers the workload as a native ESP application.
  • ENDJOB Statements: Added explicit ENDJOB delimiters for each job definition block, which is standard best practice for native ESP procedures.
  • Removed SELECT: Completely stripped out SELECT (EREPDUMP, EREPHWD, EREPSFT). Native ESP uses the APPL definition to track and submit the jobs automatically when their triggers or predecessors match.