gtpm5m0mMessages (Online)

CFLK - CFL2

CFLK0002Isegment - COUPLING FACILITY cfname WAS ADDED TO THE LOCKING CONFIGURATION

Where:

segment
The name of the segment that added the coupling facility (CF).

cfname
The name of the CF.

Explanation: The ZCFLK ADD command was entered to add a coupling facility (CF) to the CF locking configuration. This message indicates that the CF referenced in the message was added successfully to the CF locking configuration.

System Action: The coupling facility locking table (CFLT) was updated to indicate that the CF was added to the CF locking configuration.

User Response: None.

See TPF Operations for more information about the ZCFLK ADD command.

CFLK0003Isegment - COUPLING FACILITY cfname WAS DELETED FROM THE LOCKING CONFIGURATION

Where:

segment
The name of the segment that deleted the coupling facility (CF).

cfname
The name of the CF.

Explanation: The ZCFLK DELETE command was entered to remove a CF from the CF locking configuration. This message indicates that the CF referenced in the message was deleted successfully from the CF locking configuration.

System Action: The coupling facility locking table (CFLT) was updated to indicate that the CF was deleted from the CF locking configuration.

User Response: None.

See TPF Operations for more information about the ZCFLK DELETE command.

CFLK0004Isegment - ZCFLK MIGRATE PROCESSING COMPLETE

Where:

segment
The name of the segment that migrates lock residency.

Explanation: This is the normal response to the ZCFLK MIGRATE command. The lock residency for the modules in the coupling facility (CF) locking configuration was changed successfully from either a locking control unit (CU) to a CF, or from a CF to a locking CU.

System Action: None.

User Response: None.

See TPF Operations for more information the ZCFLK MIGRATE command.

CFLK0005Esegment - MIGRATE ENDED - NO ADDED COUPLING FACILITIES IN THE LOCKING CONFIGURATION

Where:

segment
The name of the segment that detected the error.

Explanation: The ZCFLK MIGRATE command was entered to change the lock residency of modules. An error occurred because there were no coupling facilities (CFs) added to the CF locking configuration from which to migrate to or from.

System Action: The command is rejected.

User Response: Do the following:

  1. Enter the ZMCFT DISPLAY command to determine which CFs exist in the processor configuration.
  2. Enter the ZCFLK ADD command to add a CF to the CF locking configuration

See TPF Operations for more information about the ZCFLK and ZMCFT commands.

CFLK0006Esegment - UNABLE TO READ COUPLING FACILITY LOCKING RECORD

Where:

segment
The name of the segment that detected the error.

Explanation: A ZCFLK command was entered. However, an error occurred while trying to find a coupling facility (CF) locking record on file.

System Action: The command is rejected.

User Response: Do the following:

  1. Review the preceding messages to determine the cause of the error.
  2. Correct the error.

See TPF Operations for more information about the ZCFLK commands.

CFLK0011Isegment - ZCFLK DISPLAY STARTS

Where:

segment
The name of the segment that issued this message.

Explanation: This is the normal response to the ZCFLK DISPLAY command with the ALL parameter specified.

System Action: None.

User Response: None.

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

CFLK0012Esegment - COUPLING FACILITY cfname DOES NOT EXIST

Where:

segment
The name of the segment that detected the error.

cfname
The name of the coupling facility (CF).

Explanation: An error occurred because there were no entries in the coupling facility locking table (CFLT) or the entry you specified does not exist when one of the following occurred:

System Action: One of the following occurred:

User Response: Do the following:

  1. Verify that you specified the correct CF name when you entered the command.
  2. Enter the ZCFLK DELETE or the ZCFLK DISPLAY command again, specifying a valid CF name.

See TPF Operations for more information about the ZCFLK commands.

CFLK0013Esegment - UNABLE TO OBTAIN FILE ADDRESS FOR COUPLING FACILITY LOCKING RECORD

Where:

segment
The name of the segment that detected the error.

