To correctly code JCL statements and parameter values, you need
to collect certain company-specific information. Use this checklist and worksheet
to document what you need to know about your company's IT environment.
Procedure
Ask your system
programmer or mentor to help you complete the following list, which identifies
elements of your work environment that might affect the JCL that you code. Use
Table 1 to
record your answers. When this worksheet is complete, you should have the
company-specific information you need for most of the jobs you will run on z/OS®.
- Determine which job entry subsystem (JES2 or JES3) is installed
on the z/OS system
you will use. For many jobs, the type of JES does not affect JCL parameters;
for certain jobs, however, the JES in use does dictate which JCL parameters,
values, or job entry control (JECL) statements you may code.
- Determine which access methods your company uses for
its data sets. An access method defines the technique that is used to store
and retrieve data. Access methods have their own data set structures to organize
data, system-provided programs (or macros) to define data sets, and utility
programs to process data sets. Access methods, therefore, determine which
JCL parameters and parameter values that you need to code.
- For direct-access storage devices (DASD), determine which
naming conventions are used, as well as default or recommended values for
data set attributes.
- For storing or backing up data on tape, determine which
tape device volume numbers and types are available for your use.
- Determine whether your company uses the Storage Management
Subsystem (SMS) to automate the use of storage for data sets. The JCL parameters
for SMS-managed (also called system-managed) data sets are different from
some parameters used for non-SMS data sets.
- Determine the information (account number, programmer
name, and so on) your company requires for each job that you submit.
Table 1. JCL worksheet| Company convention or z/OS environment
specifics |
Notes® / Values to code on JCL statements |
|---|
| Job entry subsystem JES2
or
JES3
|
|
| Access methods Queued Sequential (QSAM)
Basic Partitioned (BPAM)
Virtual Sequential (VSAM)
Basic Sequential (BSAM)
Basic Direct (BDAM)
|
|
| Direct-access storage devices (DASD) |
DSN=
UNIT=
VOL=SER=
|
| Magnetic tape devices |
LABEL=
UNIT=
VOL=SER=
|
| Data management system |
| Conventions for SMS-managed data sets |
| |
Average record |
AVGREC= |
| |
Data classes |
DATACLAS= |
| |
Management classes |
MGMTCLAS= |
| |
RACF® profile names |
SECMODEL= |
| |
Storage classes |
STORCLAS= |
| Conventions for non-SMS-managed data
sets |
| |
Data set attributes or requirements |
BLKSIZE |
| |
LRECL= |
| |
RECFM |
| |
SPACE= |
| |
SYSOUT= |
| Conventions for the JOB statement |
| |
Account number |
|
| |
Other accounting information |
|
| |
Programmer name |
|
| |
Class |
CLASS= |
| |
Message class |
MSGCLASS= |
| |
Message level |
MSGLEVEL= |
| |
Region size |
REGION= |
| |
Time limit |
TIME= |
Reusable JCL collection
Copyright IBM Corporation 1990, 2010
