Professional Documents
Culture Documents
The information contained herein is the confidential and proprietary information of Allen Systems Group, Inc. Unauthorized use of this information and disclosure to third parties is expressly prohibited. This technical publication may not be reproduced in whole or in part, by any means, without the express written consent of Allen Systems Group, Inc. Copyright 2011 Allen Systems Group, Inc. All rights reserved. All names and products contained herein are the trademarks or registered trademarks of their respective holders. ASG Worldwide Headquarters Naples Florida USA | asg.com | info@asg.com 1333 Third Avenue South, Naples, Florida 34102 USA Tel: 239.435.2200 Fax: 239.263.3692 Toll Free: 800.932.5536 (USA only)
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii
About this Publication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .iii Related Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .iv Publication Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v Worldwide Customer Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .vi ASG Documentation/Product Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Chapter 1:
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Usage Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Terminology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 PRO/JCL ESP Support Basics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 How SYMLIBs are Specified . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Chapter 2: Chapter 3:
Validating a Schedule Forecast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Viewing the Structured JCL Listing (SJL) . . . . . . . . . . . . . . . . . . . . . . 19 Using the ESP Event Criteria Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Basic Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 ESP Event Criteria Panel Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
i
ii
Preface
The ASG-PRO/JCL ESP Scheduler Interface Users Guide is for the person who runs the ASG-PRO/JCL product (herein called PRO/JCL) to accomplish any of these functions of PRO/JCL at a site running Cybermations ESP Workload Manager (herein called ESP):
JCL validity checking. JCL site standards enforcement. JCL change and JCL reformat.
This section describes the organization of the guide and discusses documentation conventions followed in the PRO/JCL documentation library.
Chapter 1, Introduction, introduces the concepts of the interface and describes how PRO/JCL users benefit from using the interface. Chapter 2, Using the JJESP EDIT Macro, describes how to use the edit macro to validate JCL in a member. Chapter 3, Validating Events, describes how to use the interface job batch to validate events. Chapter 4, Validating a Schedule Forecast, describes how to use the interface job batch to validate schedules. Chapter 5, Viewing the Structured JCL Listing (SJL), provides a brief overview of the SJL. Chapter 6, Using the ESP Event Criteria Panel, describes how to use the Event Criteria panel.
iii
Related Publications
The documentation library for PRO/JCL consists of these publications (where nnn represents the product version number):
ASG-PRO/JCL Installation Guide (PJM0300-nnn) intended for the product installer, this task-oriented guide contains information needed to install PRO/JCL, including step-by-step procedures. ASG-PRO/JCL Version Upgrade Installation Guide (PJM0300-nnn-UPG) provides instructions for upgrading PRO/JCL from one release to another. ASG-PRO/JCL System Administrators Guide (PJM2100-nnn) contains information needed to oversee the ongoing operation of PRO/JCL. ASG-PRO/JCL Reference Guide (PJM0400-nnn) provides in-depth information about PRO/JCL tasks and facilities. ASG-PRO/JCL Users Guide (PJM0200-nnn) describes how to validate, change, and reformat JCL. ASG-PRO/JCL JMP Users Guide (PJM0200-nnn-JMP) describes how to use the ASG Application Program Interface (DSSIAPI) JCL Manipulation Program (JMP) to implement JCL change and JCL standards enforcement. ASG-PRO/JCL Enhancement Summary (PJM1000-nnn) lists the enhancements for PRO/JCL. ASG-PRO/JCL Online Help provides immediate information and assistance to users who encounter problems, or need more information, while using PRO/JCL panels. ASG-PRO/JCL TWS for z/OS Scheduler Interface Users Guide (PJM0200-nnn-TWS) gives details about the use, setup and installation of the interface between PRO/JCL and IBMs TWS scheduler. ASG-PRO/JCL ESP Scheduler Interface Users Guide (PJM0200-nnn-ESP) gives details about the use, setup and installation of the interface between PRO/JCL and the ESP scheduler. ASG-PRO/JCL CA-7 Scheduler Interface Users Guide (PJM0200-nnn-CA7) gives details about the use, setup and installation of the interface between PRO/JCL and the CA-7 scheduler.
Note:
iv
Preface
Publication Conventions
ASG uses these conventions in technical publications:
Convention Arrow () Bold Usage Used in a procedure to indicate commands within menus. Also used to denote a one-step procedure. Indicates that case-sensitive usage is required for a directory, path, file, dataset, member, database, program, command, or parameter name.
Severity
1 2 3 4
Meaning
Production down, critical situation Major component of product disabled Problem with the product, but customer has work-around solution How-to questions and enhancement requests
vi
Preface
vii
viii
Chapter 1:
Introduction
1
ASG provides this guide to IT professionals who work with JCL members containing ESP symbols. The crucial point is that you want ESP to resolve the symbols prior to validation by PRO/JCL in these situations:
A single JCL member. All the jobs for an Event. An entire day's (or nights) schedule.
The facilities provided through the interface are designed to support this wide variety of requirements and enhance the overall quality and efficiency of the JCL processing at any site using the ESP.
Usage Scenarios
There are four basic usage scenarios in which resolution of ESP symbols followed by PRO/JCL validation is supported:
You are editing JCL that contains ESP symbols and want PRO/JCL to validate the JCL after the symbols have been resolved. You have made changes to the JCL used by an Event and want to use PRO/JCL to validate JCL for the entire Event. You are working with Events within the ESP environment and want to validate the JCL used by the Events. You want PRO/JCL to validate an entire batch schedule as ESP will submit it.
In all four scenarios, PRO/JCL performs thorough syntax checking and catalog simulation and creates a Structured JCL Listing (SJL) to show you exactly how the resolution was performed and whether PRO/JCL found any errors in the resolved JCL. See Catalog (Run-Time) Simulation on page 2 for more about PRO/JCLs catalog simulation and see Viewing the Structured JCL Listing (SJL) on page 19 for more about the SJL. Scenario 1 is supported by PRO/JCL Edit macro (JJESP) passing the necessary parameters to ESP, such as event ID; in turn, ESP uses the appropriate SYMLIB for symbol resolution. The Edit macro then invokes PRO/JCL to perform JCL validation.
1
Scenario 2 is supported by PRO/JCL through a batch run and through the TSO command PJEVENT. PRO/JCL confirms that the changes will not create JCL errors when the Event is next run in production. Scenario 3 is supported through ESP's ISPF interface. While working with events, you can use the JCLSCAN exit on the Simulate Event Execution Additional Options panel to validate JCL for an event (see Validating with the ESP JCLSCAN Exit on page 12). This method integrates running ESPs event simulation followed by PRO/JCLs validation, all without exiting ESP. Scenario 4 is supported by a batch job, ESPSCHED. Use this job when you want to check a schedule prior to production. It is an effective way to provide early alerts about potential problems so necessary fixes can be applied in a timely fashion. A batch job skeleton invokes the ESP extraction and symbol resolution processes. If your site uses PRO/JCL standards exits, PRO/JCL can invoke them in any of these scenarios.
1
Terminology
Event
This refers to an ESP Event. In this guide, Validate an Event refers to the processes by which the JCL associated with or generated by an ESP Event is validated by PRO/JCL.
Event Simulation
ESP uses the term simulation to refer to its multi-stage process of simulating an event:
Triggering an Event. Generating the corresponding JCL. Resolving ESP Symbols within the JCL (see Symbol Resolution on page 3).
On the most basic level, PRO/JCL ensures that the JCL is syntactically correct.
1.
See the ESP Workload Manager Reference Guide for more about this exit.
1 Introduction
environmental errors, such as security violations and programs not found. dataset disposition errors.
Whether processing a single JCL member or a sequence of members, PRO/JCL uses its powerful z/OS catalog simulation facility to ensure that the JCL steps will create, use and delete the datasets as expected.
Symbol Resolution
For this guide, there are two main types of symbols used in JCL:
Those native to the z/OS operating system and resolved by JES at run time. ESP Symbols. ESP substitutes the appropriate value when the event is triggered. These are the symbols ESP resolves prior to JCL validation by PRO/JCL.
Validation
In PRO/JCL usage, Validation is the process of analyzing JCL to identify problems that might occur in production (for example, syntax errors, security violations, catalog problems (see Catalog (Run-Time) Simulation on page 2), and so on).
JCL Checking
This term is synonymous with Validation.
ESP Scheduler uses the appropriate SYMLIB and resolves the ESP symbols and puts the JCL in execution sequence. The resolved JCL is placed in a sequential file.
3
PRO/JCL reads the JCL in the sequential file. PRO/JCL performs its validation process, including catalog simulation when checking an Event or a Schedule. PRO/JCL invokes a standards program, if requested. PRO/JCL produces its Structured JCL Listing containing the resolved and expanded JCL with all ESP and PRO/JCL messages.
1 Introduction
Chapter 2:
2
When you are editing a JCL member containing ESP symbols, use the JJESP EDIT macro to validate the JCL. JJESP invokes symbol resolution, passing the necessary criteria to ESP so that it can perform its symbol resolution. See Figure 2 on page 8. Then, the resulting JCL is given to PRO/JCL for validation. There are two essential considerations for ESP:
Specifying the subsystem running ESP. Specifying an EVENTID so ESP uses the appropriate SYMLIB reference.
Optionally, you can give ESP a ROOTJOB and up to four user-parameters. See Using the ESP Event Criteria Panel on page 21 for more about the fields in the ESP Event Criteria panel. ESP uses the Event-referenced SYMLIB to perform resolution on the JCL from the EDIT session. After that, PRO/JCL performs its validation and displays the resulting Structured JCL Listing in Browse mode. See Viewing the Structured JCL Listing (SJL) on page 19 for more information about the SJL. After review, you can return to the original JCL in the EDIT session for further modification and checking. If the JCL under consideration is used with multiple Events with many different SYMLIBs, you can run PRO/JCL several times, entering a new EVENTID each time into the ESP Event Criteria panel. This checks the JCL with each event and associated SYMLIB.
Notes: You must have a personal ESP ID identical to your TSO ID. Consult your ESP
Only those Events to which your ID has access will be available. Because the job is being checked on its own and not as part of an Application, Event or Schedule, PRO/JCL might issue error messages such as DATA SET NOT FOUND that can be confusing without the knowledge how a job is related to a schedule.
Chapter 3:
Validating Events
3
There are many situations where you might want to check all the JCL in an Event. Perhaps you have modified some of the execution JCL members, added or changed an ESP symbol, changed the execution sequence, added a new job in the sequence, and so on. Whenever this has happened, you will want to get the ESP symbols resolved and then have PRO/JCL check the entire Event for JCL errors. With the jobs presented to PRO/JCL in execution sequence, inter-job catalog simulation is done in addition to the regular syntax and environment checking. This function can be invoked in a variety of ways:
In ISPF foreground through the TSO PJEVENT command. Through a batch job. From within ESP through its JCLSCAN exit.
Because of the way PRO/JCL handles multiple jobs aggregated into a sequential dataset, you should consider the effect of the Input Statement SPLITJOBS parameter. With this parameter, PRO/JCL completely processes each job individually. Without this parameter, PRO/JCL processes all the jobs in the file. For detailed information about the use of SPLITJOBS see the ASG-PRO/JCL Users Guide.
The PRO/JCL run-time options values are derived from Run-time Options members.
2.This is the standard TSO print command. If this feature does not work, check with your system administrator for alternatives.
10
3 Validating Events
3 4
Notes: The PR1PROC used in STEP03 is the procedure to invoke PRO/JCL from batch
jobs. This PROC is included with the regular PRO/JCL installation. It might be desirable to make a copy of it and modify it for your particular use.
You might want to make changes to the options settings PRO/JCL uses for its processes that are different from the usual ones in use. If you need help with this, consult your PRO/JCL administrator or contact ASG using one of the avenues listed in the preface of this guide.
11
Each job in the Structured JCL Listing will have //* comment cards inserted by ESP stating the source library and member name for that particular job. See Viewing the Structured JCL Listing (SJL) on page 19. Any JCL errors found by PRO/JCL resulting from the syntax check, catalog simulation, other checks or improper symbol resolution will be displayed in the Structured JCL Listing.
3 Validating Events
Notes: The exit name to use is PROJCL (with no slash) not the registered trademark
PRO/JCL.
The Structured JCL Listing will have a set of //* comment cards for each job indicating the library and member name from which the JCL was derived. The execution of PRO/JCL takes place in your TSO address space. You will not be able to do anything else in your address space until the process is finished - usually only a few seconds, but this depends on system load and Event size. When the process is done, PRO/JCL displays the resulting Structured JCL Listing in BROWSE mode. You can print it using DSPRINT. Press PF3 to display a list of ESP messages associated with ESP simulation. If you put an asterisk (*) in the OUTPUT DATASET field on the SIMULATE EVENT EXECUTION panel, ESP makes the resolved JCL available for viewing. To see the resolved JCL, PF3 from the SJL; ESP displays its messages. While viewing the messages press PF7 to page up to the resolved JCL. Press PF3 again to quit and return. If your site is running more than one PRO/JCL started task, you need to modify a line in the D0JEEPJ exec: Before: After:
session_id = "ID=x"
13
14
3 Validating Events
15
16
Chapter 4:
4
There might be times when you want to perform a PRO/JCL validation on an entire night's production batch run. For this batch-oriented task, you use the existing PRO/JCL SAMPLIB JCL member, ESPSCHED. There are three steps in the batch job. The first step allocates the temporary dataset into which ESP places the resolved JCL. The second step activates ESP through a supplied PRO/JCL assembler module. The third step invokes PRO/JCL for validation of the resolved JCL in production sequence. The temporary dataset is referenced as ddname JCLFILE in its allocation in STEP01, referenced as JCLOUT in the SYSIN parameters for ESP in STEP02 and as ddname JLJOB for use by PRO/JCL in STEP03 (see Figure 8 on page 18). Be sure the same dataset name is used in all three places. If you want to look at the resolved JCL for troubleshooting purposes, change the DISP in ddname JLJOB to KEEP. In brief, when the run is complete, you first check the ESPSCHED job output for return codes and ESP messages to make sure everything ran as planned. Then, look for any errors that PRO/JCL has found that will cause problems during the batch cycle. Accordingly, review the error messages in the Structured JCL Listing and determine what needs to be done to make the corrections prior to the start of the shift. Because of the way PRO/JCL handles multiple jobs aggregated into a sequential dataset, you should consider the effect of the Input Statement SPLITJOBS parameter. With this parameter, PRO/JCL completely processes each job individually. Without this parameter, PRO/JCL processes all the jobs in the file en masse. For detailed information about the use of SPLITJOBS see the ASG-PRO/JCL Users Guide.
To validate a schedule forecast, copy the ESPSCHED member from the PRO/JCL SAMPLIB library and modify it (Figure 8 on page 18)
1 2 Modify the job card. Insert the valid ESP subsystem name on the EXEC CYBJS000 step and specify the Schedule Activity Report parameter SAR. On the SADGEN control statement, specify the starting and ending dates and times and the dataset for the SAR output. Substitute a valid dataset name for the job to use in the JCLFILE and JLJOB DD statements and in the SADGEN input cards (as shipped, the dataset name is TEMP.SCHEDULE.JCLOUT).
17
Note:
The comment on line 6 of ESPSCHED might read differently depending on the version of PRO/JCL installed. For releases older than 2.5.0H this comment reads: INTERFACE TO EXECUTION SCHEDULING PROCESSOR
18
Chapter 5:
After ESP simulation and PRO/JCL validation, PRO/JCL produces the Structured JCL Listing. Figure 9 on page 20 shows the before picture of the JCL. The member is shown for reference against the Structured JCL Listing in Figure 10 on page 20. Important items to observe are: The resolved source JCL statements. (See 1 in Figure 10 on page 20.) The comment lines inserted by ESP. (See 2 in Figure 10 on page 20.) The dataset associated with the EVENTID. This line is also inserted by ESP. (See 3 in Figure 10 on page 20.) Comment lines inserted by PRO/JCL. In the case of processing done through the JJESP EDIT macro, PRO/JCL gives ESP the JCL from the EDIT work area to resolve the JCL. These lines remind the reader that the validated JCL was from the EDIT work-area and not from the member referenced in the line marked by 3. (See 4 in Figure 10 on page 20.) Error messages and other analysis data inserted by PRO/JCL. (See 5 in Figure 10 on page 20.)
For complete details about the remainder of the Structured JCL Listing, refer to the ASG-PRO/JCL Users Guide. It describes details about the format and notational conventions used in the report.
19
Figure 10 The numbers at the far left are the objects of the Notes on page 19
********************************* Top of Data ******************************** Structured JCL Listing AS OF: 12/22/04 15:31:15 PRO/JCL Release R250J RTS Member: DEFAULT Security Exit: ON -------------------------------------------------------------------------------********************************************** *** Results of processing DSSUSR.ESPLIST *** ********************************************** 1 //DSSUSR JOB (JRR),'UNLOAD',MSGCLASS=X, 1 // NOTIFY=DSSUSR,MSGLEVEL=(1,1) 1 //* 2 //* 2 //* SCANNED BY ESP AT 15.31.14 ON WEDNESDAY SEPTEMBER 22ND, 2008 2 //* SYSTEM ESP53, SUBSYSTEM ESP3 2 //* REQUESTED BY EVENT DSSUSR.ESPTEST 3 //* JCL FROM DSSUSR.ESP.JOBLIB(ESPTEST) 2 //* 4 //* PRO/JCL - JCL WAS PROCESSED FROM EDIT WORKAREA 4 //* 1 //* 1 //IEFBR14 EXEC PGM=IEFBR14 1 //DD2 DD DSN=DSSUSR.JCL.Y2008,DISP=SHR 5 E1 - DSS20028E - Data set 'DSSUSR.JCL.Y2008' was not found in catalog. 5 --- END OF STEP --5 --- END OF JOB --5 5 JOB DSSUSR CONSISTS OF 1 PROGRAM(S), 0 PROC(S), 0 INCLUDE(S), 1 DD STATEMENT(S) ...
20
Chapter 6:
6
First PRO/JCL and then ESP perform validity checks on the values entered. If either program finds an error, PRO/JCL returns to the ESP Event Criteria panel displaying the error message. Correct the error, and press ENTER again. Anytime PRO/JCL displays this panel it inserts the most recently used values for the fields.
Basic Definitions
EVENTID
The EVENTID is divided into the PREFIX and the DESCRIPTIVE NAME fields, as you are accustomed to seeing in the ESP panels. You may type in the values directly, using wild-cards in DESCRIPTIVE NAME, just as you would in the ESP panels.
If you leave the PREFIX part blank, it defaults to the current GROUPID (which is the same as your TSO userID). If you use a PREFIX you are not authorized to access, PRO/JCL displays an ESP error message. Correct the entry and retry. If you leave the DESCRIPTIVE NAME blank, PRO/JCL gets a list of descriptive names from ESP for the PREFIX and displays them. Type S next to the one you want to choose and press ENTER.
21
If you're not sure of the ESP Subsystem ID, put blanks in the field and press ENTER. PRO/JCL will display a list of subsystems. Type 'S' next to the ESP Subsystem, and press ENTER. If you have an ESP subsystem for testing, you can use this field to switch simulation between the testing and production subsystems.
RTS Member
Type the name of the RTS member you want to use; if one is assigned by the PRO/JCL administrator, that one will be used.
22
PREFIX ===> DESCRIPTIVE NAME ===> SCHEDULE TIME ROOT JOB(S) ===>
(Simulated Date of Execution, Defaults to next SCH) ===> (Names of Jobs and Successors For A Partial Rerun) User Parameters To Be Passed To The Event: USER1 ===> USER2 ===> USER3 ===> USER4 ===> CASE SENSITIVE ===> ===> (BLANK, N or Y) ESP3 Specify ESP Sub System ID or Blank For List (Y or N)
DISPLAY SIMULATION MESSAGES ===> RTS Member ===> JMP Library ===> JMP Name ===> ( * for list) Parm ==>
THE FOLLOWING MESSAGES WERE GENERATED BY THE ESP SIMULATION. PRESS ENTER OR END TO CONTINUE. SIMULATION OF EVENT DSSUSR.ESPTEST AT 15.25.46 ON THURSDAY DECEMBER 29TH, 2008 JOBS: DSSUSR
23
PRO/JCL Messages
Depending on user input, PRO/JCL displays messages in the ESP Event Criteria panel alerting users to non-valid input values. PRO/JCL first looks at the ESP SUB SYSTEM ID field and compares the value there with the IDs in the LPAR list. If the name is found then PRO/JCL looks at the EVENTID fields; otherwise, PRO/JCL displays a list of subsystem IDs in the Select ESP Subsystem panel. If PRO/JCL finds the DESCRIPTIVE NAME field blank, it queries ESP for a list of Events authorized for the PREFIX and displays the list. Otherwise, it passes all the fields to ESP.
24
Enter Y or N
For the CASE SENSITIVE and the DISPLAY SIMULATION MESSAGES fields. Enter Y for YES or N for NO in the CASE SENSITIVE and the DISPLAY SIMULATION MESSAGES fields.
ESP Messages
If ESP detects errors, PRO/JCL displays them in the message field of the ESP Event Criteria panel. See Figure 13 on page 26.
25
===> ASDF (Simulated Date of Execution, Defaults to next SCH) ===> (Names of Jobs and Successors For A Partial Rerun)
User Parameters To Be Passed To The Event: USER1 ===> USER2 ===> USER3 ===> USER4 ===> ...
26
Index
Symbols (square brackets) v {} (braces) v A audience of guide 1 B basic process PRO/JCL ESP 3 C CASE SENSITIVE field of the ESP Event Criteria panel 21 catalog simulation 2 checking see validation D DESCRIPTIVE NAME field 21 part of Event ID 21 E EDIT macro invocation 7 name and use 7 SYMLIB usage 4 usage 7 usage scenario 1 error messages see messages ESP JCLSCAN exit for event validation 12 messages 25 ESP Event Criteria panel used with EDIT macro 7 ESP Simulation Messages field 22 ESP Subsystem ID field of the ESP Event Criteria panel 21 viewing list of 22 ESPEVENT JCL member for Event Validation 11 ESPSCHED JCL used to validate schedule 17 modifications to base member 17 Event definition 2
SYMLIB usage 4 validation batch, introduction 9 how to use batch 11 how to use JCLSCAN exit from ESP 12 how to use TSO command 9 JCLSCAN exit, introduction 9 TSO command, introduction 9 EVENTID field 21 G GROUPID see PREFIX I intended use of PRO/JCL ESP support 1 J JCL
checking or validation see validation standards exit in usage scenarios 2 JCLSCAN how to use validation exit from ESP 12 usage scenario 2 JJESP EDIT macro use 7 K KEEP, dataset disposition for resolved JCL 17 M message Descriptive Name Not Valid 25 Group Name Error 25 Non-ESP Subsystem name 25 Schedule Time Not Valid 26 messages ESP after resolution 25 PRO/JCL before resolution 24 P personal ESP ID see PREFIX PJEVENT TSO command 9 PREFIX 27
field 21 part of EVENTID 21 PRO/JCL catalog simulation 2 messages 24 run-time simulation 2 PRO/JCL ESP basic process 3 PROJCL, exit name to use in ESP JCLSCAN exit 15 R run-time simulation 2 S SADGEN, ESP command used in schedule validation 17 schedule usage scenario 2 validation 17 simulation catalog 2 event simulation definition 2 run-time see catalog single member, SYMLIB usage 4 Structured JCL Listing, explanation of messages 19 symbol resolution ESP 3 z/OS 3 SYMLIB reference in Event 4 reference to is made in event 3 telling PRO/JCL which to use 4 T TSO command PJEVENT use 9 U usage scenarios 1 USER PARAMETERS fields of the ESP Event Criteria panel 21 V validation event 9 JCL 3 single member in EDIT 7 Y Y as response to Case Sensitive field 21 ESP Simulation Messages field 22
28
CD Contents