gtpm5m14Messages (Online)

CYEA-CZSA

CYEA0022ISUBSYSTEM STORAGE PHYSICALLY ENABLED ON RCS SSID ssss

Where:

ssss
Represents a 3990 Record Cache Subsystem (RCS) ID (SSID).

Explanation: A state change interrupt was received from the 3990 RCS SSID specified in the message, indicating that the subsystem cache is no longer disabled for maintenance.

System Action: Processing is continued with the input/output (I/O) queue thresholding reset for the 3990 RCS SSID specified in the message, if it is no longer degraded.

User Response: Have your system support personnel determine whether corrective action is required to enable the subsystem cache for use.

CYEA0023INONVOLATILE STORAGE PHYSICALLY ENABLED ON RCS SSID ssss

Where:

ssss
Represents a 3990 Record Cache Subsystem (RCS) ID (SSID).

Explanation: A state change interrupt was received from the 3990 Record Cache Subsystem (RCS) ID (SSID) specified in the message, indicating that the nonvolatile storage (NVS) is no longer disabled for maintenance on the 3990 RCS SSID specified in the message.

System Action: Processing is continued with the input/output (I/O) queue thresholding reset for the 3990 RCS SSID specified in the message, if it is no longer degraded.

User Response: Have your system support personnel determine whether corrective action is required to enable the nonvolatile storage (NVS) for use.

CYEA0024IFAST WRITE FUNCTIONS RESUMED ON RCS SSID ssss

Where:

ssss
Represents a 3990 Record Cache Subsystem (RCS) ID (SSID).

Explanation: A state change interrupt was received from the 3990 Record Cache Subsystem (RCS) ID (SSID) specified in the message, indicating that the fast-write suspend state is no longer active on the 3990 RCS SSID specified in the message. Fast-write function were resumed. Fast-write functions were resumed during RCS shutdown processing.

System Action: Processing is continued with the input/output (I/O) queue thresholding reset for the RCS SSID specified in the message, if it is no longer degraded.

User Response: None.

CYEA0025WFAST WRITE FUNCTIONS SUSPENDED ON RCS SSID ssss

Where:

ssss
Represents a 3990 Record Cache Subsystem (RCS) ID (SSID).

Explanation: A state change interrupt was received from the 3990 Record Cache Subsystem (RCS) ID (SSID) specified in the message, indicating that the fast-write function was suspended on the 3990 RCS SSID specified in the message. Fast-write functions are suspended during RCS shutdown processing.

System Action: Processing is continued with the input/output (I/O) queue thresholding activated for the 3990 RCS SSID specified in the message.

User Response: See your system support personnel if an RCS shutdown is not currently active. This may indicate a status change initiated by a non-TPF attached system.

CYEA0026IIML DEVICE AVAILABLE ON RCS SSID ssss

Where:

ssss
Represents a 3990 Record Cache Subsystem (RCS) ID (SSID).

Explanation: A state change interrupt was received from the 3990 Record Cache Subsystem (RCS) ID (SSID) specified in the message, indicating that the initial machine load (IML) device for the 3990 RCS SSID specified in the message is now available.

System Action: Processing is continued with the input/output (I/O) queue thresholding reset for the 3990 RCS SSID specified in the message, if it is no longer degraded.

User Response: None.

CYEA0027ICACHE FAST WRITE ACTIVATED ON RCS SSID ssss

Where:

ssss
Represents a 3990 Record Cache Subsystem (RCS) SSID.

Explanation: A state change interrupt was received from the 3990 Record Cache Subsystem (RCS) SSID that is specified in the message, indicating that the cache fast-write capability is now activated for the 3990 RCS SSID specified in the message.

System Action: Processing is continued with the input/output (I/O) queue thresholding reset for the 3990 RCS SSID specified in the message, if it is no longer degraded.

User Response: Have your system support personnel determine whether corrective action is required to use the cache fast-write function in the subsystem.

CYEA0028WNONVOLATILE STORAGE BATTERY DEFECTIVE ON RCS SSID ssss

Where:

ssss
Represents a 3990 Record Cache Subsystem (RCS) SSID.

Explanation: A state change interrupt was received from the 3990 Record Cache Subsystem (RCS) SSID specified in the message, indicating that the nonvolatile storage (NVS) battery is defective on the 3990 RCS SSID specified in the message.

System Action: Processing is continued with the input/output (I/O) queue thresholding activated for the 3990 RCS SSID specified in the message.

