gtpm5m0hMessages (Online)

CACH-CBL1

CACH0001ICACHE CONTROL AREA HAS NOT BEEN ALLOCATED

Explanation: The ZCACH command was entered with the DISPLAY and CTL parameters specified to display the names of the current logical record caches and their addresses from main storage, but there are none currently defined.

System Action: The command is rejected.

User Response: None.

See TPF Operations for more information about the ZCACH command.

CACH0002ICACHE CONTROL AREA DISPLAY

Explanation: This is the normal response to the ZCACH command with the DISPLAY and CTL parameters specified to display the names of the current logical record caches and their addresses from main storage.

System Action: The names and addresses of the logical record caches that are currently defined in the cache control area are displayed.

User Response: None.

See TPF Operations for more information about the ZCACH command and for an example of the informational display.

CACH0003ECACHE lcache NOT FOUND

Where:

lcache
The name of the logical record cache.

Explanation: The ZCACH command was entered with the name of a logical record cache specified, but that logical record cache name was not found in the cache control area.

System Action: The entry control block (ECB) exits.

User Response: Enter the ZCACH command with the DISPLAY and CTL parameters specified to display the names of all logical record caches that are currently active.

See TPF Operations for more information about the ZCACH command.

CACH0004ICACHE ATTRIBUTE DISPLAY

Explanation: This is the normal response to the ZCACH command with the DISPLAY and ATTRIBUTE parameters specified to display specific information about the specified logical record cache and the associated coupling facility (CF).

System Action: Processing was completed successfully with information about the logical record cache and the associated CF displayed.

User Response: None.

See TPF Operations for more information about the ZCACH command and for an example of the informational display.

CACH0005ICACHE DATA COLLECTION COUNTER DISPLAY

Explanation: This is the normal response to the ZCACH command with the DISPLAY and COUNTS parameters specified to display the current data collection counters for a specific logical record cache.

System Action: Processing was completed successfully with information about the current data collection counters for the specific logical record cache displayed.

User Response: None.

See TPF Operations for more information about the ZCACH command and for an example of the informational display.

CACH0006ICACHE SYNONYM DISPLAY

Explanation: This is the normal response to the ZCACH command with the DISPLAY and SYNONYM parameters specified to display synonym chain length information for a specific logical record cache.

System Action: Processing was completed successfully with information about the synonym chain length (or hash entries) for the specific logical record cache displayed.

User Response: None.

See TPF Operations for more information about the ZCACH command and for an example of the informational display.

CACH0008EERROR RETRIEVING COUNTERS

Explanation: The ZCACH command was entered with the DISPLAY and COUNTS parameters specified to display the current data collection counters for the specified logical record cache, but an error occurred while trying to retrieve the counter values.

System Action: The entry control block (ECB) exits.

User Response: Do the following:

  1. Enter the ZCACH command again.
  2. If the error continues, see your system programmer to determine the cause of the problem and to correct it.

See TPF Operations for more information about the ZCACH command.

CACH0009EERROR RETRIEVING CACHE CONTROL RECORD

Explanation: The ZCACH command was entered to manage the logical record caches, but an error occurred while trying to find the processor unique logical record cache control record. This error occurs if the processor unique logical record cache control record has not been initialized yet by entering at least one ZCACH command with the MODIFY parameter or the CF ENABLE parameter specified.

System Action: The entry control block (ECB) exits

User Response: Do one of the following:

See TPF Operations for more information about the ZCACH command.

CACH0010EFACE ERROR ON CACHE CONTROL RECORD

Explanation: The ZCACH command was entered to modify or display information about the logical record caches, but an error occurred in the file address compute (FACE) program when the file address of the processor unique logical record cache control record could not be resolved.

System Action: The entry control block (ECB) exits.

User Response: Do one of the following:

See TPF Operations for more information about the ZCACH command. See TPF System Generation for more information about the processor unique logical record cache control record and the FCTB.

CACH0011ECACHE CONTROL RECORD NOT INITIALIZED, CACHE lcache NOT FOUND

Where:

lcache
The name of the logical record cache.

Explanation: The ZCACH command was entered with the REMOVE parameter specified for the specified logical record cache, but the processor unique logical record cache control record has not been initialized yet so the specified logical record cache was not found.

