DFS0413I INCORRECT LOG DATASET xxxxxxxx - DISCARDED RC=zz
Explanation
The DD statement xxxxxxxx for the log data set was incorrectly specified.
The error was caused by one of the following:
- A DD DUMMY or DSN=NULLFILE was specified.
- The specified secondary log data set is not used, because the log recording mode is single.
- The required primary or secondary partner for OLDS ddname was not specified. The log recording mode is dual, and the online log data sets (OLDS) must be specified in pairs (primary and secondary).
- For a batch program, the DD statement was incorrectly specified.
- For an online program, DUAL log recording mode was requested. The allocation for the primary OLDS was successful, but the allocation for the secondary OLDS failed.
- The attributes were incorrectly specified when the DD name specifies a write-ahead data set (WADS).
The reason code zz can have the following values and meanings:
- Code (Dec)
- Meaning
- 04
- Allocation failed for DDNAME=xxxxxxxx for one of these reasons:
- No DFSMDA member was found, and the DD statement was not found in the JCL stream.
- If message DFS2503W is also received, see DFS2503W for the reason for the allocation failure.
- 08
- OLDS/WADS device was not DASD.
- 12
- DEVTYPE failed for DDNAME=xxxxxxxx.
- 16
- DDNAME=xxxxxxxx was specified as DD DUMMY or DSN=NULLFILE.
- 20
- RDJFCB failed for DDNAME=xxxxxxxx.
- 28
- OBTAIN failed for the data set defined by DDNAME=xxxxxxxx.
- 32
- OLDS block size was not a multiple of 2K.
- 36
- Dual OLDS was specified, and the secondary OLDS block size (DFSOLSnn) was different from the primary OLDS block size (DFSOLPnn).
- 40
- The OLDS block size was less than the largest OLDS block size (DFSOLPnn,DFSOLSnn) successfully allocated.
- 44
- The WADS device type was inconsistent (distinct).
- 48
- The OLDS block size was greater than the track capacity.
- 52
- BUFSTOR=64 was specified on the OLDSDEF statement, but this OLDS was not an extended format data set.
- 56
- The WADS is smaller than 5 tracks.
- 60
- The IMS Logger received a nonzero return code from the DFSMS Media Manager when the logger connected to a WADS by using a CONNECT (OPEN) command. The most common reason for this error is that the WADS is not a VSAM linear data set.
- 64
- The WADS CI size was not 4 KB
- 68
- The DFSMS Media Manager is connected to an invalid write-ahead (WADS) data set. The WADS must be defined as a VSAM linear dataset.
System action
The DD error statement is discarded and system initialization continues. If DUAL is requested and an error exists in an OLDS pair, the OLDS pair is discarded. System initialization continues.
Programmer response
Check the DD statement and correct any errors so that the data set will be available the next time the system is initialized.