User Response: Have your system support personnel determine whether corrective action is required to repair or replace the defective nonvolatile storage (NVS) battery.

CYEA0029ACACHING TERMINATED ON RCS SSID ssss DUE TO SUBSYSTEM STORAGE MALFUNCTION.

Where:

ssss
Represents a 3990 Record Cache Subsystem (RCS) SSID.

Explanation: A state change interrupt was received from the 3990 Record Cache Subsystm (RCS) SSID specified in the message, indicating that caching was ended due to an error in the 3990 RCS SSID specified in the message.

System Action: Processing is continued with the input/output (I/O) queue thresholding activated for the 3990 RCS SSID specified in the message.

User Response: See your IBM service representative to address this error condition.

CYEA0030ADASD FAST WRITE TERMINATED ON RCS SSID ssss DUE TO NONVOLATILE CACHE MALFUNCTION.

Where:

ssss
Represents a 3990 Record Cache Subsystem (RCS) SSID.

Explanation: A state change interrupt was received from the 3990 Record Cache Subsystem (RCS) SSID specified in the message, indicating that DASD fast-write capability is ended due to an error in the 3990 RCS SSID specified in the message.

System Action: Processing is continued with the input/output (I/O) queue thresholding activated for the 3990 RCS SSID specified in the message.

User Response: See your IBM service representative to address this error condition.

CYEA0051WPOSSIBLE CACHE FAST WRITE DATA LOSS FOR RCS SSID ssss

Where:

ssss
Represents a 3990 Record Cache Subsystem (RCS) SSID.

Explanation: A state change interrupt was received from the 3990 Record Cache Subsystem (RCS) SSID specified in the message, indicating that the cache fast-write ID (CFWID) was changed. Cache fast-write data may be lost from this action.

System Action: Processing is continued with the input/output (I/O) queue thresholding activated for the 3990 RCS SSID specified in the message.

User Response: Have your system support personnel determine whether corrective action is required to restore or recreate any lost cache fast-write data.

CYEA0053WCACHING DEACTIVATED ON RCS SSID ssss DUE TO EXPLICIT HOST REQUEST

Where:

ssss
Represents a 3990 Record Cache Subsystem (RCS) SSID.

Explanation: A state change interrupt was received from the 3990 Record Cache Subsystem (RCS) ID (SSID) specified in the message, indicating that the caching capability was ended due to an explicit host request for the 3990 RCS SSID specified in the message.

System Action: Processing is continued with the input/output (I/O) queue thresholding activated for the 3990 RCS SSID specified in the message.

User Response: Ensure this condition was expected as a result of a prior ZBUFC ALLOCATE IMPLEMNT command request.

CYEA0054WCACHE FAST WRITE DEACTIVATED ON RCS SSID ssss

Where:

ssss
Represents a 3990 Record Cache Subsystem (RCS) SSID.

Explanation: A state change interrupt was received from the 3990 Record Cache Subsystem (RCS) ID (SSID) specified in the message, indicating that the fast-write capability was ended due to an explicit host request for the 3990 RCS SSID specified in the message.

System Action: Processing is continued with the input/output (I/O) queue thresholding activated for the 3990 RCS SSID specified in the message.

User Response: Ensure this condition was expected as a result of a prior ZBUFC FILE command request.

CYEA0055WNONVOLATILE CACHE DEACTIVATED ON RCS SSID ssss DUE TO EXPLICIT HOST REQUEST.

Where:

ssss
Represents a 3990 Record Cache Subsystem (RCS) SSID.

Explanation: A state change interrupt was received from the 3990 Record Cache Subsystem ID (SSID) specified in the message, indicating that the nonvolatile cache was ended due to an explicit host request.

System Action: Processing is continued with the input/output (I/O) queue thresholding activated for the 3990 RCS SSID specified in the message.

User Response: Ensure this condition was expected as a result of a prior ZBUFC FILE command request.

CYEA0058WCACHING DEACTIVATED FOR DEVICE dddd ON RCS SSID ssss

Where:

dddd
Represents a 3990 Record Cache device address.

ssss
Represents a 3990 Record Cache Subsystem (RCS) SSID.

Explanation: A state change interrupt was received from the 3990 Record Cache Subsystem ID (SSID) that is specified in the message, indicating that the caching capability was ended for the device specified in the message due to an explicit host request.

System Action: Processing is continued with the input/output (I/O) queue thresholding activated for the 3990 RCS SSID specified in the message.

