IEE459I (form 1 of 3)

After the above message, a heading appears:

Explanation
After the above message, a heading appears: 
UNIT DTYPE M CNT VOLSER CHPID=PATH STATUS
Then
one or more of the following lines appear:
sdddd uuuuxm
ccc vvvvvv chpid=s [...]
sdddd uuuuxm ccc vvvvvv device status
message
Another heading might also appear: 
SSID
CFW TC DFW PIN DC-STATE CCA DDC CYL CU-TYPE
Followed by one
or more of:
ssss i cc. ff. p wwwwwwwww xx yy zzzz tttt-tt
Then
a processing message might appear:
Processing message
Followed
by symbol definitions: 
symbol1symbol2
symbol n-1symbol
n
A cache heading might also appear: 
RTYPE SSID
CFW TC DFW PIN DC-STATE CCA DDC CYL CU-TYPE
Followed by one
or more of:
rrrrm ssss i cc. ff. p wwwwwwwww xx yy zzzzzzzzz
tttt-tt
For fenced information:
FENCED YYYYYYYYYY
XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX
Followed by:

                zzzzzzzz zzzzzzzz
In response to a DEVSERV PATHS
command, this message displays the following requested information: hh.mm.ss
The time in hours, minutes, and seconds.
UNIT DTYPE M CNT VOLSER CHPID=PATH STATUS
These are the column headings for the information displayed in
the message.
sdddd
The device number consists of s representing the subchannel
set number and dddd representing device number. When DEVSERV
PATHS is specified with a 5-digit device number, the device number dddd is
physically configured to the subchannel set s. When DEVSERV
PATHS is specified with a 3 or 4 digits device number, the displayed
device number sdddd represents the device that is in the
active subchannel set s.
uuuux
uuuu is the device type indicated by the UCBTYP
field. x is a modifier for a specific feature or
model. This field may contain one of the following: 3480S
Indicates 3480 with automatic cartridge loader.
3480X
Indicates 3480 with the compaction feature.

 If the DEVSERV command does not support this device
then one of the following generic types applies: CHRDR
Character reader.
CTC
Channel-to-channel adapter.
FBA
Fixed Block Architecture device (3370).
GRAPH
Display device.
TP
Communication device.
UR
Unit record device.
?dcut
This is an unknown device, where dcut is the
hexadecimal device class and unit type from the UCB.

m
This is the logical mode of the device, and may be one of the
following: A
The device is allocated.  See the use count.
F
The device is logically offline to MVS™.
M
The device has mount pending.
O
The device is logically online to MVS.
P
The device is pending offline to MVS.
N
The device is not allocatable; a system component has control.

ccc
The number of data sets allocated on the volume from the UCBDMCT
field.
vvvvvv
The volume serial label from the UCBVOL1 field.
chpid
The channel path id.
s
This indicates the status of the path, which may be one of the
following: +
The path is logically and physically available and I/O on the
path was successful.
*
The path is physically, but not logically available. The subchannel's
logical path indicator is off but I/O to the path is successful. You
can use the command VARY PATH(ddd,nn),ONLINE to make channel path nn logically
available to device ddd.
-
The path is neither logically nor physically available. The subchannel's
logical and physical indicators are both off for this channel path.
You can use the command CONFIG CHP(nn),ONLINE to make the channel
path logically available to all devices connected to the channel.
&
The device is reserved to another path. This indicator applies
to devices with the dynamic pathing selection feature. The cache
status line might not be displayed.
<
The path is installed but not physically available. The start
subchannel request received a condition code of 3.
>
The device microcode has detected an error and will not allow
I/O to complete on the path.
B
The path is unable to communicate. The device indicates that a
busy or reserve condition exists on the path.
C
A controller error occurred while accessing the device.
D
A device error occurred while accessing the device.
I
Intervention is required; the device is not ready.
R
The path is available and the device is reserved to this path/group.
This only applies to devices with the dynamic pathing feature.
T
A time out has occurred; there is no response from the device.
The cause of the time out is undetermined and this condition is transient.
U
A storage control unit or storage director error occurred while
accessing the device.
X
IOSB for the request had abnormal I/O completion
code (IOSCOD) value X'zz'.).