Explanation: The ZCFLK INITIALIZE command was entered to initialize the coupling facility (CF) locking configuration when an error occurred because the file address for the CF locking record could not be obtained.

System Action: The command is rejected.

User Response: Do the following:

  1. Review the preceding messages to determine the cause of the error.
  2. Correct the error.

See TPF Operations for more information about the ZCFLK INITIALIZE command.

CFLK0015Isegment - ZCFLK DISPLAY STARTS

Where:

segment
The name of the segment that issued this message.

Explanation: This is the normal response to the ZCFLK DISPLAY command with a specific coupling facility (CF) specified.

System Action: None.

User Response: None.

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

CFLK0018Esegment - DISPLAY ENDED - NO COUPLING FACILITIES EXIST IN THE LOCKING CONFIGURATION

Where:

segment
The name of the segment that detected the error.

Explanation: An error occurred because there were no entries found in the coupling facility locking table (CFLT) when the ZCFLK DISPLAY command with the ALL parameter specified was entered to display information about all CFs in the CF locking configuration.

System Action: The command is rejected.

User Response: None.

See TPF Operations for more information about the ZCFLK DISPLAY command.

CFLK0019Esegment - ADD ENDED - COUPLING FACILITY cfname WAS ALREADY ADDED TO THE LOCKING CONFIGURATION

Where:

segment
The name of the segment that detected the error.

cfname
The name of the coupling facility (CF).

Explanation: The ZCFLK ADD command was entered to add a CF to the CF locking configuration. An error occurred because the CF was already added through a previous ZCFLK ADD command.

System Action: The command is rejected.

User Response: Do the following:

  1. Verify that you specified the correct CF name when you entered the ZCFLK ADD command.
  2. Enter the ZCFLK ADD command again, specifying the correct CF name.

See TPF Operations for more information about the ZCFLK ADD command.

CFLK0020Esegment - MIGRATE ENDED - INPUT MODULE NUMBER RANGE IS NOT IN THE RANGE OF REALTIME MODULES

Where:

segment
The name of the segment that detected the error.

Explanation: The ZCFLK MIGRATE command was entered to change the lock residency of modules in the CF locking configuration and migrate the corresponding locking facilities. An error occurred because the range of symbolic module numbers specified to migrate (either one module number or multiple module numbers) did not fall in the correct range of real-time modules for this subsystem.

System Action: The command is rejected and no modules were migrated.

User Response: Do the following:

  1. Determine the correct range of relative symbolic numbers to migrate.
  2. Enter the ZCFLK MIGRATE command again, specifying the correct range of symbolic module numbers for the subsystem from which the command was entered.

See TPF Operations for more information about the ZCFLK MIGRATE command.

CFLK0021Isegment - ZCFLK DISPLAY STARTS

Where:

segment
The name of the segment that issued this message.

Explanation: This is the normal response to the ZCFLK DISPLAY command with the MOD parameter specified.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZCFLK DISPLAY command.

CFLK0022Esegment - DISPLAY ENDED - MODULE NUMBER modnum IS NOT VALID

Where:

segment
The name of the segment that detected the error.

modnum
The symbolic input module number of a device.

Explanation: The ZCFLK DISPLAY command was entered with the MOD parameter specified to view information about a specific module in the coupling facility (CF) locking configuration. An error occurred because the module number specified was not valid.

System Action: The command is rejected.

User Response: Do the following:

  1. Verify that you specified the correct module number when you entered the ZCFLK DISPLAY command with the MOD parameter specified.
  2. Enter the ZCFLK DISPLAY command again, specifying the correct module number.

See TPF Operations for more information about the ZCFLK DISPLAY command.

CFLK0023Esegment - DISPLAY ENDED - THE CF LOCKING DATABASE IS INITIALIZED - NO MODULES ARE ASSIGNED TO CF LOCKING

Where:

segment
The name of the segment that detected the error.

