CA Dynam for VSE User Guide

Managing Special Files
Running Tests with Production JCL
You do not have to catalog new versions of output data sets when running
tests with production JCL. The programmer test option enables you to define a
$TEST jobname in the following ways:
• In the DYNAM/T option record, you can define test jobs by specifying an
identifying character string and its starting position within the jobname.
For example, if the DYNAM/T option record specifies:
TESTJOB($$$,6)
then the following job names will be considered test jobs:
PRODT$$$
PAYRL$$$
but not $$$PRODT
but not PAY$$$
• If no user-defined name is specified in the DYNAM/T option record,
CA Dynam/T defaults to the string $TEST at position 1 of the jobname.
• When you run a test job, CA Dynam/T does not update the Catalog file at
CLOSE for output data sets. Otherwise, the system functions as usual. All
input files are selected through AVR; output scratch tapes are allocated.
Examples:
DYNAM/T option record
Valid test job JCL statement
TESTJOB(TJOB,3)
// JOB PRTJOB
// JOB ARTJOB1
(default)
// JOB $TESTPR
// JOB $TESTAR1
Cataloging Output Tapes
Output tapes do not become new versions of the data sets. They are cataloged
as TEST status tapes and are retained until the next DYNCAT SCRATCH
command is run, returning them to SCRATCH status. They will not be called
for as input to production runs. If you request their data set name as input
during a subsequent step of a $TEST job, CA Dynam/T calls the most current
$TEST version as though it were a member of the data set.
You can fully test JCL for jobs that create a file in one step, and then read the
newly created file in a later step. If you request a data set on input which
contains no test versions, CA Dynam/T inputs the appropriate production
version.
Chapter 2: Maintaining Tape Files 2–53