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-PRO/JCL
®
ESP Scheduler Interface
User’s Guide
Version 3.0.0
Publication Number: PJM0200-300-ESP
Publication Date: April 2011
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:
Using the JJESP EDIT Macro . . . 7
Chapter 3:
Validating Events. . . 9
Validating with the TSO PJEVENT Command. . . 9
Validating an Event in Batch . . . 11
Validating with the ESP JCLSCAN Exit . . . 12
Chapter 4:
Validating a Schedule Forecast . . . 17
Chapter 5:
Viewing the Structured JCL Listing (SJL) . . . 19
Chapter 6:
Using the ESP Event Criteria Panel . . . 21
Basic Definitions . . . 21
ESP Event Criteria Panel Messages . . . 24
Preface
The ASG-PRO/JCL ESP Scheduler Interface User’s 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 Cybermation’s 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.
About this Publication
This guide contains these chapters:
• 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
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 Administrator’s 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 User’s Guide (PJM0200-nnn) describes how to validate, change,
and reformat JCL.
• ASG-PRO/JCL JMP User’s 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 User’s Guide
(PJM0200-nnn-TWS) gives details about the use, setup and installation of the interface between PRO/JCL and IBM’s TWS scheduler.
• ASG-PRO/JCL ESP Scheduler Interface User’s 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 User’s Guide (PJM0200-nnn-CA7)
gives details about the use, setup and installation of the interface between PRO/JCL and the CA-7 scheduler.
Note:
Preface
Publication Conventions
ASG uses these conventions in technical publications:
Convention Usage
Arrow (►) Used in a procedure to indicate commands within menus. Also used to denote a one-step procedure.
Bold Indicates that case-sensitive usage is required for a directory, path,
file, dataset, member, database, program, command, or parameter name.
►Verify the settings in the asg.conf file.
Capitalization For system element names, this varies according to the product interface and its operating environment.
Mainframe file names use upper case, for example:
►Allocate a JSOPTEM member in the JLRCL library. Windows file names use mixed case, for example:
►Create a text file named SECLIST.txt in the C:\ProgramFiles\ASG\config directory. UNIX file names use mixed case, for example:
►Edit the databaseID.ACC file in the /database directory. Typical product and operating system elements include:
• Directory, path, file, dataset, member, database, program,
command, and parameter names.
• Window, field, field group, check box, button, panel (or
screen), and option labels.
• Names of keys. A plus sign (+) is inserted for key
combinations (e.g., Alt+Tab).
lowercase italic monospace
Information that you provide according to your particular situation. For example, you would replace filename with the actual name of the file.
Monospace Characters you must type exactly as they are shown, such as code, JCL, file listings, or command/statement syntax.
Also used for denoting brief examples in a paragraph. Underline Denotes a cursor-selectable field or line.
Vertical separator bar ( | ) with underline
Indicates options available with the default value underlined (e.g.,Y|N).
{} Braces { } indicate a choice of parameters; pick one item from the list.
Worldwide Customer Support
ASG provides support throughout the world to resolve questions or problems regarding installation, operation, or use of our products. ASG provides all levels of support during normal business hours and emergency support during non-business hours.
You can access support information at http://www.asg.com/support/support.asp.
ASG Third-party Support. ASG provides software products that run in a number of
third-party vendor environments. Support for all non-ASG products is the responsibility of the respective vendor. In the event a vendor discontinues support for a hardware and/or software product, ASG cannot be held responsible for problems arising from the use of that unsupported version.
Intelligent Support Portal (ISP)
The ASG Intelligent Support Portal (ISP) provides online support at http://isp.asg.com.
Log on to the ISP with this information: Customer ID = NNNNNNNNN Password = XXXXXXXXXX where:
NNNNNNNNN is your customer ID supplied by ASG Product Distribution. XXXXXXXXXX is your unique password supplied by ASG Product Distribution.
If you do not have your logon information, contact your local support center.
Severity Meaning
Expected Support Response Time 1 Production down, critical situation Within 30 minutes 2 Major component of product disabled Within 2 hours 3 Problem with the product, but customer has
work-around solution
Within 4 hours 4 “How-to” questions and enhancement requests Within 4 hours
Preface
ASG Documentation/Product Enhancements
Submit all product and documentation suggestions to ASG’s product management team
at http://www.asg.com/asp/emailproductsuggestions.asp.
Include your name, company, work phone, e-mail ID, and the name of the ASG product you are using. For documentation suggestions, include the publication number located on the publication’s front cover.
1
Chapter 1:
Introduction
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 night’s) 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/JCL’s 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.
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 JCLSCAN1 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 ESP’s event simulation followed by PRO/JCL’s 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.
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).
Catalog (Run-Time) Simulation
Thorough validation of production JCL requires that the JCL be analyzed on multiple levels to identify potential problems:
• On the most basic level, PRO/JCL ensures that the JCL is syntactically correct.
1 Introduction
• At the run-time level, PRO/JCL identifies:
• 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.
PRO/JCL ESP Support Basics
The basic concept of all the scenarios described in this guide is the use of ESP’s symbol library (SYMLIB) for the ESP simulation. Because the only way a SYMLIB can be specified is through an Event definition, it is always necessary to provide an EVENTID
whenever PRO/JCL ESP support is invoked (see Figure1 on page 5).
The JCL to be resolved comes either from the EDIT session or from specified JCL libraries. The ESP simulation is first invoked to perform its resolution based on the appropriate SYMLIB. After resolution is complete, PRO/JCL is invoked to check the JCL. All PRO/JCL ESP interface scenarios operate in this basic sequence:
• ESP Scheduler uses the appropriate SYMLIB and resolves the ESP symbols and
puts the JCL in execution sequence.
• 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.
How SYMLIBs are Specified
The four scenarios in “Usage Scenarios” on page 1 can be divided into two kinds as far as
the use of SYMLIBs is concerned: those where the SYMLIB is known (Events and Schedules) and those where it is unknown (single members in EDIT).
Checking Events and Schedules
Invoking the checking process for Events and Schedules is straightforward. When checking a specific Event, the Event definition contains the proper SYMLIB reference; also, when checking a complete Schedule, the necessary EVENTIDs identifying the SYMLIBs are contained within the Schedule. In each of these cases, the particular EVENTIDs are known; consequently, the process uses the appropriate SYMLIBs.
JCL Validation for a Single Member
Invoking the checking process for single members is somewhat more complex and done while in ISPF EDIT. Because you are editing the JCL removed from its normal inclusion within an Event, the only way to tell ESP which Event and SYMLIB to use is through the ESP Event Criteria panel. The JCL in the EDIT session is passed to ESP, along with the specified EVENTID and other criteria entered. ESP uses the criteria to simulate the Event and resolve the symbols. If you want to check the JCL using different SYMLIBs, the same PRO/JCL panel allows you to select different EVENTIDs and use different SYMLIBs.
1 Introduction
2
Chapter 2:
Using the JJESP EDIT Macro
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 Figure2 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
administrator for assistance.
• 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.
3
Chapter 3:
Validating Events
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 User’s Guide.
Validating with the TSO PJEVENT Command
This command can be used any time you are in ISPF. The command invokes the ESP
Event Criteria panel as shown in Figure3. Fill in the data fields as necessary. ESP
resolves symbols first followed by the PRO/JCL validation. The resulting Structured JCL
Listing will be displayed in BROWSE mode. It may be printed with the DSPRINT2
command, if needed.
Note:
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.
3 Validating Events
Validating an Event in Batch
Another way to have ESP resolve symbols and then use PRO/JCL to validate an Event’s
JCL is to set up and run a batch job. The template in Figure4 on page 12 is the
ESPEVENT member of the SAMPLIB library. You enter the information needed for ESP to find, collect and prepare the JCL. The sequential dataset is allocated in STEP01. This dataset name is passed to ESP in STEP02. ESP places the resolved JCL into the
sequential file. The file is passed to PRO/JCL in STEP03 for processing and the creation of the Structured JCL Listing. This is an excellent way to verify that changes to the execution JCL will not cause production problems.
The two required input parameters are SIMULATE EVENT and PRINT. If you wish to specify a ROOTJOB or other parameters like USER1, add them using correct ESP syntax. For example,
SIMULATE EVENT(ASG.SIMJOB) - ROOTJOB(MYJOB.A)
USER1(Parameters as needed for ESP)
PRINT('ASG.TEMP.ESPLIST')
To make ESPEVENT ready for execution
1 Modify the jobcard.
2 Change the DSN of the temporary dataset (ASG.TEMP.ESPLIST) to something
workable at your site.
3 Place the ESP subsystem name in the ESP SUB SYSTEM ID field (SUBSYS(ESP)).
4 Set up the ESP SIMULATE command parameters
(SIMULATE EVENT(ASG.SIMJOB)) as needed.
5 After submitting the job, check the resulting output for any error messages from ESP
or PRO/JCL.
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.
• 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.
Figure 4 • Batch Validation JCL Member ESPEVENT.
//ESPEVENT JOB (ACCT),'PROGRAMMER NAME' //********************************************************************* //* SAMPLE BATCH JOB TO VALIDATE EVENT JCL //* REF: SAMPLIB(ESPEVENT) //********************************************************************* //* MODIFY THIS JCL TO MEET YOUR SYSTEM'S REQUIREMENTS //********************************************************************* //STEP01 EXEC PGM=IEFBR14 //****** CREATE DATA SET TO RECEIVE RESOLVED EVENT JCL //DD1 DD DSN=.TEMP.ESPLIST,DISP=(MOD,CATLG),UNIT=SYSDA, <==== // SPACE=(TRK,(1,1),RLSE) //****** EXTRACT THE RESOLVED EVENT JCL ******************************* //STEP02 EXEC PGM=ESP,PARM='SUBSYS(ESP)',REGION=4M <==== //STEPLIB DD DSN=CPE.V5R1.SSCPLINK,DISP=SHR <==== //SYSPRINT DD SYSOUT=* //SYSIN DD * SIMULATE EVENT(DSSUSR.ESPTEST) - <==== PRINT('ASG.TEMP.ESPLIST') <==== /* //STEP03 EXEC PR1PROC,COND=(8,LT) //******************************************************************** //* PRO/JCL VALIDATE THE JCL CREATED BY ESP //******************************************************************** //JLJOB DD DSN=TEMP.SCHEDULE.JCLOUT,DISP=(OLD,DELETE) //SYSIN DD * %% INPUT DSN=ASG.TEMP.ESPLIST, %% TYPE=SEQUENTIAL, %% REPORTS=SJL
Validating with the ESP JCLSCAN Exit
There might be times when you are working within ESP to set up or modify an existing Event and you want to check the JCL after symbol resolution. A convenient method is to use PRO/JCL with the JCLSCAN exit provided within ESP. The procedure to do this is
shown in Figure5 on page 14, Figure6 on page 15 and Figure7 on page 16.
All the related ESP parameters are taken into consideration by ESP when it does its symbol resolution. A key point is that the prepared JCL from ESP is in execution sequence so the PRO/JCL validation and catalog simulation will accurately reflect the run-time environment.
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: (note the value is a single blank)
session_id = " "
After:
session_id = "ID=x"
3 Validating Events
4
Chapter 4:
Validating a Schedule Forecast
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 Figure8
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 User’s 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 Modify the job card.
2 Insert the valid ESP subsystem name on the EXEC CYBJS000 step and specify the
Schedule Activity Report parameter ‘SAR’.
3 On the SADGEN control statement, specify the starting and ending dates and times
and the dataset for the SAR output.
4 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
Figure 8 • Validating a Schedule in Run-time Order.
//*ESPSCHED JOB (ACCT),'PROGRAMMER NAME'
// SET HLQ='PRO/JCL HIGH LEVEL QUALIFIER' // JCLLIB ORDER=&HLQ..INSTALL
//********************************************************************* //********************************************************************* //* INTERFACE TO ESP (ENTERPRISE SYSTEMS PLATFORM)
//********************************************************************* //****** EXTRACT JOBS IN PREDICTED EXECUTION SEQUENCE FROM ESP ******** //********************************************************************* //STEP01 EXEC PGM=IEFBR14
//JCLFILE DD UNIT=SYSDA,SPACE=(CYL,(5,5)),DISP=(NEW,CATLG), // DSN=TEMP.SCHEDULE.JCLOUT
//STEP02 EXEC PGM=CYBJS000,PARM='SUBSYS(ES44) SAR',REGION=0M //PRODJCL DD DSN=PROD.MODIFIED.JCL,DISP=SHR // DD DSN=PROD.SCHEDULE.JCL,DISP=SHR // DD DSN=PROD.UTILITY.JCL,DISP=SHR //SYSPRINT DD SYSOUT=* //SADFILE DD DSN=CYBCC01.ESPZ.WORKFILE,DISP=SHR //ESPCOLD DD DSN=ESP.PARMLIB(ESPCOLD),DISP=SHR //ESPPARM DD DSN=ESP.PARMLIB(ESPPARM),DISP=SHR //ESPWARM DD DSN=ESP.PARMLIB(ESPWARM),DISP=SHR //SYSIN DD * SADGEN DATASET(SADFILE)
FROM('00:01 TODAY') TO('24:00 TODAY') JCLOUT('TEMP.SCHEDULE.JCLOUT')
//STEP03 EXEC PR1PROC,COND=(8,LT)
//******************************************************************** //* PRO/JCL VALIDATE THE JCL CREATED BY ESP
//******************************************************************** //JLJOB DD DSN=TEMP.SCHEDULE.JCLOUT,DISP=(OLD,DELETE) //SYSIN DD * %% INPUT DDNAME=JLJOB, %% TYPE=SEQUENTIAL, %% REPORTS=SJL 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:
5
Chapter 5:
Viewing the Structured JCL Listing
(SJL)
After ESP simulation and PRO/JCL validation, PRO/JCL produces the Structured JCL
Listing. Figure9 on page 20 shows the before picture of the JCL. The member is shown
for reference against the Structured JCL Listing in Figure10 on page 20. Important items
to observe are:
• The resolved source JCL statements. (See 1 in Figure10 on page 20.)
• The comment lines inserted by ESP. (See 2 in Figure10 on page 20.)
• The dataset associated with the EVENTID. This line is also inserted by ESP. (See 3
in Figure10 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 Figure10 on page 20.)
• Error messages and other analysis data inserted by PRO/JCL. (See 5 in Figure10 on
page 20.)
For complete details about the remainder of the Structured JCL Listing, refer to the
ASG-PRO/JCL User’s Guide. It describes details about the format and notational
Figure 10 • The numbers at the far left are the objects of the Notes on page19
********************************* 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) ...
Figure 9 • JCL before processing with ESP
//DSSUSR JOB (JRR),'UNLOAD',MSGCLASS=X, // NOTIFY=DSSUSR,MSGLEVEL=(1,1) //*
//IEFBR14 EXEC PGM=IEFBR14
6
Chapter 6:
Using the ESP Event Criteria Panel
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.
USER PARAMETERS and CASE SENSITIVE
If values in the USER PARAMETERS fields are case sensitive, type a Y in the CASE SENSITIVE field.
ESP SUB SYSTEM ID
This field contains the subsystem identifier for the LPAR that ESP runs in. If your site has a single ESP Subsystem, then you can set this field once and forget it.
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.
Display Simulation Messages
ESP generates messages during its simulation; put a Y in the DISPLAY SIMULATION
MESSAGES field to see these messages see Figure12 on page 23. Put an N to bypass
their display.
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.
JMP Library and JMP Name
Type the full dataset name and the member name of any JMP program you want to use. PRO/JCL ignores input in the JMP Library and will run its validation process without calling a JMP unless there is a member name in the JMP name field.
Figure 11 • Entering Event Criteria.
Specify ESP Criteria Command ===>
PREFIX ===> Blank Defaults to Group Name DESCRIPTIVE NAME ===> Blank Lists All Events
SCHEDULE TIME ===>
(Simulated Date of Execution, Defaults to next SCH) ROOT JOB(S) ===>
(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)
ESP SUB SYSTEM ID ===> ESP3 Specify ESP Sub System ID or Blank For List
DISPLAY SIMULATION MESSAGES ===> (Y or N)
RTS Member ===> ( * for list) JMP Library ===>
JMP Name ===> Parm ==>
Press ENTER To Launch ESP Symbol Resolution Followed by PRO/JCL Validation. 6 Using the ESP Event Criteria Panel
Figure 12 • ESP Simulation messages displayed prior to PRO/JCL validation.
- PRO/JCL --- ESP SIMULATION MESSAGES --- Row 1 to 2 of 2 COMMAND ===>
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
ESP Event Criteria Panel Messages
This subsection presents the common error messages you might encounter when using the ESP Event Criteria panel.
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.
Subsystem subsysname not found
For the ESP SUB SYSTEM ID field, if you put in a subsystem name that is not in the LPAR, PRO/JCL displays the list of subsystems in the Select ESP Subsystem panel and the message. Choose a subsystem from the list and press Enter.
A Subsystem Name Was Not Selected
For the ESP SUB SYSTEM ID field, if you do not select a subsystem name from the Select ESP Subsystem panel, PRO/JCL redisplays the ESP Event Criteria panel and this message.
RTS Member not found
For the RTS Member field. The member specified in the RTS Member field does not exist.
Data set not found
For the JMP Library field. PRO/JCL cannot find the dataset with the name given in the JMP Library field.
6 Using the ESP Event Criteria Panel
Member Not Found
For the JMP Name field. PRO/JCL cannot find the member named in the JMP Name field. This implies that the library in the JMP Library is valid.
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.
An Event Name Was Not Selected
For the DESCRIPTIVE NAME field. If you blank out the DESCRIPTIVE NAME field, PRO/JCL displays the Select an Event panel. If you do not select an Event name from this panel, PRO/JCL displays the ESP Event Criteria panel and this message.
ESP Messages
If ESP detects errors, PRO/JCL displays them in the message field of the ESP Event Criteria panel. See Figure13 on page 26.
Subsystem subsystemname Not Found
If the name you type or insert into the ESP SUB SYSTEM ID field does not contain a working ESP system, PRO/JCL displays the ESP Event Criteria panel and this ESP message where subsystemname is the erroneous name.
Group Name Error
If you do not have access to the group name you typed in the group name field, PRO/JCL displays the ESP Event Criteria panel and an ESP message.
Descriptive Name Not Valid
If you enter a non-valid DESCRIPTIVE NAME, PRO/JCL displays the ESP Event Criteria panel and an ESP message.
Schedule Time Not Valid
If you enter a non-valid schedule time, PRO/JCL displays the ESP Event Criteria panel and an ESP message ESP607E SYNTAX ERROR STARTING AT.
Figure 13 • Location of ESP Error messages
Specify ESP Criteria Command ===>
ESP607E SYNTAX ERROR STARTING AT 'ASDF'
PREFIX ===> DSSUSR Blank Defaults to Group Name DESCRIPTIVE NAME ===> ESPTEST Blank Lists All Events
SCHEDULE TIME ===> ASDF
(Simulated Date of Execution, Defaults to next SCH) ROOT JOB(S) ===>
(Names of Jobs and Successors For A Partial Rerun)
User Parameters To Be Passed To The Event: USER1 ===>
USER2 ===> USER3 ===> USER4 ===> ...
Index
Symbols (square brackets) v {} (braces) v A audience of guide 1 Bbasic 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
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
Z