SSID CFW TC DFW PIN DC-STATE CCA DDC CYL CU-TYPE
This heading appears in the display only if a device attached
to a caching subsystem is included in the DEVSERV command. The information
appearing in each column is: rrrrm
The real (true) device type of the device specified in the DEVSERV
command when DTYPE represents the emulated device type.
ssss
The subsystem identifier for this storage subsystem in hexadecimal.
i
The status of cache fast write, which is one of the following: Y
Cache fast write is active.
N
Cache fast write is inactive.
S
Cache fast write is suspended because of pinned data.

cc
The first character is one of four possible values: Y
Volume is eligible for track caching.
N
Volume is ineligible for track caching.
P
Track caching is pending inactive, de-stage is in progress for
this volume.
F
Track caching is pending inactive, de-stage has failed for this
volume.

 The second character is one of seven possible values: Y
Track caching is active for the subsystem.
N
Track caching is inactive for the subsystem.
A
Track caching is pending active for the subsystem.
T
Track caching is ended because of an error.
M
Track caching is disabled for maintenance.
P
Track caching is pending inactive, de-stage is in progress.
F
Track caching is pending inactive, de-stage has failed.
S
Subsystem is running in single cluster mode with active cache.

 The third character is a period.  Caching does
not occur unless both the first and second characters are Y.

ff
The first character is one of five possible values: Y
Volume is eligible for DASD fast-write.
N
Volume is ineligible for DASD fast-write.
I
DASD fast-write is inhibited, de-stage is in progress for this
volume.
U
Volume has data in failed non-volatile storage.
S
DASD fast-write suspended for pinned data for this volume.

 The second character is one of seven possible values: Y
Subsystem non-volatile storage is active.
N
Subsystem non-volatile storage is inactive.
P
Subsystem non-volatile storage is pending inactive for the subsystem,
de-stage is in progress.
F
Subsystem non-volatile storage is pending inactive for the subsystem,
de-stage has failed.
U
Subsystem non-volatile storage has failed.
I
Subsystem non-volatile storage battery is defective.
M
Subsystem non-volatile storage is disabled for maintenance.

 The third character is a period. DASD fast-write
does not occur unless both the first and second characters are Y.

p
This field will contain one of three possible values: N
Volume does not have pinned data in cache or non-volatile storage.
Y
Volume has pinned data in cache or non-volatile storage, DASD
fast-write and cache fast-write are permitted.
S
Volume has pinned data in cache or non-volatile storage, DASD
fast-write and cache fast-write are suspended.

wwwwwwwww
This reflects dual copy status, SPARE status or PPRC of volume; the status can be one of the
following: SIMPLEX: the volume has no dual copy association
PRI-PNDG: establishment of a duplex pair is in progress; this will be the primary of the
pair
SEC-PNDG: establishment of a duplex pair is in progress; this will be the secondary of the
pair
PRI-SDPL: primary of a suspended duplex pair; the control unit will make the operational device
the primary, and the non-operational device, the secondary
SEC-SDPL: secondary of a suspended duplex pair; the control unit will make the operational
device the primary, and the non-operational device, the secondary
PRI-SSEC: duplex pair is in a suspended state, device was originally the secondary and is now
the primary. The operational volume of a suspended duplex pair will always be the primary, while the
non-operational device will always be the secondary.
SEC-SPRI: duplex pair is in a suspended state, device was originally the primary and is now the
secondary. The operational volume of a suspended duplex pair will always be the primary, while the
non-operational device will always be the secondary.
SPARE: the device is a SPARE volume.
SPAR-PNDG: the device is in SPARE PENDING status.
SPAR-BRKN: the device is in SPARE BROKEN status.
PPRIMARY : the device is a PPRC PRIMARY volume.
PPRI-PNDG: establishment of PPRC pair is in progress; this will be the PPRC primary volume.
PPRI-FAIL: the device is in PPRC PRIMARY FAIL status.
PPRI-SUSP: primary of a suspended PPRC pair.
PSECONDRY: the device is a PPRC SECONDARY volume.
PSEC-PNDG: establishment of PPRC pair is in progress; this will be the PPRC secondary
volume.
PSEC-FAIL: the device is in PPRC SECONDARY FAIL status.
PSEC-SUSP: secondary of suspended PPRC pair.
MT-DnPnSn, where Dn
shows the number of full-duplex relations, Pn shows the number of pending
relations, and Sn shows the number of suspended relations.