User Response: This is not an expected condition. Enter the ZBUFC ENABLE command to enable caching again, if required.

CYEA0083ICACHING ACTIVE ON RCS SSID ssss

Where:

ssss
Represents a 3990 Record Cache Subsystem (RCS) SSID.

Explanation: A state change interrupt was received from the 3990 Record Cache Subsystem ID (SSID) that is specified in the message, indicating that the subsystem storage is available for caching due to an explicit host request or a resetting event in the control unit.

System Action: Processing is continued with the input/output (I/O) queue thresholding reset for the 3990 RCS SSID specified in the message if it is no longer degraded.

User Response: None.

CYEA0084ICACHING IS PENDING ACTIVE ON RCS SSID ssss

Where:

ssss
Represents a 3990 Record Cache Subsystem (RCS) SSID.

Explanation: A state change interrupt was received from the 3990 Record Cache Subsystem ID (SSID) that is specified in the message, indicating that the subsystem storage is being made available for caching due to an explicit host request or a resetting event in the control unit.

System Action: Processing is continued with the input/output (I/O) queue thresholding reset for the 3990 RCS SSID specified in the message if it is no longer degraded.

User Response: None.

CYEA0085WCACHE SUSPENDED ON RCS SSID ssid

Where:

ssid
Represents a 3990 Record Cache Subsystem (RCS) SSID.

Explanation: A state change interrupt was received from the 3990 Record Cache Subsystem ID (SSID) that is specified in the message, indicating that the the caching status is suspended due to a request to make subsystem storage unavailable while users of the concurrency filter lock facility (CFLF) are connected to lock partitions.

This condition results from:

System Action: Processing is continued with the input/output (I/O) queue thresholding activated for the 3990 RCS SSID specified in the message due to the loss of caching capability. In this state, lock entities in the subsystem are preserved and lock activity is allowed but further caching of data records is denied.

User Response: Do one of the following:

CYEA0086WCACHING PENDING OFF IN PROGRESS ON RCS SSID ssss

Where:

ssss
Represents a 3990 Record Cache Subsystem (RCS) SSID.

Explanation: A state change interrupt was received from the 3990 RCS SSID specified in the message, indicating that subsystem storage is being made unavailable for caching due to an explicit host request.

System Action: Processing is continued with the input/output (I/O) queue thresholding activated for the 3990 RCS SSID specified in the message.

User Response: Ensure this condition was the result of a ZBUFC ALLOCATE IMPLEMNT command request. If required, enter a ZBUFC ENABLE command request to activate caching for the subsystem.

CYEA0087INVS ACTIVE ON RCS SSID ssss

Where:

ssss
Represents a 3990 Record Cache Subsystem (RCS) SSID.

Explanation: A state change interrupt was received from the 3990 RCS SSID specified in the message, indicating that the nonvolatile storage (NVS) is available for fast-write cache functions.

System Action: Processing is continued with the input/output (I/O) queue thresholding reset for the 3990 RCS SSID specified in the message, if it is no longer degraded.

User Response: None.

CYEA0089WNVS DEACTIVATE PENDING ON RCS SSID ssss

Where:

ssss
Represents a 3990 Record Cache Subsystem (RCS) SSID.

Explanation: A state change interrupt was received from the 3990 RCS SSID specified in the message, indicating that the nonvolatile storage (NVS) is being made unavailable for fast-write caching functions due to an explicit host request.

System Action: Processing is continued with the input/output (I/O) queue thresholding activated for the 3990 RCS SSID specified in the message.

User Response: Ensure this condition was the result of a ZBUFC FILE command request. If required, enter a ZBUFC ENABLE command request to enable fast-write caching again.

CYEA0090ICACHING ACTIVATED FOR DEVICE dddd ON RCS SSID ssss

Where:

dddd
Represents a 3990 Record Cache device address.

ssss
Represents a 3990 Record Cache Subsystem (RCS) SSID.

Explanation: A state change interrupt was received from the 3990 RCS SSID specified in the message, indicating that the device specified in the message is available for caching functions.

System Action: Processing is continued with the input/output (I/O) queue thresholding reset for the 3990 RCS SSID specified in the message, if it is no longer degraded.

User Response: None.

CYEA0092IDASD FAST WRITE ALLOWED FOR DEVICE dddd ON RCS SSID ssss

Where:

dddd
Represents a 3990 Record Cache device address.

ssss
Represents a 3990 Record Cache Subsystem (RCS) SSID.

