Explanation
During a swap, DDR has encountered an error, preventing
successful completion of the swap request from a device. The various
errors are indicated by the variable portion of the message text.
In
the message text:
- BUFFERED DATA EXCEEDS XXXX M-BYTES
- The amount of buffered data in the failing device that needs to
be recovered by DDR is larger than the DDR storage limit set in the
DEVSUPxx member of SYS1.PARMLIB. Swap processing from dev is terminated.
- dev
- The device number of the device being swapped from.
- text
- The possible message texts and their meanings:
- NO USER FOUND
- DDR was unable to locate the user of the device after the swap
commenced. The user of the device has ended, or the user's control
blocks could not be located.
- ERP IN PROGRESS
- While attempting to rewind and unload the "FROM" tape involved
in an operator-requested swap, an error recovery procedure (ERP) was
found to be in progress.
- OPEN/CLOSE/EOV IN PROGRESS
- DDR has found that the user of the "FROM" tape is in the
process of OPEN, CLOSE, or EOV. The position of the tape is not known.
- BLOCKCOUNT UNRELIABLE
- If the user of the tape is using the EXCP macro for I/O, he did
not code the REPOS=Y parameter in his DCB macro. As a result, the
block count is not considered to be accurate and DDR cannot reposition
the tape.
If the user of the tape is using the basic sequential
access method, DDR has encountered a condition where the tape is open
for the CNTRL macro format and the block count is zero.
As a
consequence, DDR cannot determine the position of the tape. This message
also appears for all access methods if an attempt is made to SWAP
a NL tape opened for the MOD disposition.
- CANCELED BY OPERATOR
- This message is confirmation that the operator has replied ‘NO’
to message IGF500D or IGF509D. The swap from dev is
not completed.
- INVALID USER EXIT
- The installation-written NSLREPOS routine has returned an incorrect
return code to DDR.
- CATASTROPHIC ERROR
- DDR has encountered a machine check, program check, ABEND, an
I/O error that it cannot retry, or contention exists for an MIH resource.
The current swap from the indicated device is ended.
- INVALID DEVICE
- The device dev entered as the "FROM" device
in the swap command is not valid.
- CANCELED BY USER
- The installation-written NSLREPOS routine has indicated that the
swap is to be ended.
- JES3 ERROR
- An error occurred in a DDR/JES3 subsystem exit routine. The current
swap from dev abnormally ends.
- BY DEVICE SUPPORT MODULE
- The device support module could not validate the swap.
- RD BLKID ERROR
- DDR received a unit check in response to a Read Block ID command
before the actual swap. The tape position cannot be determined, nor
can the degree of data buffering be calculated.
- RD BUFFER ERROR
- DDR received a unit check in response to a Read Buffer command
before the actual swap. The buffered data, which had not yet been
written to tape, but had been sent from the host processor, cannot
be retrieved.
- GETMAIN FAILED
- During DDR processing before the actual swap, the storage for
saving the buffered data was insufficient.
- DEVICE FORCED OFFLINE
- An unrecoverable I/O error occurred which resulted in a loss of
data. The tape subsystem is boxed (forced offline).
- ACTIVATE IN PROGRESS
- The direct access storage device (DASD) swap ended because an
I/O configuration change is in progress.
- PAGE FIX ERROR
- During DDR processing before the actual swap, the storage for
saving the buffered data was unable to be page fixed for the read
buffer operation.
- UNSUPPORTED RECORD LENGTH
- During DDR processing before the actual swap, it was determined
that records buffered in the device exceed the 64 kilobytes maximum
record length supported by the 3480/3490 device support module.
- FAILURE DURING LIBRARY PROCESSING
- DDR encountered an error associated with the mount or dismount
services performed by the library automation communication services
(LACS), or an error during the volume verification services for a
system-initiated swap in a 3495 Tape Library Dataserver.
- READ ERROR IN LIBRARY
- DDR encountered an error while attempting to read the label on
the tape mounted on the 'TO' device during a system-initiated swap
in a 3495 Tape Library Dataserver.
- REPOSITIONING ERROR IN LIBRARY
- DDR encountered an error while attempting to reposition the tape
on the 'TO' device during a system-initiated swap in a 3495 Tape Library
Dataserver.
- EXIT I/O ERROR IN LIBRARY
- The Device Service Exit performed the read of the volume label
and the repositioning of the tape on the device. The swap is a system-initiated
swap in a 3495 Tape Library Dataserver. The exit returned an error
code to DDR indicating a failure during the read or repositioning
stage.
- SWITCH FAILED DUE TO I/O ERROR
- While attempting to terminate a PPRC pair, an I/O error was encountered.
- NOT A VALID PPRC PAIR
- The 'FROM' and 'TO' devices are permanent resident DASD but are
not a valid PPRC pair. Only permanent resident DASD that are part
of a PPRC pair can be swapped.
- GETMAIN FAILED - SP245
- During DDR processing before the actual swap, the storage to read
attention messages could not be obtained.
- SWAP TERMINATED BY OPERATOR
- The operator indicated that the swap should be terminated in response
to IGF520A, IGF521A, or IGF522A.
- ERROR ACQUIRING TAPE FORMAT INFO
- DDR was unable to obtain tape format information from the FROM device.
The swap is ended.
- CATASTROPHIC ERROR - RSN=xx
- DDR encountered an error and cannot retry. The current swap from
device dev ended. The reason code displayed indicates
the specific reason for the failure.
See operator response for the
description of the reason codes.
- UCB SWAP FAILURE - RSN=xx
- The attempt to swap UCBs failed. xx is the
reason code which describes the failure. For a list of reason codes,
see mapping macro IOSDSWAP in z/OS® MVS™ Data Areas in the z/OS Internet library.
System action
Operator response
The response by the operator depends on the
text of the message. Responses to each of the conditions are detailed
as follows:
- NO USER FOUND
- Issue a DISPLAY U command to determine if the "FROM" tape
is allocated. If it is not, no one is using the tape and you need
not use DDR to move the volume on it. If the tape is allocated, reenter
the swap command to retry the swap. For a swap requested by the system
as a result of a permanent error, no further action is necessary.
- ERP IN PROGRESS
- If a system-initiated DDR request does not occur as a result of
a permanent error, reenter the SWAP command to retry the swap.
- OPEN/CLOSE/EOV IN PROGRESS
- Reenter the SWAP command after the OPEN, CLOSE, or EOV processing
is complete. This would involve making required volume mounts prior
to issuing the SWAP command.
- BLOCKCOUNT UNRELIABLE
- If the user is using EXCP level I/O, he must correct the program
so that it maintains an accurate block count and ensure that the DCB
macro is coded with REPOS=YES. This will allow DDR to support the
I/O for both operator requests and upon the occurrence of errors.
If
the user is known to be using BSAM, or the tape is NL, opened for
the MOD disposition, you may attempt to reenter the SWAP command after
tape motion has taken place.
- CANCELED BY OPERATOR
- If the tape is an emulator tape, no action is required since DDR
does not support emulator tape.
- INVALID USER EXIT
- Contact the system programmer to make sure that the NSLREPOS program
is in the system. If it is, m sure that a valid return code (0, 4,
8, 12, 16, or 20) is being returned to DDR and that no programming
errors exist in NSLREPOS.
- CATASTROPHIC ERROR
- This may result when the application that had originally held
an allocation for device dev either ends or issues
a close against dev while DDR is processing the
swap. If this is the case, then a SVC dump for a program check in
DDR accompanies this message. Give this dump to the system programmer.
This
may result when an I/O error occurs for the device being swapped to.
In this case, no additional messages are issued (i.e., IOS000I) or
LOGREC entries recorded to report this error as the DDR I/O driver
bypasses error recovery procedure under certain conditions when handling
I/O, such as rewind unload in preparation for a swap. If the DDR swap
was operator-initiated, reissue the command specifying a new TO device.
If the DDR swap was system-initiated, the application holding an
allocation for device dev is posted back with a permanent error.
This
may also occur if a DISPLAY IOS, MIH or SETIOS or SET IOS=xx command
is active at the time of the DDR swap. If the DDR swap was operator-initiated,
reissue the SWAP command. If the DDR swap was system-initiated, the
application holding an allocation for device dev is posted back with
a permanent error.
- INVALID DEVICE
- Reenter the SWAP command using a valid device for the "FROM" device.
- CANCELED BY USER
- No action is required.
- JES3 ERROR
- If the swap was initiated through a SWAP command, you may attempt
to reenter the command. If, however, the swap was requested by the
system as a result of a permanent error, the affected user has been
posted with a permanent error.
- BY DEVICE SUPPORT MODULE
- No action is required.
- ERROR ON RD BLKID
- No action is required.
- ERROR ON RD BUFFER
- No action is required.
- GETMAIN FAILED
- No action is required.
- PAGE FIX ERROR
- No action is required.
- FAILURE DURING LIBRARY PROCESSING
- If there is a tape or library hardware problem, contact hardware
support.
- READ ERROR IN LIBRARY
- If there is a tape or library hardware problem, contact hardware
support.
- REPOSITIONING ERROR IN LIBRARY
- If there is a tape or library hardware problem, contact hardware
support.
- EXIT I/O ERROR IN LIBRARY
- If there is a tape or library hardware problem, contact hardware
support.
- SWITCH FAILED DUE TO I/O ERROR
- If there is a hardware problem, contact hardware support.
- NOT A VALID PPRC PAIR
- Reenter the swap command, specifying 'FROM' and 'TO' devices that
are the primary and secondary devices in the same PPRC pair.
- GETMAIN FAILED - SP245
- No action is required.
- SWAP TERMINATED BY OPERATOR
- No action is required.
- ERROR ON MEDIUM SENSE COMMAND
- No action is required.
- ERROR WRITING DATA
- No action is required.
- ERROR SETTING MODE CNTL INFORMATION
- No action is required.
- ERR ON SYNC CMD - DEV FORCED OFFLINE
- No action is required.
- ERROR ON LOCATE CMD
- No action is required.
- CATASTROPHIC ERROR - RSN=xx
- The reason code in xx specifies what failure
occurred.
- 01
- A program check occurred during DDR execution. The recovery routine
of DDR swap should have taken an SVC dump for this condition.
- 02
- A terminating condition occurred early in DDR swap processing.
- 03
- An internal error in DDR logging occurred.
- 04
- An I/O error occurred on the TO device making it not usable for
swapping. For operator and system-initiated swaps, it is possible
to select a new TO device to be used for the SWAP.
- 05
- An internal error occurred. The device type recognized by DDR
swap was not a tape, DASD, or unit record device type.
- 06
- An internal error in DDR device validation occurred.
- 07
- An internal error occurred. An attempt to pagefix a DDR module
failed.
- 08
- A required resource could not be obtained. This condition will
most likely occur when a DISPLAY IOS, SETIOS, or SET IOS=xx command
is active at the time of the swap. For an operator swap, reissue the
SWAP command. For a system-initiated swap, the application holding
an allocation for device dev is posted back with
a permanent error.
Unless otherwise noted, obtain a console dump which
includes both the MASTER and IOS address spaces (IOSAS) and contact
the IBM® Support Center for dump
assistance.
- UCB SWAP FAILURE - RSN=xx
- For a list of reason codes, see mapping macro IOSDSWAP in z/OS MVS Data
Areas in the z/OS Internet library.
If IBM support is required,
obtain a console dump which includes both the MASTER and IOS address
spaces (IOSAS) and contact the IBM Support
Center for dump assistance.
Source
Dynamic device reconfiguration (DDR)
Module
Routing code
Descriptor code