IOS291I

or

Explanation
The input/output supervisor (IOS) was unsuccessful
in its attempt to process the configuration data for the specified
device on the channel path identifier xx.
In
the message text: devn
The device number. The device number is prefixed by the subchannel
set identifier when appropriate.
xx
The channel path identifier.
rc
The associated hexadecimal reason code (see below)
textline1
Descriptive text detailing the failure (see below)
textline2
Optional descriptive text detailing the failure (see below)

RC
Textline1
Explanation

10
RCD CCW NOT
FOUND IN SENSE-ID DATA
The Read Configuration
Data (RCD) channel command word (CCW) was not found in the extended
sense ID data.

20
TOKEN NED NOT
FOUND IN CDR DATA
The configuration
data record (CDR) is missing the token node element descriptor (NED).

21
TOKEN NED MISMATCH
HAS BEEN DETECTED
The CDR token
from the specified device does not match the subsystem token.

22
I/O DEV NED
NOT FOUND IN CDR DATA
The CDR is
missing the I/O device NED.

23
REQUESTED UCB
IS NOT VALID
The requested
unit control block (UCB) pointer is not valid.

24
REQUESTED PATH
MASK IS NOT VALID
The requested
path mask is not valid.

25
CONFIGURATION
ERROR - MAXIMUM NUMBER OF NEDS EXCEEDED
The configuration
data limit was exceeded. More than the maximum of 16 NEDs were found.

26
CONFIGURATION
ERROR - MAXIMUM NUMBER OF PATHS EXCEEDED
The configuration
data limit was exceeded. More than the maximum of 8 channel paths
were found.

27
I/O DEV NED
MISMATCH HAS BEEN DETECTED
The CDR I/O
device NED from the specified device does not match the device NED
read from a previous channel path.

28
CONFIGURATION
DATA TABLE HAS NOT BEEN INITIALIZED  
Device self-description
initialization has not occurred.

29
I/O DEV NED
MATCHES AN I/O DEV NED FOR ANOTHER DEVICE 
The CDR I/O
device NED from the specified device already exists for another device.

2A
INVALID CDR
DATA FOR A PAV-BASE
Device number
is defined as a base in the I/O definition file (IODF) but the corresponding
unit address is not defined as a base in the parallel access volume
(PAV) control unit.

2B
INVALID CDR
DATA FOR A PAV-ALIAS
Device number
is defined as an alias in the IODF but the corresponding unit address
is not defined as an alias in the PAV control unit.

2C
A SOFTWARE
PROBLEM HAS OCCURRED
A software
failure has occurred during self-description processing.

2D
S/W OUT OF
SYNC WITH H/W - PAV-ALIAS NOT BOUND CORRECTLY
Device number
is defined as an alias in the IODF but the corresponding unit address
is defined as an alias of a different base in the PAV control unit.

2E
GENERAL NEQ
NOT FOUND IN CDR DATA
The configuration
data record does not end with a general node element qualifier (GNEQ).

2F
PAV-ALIAS CANNOT
BE ADDED BECAUSE ITS PAV-BASE WAS NOT FOUND
The system
could not find a CDR for the base device number associated with this
alias device number.

30
I/O ERROR OCCURRED -or-

An I/O error has occurred during
self-description processing.

I/O ERROR:
CCW=cc IOSTATUS=ddss IOSCOD=xx[-yy] 
An I/O error
has occurred during self-description processing, where:cc
is the OP code of the first CCW in the failing channel program.
ddss
is the device and subchannel status from the IRB
xx
is the IOSCOD field from the IOSB.Note: "-yy"
is displayed when there is an associated IOSCOD reason code.

Note: If the device status indicates a unit check occurred,
then textline2 will contain sense data in the form ssss ....
ssss

31
DEVICE SUPPORT
CODE RETURNED A RETURN CODE THAT WAS NOT VALID
The system
has detected a software error in device support code processing.

32
DEVICE SUPPORT
CODE DETECTED INCORRECT CDR DATA
Device support
code has detected an illegal change to the device dependent section
of the CDR.

or

AUTHENTICATION FAILURE
Device support code has detected
a control unit that has not authenticated itself for the use of parallel
access volumes.

33
DEVICE SUPPORT CODE DETECTED A PHYSICAL
VS. LOGICAL MISMATCH
The device support code has detected
that the physical and logical device characteristics do not match.

34
INCORRECT PATH
ATTRIBUTE RETURNED IN THE CDR DATA
The path attribute
in the CDR is not valid or is not consistent with respect to the other
online paths to the device.

35
REQUESTED PATH
IS QUIESCED BY C.U.I.R.
Requested path
is quiesced by C.U.I.R. processing. 

40
A PROGRAM CHECK
HAS OCCURRED
A program check
occurred.

System action
IOS takes the path offline.  If all the paths
to a device are taken offline, because the configuration data cannot
be read on all the paths, the device is taken offline.

Operator response
If the reason code associated with the message
is 21, 27, or 29, then the probable cause is a cabling error. Verify
that all channel paths are properly connected to match the configuration
defined in the IOCDS/IODF. Refer to the SYMREC in SYS1.LOGREC;  the
SYMREC contains RIDS/IOSCACDR and refers to the configuration error
detected.
For hexadecimal reason code:
Reason Code
Response
21
The reason code for the SYMREC is X'8101'.  The device
token NED and the token NED expected are supplied.
27
The reason code for the SYMREC is X'8107'.  The device
I/O NED and the I/O NED expected are supplied.
29
The reason code for the SYMREC is X'8108'.  The device
token NED and the device UCB that already has the I/O device NED are
supplied.
2A, 2B, 2D
Ensure that the definition of the parallel access volume device
in the IODF matches the definition of the corresponding unit address
in the parallel access volume control unit.
2E
Probable cause is an error in the vital product data for the device.
 Verify that a valid general node-element qualifier (GNEQ) occupies
