RCCI-018

(This message contains a formatted block of text. See the
message explanation for the message text.)
Writing data into a data set that is out of space
has resulted in an E37 error code. This message contains a data set
allocation report that you can use to determine which data set is
out of space. The report includes a header section followed by a table
that indicates the DD names that might have generated the E37 error.                           BCL Allocation Report
Stepname: stepName
Pgmname : programName
PARM    : dataSetAllocationCharacteristics

DDNAME      Disposition                              Data Set Name
--------  -------------------  --------------------------------------------

Stepname
The step name containing the DD statement that generated the E37
error.

Pgmname
The program name executed in the Stepname.

PARM
The parameter list used for the program name, if any.

DDNAME
The DD name that might have generated the E37 error.

Disposition
The disposition information for the DD name. The value of Disposition is
a three-part, comma-separated string that reports status, normal disposition,
and abnormal disposition. An example is 'NEW,DELETE,DELETE'
in which NEW is the status, DELETE is the normal disposition, and
DELETE is the abnormal disposition. If one of these values is not
defined, such as abnormal disposition, for example, the disposition
is displayed as 'NEW,DELETE, '. The following are possible
values for status, normal disposition, and abnormal disposition:

Status
SHR, NEW, OLD, and MOD

Normal disposition
DELETE, CATLG, UNCATLG, KEEP, and PASS

Abnormal disposition
DELETE, CATLG, UNCATLG, and KEEP

Data Set Name
If there is a DSN or DSNAME defined for one DD, there is a data
set name for that DD in the report. Otherwise, no data set name for
that DD is reported.
Processing of the BCL statements stops.
Using information in the BCL Allocation Report, compress
or reallocate the data set with more space and resubmit the BCL.