Explanation: A state change interrupt was received from the 3990 RCS SSID specified in the message, indicating that the device specified in the message is available for fast-write caching functions.

System Action: Processing is continued with the input/output (I/O) queue thresholding reset for the 3990 RCS SSID specified in the message, if it is no longer degraded.

User Response: None.

CYEA0093WFAST WRITE SUSPENDED FOR DEVICE dddd RCS SSID ssss DUE TO PINNED DATA

Where:

dddd
Represents a 3990 Record Cache device address.

ssss
Represents a 3990 Record Cache Subsystem (RCS) SSID.

Explanation: A state change interrupt was received from the 3990 RCS SSID specified in the message, indicating that fast-write capability is suspended for the device specified in the message due to the pinned data threshold being exceeded.

System Action: Processing is continued with the input/output (I/O) queue thresholding set for the 3990 RCS SSID specified in the message, if required.

User Response: Action is required to clear the pinned data condition before fast-write capability is restored for the device.

CYEA0094IRECORD MODE ALLOWED FOR DEVICE dddd ON RCS SSID ssss

Where:

dddd
Represents a 3990 Record Cache device address.

ssss
Represents a 3990 Record Cache Subsystem (RCS) SSID.

Explanation: A state change interrupt was received from the 3990 RCS SSID specified in the message, indicating that the device specified in the message is allowed to perform record caching functions.

System Action: Processing is continued with the input/output (I/O) queue thresholding reset for the 3990 RCS SSID specified in the message, if it is no longer degraded.

User Response: None.

CYEA0095INO PINNED DATA EXISTS FOR DEVICE dddd ON RCS SSID ssss

Where:

dddd
Represents a 3990 Record Cache device address.

ssss
Represents a 3990 Record Cache Subsystem (RCS) SSID.

Explanation: A state change interrupt was received from the 3990 RCS SSID specified in the message, indicating that the device specified in the message no longer has any pinned data in the subsystem.

System Action: Processing is continued with the input/output (I/O) queue thresholding reset for the 3990 RCS SSID specified in the message, if it is no longer degraded.

User Response: None.

CYEA0096WPINNED DATA EXISTS FOR DEVICE dddd ON RCS SSID ssss

Where:

dddd
Represents a 3990 Record Cache device address.

ssss
Represents a 3990 Record Cache Subsystem (RCS) SSID.

Explanation: A state change interrupt was received from the 3990 RCS SSDI specified in the message, indicating that the device specified in the message has pinned data tracks in the subsystem.

System Action: Processing is continued with the input/output (I/O) queue thresholding activated for the 3990 RCS SSID specified in the message.

User Response: Enter the ZBUFC DISPLAY PINNED command, as required, to determine where the pinned data resides. If required, start a DASD copy operation to ensure data is filed to another DASD volume surface before taking the module offline.

CYED0001IMODULE QUEUE FOR xxxx MAY BE STALLED.

Where:

xxxx
The device address.

Explanation: A nonempty queue is detected in the file status table for this device and this device has had no activity since the last scan of the table. This indicates that the TPF system is probably running in a stressed environment. If the capture function or the file copy function is running, this message may appear intermittently.

System Action: The normal CYED message sequence is: CYED01, CYED04, and CYED05. The first time CYED detects a device whose queue has not moved in two scans, it writes the CYED01 message and time stamps the device. On the next scan, if the device queue still has not moved, it issues the CYED04 message. Afterward, it issues the CYED05 message until the device queue moves. When the device queue moves, CYED resets and starts the process over.

User Response: If the message continues, a manual intervention is required to analyze and correct the problem.

CYED0004IPOSSIBLE STALLED MODULE QUEUE FOR addr

Where:

addr
The device address.

Explanation: A nonempty queue is detected in the file status table for this device and this device has had no activity in the last three scans of the table. This indicates that the TPF system is probably running in a very stressed environment. If the capture function or the file copy function is running, this message may appear intermittently.

System Action: The normal CYED message sequence is: CYED01, CYED04, and CYED05. The first time CYED detects a device whose queue has not moved in two scans, it writes the CYED01 message and time stamps the device. On the next scan, if the device queue still has not moved, it issues the CYED04 message. Afterward, it issues the CYED05 message until the device queue moves. When the device queue moves, CYED resets and starts the process over.

User Response: If this message continues, a dump and manual intervention are required to analyze and correct the problem.

CYED0005IMODULE QUEUE FOR xxxx STALLED FOR ABOUT yyyy SECONDS, CURRENT QUEUE COUNT zzzzzz

