0B1

Explanation
System initialization cannot continue because of
a problem in the LOADxx member, the I/O definition
file (IODF) data set, or a device.
The right-most four bytes
of the program status word (PSW) have the following format: xrr00www
 where: x
Irrelevant information.
rr
A hexadecimal reason code indicating the reason for the failure.
www
The wait state code.

The reason code (rr) is one
of the following: 01
The required data set was not found.
02
The IODF occupies more than one extent.
03
A required device is not defined.
04
MSCH instruction failed for a required device.
05
The IODF is not valid for an IPL.
06
The configuration ID specified in the LOADxx member does not match
any I/O configuration contained in the IODF.
07
The LOADxx member contains blanks as the configuration ID. If
there is only one I/O configuration defined in the IODF, then the
system ignores the blanks and uses the I/O configuration. In this
case, the IODF contains multiple definitions and the system requires
that you specify a valid configuration ID in the LOADxx member.
08
The IODF suffix is not valid.
09
The IODF data set name high level qualifier is not valid.
0A
The IODF is not valid for an IPL.  It must be a VSAM data set.

Note: This wait state can also occur because of
an invalid IODF statement. In addition to incorrect data entries this
wait state can also be caused by incorrect keyword filtering using
the HWNAME, LPAR NAME, and VMUSERID keywords.

System action
The system enters nonrestartable wait state X'0B1'.
The system issues the following messages with the following wait state
reason codes: Code
Accompanying Message
01
IEA513W.
02
IEA514W.
03
IEA515W, to display the device number.
04
IEA516W, to display the device number.
05
IEA517W.
06
IEA518W.
07
None.
08
IEA512W.
09
None.

Operator response
Notify the system programmer.

System programmer response
Depending on the hexadecimal reason
code, one of the following: Code
Action
01
Verify that the correct device number was specified on the LOAD
parameter. Enter the correct IODF data set name in the LOADxx member.
02
Ensure that the IODF data set is allocated as a single extent
data set.
03
Verify that the device specified on the LOAD parameter is defined
to the channel subsystem. (There is no device with the proper subchannel
identifier.) Verify that the correct device number was specified on
the LOAD parameter. Verify that the hardware configuration matches
the definitions in the IODF.
04
Move any of the following data sets (that are on the device specified
on the LOAD parameter) to a different device: IODF
SYS1.PARMLIB
SYSn.IPLPARM

05
Change the LOADxx member to specify another IODF. Be sure to specify
the name of a production-IODF (instead of work-IODF).
06
Change the LOADxx member to specify the correct IODF or to specify
the correct operating system configuration ID.
07
Specify the correct operating system configuration identifier.
08
Verify that the IODF data set name suffix specified in the LOADxx
member is a valid hexadecimal number X'00' through X'FF'.
Enter the correct IODF data set name in the LOADxx member.

In each case, ask the operator to reIPL the
system.

Problem determination
If the problem persists, search problem
reporting data bases for a fix for the problem. Provide the following
search argument: WS/D0B1: Wait state code
PRCS/00000rrr: Reason code
MS/IEAnnnW: Message identifier

 If no fix exists, ask the operator to obtain the stand-alone
dump. Contact the IBM® Support
Center. Provide the stand-alone dump, the accompanying message, and
the reason code.

Source
Input/output supervisor (IOS)