Explanation: The ZCFLK DISPLAY command was entered with the MOD parameter specified to view information about a specific module in the coupling facility (CF) locking configuration. An error occurred when the TPF system tried to access the distribution list slot for the module and found that the CF locking database was initialized through the ZCFLK INITIALIZE command. As a result, no CFs were added to the CF locking configuration so there is no CF available to which the lock residency of the module can be assigned.

System Action: The command is rejected.

User Response: Do the following:

  1. Enter the ZMCFT ADD command to add the CF for the processor to the processor configuration.
  2. Enter the ZCFLK ADD command to add the CF to the CF locking configuration.
  3. Enter the ZCFLK DISPLAY command again.

See TPF Operations for more information about the ZMCFT ADD command and the ZCFLK commands.

CFLK0024Esegment - ADD ENDED - SIZE SPECIFIED IS TOO SMALL

Where:

segment
The name of the segment that detected the error.

Explanation: The ZCFLK ADD command was entered with the SIZE parameter specified to add a coupling facility (CF) to the CF locking configuration. An error occurred because the number of 4K blocks specified is less than the minimum size allowed, which is one thousand 4K blocks.

System Action: The command is rejected.

User Response: Do the following:

  1. See the TPF Database Reference and your data collection information to determine a reasonable size based on your current lockspace requirements.
  2. Enter the ZCFLK ADD command again, specifying a valid number of 4 K blocks that is greater than or equal to the minimum size allowed.

See TPF Operations for more information about the ZCFLK ADD command. See the TPF Database Reference for more information about lockspace requirements.

CFLK0025Esegment - ADD ENDED - THE COUPLING FACILITY LOCKING CONTROL TABLE IS FULL

Where:

segment
The name of the segment that detected the error.

Explanation: The ZCFLK ADD command was entered to add a coupling facility (CF) to the CF locking configuration. An error occurred because there were no available entries in the CF locking control table (CFLCT).

System Action: The command is rejected.

User Response: Do the following:

  1. Enter ZCFLK DISPLAY ALL to view the CFs defined in the CF locking configuration.
  2. Enter the ZCFLK DELETE command to remove any CFs that are no longer needed from the CF locking configuration.
  3. Enter the ZCFLK ADD command again to add the CF to the CF locking configuration.

See TPF Operations for more information about the ZCFLK commands.

CFLK0026Esegment - ZCFLK COMMANDS ARE NOT SUPPORTED ON A LOADER GENERAL FILE IPL

Where:

segment
The name of the segment that detected the error.

Explanation: An error occurred because a ZCFLK command was entered during a loader general file (LGF) initial program load (IPL). The ZCFLK command cannot be entered at this time because the coupling facility locking table (CFLT) was not built in storage during restart.

System Action: The command is rejected.

User Response: Do the following:

  1. Wait for the IPL of the loader general file (LGF) to complete.
  2. Enter the ZCFLK command again.

See TPF Operations for more information about the ZCFLK and ZIFIL commands.

CFLK0027Esegment - UNABLE TO FILE COUPLING FACILITY LOCKING RECORD

Where:

segment
The name of the segment that detected the error.

Explanation: A file error occurred while filing a coupling facility locking record (CFLR) in the coupling facility locking control table (CFLCT).

System Action: The request ends.

User Response: Do the following:

  1. Review the preceding error messages to determine the cause of the error.
  2. Correct the error.

CFLK0028Isegment - THE COUPLING FACILITY LOCKING DATABASE HAS BEEN INITIALIZED SUCCESSFULLY

Where:

segment
The name of the segment that initialized the database.

Explanation: The ZCFLK INITIALIZE command was entered to initialize the coupling facility (CF) locking configuration. The CF locking database was cleared and initialized for use successfully.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZCFLK INITIALIZE command.

CFLK0029Tsegment - CONNECTION ATTEMPT FAILED TO COUPLING FACILITY cfname - CONNECT RETURN CODE WAS retcode