Where:

xxxx
The device address.

yyyy
The approximate number of seconds the queue has been stalled.

zzzzz
The number of input/output blocks (IOBs) on the module queue.

Explanation: A nonempty queue is detected in the file status table for this device and this device has had no activity for three or more scans of the table. This indicates that the TPF system is probably running in a stressed environment and this message will appear intermittently.

System Action: None.

User Response: Manual intervention is required to analyze and correct the problem.

CYED0007WCFLF RECONNECT FAILED FOR DEVICE dddd SSID ssss

Where:

dddd
The device address for which a multi-path lock facility (MPLF) connect request was requested.

ssss
The associated DASD subsystem ID to which the device is attached.

Explanation: A path to the MPLF connect device has been lost. The attempt to connect to the device again over an alternate path failed.

System Action: None.

User Response: Manual intervention is required to analyze and correct the problem.

CYED0008TCFLF RECONNECT ABANDONED FOR SSID ssss

Where:

ssss
The DASD subsystem ID for which an attempt to establish a multi-path lock facility (MPLF) connect device has been abandoned.

Explanation: The DASD subsystem connect device was taken offline. The attempt to establish a new MPLF connect device on the DASD subsystem was abandoned because no usable modules were found.

System Action: None.

User Response: Manual intervention is required to analyze and correct the problem.

CYED0009ICFLF RECONNECT COMPLETE ON DEVICE dddd SSID ssss

Where:

dddd
The newly established multi-path lock facility (MPLF) connect device address.

ssss
The associated DASD subsystem ID to which the device is attached.

Explanation: The DASD subsystem connect device was taken offline. The attempt to establish a new MPLF connect device on the DASD subsystem completed successfully.

System Action: None.

User Response: None.

CYED0010Innnn MODULES WERE STALLED. SOME MESSAGES WERE SUPPRESSED.

Where:

nnnn
The total number of stalled module queues detected on this scan.

Explanation: During stalled module queue processing in CCSONS(CJIC), the indicated number of stalled modules were detected. Detailed diagnostic messages were previously issued for the first 50 stalled modules detected; all subsequent stalled module queue messages were suppressed.

System Action: The TPF system has performed the appropriate scanning and queue restart functions for all DASD modules. However, only the first 50 affected modules are individually reported.

User Response: Detailed diagnostic messages were issued for the first 50 stalled modules. Follow the user responses indicated for those diagnostic messages.

CYEM0100Eerrdesc, SSID-ssid, DVC-ccud, TYPE-tttt, MOD-sym, faddr, CHR-cccchhrr, CSW-stst, CCW-cc, SNS-ssssssss ssssssss ssssssss ssssssss, CHPID-path

Where:

errdesc
Message text varies based on the error condition.

ssid
The 3990 record cache subsystem (RCS) ID, if applicable.

ccud
The device address in hexadecimal.

tttt
The device type.

sym
The symbolic module in hexadecimal, which is only displayed when the module is a real-time module or the copy module.

faddr
One of the following:

FADR-fileaddr
The file address of the associated data record, where fileaddr is a 16-digit hexadecimal file address. This field is omitted if the operation is FNSPC, FLSPC, FDCTC, or the address is not in file address reference format (FARF).

MCHR-mmcchhrr
The file address of the associated data record, where mmcchhrr is a hexadecimal file address in MCHR format. This field is omitted when the operation is FDCTC.

cccchhrr
The cylinder, head, and record, in hexadecimal, where the I/O error occurred. This is omitted when there is no disk address associated with the error.

stst
Status bytes, in hexadecimal, of the channel status word.

cc
The command code, in hexadecimal, of the channel command word being processed during the error. This defaults to ** if there is no command code.

ssssssss
32 sense bytes if the device supports 32 sense bytes; otherwise, 24 sense bytes and 8 bytes of zeros are displayed.

path
1-byte channel path ID (CHPID) value, in hexadecimal, representing the last path used mask (LPUM) associated with the error.

Explanation: A hardware error or a channel program error has been detected.

System Action: None.

User Response: Do the following:

  1. Run the EREP utility to obtain more information about the error.
  2. Give the information collected in step 1 to your IBM service representative. If frequent errors continue, consider taking the device offline.

See the following publications from the IBM Storage Subsystem product library:

CYEN0099EDVC-ccud MOD-sym TAKEN OFF-LINE DUE TO errdesc