xx
Two hexadecimal digits that are the channel connection address.
yy
Two hexadecimal digits that are the director-to-device connection
address.
zzzzzzzzz
When this column is prefixed with "ALT", the number after "ALT"
reflects the device number of the other device of an established or
pending dual copy pair. For primary entry, this identifies the secondary
device. For secondary entry, this identifies the primary device. For
simplex volumes and control units that don't support Dual Copy, this
column shows number of cylinders in this device.
tttt-tt
This provides the control unit type to which the device is attached.

device-status-message
The device status message may be one of the following: DEVICE CLASS/TYPE NOT SUPPORTED BY DEVSERV COMMAND
The device must be a tape drive or DASD.
DEVICE UNAVAILABLE, SCP ROUTINE IN CONTROL
The control program is using the device. The system may be attempting
recovery.
SUBCHANNEL ERROR, PATH STATUS UNAVAILABLE
Information from the SCHIB is not available. There may be a problem
with the processor.
UCB NOT CONNECTED, PATH STATUS UNAVAILABLE
The unit control block does not contain a subchannel number. The
path may need to be varied offline.
DEVICE BOXED, PATH STATUS UNAVAILABLE
IOS has forced the device offline.
** FENCED {STORAGE PATH|CHANNEL|DEVICE} xxxxxxxx xxxxxxxx xxxxxxxx
xxxxxxxx
The storage control subsystem has ‘fenced’ one or
more of the four storage paths (0, 1, 2, and 3). ‘Fenced’
means that the indicated path to the device will not be used; alternate
path(s) to the device will be used. For a 2107 control
unit, 'Fenced' indicates that the device specified is in a soft fenced
state.  When the device is in a soft fenced state, commands that read
and write data to the volume are not allowed.  The soft fenced state
remains across an IML until it is explicitly reset.  The resetting
of the soft fenced state can be done by issuing a host command or
a user interface command. Use the ICKDSF CONTROL command with the
CLEARFENCE parameter to clear the soft fence state. For more information,
see Device Support Facilities (ICKDSF) User's Guide and Reference.
The
degree of fencing is indicated by: STORAGE PATH
A storage path is unavailable to all devices.
CHANNEL
A storage path is unavailable to all devices from one or more
channel interfaces; some channel interfaces will continue to use the
storage path.
DEVICE
A storage path is unavailable to the indicated device.

 xxxxxxxx represents the
four hexadecimal bytes of storage path status for each path. 

processing message
The following processing information may be contained in the message: ** NO DEVICES MEET SELECTION CRITERIA **
No devices at or higher than the address you specified met your
online/offline requirements.
** NO OTHER DEVICES MEET SELECTION CRITERIA **
An insufficient number of devices at or higher than the address
you specified met your online/offline requirements.

symbol1 ... symboln
The meaning of the symbols used in a given display.
XXXXXXXX
The first 16 bytes of storage path status.
zzzzzzzz
The last 8 bytes returned from read subsystem status.

Notes: The DISPLAY MATRIX command output may not always agree with DEVSERV's
display. DEVSERV's path status is based on the results of real I/O.
Due to transient conditions in the system, repetitive issuing
of the DEVSERV command may yield different results.
With JES3, a device can be online to JES3, but offline to the MVS system
on which the DEVSERV command was issued.

Operator response
If the device status indicates that the storage
control subsystem has fenced one or more storage paths, contact your
service representative to fix the condition that caused the fencing.
If the device has been fenced, refer to the z/OS DFSMSdfp Storage Administration for
an explanation of the CONTROL command needed to unfence the device.
Otherwise,
follow your installation's procedures for the status which is indicated
in the message display. Recovery actions are contingent upon the following:
hardware and software configurations, system load and job mix. However,
the following are some examples of possible actions: Path Status
Action
<
Check all path switches for correct settings.
&
Check if shared device is in use by another system.
T
Re-enter DEVSERV, and if the condition still exists, end the program
which is tying up the device.

 IEE459I hh.mm.ss DEVSERV