Where:

segment
The name of the segment that detected the error.

cfname
The name of the coupling facility (CF).

retcode
The return code.

Explanation: The ZCFLK ADD command was entered to add a CF to the CF locking configuration. An error occurred while connecting to the CF.

System Action: The command is rejected.

User Response: See your IBM service representative.

See TPF Operations for more information about the ZCFLK ADD command. See TPF System Macros for more information about the CFCONC macro.

CFLK0030Esegment - ADD ENDED - A ZMCFT ADD HAD NOT BEEN DONE FOR COUPLING FACILITY cfname ON THIS PROCESSOR

Where:

segment
The name of the segment that detected the error.

cfname
The name of the coupling facility (CF).

Explanation: The ZCFLK ADD command was entered to add a CF to the CF locking configuration. One of the following errors occurred:

System Action: The command is rejected and the CF is not added to the CF locking configuration.

User Response: Do the following:

  1. Enter ZMCFT DISPLAY ALL to view the CFs defined in the processor configuration.
  2. Do one of the following:

See TPF Operations for more information about the ZCFLK ADD and ZMCFT commands.

CFLK0031Esegment - DELETE ENDED - COUPLING FACILITY cfname CANNOT BE DELETED - IT IS THE LAST CF IN THE LOCKING CONFIGURATION AND LOCKS STILL RESIDE ON IT

Where:

segment
The name of the segment that detected the error.

cfname
The name of the coupling facility (CF).

Explanation: The ZCFLK DELETE command was entered to remove a CF from the CF locking configuration. An error occurred because you tried to remove the last CF used for locking that is defined in the CF locking configuration, and at least one module is defined to use this CF for locking.

System Action: The command is rejected and the CF is not removed from the locking configuration.

User Response: Do the following:

  1. Enter the ZCFLK MIGRATE command to migrate the lock residency for all affected modules back to the locking control units (CUs). If you are migrating an online module, then the duplicate module is also migrated. This is to ensure that the locks for the module reside on only a CF or a locking CU.
  2. Enter the ZCFLK DELETE command again to remove the CF from the CF locking configuration.

See TPF Operations for more information about the ZCFLK commands.

CFLK0032Esegment - MIGRATE ENDED - STARTING MODULE NUMBER IS GREATER THAN THE ENDING MODULE NUMBER IN RANGE

Where:

segment
The name of the segment that detected the error.

Explanation: The ZCFLK MIGRATE command was entered to change the lock residency of modules in the coupling facility (CF) locking configuration from a locking control unit (CU) to CF, or from CF to a locking CU. An error occurred because the starting module number specified was greater than the ending module number specified in the range of symbolic module numbers.

System Action: The command is rejected and the lock residency of modules in the locking configuration is not changed.

User Response: Enter the ZCFLK MIGRATE command again by using a valid range of symbolic module numbers by specifying a starting symbolic module number that is less than the ending module number.

See TPF Operations for more information about the ZCFLK MIGRATE command.

CFLK0033Esegment - INIT ENDED - INIT CANNOT BE PERFORMED UNLESS THIS PROCESSOR IS THE FIRST TO IPL AND IN RESTART

Where:

segment
The name of the segment that detected the error.

Explanation: The ZCFLK INITIALIZE command was entered to initialize the coupling facility (CF) locking configuration. An error occurred because the TPF system was not the first to IPL or not in restart for processing this command. You can only use the ZCFLK INITIALIZE command the first time the TPF system comes up with CFs to add to the CF locking configuration.

System Action: The command is rejected. The CF locking control record was found successfully so these records were initialized and the TPF system may be using them for locking.

User Response: Do the following:

  1. Cycle the TPF system to be the first to IPL and in restart.
  2. Enter the ZCFLK INITIALIZE command again to initialize the CF locking configuration.

See TPF Operations for more information about the ZCFLK commands.

CFLK0034Esegment - A CHANGE TO THE LOCKING CONFIGURATION IS ALREADY IN PROGRESS