Where:

ccud
The device address (in hexadecimal).

sym
The symbolic module (in hexadecimal). The symbolic module is displayed only when the module is a real-time module or the copy module.

errdesc
Provides a brief description of why the module is being taken offline.

CC-3 ON ALL PATHS
Unable to communicate with the device over any defined path.

CFLF SUBSYSTEM FAILURE
The concurrency filter lock facility (CFLF) subsystem failed. See the information provided for the CYGN-prefixed messages that follow this message.

CHANNEL CHECKS
Channel checks were detected while trying to communicate with the device over all defined paths.

DEVICE NOT OPERATIONAL
There are path errors with the equipment check, and intervention required is set.

EQUIP CHECK
The device equipment check that caused the loss of paths.

EQUIP CHECK - PATH UNAVAILABLE
The equipment check on the path.

INTERNAL CONTROL I/O FAILURE
An internally-initiated recovery I/O operation failed to the device referenced in the message.

INTERVENTION REQUIRED
The device reported that intervention is required; loss of ready status.

LOST INTERRUPT
Unable to communicate with the device within a user-defined time period.

PERSISTENT LOCK FAILURE
An undefined multi-path lock facility (MPLF) return code was found while processing a lock input/output (I/O) operation. The device is taken offline following a 000706 system error.

PERSISTENT SENSE FAILURE
A sense failure was detected. After resetting and clearing the subchannel and retrying I/O, the sense failed again.

PINNED DATA CONDITION
An I/O operation failed because of a pinned data condition on the 3990 Record Cache Subsystem. An attempt is made to clear the pinned data for the device prior to taking the device offline.

RCS QUEUE THRESHOLD EXCEEDED
The TPF system was directed (through a user exit interface) to take the specified record cache subsystem (RCS) device offline because the total subsystem I/O queue exceeded a computed I/O queue threshold limit.

SUBCHANNEL REMOVED FROM CONFIGURATION
A channel report word (CRW) was received and an analysis by common input/output (CIO) indicates that the subchannel belonging to the specified device was deleted from the configuration. This is probably the result of detaching a device while running under the IBM Virtual Machine (VM) system.

RCS STATE-CHANGE-PENDING TIMER EXPIRED
A stalled device queue associated with an RCS device in the state change pending condition, persisted beyond the user specified time-out value.

Explanation: The device referenced in the message was taken offline because of the error referenced in the message. Depending on the cause of the failure, the CYEM0099E error message may accompany this message.

System Action: None.

User Response: Do the following:

  1. Determine the cause of the error.
  2. Correct the error.
  3. Enter the ZMCPY UP command to bring the module back online.

See TPF Operations for more information about the ZMCPY UP command.

CYF90001TUNABLE TO READ CTK9 (CYYM ERROR)

Explanation: Program CYF9 entered program CYYM to retrieve CTK9, but CYYM could not retrieve it.

System Action: Recoup processing ends.

User Response: Do the following:

  1. Determine the cause of the problem.
  2. Correct the problem.
  3. Start the function again.

CYGM0005WUNABLE TO RETRIEVE CTK9 WILL TRY AGAIN IN ONE MINUTE

Explanation: The CYYM monitor called program experienced a problem retrieving keypoint 9.

System Action: The monitor tries to retrieve keypoint 9 again in one minute. A CTL-0FB precedes this message indicating a possible DASD hardware error or system definition problem.

User Response: Review the system error dump to determine the cause of the error and to correct it.

CYGM0006WIN xxx devtype POOL, numaddr ADDRESSES HAVE BEEN ADDED

Where:

xxx
One of the following pool types: SLT, LLT, 4LT, SDP, LDP, 4DP, or 4D6.

devtype
The device type.

numaddr
The number of addresses from the pool type that were added.

Explanation: The number of available addresses for the pool type specified in this message has increased.

System Action: None.

User Response: None.

CYGM0007WEXCESSIVE USE OF xxx devtype ADDRS- numaddr USED IN LAST 3 MIN.

Where:

xxx
One of the following pool types: SLT, LLT, 4LT, SDP, LDP, 4DP, or 4D6.

devtype
The device type.

numaddr
The number of addresses from the pool type that were used in the last 3 minutes.

Explanation: The pool type specified in the message exceeded the usage limits set in keypoint 9 in the three previous 1-minute intervals. These limits can be set by entering the ZGFSP command.

System Action: None.