System Action: The entry control block (ECB) exits.

User Response: None.

See TPF Operations for more information about the ZCACH command.

CACH0013ECF, DELETE, FLUSH, MODIFY OR REMOVE MUST BE ISSUED FROM THE BSS SUBSYSTEM

Explanation: The ZCACH command was entered with the CF, DELETE, FLUSH, MODIFY, or REMOVE parameter specified, but an error occurred because the command was not entered from the basic subsystem (BSS).

System Action: The entry control block (ECB) exits.

User Response: Enter the ZCACH command again from the BSS with the appropriate parameter specified.

See TPF Operations for more information about the ZCACH command.

CACH0016ICACHE lcache SUCCESSFULLY REMOVED

Where:

lcache
The name of the logical record cache.

Explanation: This is the normal response to the ZCACH command with the REMOVE parameter specified.

System Action: The cache definition for the specified logical record cache is removed from the processor unique logical record cachecontrol record.

User Response: None.

See TPF Operations for more information about the ZCACH command.

CACH0017ICACHE lcache SUCCESSFULLY MODIFIED

Where:

lcache
The name of the logical record cache.

Explanation: This is the normal response to the ZCACH command with the MODIFY parameter specified to change the number of entries for the logical record cache specified in the processor unique logical record cache control record.

System Action: The number of entries for the logical record cache specified in the processor unique logical record cache control record is changed.

User Response: None.

See TPF Operations for more information about the ZCACH command.

CACH0018ENO ENTRIES AVAILABLE IN CACHE CONTROL RECORD FOR MODIFICATION OF CACHE lcache

Where:

lcache
The name of the logical record cache.

Explanation: The ZCACH command with the MODIFY parameter specified was entered to change the number of entries for the logical record cache in the processor unique logical record cache control record, but an error occurred because the processor unique logical record cache control record contains the maximum entries allowed and has no available entries remaining to satisfy the current request.

System Action: The entry control block (ECB) exits.

User Response: Do the following:

  1. Enter the ZCACH command with the DISPLAY, CTL, and FILE parameters specified to display information about the logical record caches currently defined in the processor unique logical record cache control record.
  2. Determine if a definition for a logical record cache can be removed from the processor unique logical record cache control record to make room for the current request. If so, go to step 3; otherwise, there is no more action for you to take.
  3. Enter the ZCACH command with the REMOVE parameter specified to remove the definition for the logical record cache from the processor unique logical record cache control record.
  4. Enter the ZCACH command again with the MODIFY parameter specified to define a logical record cache in the processor unique logical record cache control record.

See TPF Operations for more information about the ZCACH command.

CACH0019ICACHE SUPPORT ENABLED TO USE CF

Explanation: This is the normal response to the ZCACH command with the CF ENABLE parameter specified to enable the processor shared caches to use coupling facilities (CFs) for cache synchronization.

System Action: The TPF system successfully set the indicator to allow CFs to synchronize the processor shared caches and successfully tried to connect all active processor-shared caches in all processors to the coupling facilities (CFs) that are currently defined.

User Response: None.

See TPF Operations for more information about the ZCACH command. See TPF Database Reference for more information about logical record cache and CF cache support.

CACH0020ICACHE SUPPORT DISABLED FOR USE OF CF. ALL ACTIVE SHARED CACHES SET TO LOCAL

Explanation: This is the normal response to the ZCACH command with the CF DISABLE parameter specified to disable the processor shared caches from using the coupling facility (CF) for cache synchronization.

System Action: The TPF system successfully reset the indicator to disallow use of the CF to synchronize the processor shared caches and successfully disconnected all active processor shared caches in all processors from the CFs.

User Response: None.

See TPF Operations for more information about the ZCACH command. See TPF Database Reference for more information about logical record cache and CF cache support.

CACH0022ICACHE lcache SUCCESSFULLY DELETED

Where:

lcache
The name of the logical record cache.

Explanation: This the normal response to the ZCACH command with the DELETE parameter specified.

System Action: The logical record cache is deleted from the processor.

User Response: None.

See TPF Operations for more information about the ZCACH command.

CACH0023ICACHE lcache SUCCESSFULLY FLUSHED

Where:

lcache
The name of the logical record cache.

Explanation: This is the normal response to the ZCACH command with the FLUSH parameter specified.