Where:

segment
The name of the segment that detected the error.

Explanation: The ZCFLK ADD, ZCFLK DELETE, or ZCFLK MIGRATE command was entered when the coupling facility (CF) locking configuration was already in the process of being changed. The CF locking configuration is changed whenever one of the following occurs:

System Action: The command is rejected.

User Response: Do the following:

  1. Wait for the previous request to change the CF locking configuration to complete.
  2. Enter the ZCFLK ADD or ZCFLK DELETE command again.

See TPF Operations for more information about the ZCFLK commands.

CFLK0035Esegment - ADD ENDED - INSUFFICIENT SPACE FOR THE NOTIFY STRUCTURE IN COUPLING FACILITY cfname

Where:

segment
The name of the segment that detected the error.

cfname
The name of the coupling facility (CF).

Explanation: Due to a ZCFLK ADD command request, an attempt was made to create a CF structure on the CF for use during lock contention and lock granted notifications. However, an error occurred because there is not enough space in the CF to create the CF structure.

System Action: The command is rejected and the CF structure is not created.

User Response: Do the following:

  1. Enter the ZMCFT CLEAR command to remove CF structures from a CF that are unknown to the processor configuration.
  2. Enter the ZCFLK ADD command again. If there is still insufficient space on the CF to create the CF structure, enter the ZCFLK ADD command for a CF that has more space available.

See TPF Operations for more information about the ZCFLK ADD and ZMCFT CLEAR commands.

CFLK0036Esegment - ADD ENDED - INSUFFICIENT SPACE FOR THE LOCKSPACE STRUCTURE IN COUPLING FACILITY cfname

Where:

segment
The name of the segment that detected the error.

cfname
The name of the coupling facility (CF).

Explanation: Because of a ZCFLK ADD command request, an attempt was made to create a CF structure on the CF to be used for lock holder information. However, an error occurred because there is not enough space in the CF to create the CF structure.

System Action: The command is rejected and the CF structure is not created.

User Response: Do the following:

  1. Enter the ZMCFT CLEAR command to remove CF structures from a CF that are unknown to the processor configuration.
  2. Enter the ZCFLK ADD command again. If there is still insufficient space on the CF to create the CF structure, do one of the following:

See TPF Operations for more information about the ZCFLK ADD and ZMCFT CLEAR commands.

CFLK0037Esegment - ADD ENDED - UNABLE TO MONITOR THE NOTIFY STRUCTURE IN COUPLING FACILITY cfname

Where:

segment
The name of the segment that detected the error.

cfname
The name of the coupling facility (CF).

Explanation: Due to a ZCFLK ADD command request, an attempt was made to monitor the CF structure on the CF used for lock contention and lock granted notifications. However, an error occurred because the monitor request was not successful.

System Action: The command is rejected and the CF structure is not monitored.

User Response: Do the following:

  1. Enter the ZDCFT command to view the CF trace information.
  2. See your IBM service representative, and provide the CF trace information.

See TPF Operations for more information about the ZCFLK ADD and ZDCFT commands.

CFLK0038Esegment - ADD ENDED - ALL PROCESSORS COULD NOT CONNECT TO COUPLING FACILITY cfname

Where:

segment
The name of the segment that detected the error.

cfname
The name of the coupling facility (CF).

Explanation: The ZCFLK ADD command was entered to add a CF to the CF locking configuration. In order for this request to be successful, all processors in the processor configuration must be connected to the CF. An error occurred in this case because at least one processor in the processor configuration could not connect the CF.

System Action: The command is rejected and the CF is not added to the CF locking configuration.

User Response: See any preceding error messages for this processor or other processors for detailed information about this error.

See TPF Operations for more information about the ZCFLK ADD command.

CFLK0039Esegment - ADD ENDED - NO MORE STRUCTURES CAN BE CREATED ON COUPLING FACILITY cfname

Where:

segment
The name of the segment that detected the error.

cfname
The name of the coupling facility (CF).

Explanation: Because of a ZCFLK ADD command request an attempt was made to create CF structures on the CF. An error occurred because the CF specified already has the maximum number of allowed CF structures allocated on it.

System Action: The command is rejected and the CF structure is not created on the CF.

User Response: Do the following:

  1. Enter the ZMCFT CLEAR command to remove CF structures from the CF that are unknown to the processor configuration.
  2. Enter the ZCFLK ADD command again. If the CF structure still cannot be created on this CF, continue with step 3. If you can create the CF structure, there is no further action for you to take.
  3. Enter the ZMCFT DISPLAY command to view the status of one or more CFs in the processor configuration and to determine which CF structures are allocated on a CF.
  4. Enter the ZCFLK ADD command for a CF that has fewer CF structures allocated on it.

See TPF Operations for more information about the ZMCFT and ZCFLK commands.

CFLK0040Esegment - MIGRATE ENDED - CANNOT MIGRATE BACK TO NON-MPLF CONTROL UNITS WHILE LOOSELY COUPLED

Where:

segment
The name of the segment that detected the error.

Explanation: The ZCFLK MIGRATE command was entered to migrate the lock residency for all affected modules back to the locking control units (CUs). An error occurred because at least one of the locking CUs is a non-multi-path lock facility (MPLF) CU in a loosely coupled complex.

System Action: The command is rejected.

User Response: Do the following:

  1. Ensure that all CUs are MPLF CUs in a loosely coupled complex or the TPF system that is running in uniprocessor mode.
  2. Enter the ZCFLK MIGRATE command again.

See TPF Operations for more information about the ZCFLK MIGRATE message.

CFLK0041Tsegment - STRUCTURE DOES NOT EXIST ON COUPLING FACILITY cfname

Where:

segment
The name of the segment that detected the error.

cfname
The name of the coupling facility (CF).

Explanation: Because of a ZCFLK ADD command request was entered from one processor an attempt was made to create CF structures on a CF and was successful. However, an attempt to connect to these CF structures by another processor in the processor configuration was not successful because the CF structures no longer exist.

System Action: The command is rejected.

User Response: Enter the ZCFLK ADD command again.

See TPF Operations for more information about the ZCFLK ADD command.

CFLK0042Tsegment - COUPLING FACILITY LOCKING TABLE ENTRY VALIDATION FAILED

Where:

segment
The name of the segment that detected the error.

Explanation: The ZCFLK ADD command that was entered was not successful because the entry in the coupling facility locking table (CFLT) was not in the correct state. One of the following errors occurred:

System Action: The command is rejected.

User Response: Do the following:

  1. Enter the ZCFLK ADD command again. If the error occurs again, continue with step 2. If you the error does not occur again, there is no further action for you to take.
  2. Perform an initial program load (IPL) for the processor, and then enter the ZCFLK ADD command again.

See TPF Operations for more information about the ZCFLK ADD command.

CFLK0043Esegment - COUPLING FACILITY cfname WAS DELETED FROM THE LOCKING CONFIGURATION DUE TO ERROR

Where:

segment
The name of the segment that deleted the coupling facility (CF).

cfname
The name of the CF.

Explanation: This message indicates that the CF referenced in the message was deleted from the CF locking configuration because of bad return codes.

System Action: The CF entry is removed from the coupling facility locking table (CFLT) so it can no longer be used for record locking purposes. The lock residency for all locks stored on this CF are redispursed automatically among the remaining CFs in the CF locking configuration on a module-by-module basis. As a result, locks can no longer be stored on this CF and the CF is removed from the CF locking configuration.

User Response: See any preceding error messages for this processor or other processors for detailed information about this error.

CFLK0045Esegment - A MODULE IS CURRENTLY IN COPY - PLEASE RETRY THE ZCFLK MESSAGE WHEN THE COPY HAS COMPLETED

Where:

segment
The name of the segment that detected the error.

Explanation: A ZCFLK ADD, ZCFLK DELETE, or ZCFLK MIGRATE command was entered while at least one module in the complex was in copy state. Since these commands may change the residency of the copy lock and the copy lock is not moved in move locks, it is best to wait for the copy to have completed before entering these ZCFLK commands.

System Action: The command is rejected.

User Response: Do one of the following:

See TPF Operations for more information about the ZCFLK commands and the ZMCPY ABORT command.

CFLK0046Esegment - DELETE ENDED - COUPLING FACILITY cfname CANNOT BE DELETED - IT IS THE LAST CF IN THE LOCKING CONFIGURATION AND CACHING IS ENABLED FOR CF

Where:

segment
The name of the segment that detected the error.

cfname
The name of the coupling facility (CF).

Explanation: The ZCFLK DELETE command was entered to remove a CF from the CF locking configuration, but an error occurred because you tried to remove the last CF that was added and the ZCACH command with the CF ENABLE parameter specified was entered.

System Action: The command is rejected and the CF is not removed from the locking configuration.

User Response: Do the following:

See TPF Operations for more information about the ZCFLK DELETE and ZCACH commands.

CFLK0200ICOUPLING FACILITY LOCKING RESTART PHASE ONE COMPLETED

Explanation: Coupling facility locking restart completed successfully.

System Action: CF locking restart continues with the next phase.

User Response: None.

CFLK0201Esegment - ERROR RECONCILING COUPLING FACILITY LOCKING CONFIGURATION - CORRECT OR REMOVE FAILING COUPLING FACILITIES

Where:

segment
The name of the segment that detected the error.

Explanation: One of the following errors occurred:

System Action: Forced uniprocessor mode is set in Phase two of CF locking restart.

User Response: Do one of the following:

If none of the previous actions correct the error, see your IBM service representative.

See TPF Operations for more information about the ZMCFT ADD, ZCFLK ADD, and ZCFLK DELETE commands.

CFLK0202Esegment - CONNECTION ATTEMPT FAILED TO COUPLING FACILITY cfname - CONNECT RETURN CODE WAS retcode

Where:

segment
The name of the segment that detected the error.

cfname
The name of the coupling facility (CF).

retcode
The return code.

Explanation: This message indicates that the connection routine did not connect successfully to the CF referenced in the message. One of the following conditions caused this error:

All of these conditions must be met successfully to use the CF for locking.

System Action: Forced uniprocessor mode is set in Phase two of CF locking restart.

User Response: Correct the error indicated by the return code.

See TPF System Macros for more information about the CFCONC macro.

CFLK0204ICOUPLING FACILITY LOCKING RESTART PHASE TWO COMPLETED

Explanation: Phase two of coupling facility (CF) locking restart completed successfully.

System Action: Restart continues.

User Response: None.

CFLK0205Esegment - CONNECTION ATTEMPT FAILED TO COUPLING FACILITY cfname - INSUFFICIENT SPACE FOR STRUCTURE structure SIZE REQUESTED size-requested SIZE RETURNED size-returned

Where:

segment
The name of the segment that detected the error.

cfname
The name of the CF.

structure
The name of the coupling facility (CF) structure.

size-requested
The decimal number of 4-KB blocks requested.

size-returned
The decimal number of 4-KB blocks returned.

Explanation: An error occurred on a connect because the CF structure size that was returned was less than the size requested for that structure.

System Action: The TPF system is forced into uniprocessor mode.

User Response: Do the following:

  1. Enter the ZMCFT CLEAR command to remove CF structures from a CF that are unknown to the processor configuration.
  2. Enter the ZCFLK ADD command. If there is still not enough space on the CF to create the CF structure, do one of the following:
  3. Perform an initial program load (IPL) of the TPF system.

CFLK0206Esegment - RETURN CODE retcode FROM LEMIC CLEARUSER OPERATION STRUCTURE structure COUPLING FACILITY cfname

