IDC31606I UNABLE TO action -PROBABLE CAUSE IS cause -VOLUME volser
Explanation
A SETCACHE or LISTDATA request cannot be run because the state of the subsystem or device is not as required.
For
a SETCACHE request, action and cause can
be replaced with the following values:
- Action
- Causes/Responses
- SET DEVICE CACHING ON
- -PINNED DATA: Probable cause for the device being in pending
state is pinned data. In order for the device to be activated for
caching the pinned data must first be discarded (SETCACHE DISCARDPINNED).
A PINNED TRACK REPORT can be generated (LISTDATA PINNED), and the data set with pinned retriable or non-retriable tracks can then be copied to a device prior to discarding the pinned data. (Possible utilities for copying the data set are IEBCOPY and IEBGENER.) For other types of pinned data, reaccess and try to destage or discard.
- SET DEVICE CACHING OFF
- -DASDFASTWRITE FAILED: The ‘DASD fast write failed’ condition exists for this device. The command is ended and results in no action taken.
- DISCARDPINNED
- -DASDFASTWRITE FAILED: The ‘DASD fast write failed’ condition exists for this device. The command is ended and results in no action taken.
- DESTAGE
- -NVS FAILED: The nonvolatile storage is failed. The command is ended and results in no action taken.
- SET SUBSYSTEM STORAGE OFF
- -NVS FAILED: The nonvolatile storage is failed. The command is ended and results in no action taken.
- SET SUBSYSTEM STORAGE ON
- -PINNED DATA: Probable cause for the subsystem being in pending state is pinned data. To activate the subsystem storage, the pinned data must first be discarded by a SETCACHE DISCARDPINNED for each volume with pinned data or a SUBSYSTEM PENDINGOFF, which causes cache fast write pinned data in the cache to be discarded. (SUBSYSTEM PENDINGOFF will not work for data pinned in the NVS.) A PINNED TRACK REPORT can be generated (LISTDATA PINNED), and then the data set with pinned retriable or non-retriable tracks can be copied to a device prior to discarding the pinned data. (Possible utilities for copying the data set are IEBCOPY and IEBGENER.) For other types of pinned data, reaccess and try to destage or discard.
- -DISABLED FOR MAINTENANCE: To activate subsystem storage, rerun the SETCACHE command when the subsystem is no longer disabled for maintenance (probable SR action to enable).
- SET SUBSYSTEM STORAGE PENDINGOFF
- -WRONG COMMAND ISSUED: The subsystem is not in pending state with scan complete. The SETCACHE SUBSYSTEM OFF would probably have resulted in the subsystem storage being deactivated.
- -NVS PINNED DATA: There is pinned data in the NVS. A PINNED TRACK REPORT can be generated (LISTDATA PINNED), and then the data set with pinned retriable or non-retriable tracks can be copied to a device prior to discarding the pinned data. (Possible utilities for copying the data set are IEBCOPY and IEBGENER.) For other types of pinned data, reaccess and try to destage or discard.
- SET NVS ON
- -PINNED DATA: Probable cause for the NVS being in pending state is pinned data. To activate the NVS, the pinned data for each volume must first be discarded (SETCACHE DISCARDPINNED). If the volume is a DASD fast write volume and in pending state, the data can be discarded with a SETCACHE DASDFASTWRITE PENDINGOFF. A PINNED TRACK REPORT can be generated (LISTDATA PINNED), and then the data set with pinned retriable or non-retriable tracks can be copied to a device prior to discarding the pinned data. (Possible utilities for copying the data set are IEBCOPY and IEBGENER.) For other types of pinned data, reaccess and try to destage or discard.
- -PINNED DATA OR NVS FAILED: If the DASD FAST WRITE volumes show pending in the ‘STATUS REPORT’ or NVS is failed (which is caused by a malfunction or NVS being taken offline by a SR action), a SETCACHE DASDFASTWRITE PENDINGOFF can be issued for the devices which are pending (have pinned data). A PINNED TRACK REPORT can be generated (LISTDATA PINNED), and then the data set with pinned retriable or non-retriable tracks can be copied to a device prior to discarding the pinned data. (Possible utilities for copying the data set are IEBCOPY and IEBGENER.) For other types of pinned data, reaccess and try to destage or discard.
- -DISABLED FOR MAINTENANCE: To activate the NVS, rerun the SETCACHE command when the NVS is no longer disabled for maintenance (probable SR action to enable).
- SET NVS OFF
- -NVS INITIALIZING: Rerun the SETCACHE job when the NVS has finished initialization.
- SET DASD FAST WRITE ON
- -NVS FAILED: Probable cause is malfunction or SR action. This message may occur after a duplex pair has been ended (with a RESETTOSIMPLEX parameter). If DASD fast write is on prior to ending a duplex pair, IDCAMS will attempt to set DASD fast write off and then restore to active status after the end. This is done to assure that the pairs are true copies.
- SET DASD FAST WRITE OFF
- -DASDFASTWRITE FAILED: This is caused by an incorrect ‘device ID’ (DASD fast write failed) and the device is DASD fast write active.
- -INVALID DFW DATA FOR SYNC: There is data for the device in the failed nonvolatile storage and the data is not in cache storage. This condition prevents the scheduling of destage of all DASD fast write data for the device, and the setting of indicators to prevent further DASD fast write activity on the device.
- SET DASD FAST WRITE PENDINGOFF
- -WRONG COMMAND ISSUED: The SETCACHE DASDFASTWRITE OFF command would probably have resulted in the DASD fast write being deactivated.
- SET CACHE FAST WRITE ON
- -PINNED DATA: A PINNED TRACK REPORT can be generated (LISTDATA PINNED), and then the data set with pinned retriable or non-retriable tracks can be copied to a device prior to discarding the pinned data. (Possible utilities for copying the data set are IEBCOPY and IEBGENER.) For other types of pinned data, reaccess and try to destage or discard.
- ESTABLISH A DUPLEX PAIR
- -NVS OFFLINE: Issue a SETCACHE NVS ON to activate NVS.
- -CACHE OFFLINE: Issue a SETCACHE SUBSYSTEM ON to activate subsystem storage.
- -PRIMARY DEVICE NOT SIMPLEX: A volser was selected which is already being used for dual copy operations. Reissue the command with a non-duplex pair volser specified.
- -SECONDARY DEVICE NOT SIMPLEX: A device ID was selected which is already being used for dual copy operations. Reissue the command with a non-duplex pair device ID specified.
- -CACHING ACTIVE: Although IDCAMS will set device caching off to both devices prior to attempting to establish a duplex pair, if device caching is inadvertently set back on (perhaps by another host) or is in pending state this cause is given. Note that IDCAMS restores the device caching state of the duplex pair to the original state of the primary device after the establish duplex pair channel program has run.
- -PRIMARY AND SECONDARY ARE SAME DEVICE: The volser of the requested primary and the device id of the requested secondary are the same device.
- -DEVICE RESERVED OR BUSY TO ANOTHER PROCESSOR: An attempt to establish a duplex pair has failed because the target secondary device was busy when the 3990 attempted to claim the volume. A possible reason for the target secondary to be busy is that the device is not offline to ALL attached hosts and there is host activity using this volume. (Operator commands like a DEVSERV against the target volume will cause host I/O to the volume.) Synchronize the target secondary device on all attached hosts and reissue the command.
- -PATH-GROUPS ARE NOT COMPATIBLE: The 3990 command rejected the establishment of the duplex pair with sense indicating that the proposed secondary device for the duplex pair has at least one path group established, and that the primary and secondary devices do not have the same path groups established on all channel paths. A possible reason for this is that some other host attached to this device had the device ONLINE and another non-MVS host attached to the secondary has a path group established for the secondary. Note that this 3990 check is to help insure that the secondary is in the proper state; that is, either no path group exists or the path group of the secondary is the same as that for the primary. Insure that the target secondary device is OFFLINE to all attached MVS™ hosts. If non-MVS hosts are attached to the device insure that the path groups for the secondary device are resigned or equal to the primary.
- REESTABLISH A DUPLEX PAIR
- -PINNED DATA: The suspended duplex primary volume has pinned data. A PINNED TRACK REPORT can be generated (LISTDATA PINNED), and then the data set with pinned retriable or non-retriable tracks can be copied to a device prior to discarding the pinned data. (Possible utilities for copying the data set are IEBCOPY and IEBGENER.) Discard using DISCARDPINNED or DASDFASTWRITE PENDINGOFF (depending on the circumstances).
- -NVS OFFLINE: Issue a SETCACHE NVS ON to activate NVS.
- -CACHE OFFLINE: Issue a SETCACHE SUBSYSTEM ON to activate subsystem storage.
- -DEVICE IS NOT A PRIMARY: The volser specified as the primary volume is not part of a duplex pair or is the secondary volume of a duplex pair. Probable user error. Correct the volser and reissue the command. volser.
- -ALTERNATE DEVICE NOT SIMPLEX: A device ID was selected which is already being used for dual copy operations. Reissue the command with a non-duplex pair device ID specified.
- -CACHING ACTIVE: Although IDCAMS will set device caching off to the alternate device prior to attempting to establish a duplex pair, if device caching is inadvertently set back on (perhaps by another host) or is in pending state this cause is given.
- -PRIMARY AND ALTERNATE ARE SAME DEVICE: The volser of the requested primary and the device ID of the requested alternate are the same device.
- -DEVICE RESERVED OR BUSY TO ANOTHER PROCESSOR: An attempt to establish a duplex pair has failed because the target alternate device was busy when the 3990 attempted to claim the volume. The target alternate could be busy because the device is not offline to all attached hosts and there is host activity using this volume (operator commands like a DEVSERV against the target volume will cause host I/O to the volume). Synchronize the target alternate device on all attached hosts and reissue the command.
- -PATH-GROUPS ARE NOT COMPATIBLE: The 3990 command rejected the establishment of the duplex pair with sense indicating that the proposed alternate device for the duplex pair has at least one path group established and that the primary and alternate devices do not have the same path groups established on all channel paths. A possible reason for this is that some other host attached to the alternate had the alternate ONLINE and another non-MVS host attached to this device has a path group established for the device. Note that this 3990 check is to help insure that the alternate is in the proper state; that is, either no path group exists or the path group of the alternate is the same as that for the primary. Insure that the target alternate device is OFFLINE to all attached MVS hosts. If non-MVS hosts are attached to the device insure that the path groups for the alternate device are resigned or equal to the primary.
- ESTABLISH A DUPLEX PAIR FROM SUSPENDED DUPLEX
- -PINNED DATA: The suspended duplex primary volume has pinned data. A PINNED TRACK REPORT can be generated (LISTDATA PINNED), and then the data set with pinned retriable or non-retriable tracks can be copied to a device prior to discarding the pinned data. (Possible utilities for copying the data set are IEBCOPY and IEBGENER.) Discard using DISCARDPINNED or DASDFASTWRITE PENDINGOFF (depending on the circumstances).
- -NVS OFFLINE: Issue a SETCACHE NVS ON to activate NVS.
- -CACHE OFFLINE: Issue a SETCACHE SUBSYSTEM ON to activate subsystem storage.
- -DEVICE IS NOT A PRIMARY: The volser specified as the primary volume is not part of a duplex pair or is the secondary volume of a duplex pair. Probable user error. Correct the volser and reissue the command.
- TERMINATE A DUPLEX PAIR
- -DEVICE IS NOT A PRIMARY: The volser specified as the primary volume is not part of a duplex pair or is the secondary volume of a duplex pair. Probable user error. Correct the volser and reissue the command.
- -PINNED DATA: DASD fast write is in pending state. A PINNED TRACK REPORT can be generated (LISTDATA PINNED), and then the data set with pinned retriable or non-retriable tracks can be copied to a device prior to discarding the pinned data. (Possible utilities for copying the data set are IEBCOPY and IEBGENER.) Discard using DISCARDPINNED or DASDFASTWRITE PENDINGOFF (depending on the circumstances).
- SUSPEND A DUPLEX PAIR
- -DEVICE IS NOT A PRIMARY: The volser specified as the primary volume is not part of a duplex pair or is the secondary volume of a duplex pair. Probable user error. Correct the volser and reissue the command.
- -PAIR ALREADY SUSPENDED: A request to suspend an already suspended duplex pair results in no action being taken.
- -SUSPENDPRIMARY TO DUPLEX PENDING PAIR: A request to suspend a duplex pair with the primary as the suspended device while establishing a duplex pair is pending. The SUSPENDPRIMARY command is ended with no action taken.
For a LISTDATA request, action and cause can
be replaced with the following values:
- Action
- Cause
- READ PINNED TRACK DATA
- -CACHE STORAGE IS FAILED OR UNAVAILABLE: An attempt to read pinned track data was unsuccessful because cache storage was not available or pending.
In the message text:
- volser
- The volume serial number.
- action
- The specified action.
- cause
- The cause of the error.
System action
Processing continues.
Programmer response
Resubmit when the state changes to allow the command. Most can be checked with LISTDATA...STATUS. In the case of a user error, correct the volser or other erroneous condition and reissue the command.
Source
DFSMSdfp