DFS0414I CONTINUING WITH ALTERNATE LOG

or

  Explanation

or

PERMANENT I/O ERROR ON ddname -
    DURING LOG zzzz
    xx

  Explanation
   Either form of this message can be issued. The first message indicates that a permanent I/O
    error occurred in the log data set specified by the ddname. The log data set is either an online
    log data set (OLDS), a write-ahead data set (WADS), or a batch system log data set (SLDS). The
    value of zzzz is WRITE or READ.
The second message indicates that the
    system continues with an alternate log data set.
For WRITE errors, xx
    is an invalid DECB post code, which is contained in the first byte of the ECB (ECBCC). No
     xx value with a WRITE error indicates that a log data set CLOSE error
    occurred during EOV processing.
For READ errors, xx is an OSAM error
    return code.
The values and meanings of xx are as follows:

    Code (hex)
Explanation

     01

     DD statement missing.

     02

     Concatenated data set.

     03

     Fewer units than volumes specified for a DASD data set.

     04

     JCL specified a DSORG type not permitted by OSAM.

     05

     DSCB for data set not found.

     06

     First volume DSCB specified a DSORG type not permitted by
      OSAM.

     07

     DCB block size not equal to DSCB block size after JFCB/DCB
      merge.

     08

     DCB LRECL size not equal to DSCB LRECL size after JFCB/DCB
      merge.

     09

     Neither the LRECL nor block size was specified in the DSCB, DCB, or
      JCL.

     0A

     The specified block size is less than LRECL.

     0B

     The specified block size exceeds track size for the specified
      device.

     0C

     A previous OPEN or EOV failed.

     0D

     VIO not supported by OSAM. The data set is allocated to a VIO
      unit.

     0E

     Tape devices are not supported. The data set is allocated to a tape
      device.

     0F

     Some internal error occurred in the OSAM DEB subroutine. DCBWRK1 indicates
      the error code.

     10

     Block size greater than track size.

   If an error is detected by IOS, the message text might also contain
    I/O completion codes. For more information, see the IOSCOD field in z/OS: IOSB mapping.

   If hardware errors occur, see the z/OS® IOS000I message issued before this message.

  System action
   IMS continues
    execution with a spare WADS (DFSWADSn, n=0,1,...9), if one is available. If no
    such WADS exists, IMS continues logging in a degraded mode by truncating log buffers to ensure the
    preservation of Log-Write Ahead Protocols (LWA).
One of the following occurs for the other
    WRITE error cases: 

      OLDS

      IMS continues
       execution if 2 or more OLDS remain. If only one OLDS remains, an internal CHECKPOINT FREEZE
       is performed. If no OLDS remains, IMS abends with abend 0616.

      SLDS

      IMS continues
       execution if dual logging is in effect and an alternate SLDS exists. If an alternate SLDS is
       unavailable, IMS
       abends with abend 0616.

  Operator response
   If the error occurs on an OLDS and dual logging was not being used, or if errors occur on both
    copies of a dual OLDS log, then run the Log Recovery utility to close the OLDS in
    error.
For an invalid DECB post code with no associated hardware error, set a SLIP to
    capture a memory dump at the next message occurrence and contact IBM® Software
			Support.
If an error IOS002A occurred indicating no paths were
    available to the allocating device and CLOSE processing also involving an I/O request is
    started, the CLOSE might still appear hung. Issue V OFFLINE to the UCB.

  Module
DFSFDLS0 