QDASD (id)
After the above message, the system
displays requested DEVSERV DASD information. UNIT VOLSER SCUTYPE DEVTYPE     CYL  SSID SCU-SERIAL DEV-SERIAL EFC
Then, one or more of the following lines appear:
sdddd vvvvvv ccccmmm ddddmmm?  nnnnnnnnn*  ssid mmpp-sssss mmpp-sssss fff
aaaaaaa
bbbbbbb
**** ggg DEVICE(S) MET THE SELECTION CRITERIA
**** iii DEVICE(S) FAILED EXTENDED FUNCTION CHECKING

DASD
device attributes are displayed for each device if the “ATTRIBUTE”
keyword is specified. UNIT VOLSER SCUTYPE DEVTYPE     CYL  SSID SCU-SERIAL DEV-SERIAL EFC
  ATTRIBUTE/FEATURE        YES/NO  ATTRIBUTE/FEATURE      YES/NO
sdddd vvvvvv ccccmmm ddddmmm?  nnnnnnnnn*  ssid mmpp-sssss mmpp-sssss fff
  ttttttttttttttttttttttttttt q      ttttttttttttttttttttttttttt q
aaaaaaa
bbbbbbb
**** ggg DEVICE(S) MET THE SELECTION CRITERIA
**** iii DEVICE(S) FAILED EXTENDED FUNCTION CHECKING

QUERY HOST ACCESS TO VOLUME attributes are displayed for
each device if the “QHA” keyword is specified. UNIT VOLSER SCUTYPE DEVTYPE     CYL  SSID SCU-SERIAL DEV-SERIAL
  QUERY HOST ACCESS TO VOLUME
   PATH-GROUP-ID           FL STATUS  SYSPLEX   MAX-CYLS
sdddd vvvvvv ccccmmm ddddmmm?  nnnnnnnnn*  ssid mmpp-sssss mmpp-sssss fff
  ttttttttttttttttttttttttttt q      ttttttttttttttttttttttttttt q
aaaaaaa
bbbbbbb
**** pgi PATH GROUP ID(S) MET THE SELECTION CRITERIA
**** ggg DEVICE(S) MET THE SELECTION CRITERIA
**** iii DEVICE(S) FAILED EXTENDED FUNCTION CHECKING

Note: aaaaaaaa and bbbbbbbb are
optional display as requested in the DS QDASD command. A brief explanation
of the command syntax is displayed by typing DS QD,?. For a complete
explanation of the command syntax, see z/OS MVS System Commands. 
 sdddd
The device number consists of s representing the subchannel
set number and dddd representing device number.The device dddd is
in the active subchannel set:When 3- or 4-digit device number is specified without MACH, SSID
nor TYPE unit selection parameter.
When VOL unit selection parameter is specified. For PPRC devices,
this is the "primary" device, including failover scenarios.

The device dddd is physically configured to subchannel
set s:When a 5-digit device number is specified for the device selection.
When MACH, SSID or TYPE unit selection parameter is specified.

This allows DEVSERV commands to a PPRC secondary devices, including
when these are configured in alternate subchannel sets.

vvvvvv
volume serial number. A volume serial number of
'--RSV1' indicates that the volume is in a reserved state and cannot
be brought online. A volume serial number
of '---FBA' indicates that the volume is Fixed Block Architecture
(FBA).A volume serial number, if available, is
displayed for offline CKD volumes when the parameter OFFLINE is specified.
When the OFFLINE parameter is not specified or the volume has not
been initialized, '------' is displayed for offline volumes.
ccccmmm
control unit type and model
ddddmmm
device type and model, where a ? after ddddmmm indicates
the defined device type is incompatible with the real device type
nnnnnnnnn
number of cylinders, where an * after nnnnnnnnn indicates
a VM mini-disk
ssid
subsystem identifier
mmpp-sssss
control unit or device serial number
fff
Result of a status validation, where a ? after fff indicates
the device failed the extended function consistency checking. fff represents:*OK
Host view is consistent with subsystem view of control unit and
device function status.
ASC
Asynchronous Commit status is inconsistent.
BYP
The EF consistency check was bypassed, no MVS storage
resident status was found. Device is offline, or it is a VM mini-disk,
or it does not support extended functions.
CCA
Channel Connection Address is incorrect.
CUC
Subsystem cache status is inconsistent.
DC
Dual Copy status is invalid.
DCA
Dual Copy Alternate Channel Connection address is invalid.
DDC
Director to Device Connection address is incorrect.
DFW
DASD Fast Write Status is inconsistent.
DST
Destage pending status is inconsistent.
DVC
Device Caching  status is inconsistent.
FNV
Status of data in failed NVS is inconsistent.
NVS
NVS status is inconsistent.
PIN
Pinned Data status in invalid.
RDF
Feature table is inconsistent with control unit.
REB
Volume is part of a RAID Rank that is undergoing RAID rebuild.
SOF
Device is in a soft fenced state (2107 control unit).
SPA
SPARE volume status is inconsistent between the software control
blocks and devices which supports SPARING.
SSI
Device has inconsistent SSID.
UCB
UCB to device relationship inconsistent.

