0B0

Explanation
The system could not recognize the I/O definition
file (IODF) specified in the LOADxx parmlib member.
Note: If
equals ('==') was specified as the IODF suffix in the LOADxx parmlib
member, MVS™ uses the IODF suffix
obtained from the hardware token in the Hardware System Area (HSA).
If equals ('========') was specified as the IODF high-level qualifier
in the LOADxx parmlib member, MVS uses the high-level qualifier obtained from
the hardware token in the HSA. If the characters 'IODF' are not found,
or the IODF suffix is not X'00' to X'FF', MVS will load wait state X'0B1' reason
code X'00B'. MVS uses
the same rules for determining its ability to use the IODF name explicitly
specified in LOADxx.
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 input/output supervisor (IOS) section of the IODF is not compatible
with the system code.
02
The allocation section of the IODF is not valid. The most likely
reason for this is that the IODF was created by a system with a higher
release level than the system that is attempting to use the IODF.

System action
The system enters nonrestartable wait state X'0B0'.

System programmer response
If the correct IODF is being used,
it is likely that a recent release of the operating system has converted
the IODF to a format not supported by the current release and service
level. Search RETAIN® for
an appropriate compatibility PTF to bring this system up to the required
service level.
If the correct IODF is not being used, enter
the correct IODF data set name in the LOADxx PARMLIB
member. Ask the operator to REIPL the system.

Source
Input/output supervisor (IOS)