You can create
an output data set from the batched repository-update facility to
hold the CREATE statements produced from DUMP commands.
This data set is in the correct format for re-input to the batched
repository-update facility without further editing; that is, it does
not contain heading lines and the data is aligned in the correct columns.
Note, however, that you may still need to edit this output data to
modify the context, group names, version numbers, and so on.
When you use the DUMP command (see
Creating and maintaining CICSPlex SM definitions),
you may use the OUTPUT command to request that any resulting CREATE
commands are written to an output data set, in addition to the normal
report. The OUTPUT command must be the first command in the BATCHREP
input data stream, to ensure that the command precedes any DUMP commands.
You cannot specify more than one OUTPUT command.
Note: If a partitioned
data set is used as the output data set, you must ensure that the
data set has enough space to handle the output. A full partitioned
data set without sufficient directory space may cause multiple abends
resulting in the termination of the CMAS. To avoid multiple abends
during CICS recovery, direct output to a sequential data set. If required,
you can then copy the sequential data set output to a partitioned
data set.
The format of the OUTPUT command
is:
OUTPUT DATASET DSNAME(data.set.name(member)) INQUOTES(NO|YES);
where:
- DATASET
- This keyword must be specified.
- DSNAME
- Specifies a data set name. You must specify a data set name and
the data set must exist. The output data set cannot be the same as
the input data set. The data set must consist of fixed-length, 80-byte
records; the records may be blocked and any block size is acceptable.
- data.set.name
- The data set name must not exceed 44 characters in length. Each
component of the name cannot be more than 8 characters long, and the
components must be separated by full stops. The data set name must
be a fully-qualified data set name. The first component of the data
set name does not default to the logged-on user id.
- member
- The member name, if the output data set is partitioned. The member
name cannot be more than 8 characters long. The member name must be
omitted if the output data set is not partitioned.
- INQUOTES(NO|YES)
- Identifies whether or not you want field values enclosed in quotes
on the output data set. You may need to use this control statement
if you have any data on your data repository that contains unbalanced
parentheses. If you omit this keyword, the default value of NO is
assumed.
- NO
- The values of parameters are not enclosed in quotes on the output
data set. This setting is perfectly adequate for input to the batched
repository-update facility, but you might encounter problems if the
parameter values contain unbalanced parentheses.
Note that, if
you specify INQUOTES(NO), the BATCHREP output can be used as input
to any release of the CICSPlex SM batched repository-update facility.
- YES
- All values of parameters are enclosed in quotes on the output
data set. The CICSPlex SM batched repository-update facility terminates
the parameter value at the final quote, not at an embedded parenthesis.
For example, suppose a DESCRIPTION field contains
the value:
1) Describe Resource
If
you specify INQUOTES(NO), which is the default, the DUMP routine will
produce the following statement in the output data set:
DESCRIPTION(1) Describe Resource)
The
CICSPlex SM batched repository-update facility interprets this as
a DESCRIPTION field containing the value 1, followed by two unrecognizable
keywords.
If you specify INQUOTES(YES), the DUMP routine places
quotes around the field value. The output data set would contain the
statement:
DESCRIPTION('1) Describe Resource')
This
statement is interpreted correctly by the CICSPlex SM batched repository-update
facility.
Last updated: Thursday, 27 June 2019