ATTRIBUTE/FEATURE
SOLID STATE DRIVES
The device is a solid state device if q is y.
ENCRYPTION
The device is a encrypted device if q is y.

aaaaaaaa
requested dump description: UCB AT Vxxxxxxxx
UCB contents at location xxxxxxxx in storage
UCB PREFIX AT Vxxxxxxxx
UCB PREFIX contents at location xxxxxxxx in
storage
UCB COMMON EXTENSION AT Vxxxxxxxx
UCB COMMON EXTENSION contents at location xxxxxxxx in
storage
SSSCB AT Vxxxxxxxx
Storage subsystem status control block contents at location xxxxxxxx in
storage
SSSCB DEVICE TABLE HEADER ENTRY AT Vxxxxxxxxx
The device header entry contents of the SSSCB at location Vxxxxxxxx in
storage
SSSCB DEVICE ENTRY AT Vxxxxxxxx
The device entry contents of the SSSCB at location xxxxxxxx in
storage
FEATURE CODES AT Vxxxxxxxx
The feature code table is at location xxxxxxxx in storage
DPCT AT Vxxxxxxxx
address of Device Performance Capabilities Table at location xxxxxxxx in
storage
READ DEVICE CHARACTERISTIC
data returned from read device characteristic ccw
READ CONFIGURATION DATA
data returned from read configuration data ccw
SENSE SUBSYSTEM STATUS
data returned from sense subsystem status ccw

bbbbbbbb
requested dump details in HEX digits
pgi
The path group ID or IDs that met the selection criteria.
ggg
The number of unit addresses encountered which meet selection
criteria
iii
The number of unit addresses encountered which MVS storage
resident status information was inconsistent with that of the physical
device.
PATH-GROUP-ID
The path group ID. The device is grouped or un-grouped to the
path group ID. An asterisk '*' next to the PATH-GROUP-ID indicates
the system that the I/O request is issued from.
FL
The path status flags byte.Bit
Description

0-1
Grouped state:00
Device is not grouped to any path in the path group.
01
Device is grouped to one or more paths in the path group.
10-11
Reserved.

2
If set to '1', device is reserved to this path
group.

3
If set to '0', device is in single path mode.
If set to '1', device is in multi-path mode.

4-7
Not used.

STATUS
The path status as in path status flags byte.ON
ONLINE
OFF
OFFLINE
ON-RSV
ONLINE and RESERVED
OFF-RSV
OFFLINE and RESERVED

SYSPLEX
The sysplex name that the path group ID is associated with.
MAX-CYLS
The maximum number of cylinders per volume supported by the host.

The following text might appear within the
display associated with a specific unit number:
-INFORMATION UNAVAILABLE-
The device does not support Self Description commands or there
is no physical device accessible through the indicated device number
NO VALID SSSCB EXIST FOR DEVICE
The device has not been initialized by MVS.
 NO DEVICE TABLE EXISTS FOR THIS SSSCB
If there isn't a device    table then there won't be any entries
for this device either.
  NO DEVICE TABLE ENTRY EXISTS FOR THIS DEVICE
The device has a    SSSCB and table information but does not have
an entry in the    table.

The following text might appear with the detailed
unit information when a unit address is encountered for which no information
is available. ****  UNLISTED DEVICE(S) AND

 REASON CODES:

     sdddd(rc) sdddd(rc)... ... ...

