Reason:
File mapping has detected a conflict between the attributes requested for a data set and the actual attributes for the data set. Processing is terminated.
The IDD file entity associated with the map specified attributes different from the attributes detected by file mapping.
If the level 1 error message indicates a SUPPLEMENTARY OPEN, then this is not the first map bound to the file; thus it is already open and the file characteristics have been established, which mandates that all other file mapbinds must bind maps whose file characteristics are in agreement with the established characteristics.
If the level 1 error message indicates a BASE OPEN, then this is the first map to bind to the file, and file mapping has detected a conflict between certain critical file characteristics associated with the map (that is, specifications in the IDD file entity) and the actual data set characteristics.
If the conflicting parameter is RECFM, then the IDD file entity tied to the map contains a RECORDING MODE that is incompatible with the data set record format (SUPPLEMENTARY OPEN only).
If the conflicting parameter is LRECL, then the IDD file entity tied to the map contains a MAXIMUM RECORD SIZE that is not equal to the actual data set logical record length (SUPPLEMENTARY OPEN Only).
If the conflicting parameter is BLKSIZE, then the IDD file entity tied to the map contains a BLOCK SIZE that is not equal to the actual data set block size (SUPPLEMENTARY OPEN only).
If the conflicting parameter is TAPE LABEL, then the IDD file entity tied to the map designates a LABELS option that does not agree with the actual data set labeling (SUPPLEMENTARY OPEN only).
If the conflicting parameter is USAGE, then the IDD file entity FILE-TYPE and the file usage as known to CA ADS Batch (INPUT, OUTPUT, I/O) are incompatible; or the usage requested is not supported by file mapping for this file type (example: Specifying SYSOUT=A on a DD statement and then attempting to use the file name for input purposes) (BASE or SUPPLEMENTARY OPEN).
If the conflicting parameter is DEVICE, then the IDD file entity tied to the map designates a DEVICE-TYPE which is not the actual device type; or the requested device-type is not supported by file mapping (BASE or SUPPLEMENTARY OPEN).
If the conflicting parameter is FILE TYPE, then the IDD file entity tied to the map designates a FILE-TYPE (or VSAM-TYPE) that is not the actual data set organization (BASE OPEN).
Module:
RHDCBCTL
Severity:
0
|
Copyright © 2014 CA.
All rights reserved.
|
|