User Response: Do the following:

  1. Determine the cause of the excess usage.
  2. Adjust the limits, if needed, by entering the ZGFSP command.

CYGM0008Wxxx devtype POOL IS BELOW MINIMUM LIMIT, numaddr AVAILABLE

Where:

xxx
One of the following pool types: SLT, LLT, 4LT, SDP, LDP, 4DP, or 4D6.

devtype
The device type.

numaddr
The number of addresses available.

Explanation: The number of addresses available for the pool type specified in the message has fallen below the minimum level.

System Action: None.

User Response: Replenish the pool records through a directory update or a pool recoup.

CYGM0009WFACS ERROR ON CY2KT ORDINAL xx WILL TRY AGAIN IN ONE MINUTE

Where:

xx
Record ordinal number of a #CY2KT fixed file record.

Explanation: The pool monitor experienced a problem while retrieving a #CY2KT fixed file record.

System Action: The pool monitor tries to retrieve the #CY2KT fixed file record again in 1 minute.

User Response: Determine the cause of the problem and whether the pool monitor needs to be turned off by entering the ZGFSP OPT command with the NOMON parameter specified.

See TPF Operations for more information about the ZGFSP OPT command. See TPF System Macros and TPF Application Programming for more information about the file address compute (FACE) program and the FACE interface.

CYGM0010WFIND ERROR ON CY2KT ORDINAL xx WILL TRY AGAIN IN ONE MINUTE

Where:

xx
Record ordinal number of a #CY2KT fixed file record.

Explanation: The pool monitor experienced a problem while retrieving a #CY2KT fixed file record.

System Action: The pool monitor tries to retrieve the #CY2KT fixed file record again in 1 minute.

User Response: Determine the cause of the problem and whether the pool monitor needs to be turned off by entering the ZGFSP OPT command with the NOMON parameter specified.

See TPF Operations for more information about the ZGFSP OPT command. See TPF General Macros and TPF Application Programming for more information about find errors.

CYGM0011Wxxx devtype POOL USE HAS EXCEEDED LIMIT. numaddr ADDRESSES USED IN LAST MIN.

Where:

xxx
One of the following pool types: SLT, LLT, 4LT, SDP, LDP, 4DP, and 4D6.

devtype
The device type.

numaddr
The number of addresses from pool type that were used in the last minute.

Explanation: The pool type specified in the message exceeded the usage limits set in keypoint 9 in the last minute. These limits can be set by entering the ZGFSP command.

System Action: None.

User Response: Do the following:

  1. Determine the cause of the excess usage.
  2. Adjust the limits, if needed, by entering the ZGFSP command.

CYGN0001ECFLF ERROR CODE ret_code ON

Where:

ret_code
The return code.

Explanation: An abnormal return code is returned from a concurrency filter lock facility (CFLF) operation. This message is followed by the CYGN0002I message to identify the subsystem on which the error occurred.

System Action: Processing is continued.

User Response: None.

See 3990 Transaction Processing Facility Support RPQs for more information about the return codes.

CYGN0002IDASD SUBSYSTEM ID ssid

Where:

ssid
The subsystem identifier.

Explanation: This message accompanies the CYGN01E, CYGN03I, and CYGN09W messages to identify the subsystems these messages refer to.

System Action: Processing is continued.

User Response: None.

CYGN0003ILOCK RECOVERY STARTING

Explanation: Lock recovery has started. This message is preceded by the CYGN0002I message to indicate the subsystem ID on which the recovery is taking place.

System Action: Lock recovery processing is continued.

User Response: None.

CYGN0004ISUBSYSTEM IN LOCK SUSPENSE

Explanation: This message is issued during lock recovery to inform you that all modules on the affected subsystem are placed in lock-suspended state

System Action: Lock recovery processing is continued.

User Response: None.

CYGN0005ISUBSYSTEM CLEARED

Explanation: This message is issued during lock recovery to inform you that global disconnect orders were completed. The affected subsystem is cleared and ready to be rebuilt.

System Action: Lock recovery processing is continued.

User Response: None.

CYGN0006ISUBSYSTEM RECONNECTED

Explanation: This message is issued during lock recovery to inform you that reconnect orders were completed. Each processor is reconnected to the affected subsystem.

System Action: Lock recovery processing is continued.

User Response: None.

CYGN0007ILOCK RECOVERY COMPLETED

Explanation: Lock recovery is complete. Modules on the affected subsystems are now usable.

System Action: The TPF system is now available for use.

User Response: None.