where: sdddd
The device number the system is displaying. ‘s’ indicates
the requested subchannel set with ‘s’ defaulting to 0. ‘dddd’
is a 3 or 4 digit device number. If the a subchannel set number is
not 0 and the device number is 3 digits, the 3 digits device number
must be preceded by a 0, for example, 10800.
rc
reason code why no information is presented, where: 01
device not configured, UCB not found
02
UCB not connected to a physical drive
03
device unavailable - system routine in control
04
subchannel error detected
05
device boxed
06
UCB not defined as DASD device
07
I/O error accessing the device
08
UCB not connected to a DASD device
09
internal error, DSE-1 CCW build failed
0A
Features validation failed
0B
CHPID value not valid for device

The following text might appear indicating
the results of the DS QD command execution:
****  TYPE=tttt IS AN INVALID UCB TYPE
TYPE= and DEFINED were both specified, and no DASD units of the
type tttt were found.
****  hhh DEVICE(S) WITH INCONSISTENT UCB TYPE
DEFINED
hhh is the number of unit addresses encountered
for which the defined device type is inconsistent with the connected
physical device

IEE459I hh.mm.ss DEVSERV QTAPE
(id)
There are two formats for DEVSERV TAPE
information. When DEVSERV QTAPE is issued without the MED option
the following DEVSERV TAPE information is displayed after the above
message:
First, a header appears:
UNIT DTYPE DTATUS CUTYPE      DEVTYPE    CU-SERIAL   DEV-SERIAL
ACL LIBID

Then, one or more of the following lines appear:
uuuu ddddd tttttttttt ddddmmm   ddddmmm?* mmpp-sssss mmpp-sssss
acl   lllll     aaaaaaa     bbbbbbb  **** ggg DEVICE(S)
MET THE SELECTION CRITERIA  **** iii  DEVICE(S)
FAILED EXTENDED FUNCTION CHECKING

Note: aaaaaaaa and bbbbbbbb are
optional display as requested in the DS QTAPE command. A brief explanation
of the command syntax is displayed by typing DS QT,?. For a complete
explanation of the command syntax, see z/OS MVS System Commands. 
where: uuuu
external device ID (unit number)
ddddd
device type, same as DTYPE in DS P command
ttttttt
device status indication, where: ON
online
OFFLINE
offline
RDY
ready
NRY
not ready

cccmmm
control unit type and model
ddddmmm
device type and models, where: ? after ddddmmm indicates the defined (UCB)
device is incompatible with the real device type
* after ddddmmm indicates the emulated device
type

Note: For the TS7720 disk-only Virtualization Engine, this field
contains all zeroes.

mmpp-ssss
control unit or device serial number
acl
automatic cartridge loader facility status, where: I
installed; the ACL field shows I for the 3490E models C1A and
C2A even though the device does not have automatic cartridge loader
installed.
A
active
(blank)
otherwise

lllll
library attachment facility identification, for library devices
only
aaaaaaaa
requested dump description: UCB AT Vxxxxxxxx
UCB contents at location xxxxxxxx in storage
UCB PREFIX AT Vxxxxxxxx
UCB PREFIX contents at location xxxxxxxx in
storage
UCB COMMON EXTENSION AT Vxxxxxxxx
UCB COMMON EXTENSION contents at location xxxxxxxx in
storage
READ DEVICE CHARACTERISTIC
data returned from read device characteristic ccw
READ CONFIGURATION DATA
data returned from read configuration data ccw

bbbbbbbb
requested dump details in HEX digits

The following text might appear within the
display associated with a specific unit number:
- NO DATA -
The device does not support Self Description commands
so the information is not available for QTAPE to display

The following text might appear with the detailed
unit information when a unit address is encountered for which no information
is available: ****  UNLISTED DEVICE(S) AND REASON CODES:

     uuuu(rc) uuuu(rc) … … …

where: uuuu
unit number
rc
reason code why no information is presented, where: 01
device not configured, UCB not found
02
UCB not connected to a physical drive
03
device unavailable - system routine in control
04
subchannel error detected
05
device boxed
06
UCB does not define as tape device
07
I/O error accessing the device
08
UCB not connected to a tape device
09
QTAPE does not support the tape device since it is not capable
of SENSEID