the last 32-byte field of the configuration data record. For more
information refer to the SYMREC in the logrec recording medium.  The
SYMREC contains RIDS/IOSCACDR and refers to the configuration error
detected.  The reason code for the SYMREC is X'810E'.  The
last 32-byte field of the configuration data record is supplied.
32
For CDR data problems, ensure that the device is offline before
making any configuration changes to the device.
For authentication
failure, check with the IBM® Hardware
Support Center or the OEM vendor Hardware Support Center to determine
if the correct licensed internal code (LIC) supports parallel access
volumes. If the LIC supports PAV, then contact the IBM Software Support Center.

See Common I/O-Device Commands for
the format of the data being returned.
For other reason codes,
contact the IBM Support Center.
Provide the reason code.

Source
Input/output supervisor (IOS)

Module
IOSVSLFD

Routing code
1

Descriptor code
4

RC	Textline1	Explanation
10	RCD CCW NOT FOUND IN SENSE-ID DATA	The Read Configuration Data (RCD) channel command word (CCW) was not found in the extended sense ID data.
20	TOKEN NED NOT FOUND IN CDR DATA	The configuration data record (CDR) is missing the token node element descriptor (NED).
21	TOKEN NED MISMATCH HAS BEEN DETECTED	The CDR token from the specified device does not match the subsystem token.
22	I/O DEV NED NOT FOUND IN CDR DATA	The CDR is missing the I/O device NED.
23	REQUESTED UCB IS NOT VALID	The requested unit control block (UCB) pointer is not valid.
24	REQUESTED PATH MASK IS NOT VALID	The requested path mask is not valid.
25	CONFIGURATION ERROR - MAXIMUM NUMBER OF NEDS EXCEEDED	The configuration data limit was exceeded. More than the maximum of 16 NEDs were found.
26	CONFIGURATION ERROR - MAXIMUM NUMBER OF PATHS EXCEEDED	The configuration data limit was exceeded. More than the maximum of 8 channel paths were found.
27	I/O DEV NED MISMATCH HAS BEEN DETECTED	The CDR I/O device NED from the specified device does not match the device NED read from a previous channel path.
28	CONFIGURATION DATA TABLE HAS NOT BEEN INITIALIZED	Device self-description initialization has not occurred.
29	I/O DEV NED MATCHES AN I/O DEV NED FOR ANOTHER DEVICE	The CDR I/O device NED from the specified device already exists for another device.
2A	INVALID CDR DATA FOR A PAV-BASE	Device number is defined as a base in the I/O definition file (IODF) but the corresponding unit address is not defined as a base in the parallel access volume (PAV) control unit.
2B	INVALID CDR DATA FOR A PAV-ALIAS	Device number is defined as an alias in the IODF but the corresponding unit address is not defined as an alias in the PAV control unit.
2C	A SOFTWARE PROBLEM HAS OCCURRED	A software failure has occurred during self-description processing.
2D	S/W OUT OF SYNC WITH H/W - PAV-ALIAS NOT BOUND CORRECTLY	Device number is defined as an alias in the IODF but the corresponding unit address is defined as an alias of a different base in the PAV control unit.
2E	GENERAL NEQ NOT FOUND IN CDR DATA	The configuration data record does not end with a general node element qualifier (GNEQ).
2F	PAV-ALIAS CANNOT BE ADDED BECAUSE ITS PAV-BASE WAS NOT FOUND	The system could not find a CDR for the base device number associated with this alias device number.
30	I/O ERROR OCCURRED -or-	An I/O error has occurred during self-description processing.
	I/O ERROR: CCW=`cc` IOSTATUS=`ddss` IOSCOD=`xx`[`-yy`]	An I/O error has occurred during self-description processing, where: `cc` is the OP code of the first CCW in the failing channel program. `ddss` is the device and subchannel status from the IRB `xx` is the IOSCOD field from the IOSB. Note: "`-yy`" is displayed when there is an associated IOSCOD reason code. Note: If the device status indicates a unit check occurred, then textline2 will contain sense data in the form `ssss .... ssss`
31	DEVICE SUPPORT CODE RETURNED A RETURN CODE THAT WAS NOT VALID	The system has detected a software error in device support code processing.
32	DEVICE SUPPORT CODE DETECTED INCORRECT CDR DATA	Device support code has detected an illegal change to the device dependent section of the CDR.
	or
	AUTHENTICATION FAILURE	Device support code has detected a control unit that has not authenticated itself for the use of parallel access volumes.
33	DEVICE SUPPORT CODE DETECTED A PHYSICAL VS. LOGICAL MISMATCH	The device support code has detected that the physical and logical device characteristics do not match.
34	INCORRECT PATH ATTRIBUTE RETURNED IN THE CDR DATA	The path attribute in the CDR is not valid or is not consistent with respect to the other online paths to the device.
35	REQUESTED PATH IS QUIESCED BY C.U.I.R.	Requested path is quiesced by C.U.I.R. processing.
40	A PROGRAM CHECK HAS OCCURRED	A program check occurred.