gtpm5m14 | Messages (Online) |
CYEA0022I | SUBSYSTEM STORAGE PHYSICALLY ENABLED ON RCS SSID ssss |
Where:
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.
CYEA0023I | NONVOLATILE STORAGE PHYSICALLY ENABLED ON RCS SSID ssss |
Where:
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.
CYEA0024I | FAST WRITE FUNCTIONS RESUMED ON RCS SSID ssss |
Where:
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.
CYEA0025W | FAST WRITE FUNCTIONS SUSPENDED ON RCS SSID ssss |
Where:
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.
CYEA0026I | IML DEVICE AVAILABLE ON RCS SSID ssss |
Where:
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.
CYEA0027I | CACHE FAST WRITE ACTIVATED ON RCS SSID ssss |
Where:
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.
CYEA0028W | NONVOLATILE STORAGE BATTERY DEFECTIVE ON RCS SSID ssss |
Where:
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.
CYEA0029A | CACHING TERMINATED ON RCS SSID ssss DUE TO SUBSYSTEM STORAGE MALFUNCTION. |
Where:
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.
CYEA0030A | DASD FAST WRITE TERMINATED ON RCS SSID ssss DUE TO NONVOLATILE CACHE MALFUNCTION. |
Where:
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.
CYEA0051W | POSSIBLE CACHE FAST WRITE DATA LOSS FOR RCS SSID ssss |
Where:
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.
CYEA0053W | CACHING DEACTIVATED ON RCS SSID ssss DUE TO EXPLICIT HOST REQUEST |
Where:
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.
CYEA0054W | CACHE FAST WRITE DEACTIVATED ON RCS SSID ssss |
Where:
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.
CYEA0055W | NONVOLATILE CACHE DEACTIVATED ON RCS SSID ssss DUE TO EXPLICIT HOST REQUEST. |
Where:
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.
CYEA0058W | CACHING DEACTIVATED FOR DEVICE dddd ON RCS SSID ssss |
Where:
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.
CYEA0083I | CACHING ACTIVE ON RCS SSID ssss |
Where:
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.
CYEA0084I | CACHING IS PENDING ACTIVE ON RCS SSID ssss |
Where:
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.
CYEA0085W | CACHE SUSPENDED ON RCS SSID ssid |
Where:
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:
CYEA0086W | CACHING PENDING OFF IN PROGRESS ON RCS SSID ssss |
Where:
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.
CYEA0087I | NVS ACTIVE ON RCS SSID ssss |
Where:
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.
CYEA0089W | NVS DEACTIVATE PENDING ON RCS SSID ssss |
Where:
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.
CYEA0090I | CACHING ACTIVATED FOR DEVICE dddd ON RCS SSID ssss |
Where:
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.
CYEA0092I | DASD FAST WRITE ALLOWED FOR DEVICE dddd ON RCS SSID ssss |
Where:
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.
CYEA0093W | FAST WRITE SUSPENDED FOR DEVICE dddd RCS SSID ssss DUE TO PINNED DATA |
Where:
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.
CYEA0094I | RECORD MODE ALLOWED FOR DEVICE dddd ON RCS SSID ssss |
Where:
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.
CYEA0095I | NO PINNED DATA EXISTS FOR DEVICE dddd ON RCS SSID ssss |
Where:
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.
CYEA0096W | PINNED DATA EXISTS FOR DEVICE dddd ON RCS SSID ssss |
Where:
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.
CYED0001I | MODULE QUEUE FOR xxxx MAY BE STALLED. |
Where:
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.
CYED0004I | POSSIBLE STALLED MODULE QUEUE FOR addr |
Where:
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.
CYED0005I | MODULE QUEUE FOR xxxx STALLED FOR ABOUT yyyy SECONDS, CURRENT QUEUE COUNT zzzzzz |
Where:
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.
CYED0007W | CFLF RECONNECT FAILED FOR DEVICE dddd SSID ssss |
Where:
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.
CYED0008T | CFLF RECONNECT ABANDONED FOR SSID ssss |
Where:
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.
CYED0009I | CFLF RECONNECT COMPLETE ON DEVICE dddd SSID ssss |
Where:
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.
CYED0010I | nnnn MODULES WERE STALLED. SOME MESSAGES WERE SUPPRESSED. |
Where:
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.
CYEM0100E | errdesc, SSID-ssid, DVC-ccud, TYPE-tttt, MOD-sym, faddr, CHR-cccchhrr, CSW-stst, CCW-cc, SNS-ssssssss ssssssss ssssssss ssssssss, CHPID-path |
Where:
Explanation: A hardware error or a channel program error has been detected.
System Action: None.
User Response: Do the following:
See the following publications from the IBM Storage Subsystem product library:
CYEN0099E | DVC-ccud MOD-sym TAKEN OFF-LINE DUE TO errdesc |
Where:
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:
See TPF Operations for more information about the ZMCPY UP command.
CYF90001T | UNABLE 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:
CYGM0005W | UNABLE 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.
CYGM0006W | IN xxx devtype POOL, numaddr ADDRESSES HAVE BEEN ADDED |
Where:
Explanation: The number of available addresses for the pool type specified in this message has increased.
System Action: None.
User Response: None.
CYGM0007W | EXCESSIVE USE OF xxx devtype ADDRS- numaddr USED IN LAST 3 MIN. |
Where:
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:
CYGM0008W | xxx devtype POOL IS BELOW MINIMUM LIMIT, numaddr AVAILABLE |
Where:
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.
CYGM0009W | FACS ERROR ON CY2KT ORDINAL xx WILL TRY AGAIN IN ONE MINUTE |
Where:
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.
CYGM0010W | FIND ERROR ON CY2KT ORDINAL xx WILL TRY AGAIN IN ONE MINUTE |
Where:
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.
CYGM0011W | xxx devtype POOL USE HAS EXCEEDED LIMIT. numaddr ADDRESSES USED IN LAST MIN. |
Where:
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:
CYGN0001E | CFLF ERROR CODE ret_code ON |
Where:
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.
CYGN0002I | DASD SUBSYSTEM ID ssid |
Where:
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.
CYGN0003I | LOCK 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.
CYGN0004I | SUBSYSTEM 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.
CYGN0005I | SUBSYSTEM 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.
CYGN0006I | SUBSYSTEM 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.
CYGN0007I | LOCK 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.
CYGN0008E | LOCK RECOVERY FAILURE |
Explanation: Lock recovery cannot complete because:
System Action: The modules are brought offline.
User Response: Do the following:
See 3990 Transaction Processing Facility Support RPQs for more information.
CYGN0009W | SUBSYSTEM 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:
See 3990 Transaction Processing Facility Support RPQs for more information.
CYGN0010E | RECOVERY 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:
See 3990 Transaction Processing Facility Support RPQs for more information.
CYGN0011E | RECOVERY 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:
See 3990 Transaction Processing Facility Support RPQs for more information.
CYGR0001T | PXP MIGRATION NOT COMPLETE ON SS-ssuname |
Where:
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:
See TPF Migration Guide: Program Update Tapes for more information about pool expansion and integrated online pool maintenance and recoup support migration.
CYGR0002T | STORAGE 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.
CYGR0099T | POOL 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.
CYYE0050E | ERROR 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:
See TPF Operations for more information about displaying keypoint C.
CYYE0051E | ERROR 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:
See TPF Operations for more information about displaying keypoint C.
CZSA0001E | SYSPLEX 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.