The following text might appear indicating
the results of the DS QT command execution:
****  TYPE=tttt IS AN INVALID UCB TYPE
TYPE= and DEFINED were both specified, and no DASD units of the
type tttt were found
****  hhh DEVICE(S) WITH INCONSISTENT UCB TYPE
DEFINED
hhh is the number of unit addresses encountered
for which the defined device type is inconsistent with the connected
physical device
****  hhh DEVICE(S) WITH DEVICE EMULATION ACTIVE
hhh is the number of devices in emulation mode

Operator response
If the device status indicates that the storage
control subsystem has fenced one or more storage paths, contact your
service representative to fix the condition that caused the fencing.
If the device has been fenced, refer to the z/OS DFSMSdfp Storage Administration for
an explanation of the CONTROL command needed to unfence the device.
If the device is in a soft fenced state, commands that
read and write data to the volume are not allowed.  The soft fenced
state remains across an IML until it is explicitly reset.  The resetting
of the soft fenced state can be done by issuing a host command or
a user interface command. Use the ICKDSF CONTROL command with the
CLEARFENCE parameter to clear the soft fence state. For more information,
see Device Support Facilities (ICKDSF) User's Guide and Reference.
Otherwise,
follow your installation's procedures for the status which is indicated
in the message display. Recovery actions are contingent upon the following:
hardware and software configurations, system load and job mix. However,
the following are some examples of possible actions: Path Status
Action
<
Check all path switches for correct settings.
&
Check if shared device is in use by another system.
T
Re-enter DEVSERV, and if the condition still exists, end the program
which is tying up the device.

IEE459I hh.mm.ss DEVSERV
QTAPE (id)
There are two formats for DEVSERV
TAPE information. When DEVSERV QTAPE MED is issued the following
DEVSERV TAPE information is displayed after the above message:
First,
a header appears:
UNIT RDTYPE EDTYPE EXVLSR INVLSR RMEDIA EMEDIA WWID
Where:UNIT
tape device address
RDTYPE
real device typeNote: For the TS7720 disk-only Virtualization
Engine, this field contains all zeroes.

EDTYPE
emulated device type
EXVLSR
external volume serial of cartridge
INVLSR
internal volume serial of cartridge
RMEDIA
real media type of the volume mounted on the drive
EMEDIA
emulated media type of the volume mounted on the drive
WWID
worldwide unique cartridge identifier

Then, one or more lines of data appear:
unit rdtype edtype exvlsr invlsr rmedia emedia wwid
Where:unit
The tape device address is displayed in each line.
rdtype
The real device type is displayed if information is available,
otherwise it is blank. 
edtype
The emulated device type is displayed if available, otherwise
it is blank.
exvlsr
The external volume serial of the cartridge is displayed if available,
otherwise it is blank.
invlsr
The internal volume serial of the cartridge is displayed if available,
otherwise it is blank.
rmedia
The real media type of the volume mounted on the drive. The value
will be one of the following:1
CST
2
EC-CST
3
3590 STD length tape
4
3590 EXT length tape
5
3592 Enterprise Tape Cartridge
6–W
3592 Enterprise WORM Tape Cartridge
7
3592 Enterprise Economy Tape Cartridge
8–W
3592 Enterprise Economy WORM Tape Cartridge
(blank)
Media type is undefined or can not be determined

emedia
The emulated media type of the volume mounted on the drive. The
value will be one of the following:1
CST
2
EC-CST
3
3590 STD length tape
4
3590 EXT length tape
(blank)
Media type is undefined or can not be determined

The following text might appear with the
detailed unit information when a unit address is encountered for which
no information is available: ****  UNLISTED DEVICE(S) AND REASON CODES:
     uuuu(rc) uuuu(rc) … … …

where:uuuu
unit number
rc
reason code why no information is presented, where: 07
I/O error accessing the device
10
The device type is not supported
11
The device is not ready

Source
DFSMSdfp

Module
IGUDST02

Routing code
#

Descriptor code
8,9

Bit	Description
0-1	Grouped state: 00 Device is not grouped to any path in the path group. 01 Device is grouped to one or more paths in the path group. 10-11 Reserved.
2	If set to '1', device is reserved to this path group.
3	If set to '0', device is in single path mode. If set to '1', device is in multi-path mode.
4-7	Not used.