Where:

segment
The name of the segment that detected the error.

retcode
The return code.

structure
The name of the coupling facility (CF) structure.

cfname
The name of the CF.

Explanation: This message indicates that the tpf_lemic function returned a non-zero return code.

System Action: The TPF system is forced into uniprocessor mode.

User Response: Do the following:

  1. Review the return code on the LEMIC macro.
  2. Correct the error indicated by the return code.

See TPF C/C++ Language Support User's Guide for more information about the tpf_lemic function. See TPF System Macros for more information about the LEMIC macro.

CFLK0207Esegment - RETURN CODE retcode FROM LEMIC DELETESET OPERATION STRUCTURE structure COUPLING FACILITY cfname

Where:

segment
The name of the segment that detected the error.

retcode
The return code.

structure
The name of the coupling facility (CF) structure.

cfname
The name of the CF.

Explanation: This message indicates that the tpf_lemic function returned a non-zero return code.

System Action: The TPF system is forced into uniprocessor mode.

User Response: Do the following:

  1. Review the return code on the LEMIC macro.
  2. Correct the error indicated by the return code.

See the TPF C/C++ Language Support User's Guide for more information about the tpf_lemic function. See TPF System Macros for more information about the LEMIC macro.

CFLK0208Esegment - RETURN CODE retcode FROM LEMIC MONITOR OPERATION CONNECTION ATTEMPT FAILED TO COUPLING FACILITY cfname

Where:

segment
The name of the segment that detected the error.

retcode
The return code.

cfname
The name of the CF.

Explanation: This message indicates that the tpf_lemic function returned a non-zero return code.

System Action: The TPF system is forced into uniprocessor mode.

User Response: Do the following:

  1. Review the return code on the LEMIC macro.
  2. Correct the error indicated by the return code.

See the TPF C/C++ Language Support User's Guide for more information about the tpf_lemic function. See TPF System Macros for more information about the LEMIC macro.

CFLK0209Wsegment - RUNNING IN FORCED UNIPROCESOR MODE

Where:

segment
The name of the segment that detected the error.

Explanation: Coupling facility (CF) locking restart was not successful on the first processor. Therefore, the TPF system prevents other processors from joining the processor configuration.

System Action: None.

User Response: Do the following:

  1. See any preceding error messages for detailed information about this error.
  2. Correct the error.
  3. Perform an initial program load (IPL) of the TPF system.

CFLK0211Esegment - COUPLING FACILITIES ARE REQUIRED FOR LOCKING - NO COUPLING FACILITIES FOUND OR CONNECTED - CORRECT OR REMOVE FAILING COUPLING FACILITIES

Where:

segment
The name of the segment that detected the error.

Explanation: One of the following errors occurred:

System Action: Forced uniprocessor mode is set in CF locking restart.

User Response: Do one of the following:

If none of the previous actions correct the error, see your IBM service representative.

See TPF Operations for more information about the ZMCFT ADD, ZCFLK ADD, and ZCFLK MIGRATE commands.

CFLK0212ECFL5 - RETURN CODE retcode FROM LEMIC LOCATEMOD OPERATION FOR SDA sda

Where:

retcode
The tpf_lemic return code.

sda
The symbolic device address (SDA).

Explanation: The coupling facility (CF) lock distribution algorithm (LDA) called the tpf_lemic function to determine the CF index of a general data set (GDS). The return code reference in the message indicates the error that occurred.

System Action: The CF residency for the module is left unchanged. The LDA routine continues with the next device.

User Response: See the TPF C/C++ Language Support User's Guide for more information about the tpf_lemic function and how to correct this error.

CFL20001WLOCK TABLE FULL ON CF - cfname

Where:

cfname
The name of the coupling facility (CF).

Explanation: The CF attached has no lock space available.

System Action: None.

User Response: Do the following:

  1. Review the current lock space size.
  2. Make any needed modifications.