CYGN0008ELOCK RECOVERY FAILURE

Explanation: Lock recovery cannot complete because:

System Action: The modules are brought offline.

User Response: Do the following:

  1. Correct the affected subsystem.
  2. Bring the modules back online.

See 3990 Transaction Processing Facility Support RPQs for more information.

CYGN0009WSUBSYSTEM IS BEING TAKEN DOWN

Explanation: This message is issued when the lock recovery fails and, as a result, a permanent concurrency filter lock facility (CFLF) error occurs.

System Action: All of the modules on the subsystem are taken offline.

User Response: Do the following:

  1. Correct the affected subsystem.
  2. Bring the modules back online.

See 3990 Transaction Processing Facility Support RPQs for more information.

CYGN0010ERECOVERY DISCONNECT/RECONNECT FAILURE

Explanation: During concurrency filter lock facility (CFLF) lock recovery processing, CYGN is unable to disconnect or reconnect to the affected subsystem.

System Action: The subsystem is brought offline.

User Response: Do the following:

  1. Correct the affected subsystem.
  2. Bring the modules back online.

See 3990 Transaction Processing Facility Support RPQs for more information.

CYGN0011ERECOVERY EVENT NOT FOUND

Explanation: During concurrency filter lock facility (CFLF) lock recovery processing and while CYGN is requesting various functions, an event is not found.

System Action: The subsystem is brought offline.

User Response: Do the following:

  1. Correct the affected subsystem.
  2. Bring the modules back online.

See 3990 Transaction Processing Facility Support RPQs for more information.

CYGR0001TPXP MIGRATION NOT COMPLETE ON SS-ssuname

Where:

ssuname
The subsystem user (SSU) name.

Explanation: Pool expansion migration was not completed before integrated online pool maintenance and recoup support was installed on the TPF system.

System Action: State change is disabled, and restart processing is stopped.

User Response: Do the following:

  1. Bring up the TPF system with the old image.
  2. Follow the instructions in TPF Migration Guide: Program Update Tapes for pool expansion migration.
  3. Follow the instructions in TPF Migration Guide: Program Update Tapes for integrated online pool maintenance and recoup support migration.

See TPF Migration Guide: Program Update Tapes for more information about pool expansion and integrated online pool maintenance and recoup support migration.

CYGR0002TSTORAGE CARVED FOR POOL STRUCTURES WAS TOO SMALL. CARVE SIZE HAS BEEN RESET FOR THE NEXT IPL.

Explanation: Storage carved by the CTIN programs for pool structures is based on an aggregate carve size value stored in keypoint B. When segment CYGR attempted to use this storage to set up various pool structures, the storage was found to be too small. The correct amount of storage required has been calculated and stored in keypoint B. The correct value is used the next time you IPL the TPF system.

System Action: State change is disabled and restart processing is stopped.

User Response: IPL the TPF system again to pick up the corrected storage carve size value.

CYGR0099TPOOL RESTART FAILED - STATE CHANGE DISABLED.

Explanation: A severe error occurred causing pool restart processing to fail. To obtain diagnostic information, view the console for online message CYGR0001T or CYGR0002T, or system error message 000690, 000698, 00069A, or 00069B.

System Action: Restart processing is stopped with state change disabled.

User Response: See the user response for the online error message CYGR0001T or CYGR0002T, or system error 000690, 000698, 00069A, or 00069B to correct the problem.

CYYE0050EERROR OCCURRED DURING FILING OF KEYPOINT C

Explanation: The CYYA program returned an error to the CYYE program while trying to file the updated core copy of keypoint C.

System Action: None.

User Response: Do the following:

  1. Review the system error dump to determine the cause of the error.
  2. Correct the error.

See TPF Operations for more information about displaying keypoint C.

CYYE0051EERROR OCCURRED DURING FINDING OF KEYPOINT C

Explanation: The CYYA program returned an error to the CYYE program while trying to retrieve the file copy of keypoint C.

System Action: None.

User Response: Do the following:

  1. Review the system error dump to determine the cause of the error.
  2. Correct the error.

See TPF Operations for more information about displaying keypoint C.

CZSA0001ESYSPLEX TIMER SYNCHRONISM CHECK

Explanation: The sysplex timer (STR) machine check handler (CZSA) issues this message when a machine check interruption reports an STR synchronism check.

System Action: None.

User Response: None.

See TPF Main Supervisor Reference for more information about machine check handling. Also see ESA/390 Principles of Operation for more information about machine check handling.