
Running Test Jobs With Production Datasets Using BIM-EPIC's JCL Features
7-64 User Reference
Running Test Jobs With Production Datasets
BIM-EPIC’s test job feature allows you to run test jobs with production datasets without
affecting production processing. Test job names are defined by the TSTJOB configuration
option. The TSTJOB configuration option can include wildcard characters to allow greater
flexibility in creating test job names. A question mark (?) specifies that any character in that
position is a valid character. An asterisk (*) specifies that all characters in that position and
any following are valid.
All versions of controlled datasets created using test jobs are recorded in the DSN Catalog
with a status of "conditionally cataloged". Only such versions can be accessed by subsequent
test job executions. Production jobs will not use the conditionally cataloged versions. These
versions are retained until the following day, when they become eligible for scratch. If you
close a conditionally cataloged version using Online Manager (or TSIDMNT) during that
time, it becomes an active version (version 1), can be accessed by production jobs, and is
maintained according to its EDD retention criteria.
No special entries are required.
To test a single dataset, specify a conditional catalog option on its label:
For... Use...
DLBLs C
TLBLs 32
DD statements DISP=(xxx,CONDCAT)
To test an entire job, specify a valid test job name on the VSE JOB statement.
If TSTJOB=A*, the test job feature is activated by any job name beginning with A.
If TSTJOB=A?AAAA, the test job feature is activated by the job names ABAAAA,
AXAAAA, A1AAAA, and so on.
If TSTJOB=A?A*, the test job feature is activated by the job names ABAAAA, AXA,
ACAXX, and so on.
Description
DSN Catalog
JCL Requirements
Examples
Kommentare zu diesen Handbüchern