System Action: The entries are cleared from the logical record cache.

User Response: None.

See TPF Operations for more information about the ZCACH command.

CACH0024EERROR CONNECTING TO CF FOR CACHE lcache

Where:

lcache
The name of the logical record cache.

Explanation: An error occurred when the processor tried to connect to the CF for cache synchronization for the logical record cache specified.

System Action: The entry control block (ECB) exits.

User Response: Review the previous messages that were displayed to determine the cause of the error and correct it.

See TPF Database Reference for more information about logical record cache and CF cache support.

CACH0025EERROR DISCONNECTING FROM THE CF FOR CACHE lcache

Where:

lcache
The name of the logical record cache.

Explanation: An error occurred when the processor tried to disconnect from the coupling facility (CF) that was used for cache synchronization for the logical record cache specified.

System Action: The entry control block (ECB) exits.

User Response: Review the previous messages that were displayed to determine the cause of the error and correct it.

See TPF Database Reference for more information about logical record cache and CF cache support.

CACH0026ICACHE CONTROL RECORD DISPLAY

Explanation: This is the normal response to the ZCACH command with the DISPLAY, CTL, and FILE parameters specified.

System Action: The names of the logical record caches that are currently defined in the processor unique logical record cache control record and their assigned sizes are displayed.

User Response: None.

See TPF Operations for more information about the ZCACH command.

CACH0027ENO LOCKING CF DEFINED, CANNOT ENABLE CF FOR CACHE

Explanation: The ZCACH command was entered with the CF ENABLE parameter specified to enable the processor shared caches to use the coupling facility (CF) for cache synchronization, but no CFs have been added to the CF locking configuration by entering the ZCFLK ADD command.

System Action: The entry control block (ECB) exits.

User Response: Do the following:

  1. Enter the ZCFLK ADD command to add a CF to the CF locking configuration, which then enables the CF for use as an external locking facility (XLF) so new locks can be stored on it.
  2. Enter the ZCACH command again with the CF ENABLE parameter specified.

See TPF Operations for more information about the ZCACH andZCFLK ADD commands.

CACH0032WALL CACHES NOW OPERATING IN LOCAL MODE

Explanation: An error occurred because the last coupling facility (CF) in the CF locking configuration has been lost. The logical record caches have fallen back to local mode where entries are cast out depending on the passed timeout value rather than cross invalidates from other processors.

System Action: The logical record caches have fallen back to local mode where entries are cast out depending on the passed timeout value rather than cross invalidates from other processors.

User Response: None.

See TPF Database Reference for more information.

CACH0034WERROR CONNECTING TO CF, CACHE lcache LEFT IN LOCAL MODE

Where:

lcache
The name of the logical record cache.

Explanation: The TPF system was unable to successfully create or connect the logical record cache specified to the corresponding coupling facility (CF) cache structure.

System Action: The CF cache structure operates in local mode where entries are cast out depending on the passed time out value rather than the cross invalidates from other processors.

User Response: Do the following:

  1. Determine the cause of the problem (what prevented the successful use of the CF) and correct it.
  2. Enter the ZCACH command with the CF ENABLE parameter specified to enable the processor shared caches to use the CF for cache synchronization.

See TPF Operations for more information about the ZCACH command.

CANT0001IANT LOAD SUCCESSFUL

Explanation: This is the normal response after the application name table was loaded into core successfully.

System Action: None.

User Response: None.

CBC00001AUNABLE TO OBTAIN BUFFER FOR MPIF FUNCTION

Explanation: While trying to obtain a Multi-Processor Interconnect Facility MPIF) buffer to perform a MPIF function, a series of failures occurred.

System Action: The buffer is not obtained and the requesting function is so informed. The requesting function normally generates additional messages.

User Response: Have your system programmer determine the cause of the error and correct it.

CBC00002AUNABLE TO LOCATE AVAILABLE SLOT IN tbl TABLE.

Where:

tbl
The table name.

Explanation: While trying to process a connect request, no available entry was located in the table referenced in the message.

System Action: The connect request was not processed. The calling user function was notified and will normally generate additional messages.

User Response: Have your system programmer determine the cause of the error and correct it.

The number of entries to be allocated for the table in question can be changed by entering a ZMPIF SET command.

