The LABELS statement specifies if user labels are to be treated
as data by IEBGENER. For a detailed discussion of this option, refer
to Processing User Labels.
The LABELS statement is used when you want to specify that: no
user labels are to be copied to the output data set; user labels are
to be copied to the output data set from records in the data portion
of the SYSIN data set; or user labels are to be copied to the output
data set after they are modified by the user's label processing routines.
If more than one valid LABELS statement is included, all but the last
LABELS statement are ignored.
The syntax of the LABELS statement is:
Label |
Statement |
Parameters |
---|
[label]
|
LABELS
|
[DATA={YES|NO|ALL|
ONLY|INPUT}]
|
where:
- DATA={YES|NO|ALL|ONLY|INPUT}
- specifies if user labels are to be treated as data by IEBGENER.
These values can be coded:
- YES
- specifies that any user labels that are not rejected by a label
processing routine you have specified on the EXITS statement are to
be treated as data. Processing of labels as data ends in compliance
with standard return codes. YES is the default.
- NO
- specifies that user labels are not to be treated as data. In
order to make standard user label (SUL) exits inactive, NO must be
specified when processing input/output data sets with nonstandard
labels (NSL).
- ALL
- specifies that all user labels in the group currently being
processed are to be treated as data. A return code of 16 causes IEBGENER
to complete processing the remainder of the group of user labels and
to stop the job step.
- ONLY
- specifies that only user header labels are to be treated as
data. User header labels are processed as data regardless of any return
code. The job ends upon return from the OPEN routine.
- INPUT
- specifies that user labels for the output data set are supplied
as 80-byte input records in the data portion of SYSIN. The number
of input records that should be treated as user labels must be identified
by a RECORD statement.
LABELS DATA=NO must be specified to make standard user labels (SUL)
exits inactive when input/output data sets with nonstandard labels
(NSL) are to be processed.