z/VM: System Messages and Codes Š CP - z/VM - IBM

IOS010
Explanation: The I/O function code specified in the
IORTYPE, used to call HCPIOSRQ, is incorrect.
User Response: Examine the save area or CP trace
table entries to determine the calling module. Check
R10 to see that it is pointing to a valid IORBK. The valid
I/O function codes are ’IORSIO’ (x’00’) and ’IORCUSER’
(x’FE’). If R10 contains the address of the IORBK,
storage was probably overlaid. Otherwise, the requestor
probably did not set the register correctly.
IOS017
Explanation: The deferred execution counter,
VMDDFRWK in the VMDBK, was about to become
negative.
User Response: Examine the CP trace table and
storage dump to see why the VMDBK in R11 has a zero
value for the VMDDFRWK field.
See the description of DFR017 for possible reasons
why this may have occurred.
IOS020
Explanation: Start-Subchannel (SSCH) simulation for
a logical device resulted in one of the following:
v A return code that was greater than 12 or not a
multiple of 4.
v A return code 8, which correlates to a SSCH
condition code 2. An I/O operation was attempted
while another one was in progress for the same
logical device.
User Response: Examine the CP trace table to
analyze other events relating to the logical device or
subchannel.
Look at the RDEV (pointed to by R8), which is used by
HCPIOS to manage the logical device. The RDEV field,
RDEVLSOP, points to the corresponding logical
subchannel.
Verify that the SSCH simulation module for logical
devices (HCPLCISS) is adhering to the interface defined
in the prolog.
IOS023
Explanation: Store-subchannel (STSCH) simulation
for a logical device indicated that a return code does not
correlate to a condition code defined by the XA
Architecture for the STSCH instruction.
User Response: Look at the RDEV (pointed to by
R8), which is used by HCPIOS to manage the logical
device. The RDEV field RDEVLSOP points to the
corresponding logical subchannel.
Verify that the STSCH simulation module for logical
devices (HCPLCIST) is adhering to the interface defined
in the prologue.
IOS024
Explanation: Set-Address-Limit (SAL) simulation for a
logical channel subsystem indicated a return code other
than zero.
User Response: Verify that the SAL simulation
module for logical devices (HCPLCISA) adheres to the
interface defined in the prologue.
IOS025
Explanation: Set-Channel-Monitor (SCHM) simulation
for a logical channel subsystem indicated a return code
other than zero.
User Response: Verify that the SCHM simulation
module for logical devices (HCPLCISC) is adhering to
the interface defined in the prologue.
IOS026
Explanation: Halt-Subchannel (HSCH) simulation for a
logical device indicated one of the following:
v A return code that was greater than 12 or not a
multiple of 4.
v A return code 8, which correlates to a HSCH
condition code 2. A HSCH was attempted while the
logical subchannel was busy processing another
HSCH or CSCH.
User Response: Examine the trace table to analyze
other events relating to that logical device / subchannel.
Look at the RDEV (pointed to by R8), which is used by
HCPIOS to manage the logical device. The RDEV field
RDEVLSOP points to the corresponding logical
subchannel.
Verify that HSCH simulation module for logical devices
(HCPLCIHS) is adhering to the interface defined in the
prologue.
IOS027
IOS010 IOS027
Explanation: Clear-Subchannel (CSCH) simulation for
a logical device indicated one of the following:
v A return code that was greater than 12 or not a
multiple of 4.
v A return code 4 or 8, which correlates to a CSCH
condition code 1 or 2 respectively. Both condition
codes are undefined by the XA Architecture for a
CSCH.
User Response: Look at the RDEV (pointed to by
R8), which is used by HCPIOS to manage the logical
device. The RDEV field RDEVLSOP points to the
corresponding logical subchannel.
Verify that CSCH simulation module for logical devices
Chapter 2. System Codes 53