See TPF Operations for more information about the ZMPIF SET command.

CBC10002AUNABLE TO LOCATE AVAILABLE SLOT IN table TABLE

Where:

table
The table name.

Explanation: While trying to process an identify request, no available entry was located in the table referenced in the message.

System Action: The identify request was not processed. The calling user function was notified and will normally generate additional messages.

User Response: Have your system programmer determine the cause of the error and correct it.

The number of entries to be allocated for the table in question can be changed by entering a ZMPIF SET command.

See TPF Operations for more information about the ZMPIF SET command.

CBC30050ECONNECTION TIME-OUT BETWEEN user1 AND user2 IN SYSTEM systemname

Where:

user1
The first user ID.

user2
The second user ID.

systemname
The TPF system name.

Explanation: The first user referenced in the message requested a connection with the second user in the TPF system referenced in the message. The second user did not respond within the required time period.

System Action: The connect request is ended. A connect failure message is sent to the TPF system referenced in the message. The connect complete exit for user user1 is activated to provide notification that the connect request failed.

User Response: None.

CBG20002WFACE ERROR ON PATH DEFINITION RECORD ORDINAL 1 -- MPIF COMPLEX DATA UPDATE FAILED

Explanation: While trying to update data in keypoint E, CBG2 was unable to acquire a valid file address for the path definition record (PDR), ordinal 1. Multi-Processor Interconnect Facility (MPIF) data used by CTIN on the next initial program load (IPL) may not be correct.

System Action: MPIF restart is aborted. The TPF system goes to 1052 state and state change is disable.

User Response: Have your system programmer determine the cause of the error and correct it.

MPIF data in keypoint E may need to be reinitialized by using MPIF commands. Check the 00156 system error dump for the cause of the error. It corruption is suspected, the cause should be determined.

CBG20003WFIND ERROR ON PATH DEFINITION RECORD ORDINAL 1 -- F.A. address - MPIF COMPLEX DATA UPDATE FAILED

Where:

address
The address.

Explanation: While trying to update data in keypoint E, CBG2 was unable to retrieve the path definition record (PDR), ordinal 1. Multi-Processor Interconnect Facility (MPIF) data used by CTIN on the next initial program load (IPL) may not be correct.

System Action: MPIF restart is aborted. The TPF system goes to 1052 state and state change is disabled.

User Response: Have your system programmer determine the cause of the error and correct it. MPIF data in keypoint E may need to be reinitialized by using MPIF commands. Check the 00156 system error dump for the cause of the error. If corruption is suspected, the cause should be determined.

CBG20004WKEYPOINT CTKE FOR PROCESSOR pp CANNOT BE RETRIEVED -- MPIF COMPLEX DATA UPDATE FAILED

Where:

pp
The processor name.

Explanation: While trying to update data in keypoint E, CBG2 was unable to retrieve the keypoint (error was returned from CYYD). Multi-Processor Interconnect Facility (MPIF) data used by CTIN on the next IPL may not be correct.

System Action: MPIF restart is aborted. The TPF system goes to 1052 state and state change is disabled.

User Response: Have your system programmer determine the cause of the error and correct it. MPIF data in keypoint E may need to be reinitialized by using MPIF commands. Check the 00156 system error dump for the cause of the error. If corruption is suspected, the cause should be determined.

CBG20005WKEYPOINT CTKE FOR PROCESSOR pp CANNOT BE FILED -- MPIF COMPLEX DATA UPDATE FAILED

Where:

pp
The processor name.

Explanation: While trying to rebuild data in keypoint E, CBG2 was unable to file the updated keypoint (error returned from CYYB). Multi-Processor Interconnect Facility (MPIF) data used by CTIN on the next initial program load (IPL) may not be correct.

System Action: MPIF restart is aborted. The TPF system goes to 1052 state and state change is disabled.

User Response: Have your system programmer determine the cause of the error and correct it. MPIF data in keypoint E may need to be reinitialized by using MPIF commands. Check the 00156 system error dump for the cause of the error. If corruption is suspected, the cause should be determined.

CBG20006WFILE ERROR ON PATH DEFINITION RECORD ORDINAL 1 -- F.A. address - MPIF COMPLEX DATA UPDATE FAILED

Where:

address
The address.

Explanation: CBG2 was unable to file the path definition record (PDR), ordinal 1. Multi-Processor Interconnect Facility (MPIF) data used by CTIN on the next initial program load (IPL) may not be correct.

System Action: MPIF restart is aborted. The TPF system goes to 1052 state and state change is disabled.

User Response: Have your system programmer determine the cause of the error and correct it. MPIF data in keypoint E may need to be reinitialized by using MPIF commands. Check the 00156 system error dump for the cause of the error. If corruption is suspected, the cause should be determined.

CBG20051IMPIF CONVERSION COMPLETE, PDR RECORDS ARE NOW SAFE FOR GREATER THAN 8-WAY LOOSELY COUPLED

Explanation: This is the normal response to the ZMIGR command with the MPIF and CONVERT parameters specified.

System Action: #PDREC ordinal 2 and #PDREC ordinal 3 are copied to #IBMM4 ordinal X'A9' and #IBMM4 ordinal X'AA' respectively as save areas for fallback. #PDREC ordinals 2 and 3 are initialized for use as an extension of Multiprocessor Processor Interconnect Facility (MPIF) system data to support 32 processors.

User Response: None.

See TPF Operations for more information about the ZMIGR command.

CBG20052IMPIF FALLBACK COMPLETE, PDR RECORDS ARE NOT SAFE FOR GREATER THAN 8-WAY LOOSELY COUPLED

Explanation: This is the normal response to the ZMIGR command with the MPIF and FALLBACK parameters specified.

System Action: #PDREC ordinal 2 and #PDREC ordinal 3 are copied from #IBMM4 ordinal X'A9' and #IBMM4 ordinal X'AA' respectively. PDREC ordinals 2 and 3 are not used as an extension of Multiprocessor Processor Interconnect Facility (MPIF) system data to support 32 processors.

User Response: None.

See TPF Operations for more information about the ZMIGR command.

CBG20053IMPIF IS NOT CONVERTED FOR GREATER THAN 8-WAY LOOSELY COUPLED

Explanation: This is the normal response to the ZMIGR command with the MPIF and STATUS parameters specified.

System Action: The current state of Multiprocessor Processor Interconnect Facility (MPIF) readiness for greater than 8-way loosely coupled processors is displayed.

User Response: None.

See TPF Operations for more information about the ZMIGR command.

CBG20054IMPIF IS CONVERTED FOR GREATER THAN 8-WAY LOOSELY COUPLED

Explanation: This is the normal response to the ZMIGR command with the MPIF and STATUS parameters specified.

System Action: The current state of Multiprocessor Processor Interconnect Facility (MPIF) readiness for greater than 8-way loosely coupled processors is displayed.

User Response: None.

See TPF Operations for more information about the ZMIGR command.

CBI00002AUNABLE TO LOCATE AVAILABLE SLOT IN table TABLE.

Where:

table
The table name.

Explanation: While trying to process an identify request no available entry was located in the table referenced in the message.

System Action: The identify request was not processed. The calling user function was notified and normally generates additional messages.

User Response: Have your system programmer determine the cause of the error and correct it. The number of entries to be allocated for the table in question can be changed by entering a ZMPIF SET command.

See TPF Operations for more information about the ZMPIF SET command.

CBJ00002AUNABLE TO LOCATE AVAILABLE SLOT IN table TABLE.

Where:

table
The table name.

Explanation: While trying to process a query request no available entry was located in the table referenced in the message.

System Action: The query request was not processed. The calling user function was notified and normally generates additional messages.

User Response: Have your system programmer determine the cause of the error and correct it. The number of entries to be allocated for the table in question can be changed by entering a ZMPIF SET command.

See TPF Operations for more information about the ZMPIF SET command.

CBL00001ISTOP PATH WITH QUIESCE COMPLETED FOR PATH path

Where:

path
The path name.

Explanation: A stop path purge-no request completed for the path referenced in the message.

System Action: None.

User Response: None.

CBL10040WLOST INTERRUPT HAS OCCURRED ON PATH path, PATH HALTED

Where:

path
The path name.

Explanation: The Multi-Processor Interconnect Facility (MPIF) path monitor detected a potential lost interrupt on the path referenced in the message.

System Action: The path is halted and the associated device links are primed again.

User Response: None.