gtpm5m0q | Messages (Online) |
CLMB0001W | ACTIVE LOCKS CLEARED FROM CU xxxx CYCLING TO DEACTIVATE STATUS |
Where:
Explanation: During the deactivation of the host processor, an unlock command was issued to the specified control unit. The control unit contained locks either held or awaited by the host processor. This is not an error situation although it is abnormal to find lock names that are engaged by a processor that is being deactivated.
System Action: Deactivation is continued.
User Response: None.
CLM00002E | CONNECT TO LOCKING FACILITY FAILED, ENTER: ZCORO NOAPPLY - TO INITIALIZE THE RECOVERY LOG, OR ZCORO APPLY - TO APPLY THE RECOVERY LOG WITHOUT LOCKS |
Explanation: Coupling facility (CF) locking restart was unsuccessful acquiring a concurrency filter lock facility (CFLF) control unit or a CF lock to ensure a safe restore of the recovery log.
System Action: None.
User Response: Determine whether it is safe to apply the recovery log. Applying the recovery log without correct locking can affect databse integrity. If you do not apply the recovery log, you can lose valuable data from the log.
You must do one of the following:
See TPF Operations for more information about the ZCORO and ZPSMS commands.
CLM10001I | CFLF RESTART SUCCESSFUL |
Explanation: All online concurrency filter lock facility (CFLF) subsystems are successfully connected during restart.
System Action: Processing is continued.
User Response: None.
CLM10003W | RUNNING IN FORCED UNIPROCESSOR MODE |
Explanation: This message is issued when:
System Action: If RCS initialization is successful, the TPF systemforces a re-IPL and tries the connect order again.
If RCS initialization is unsuccessful or if a second attempt fails, the TPF system continues restart in uniprocessor mode.
User Response: Correct the hardware or licensed internal code problem.
CLM10004W | PROCESSOR id RUNNING IN FORCED UNIPROCESSOR MODE |
Where:
Explanation: To maintain database integrity, the first processor to IPL (id) is preventing other processors from joining the complex.
System Action: An irrecoverable system error (CTL-708) is issued.
User Response: Re-IPL this processor after the first processor successfully completes concurrency filter lock facility (CFLF) restart.
CLM20001W | ORDER order FAILED, CODE ret_code DEVICE device SSID ssid |
Where:
Explanation: The concurrency filter lock facility (CFLF) connect order failed on the specified device.
System Action: The TPF system initializes the record cache subsystem unless the return code was X'FF'.
User Response: If the return is X'FF', a re-IPL of the multi-path lock facility (MPLF) control unit may be necessary.
CLM20002W | CANNOT RECOVER COPY LOCK, DEVICE device SSID ssid |
Where:
Explanation: A module is in copy state, but the concurrency filter lock facility (CFLF) partition reserved for the copy lock contains either no locks or more than one lock.
System Action: A disconnect order is issued to the CFLF partition reserved for the copy lock, followed by a connect order to that partition.
User Response: Enter the ZMCPY ABORT command after restart is completed.
CLM20003I | WAITING TO CONNECT, DEVICE device SSID ssid |
Where:
Explanation: A connect order failed because a disconnect order, which was issued previously, is currently in progress.
System Action: The TPF system waits for the disconnect to complete and then retries the connect order.
User Response: None.
CLM20091E | TIMEOUT DURING CONNECT DEVICE dev SSID ssid |
Where:
Explanation: The TPF system retried the connect order the maximum number of times allowed.
System Action: The TPF system returns with a bad return code and the connect order fails.
User Response: This may be a hardware error. Determine why the disconnect order did not complete.
If the return code shown in the CLM201W message, which follows this message, is X'FF', a re-IPL of the multi-path lock facility (MPLF) control unit may be necessary.
CLM60001W | UNABLE TO SET LOCK OF CF cfname FOR PROCESSOR id |
Where:
Explanation: During processing of ZPSMS command or a destructive initial program load (IPL) request, an attempt to obtain the CF lock for the CF referenced in the message was not successful. This error occurs when the CF fails to respond to CF commands.
System Action: Processing continues for other CFs in the locking configuration.
User Response: Do the following:
See TPF Operations for more information about the ZPSMS command.
CLM60002W | UNABLE TO DETACH USER FROM STRUCTURE strindex ON CF cfname FOR USER ID userid |
Where:
Explanation: The CF was unable to detach the processor referenced in the message from the locking structure or the notification structure on the CF. This error occurs when the CF is unable to proces commands. Additional error messages usually accompany this message.
System Action: Processing continues for other locking structures on this CF and for other CFs in the locking configuration.
User Response: Do the following:
CLM60003W | UNABLE TO RELEASE LOCK OF CF cfname FOR PROCESSOR id |
Where:
Explanation: During processing of a ZPSMS command or a destructive initial program load (IPL) request, an attempt to release the CF lock for the CF referenced in the message was not successful. This error occurs when the CF fails to respond to CF commands.
System Action: Processing continues for other locking structures on this CF and for other CFs in the locking configuration.
User Response: Do the following:
See TPF Operations for more information about the ZPSMS command.
CLM60004W | UNABLE TO DISCONNECT FROM CF cfname, RRC=0008080B |
Where:
Explanation: During processing of a ZPSMS command, an attempt to disconnect from the locking structures on the CF referenced in the message ws not successful since activity against the locking structures did not quiesce.
System Action: Processing continues for other CFs in the locking configuration.
User Response: See your IBM service representative to determine the cause of the problem.
CLM60005W | UNABLE TO DISCONNECT USER ID userid FROM COUPLING FACILITY LOCKING STRUCTURES DUE TO READ ERROR |
Where:
Explanation: During processing of a ZPSMS command or a destructive initial program load (IPL) request, an error occurred while trying to find a coupling facility (CF) record on file.
System Action: Processing continues for other locking structures on this CF and for other CFs in the locking configuration.
User Response: Do the following:
See TPF Operations for more information about the ZPSMS command.
CLM80001E | INVALID MESSAGE SYNTAX |
Explanation: An error occurred because the ZDLCK command was entered incorrectly.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZDLCK commands.
CLM80002E | CANNOT ALLOCATE MEMORY |
Explanation: An error occurred while processing a ZDLCK command because there is not enough heap storage available.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZDLCK commands.
CLM80004E | LOCK NAME NOT FOUND |
Explanation: The ZDLCK DISPLAY or ZDLCK DELETE command was entered to display the lock names that exist in the coupling facility (CF). However, an error occurred because the lock name specified was not found on any CF in the CF locking configuration.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZDLCK DISPLAY and ZDLCK DELETE commands.
CLM80005E | CF LOCK READ FAILED. RETURN CODE retcode |
Where:
Explanation: The LEMIC macro with the READ parameter specified was issued to read information about one or more locks in the coupling facility (CF). However, an error occurred and the return code referenced in the message was issued.
System Action: The ZDLCK command is rejected.
User Response: Do the following:
See TPF System Macros for more information about the LEMIC macro. See theTPF C/C++ Language Support User's Guide for more information about the tpf_lemic function. See TPF Operations for more information about the ZDLCK commands.
CLM80007E | READ LOCK ILLOGICAL CONDITION |
Explanation: An error occurred because an illogical condition was detected.
System Action: The function is not performed.
User Response: See your IBM service representative to determine the cause of the error.
CLM80008E | CANNOT DECODE FILE ADDRESS |
Explanation: The ZDLCK DISPLAY or ZDLCK DELETE command was entered with the FA parameter specified to display information about the locks for a specific file address or to delete locks. However, an error occurred because the TPF system was unable to decode the file address into module, cylinder, head and record (MCHR).
System Action: The function is not performed.
User Response: Do the following:
See TPF Operations for more information about the ZDLCK DISPLAY and ZDLCK DELETE commands.
CLM80009I | ZDLCK DISPLAY STARTS |
Explanation: This is the normal response to the ZDLCK DISPLAY command with the FA or LOCKNAME parameter specified.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZDLCK DISPLAY command and for an example of the informational display.
CLM80010E | MODULE NUMBER IS NOT VALID |
Explanation: The ZDLCK DISPLAY command was entered with the MOD parameter specified to display information about the locks for a specific module number. However, an error occurred because the TPF system was unable to decode the file address into module, cylinder, head and record (MCHR) format.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZDLCK DISPLAY command.
CLM80011I | ZDLCK DISPLAY MOD STARTS |
Explanation: This is the normal response to the ZDLCK DISPLAY command with the MOD parameter specified.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZDLCK DISPLAY command and for an example of the informational display.
CLM80012I | ZDLCK DISPLAY MOD CONTINUES |
Explanation: This is the normal response to the ZDLCK DISPLAY command with the MOD parameter specified when a continuation was necessary and ZPAGE was entered.
System Action: The display continues.
User Response: None.
See TPF Operations for more information about the ZDLCK DISPLAY command.
CLM80027I | LOCK DELETION COMPLETE, CTL-4627 MAY OCCUR |
Explanation: The ZDLCK DELETE command was entered to delete a specific lock residing on a coupling facility (CF).
System Action: The lock is deleted.
User Response: None.
See TPF Operations for more information about the ZDLCK DELETE command.
CLTR0001I | TCP/IP CONFIGURATION TABLE INITIALIZED AND FILED |
Explanation: The Transmission Control Protocol/Internet Protocol (TCP/IP) configuration table has been initialized and filed for the first time during TPF system restart. Once the table is filed, this message will not be displayed on subsequent IPLs of the TPF system.
This message can also occur when the Transmission Control Protocol/Internet Protocol (TCP/IP) configuration table must be initialized as a result of an error while attempting to convert from #IBMM4 to #IBMMP4 fixed records.
System Action: None.
User Response: None.
CLTR0006I | FILE COPY CONVERSION OF TCP/IP CONFIGURATION TABLE SUCCESSFUL |
Explanation: The TCP/IP configuration table was successfully converted from #IBMM4 records to #IBMMP4 records.
System Action: TPF restart continues.
User Response: None.
See TPF Transmission Control Protocol/Internet Protocol for more information about the TCP/IP configuration table
CLUS0001I | NEGATIVE RSP TO CLU-CLU SESSION COMMAND CLU NAME: clu CMD: cmd SENSE: sense |
Where:
Explanation: When a negative response to a CLU-CLU private protocol path information unit (PIU) is received, a message is sent to the communications console describing the CLU name, command type, and sense code.
System Action: None.
User Response: None.
CLVQ0050A | CCP TRACE DATA DISCARDED. RTL NOT MOUNTED |
Explanation: The operator requested that the communications control program (CCP) trace be written to tape, but the RTL/RTA tape is not available.
System Action: The TPF system stores the CCP trace table in core memory until the RTL/RTA tape is mounted. Information stored in the CCP trace table wraps around when the trace table becomes full.
User Response: Mount the RTL/RTA tape.
See TPF Non-SNA Data Communications Reference for more information about the CCP trace.
CLXV0001E | LEID xxxxxx RID IS 0 |
Where:
Explanation: The TPF system tried to send a message to a NEF, AX.25, or the XALCI device that has a resource identifier of 0 in its WGTA entry.
System Action: None.
User Response: Do the following:
CL110001I | COMMIT/ROLLBACK TABLE INITIALIZATION.....COMPLETE |
Explanation: All TPF transaction services internal tables were initialized during TPF systemrestart.
System Action: None.
User Response: None.
CL110002I | COMMIT/ROLLBACK RECOVERY.................COMPLETE |
Explanation: Processing of the TPF transaction services recovery log was completed successfully.
System Action: None.
User Response: None.
CL110003I | LOG RECOVERY FOR CPU-X .................COMPLETE |
Explanation: Log takeover processing for the TPF transaction services recovery log of another processor was completed successfully.
System Action: None.
User Response: None.
CL110004E | LOG RECOVERY FOR CPU-X ..................ABORTED |
Explanation: Log takeover processing for the TPF transaction services recovery log of another processor ended abnormally.
System Action: An error indicator is returned to the function that requested the log takeover. In addition, system error dumps are issued to indicate what errors caused the takeover process to discontinue.
User Response: Review the system error dumps to determine the cause of the problem.
CL140011I | TRANSACTION BRANCHES RECOVERED - x |
Where:
Explanation: Transaction branches that are written to the recovery log but not hardened are recovered during restart.
System Action: None.
User Response: None.
CL210001I | RECOVERY LOG FOR CPU-X ..............INITIALIZED |
Explanation: The TPF transaction services recovery log was initialized again for the specified processor.
System Action: None.
User Response: None.
CL210002E | SS/SSU CONFIGURATION HAS CHANGED FOR CPU-X , ENTER: ZCORO NOAPPLY -TO INITIALIZE THE RECOVERY LOG, OR ZCORO APPLY -TO APPLY THE RECOVERY LOG, OR RE-IPL WITH THE SAME SS/SSU CONFIGURATION |
Explanation: Recovery log processing detected a change in the subsystem (SS) or subsystem user (SSU) configuration between this IPL and the previous IPL. Recovery of the recovery log may result in database record corruption.
System Action: Recovery log processing waits until you enter the ZCORO command with the APPLY or NOAPPLY parameter specified.
User Response: Do the following:
See TPF Operations for more information about the ZCORO command. See TPF Application Programming for more information about recovery logs.
CL210003E | SS/SSU CONFIGURATION HAS CHANGED FOR CPU-X, ENTER: ZCORO NOAPPLY -TO INITIALIZE THE RECOVERY LOG ON ssn, OR RE-IPL WITH THE SAME SS/SSU CONFIGURATION TO KEEP THE RECOVERY LOG ON psn |
Where:
Explanation: Recovery log processing detected a change in the subsystem (SS) or subsystem user (SSU) configuration between this initial program load (IPL) and the previous IPL. The new SS or SSU configuration has the recovery log records allocated on a different subsystem. The TPF system cannot access the previous recovery log for recovery processing.
System Action: Recovery log processing waits until you enter the ZCORO command with the NOAPPLY parameter specified or you re-IPL the TPF system. When you enter ZCORO NOAPPLY, the TPF system continues processing and initializes the recovery log in its new location. If any data is present on the previous log, it is now lost.
User Response: Do the following:
See TPF Operations for more information about the ZCORO command. See TPF Application Programming for more information about recovery logs.
CL210004W | UNKNOWN PROGRAM NAME name IN count LOG RECORDS |
Where:
Explanation: TPF transaction services recovery log records contain an unknown program name. This can occur when any new resource manager is added and a fallback condition occurs after the resource manager has written records to the recovery log.
System Action: The log records are discarded.
User Response: Do one of the following:
See TPF Application Programming for more information about recovery logs.
CL210005I | VPARS RLOG ALLOCATION CHANGE ACCEPTED |
Explanation: The number of records allocated for the recovery log has been changed to allow a test system controlled by VPARs to run without filling up the VPARS buffer area. This message indicates that the new allocation has been accepted.
System Action: The control record is updated with the new allocation values and the rve ecovery log is initialized again.
User Response: None.
CL220001E | LOG RECOVERY FAILURE ................CYCLE UP IS INHIBITED |
Explanation: Log recovery processing for the TPF transaction services recovery log ended abnormally.
System Action: The cycle inhibit indicator is set and system restart is ended. In addition, system error dumps are issued to indicate what errors caused the recovery process to discontinue.
User Response: Review the system error dumps to determine the cause of the problem.
Where:
Explanation: The machine check FLIH (CPPMKH) issues this message when it is interrupted by a second machine check.
System Action: The TPF system is restarted by CPPMKH.
User Response: None.
See TPF Main Supervisor Reference and ESA/390 Principles of Operation for more information about machine check handling.
Where:
Explanation: The machine check FLIH (CPPMKH) issues this message after an irrecoverable machine check.
System Action: The TPF system is restarted by CPPMKH.
User Response: None.
See TPF Main Supervisor Reference and ESA/390 Principles of Operation for more information about machine check handling.
CMKH0003E | UNRECOVERABLE MACHINE CHECK DAMAGE |
Explanation: After an irrecoverable machine check, the machine check FLIH (CCPMKH) issues this message followed by one or more lines that indicate the machine check conditions reported during the machine check interruption.
System Action: The TPF system is restarted by CPPMKH.
User Response: None.
See TPF Main Supervisor Reference for more information about machine check handling.
CMKH0004I | RAN OUT OF PATCH FRAMES |
Explanation: The machine check FLIH (CPPMKH) issues this message when it runs out of patch frames trying to recover from an uncorrected storage or storage key error.
System Action: The TPF system is restarted by CPPMKH.
User Response: None.
See TPF Main Supervisor Reference for more information about machine check handling.
CMKH0005T | INHIBITED CRITICAL RECORD FILING |
Explanation: After an irrecoverable machine check, the machine check FLIH (CPPMKH) and the check stop handler (CPPMAL) issue this message when there is reason to believe the critical records would be corrupted if in restarting the TPF system the critical records were filed.
System Action: The TPF system is restarted by CPPMKH or CPPMAL without filing the critical records.
User Response: None.
See TPF Main Supervisor Reference for more information about machine check handling.
CMKH0006A | SWITCH TO BACKUP PROCESSING COMPLEX |
Explanation: After an irrecoverable machine check, the machine check FLIH (CPPMKH) and the check stop handler (CPPMAL) issue this message when there is reason to believe there is no point in restarting or re-IPLing the current processing complex.
System Action: The TPF system is ended by CPPMKH or CPPMAL.
User Response: None.
See TPF Main Supervisor Reference for more information about machine check handling.
CMKH0007I | REACHED CATASTROPHIC MACHINE CHECK THRESHOLD |
Explanation: After an irrecoverable machine check, the machine check FLIH (CPPMKH) and the check stop handler (CPPMAL) issue this message when the threshold for irrecoverable machine checks is reached.
System Action: The TPF system is ended by CPPMKH or CPPMAL.
User Response: None.
See TPF Main Supervisor Reference for more information about machine check handling.
CMKH0008A | RE-IPL THIS PROCESSING COMPLEX |
Explanation: After an irrecoverable machine check, the machine check FLIH (CPPMKH) and the check stop handler (CPPMAL) issue this message when there is some reason to believe there is no point in restarting the TPF system without re-IPLing the current processing complex.
System Action: The TPF system is ended by CPPMKH or CPPMAL.
User Response: None.
See TPF Main Supervisor Reference for more information about machine check handling.
CMKH0009E | OVERRAN MACHINE CHECK BUFFER |
Explanation: After buffer, the machine check FLIH (CCPMKH) issues this message followed by one or more lines that indicate the machine check conditions reported during the last five machine check interruptions.
System Action: The TPF system is restarted by CPPMKH.
User Response: See your IBM service representative.
See TPF Main Supervisor Reference for more information about machine check handling.
CMKH0010E | MALFUNCTION ALERT FROM I-STREAM aa (CPU bb) |
Where:
Explanation: The check stop handler (CPPMAL) issues this message when it receives a malfunction alert.
System Action: The TPF system is restarted by the CPPMAL.
User Response: None.
See TPF Main Supervisor Reference and ESA/390 Principles of Operation for more information about machine check handling.
CMKH0011E | TERMINATED E-TYPE PROGRAM |
Explanation: After the machine check FLIH (CCPMKH) ends an E-typeprogram, the machine check SLIH (CMKHRDO) issues this message followed by one or more lines that indicate the machine check conditions reported during the machine check interruption.
System Action: The machine check interrupted E-type program is ended by CPPMKH.
User Response: None.
See TPF Main Supervisor Reference for more information about machine check handling.
CMKH0012E | EXTERNAL DAMAGE WITHOUT VALID CODE |
Explanation: The machine check SLIH (CMKHRDO) issues this message when it detects a machine check reporting both external damage and external damage code that is not valid.
This is noteworthy because some Sysplex Timer (STR) exceptions are reported as external damage and external damage code that is not valid prevents CMKHRDO from knowing whether any STR exceptions occurred.
System Action: None.
User Response: None.
See TPF Main Supervisor Reference and ESA/390 Principles of Operation for more information about machine check handling.
CMKH0013E | CYCLING DOWN DUE TO DEGRADATION |
Explanation: The machine check SLIH (CMKHRDO) issues this message when it detects a machine check reporting degradation, the TPF system is above 1052 state, and cycling is enabled.
System Action: The TPF system is cycled down by CMKHRDO.
User Response: Do the following:
See TPF Main Supervisor Reference and ESA/390 Principles of Operation for more information about machine check handling.
CMKH0014E | CYCLING DOWN DUE TO SERVICE PROCESSING DAMAGE |
Explanation: The machine check SLIH (CMKHRDO) issues this message when it detects a machine check reporting service processing damage, the TPF system is 1052 state, and cycling is enabled.
System Action: The TPF system is cycled down by CMKHRDO.
User Response: Do the following:
See TPF Main Supervisor Reference and ESA/390 Principles of Operation for more information about machine check handling.
CMKH0015E | CYCLING DOWN DUE TO WARNING |
Explanation: The machine check SLIH (CMKHRDO) issues this message when it detects a machine check reporting warning, the TPF system is above 1052 state, and cycling is enabled.
System Action: The TPF system is cycled down by CMKHRDO.
User Response: Do the following:
See TPF Main Supervisor Reference and ESA/390 Principles of Operation for more information about machine check handling.
CMQB0001A | LU MESSAGE BLOCKING TABLE FULL, SLOT ALLOCATION FAILED FOR LU nnnnnnnn |
Where:
Explanation: Data was transmitted to an LU that supports the general access to the X.25 Transport Extension/Fast Transaction Processing Interface (GATE/FTPI) but no slots are available in the LU message blocking table (LUB). Either no table was allocated or the table is too small.
System Action: If no LUB slots are available, data flow continues without taking advantage of the GATE/FTPI message blocking protocol.
User Response: Verify that the NBLKLU keyword in the SNAKEY macro used for keypoint record 2 (CTK2) generation specifies a value equal to or greater than the number of GATE/FTPI LUs that can be in session with the TPF system.
CMTN0001I | NODE xxxxxxxx O/P Q HELD |
Where:
Explanation: The condition causing the failure to the functional support console (FSC) is detected and the queue is held.
System Action: None.
User Response: None.
See TPF Database Reference for more information about the computer room agent set (CRAS) support.
CMTN0002I | NODE xxxxxxxx O/P Q RESTARTED |
Where:
Explanation: The condition causing the failure to the functional support console (FSC) was corrected and the queue that was held previously was restarted.
System Action: None.
User Response: None.
See TPF Database Reference for more information about the computer room agent set (CRAS) support.
CMWA0001I | xxxxxxxx PACING LIMIT REACHED, CURRENT VALUE -- n |
Where:
Explanation: Either the functional management message router (FMMR) session has pacing count errors or the pacing window is exhausted.
System Action: None.
User Response: Have your system programmer determine the cause of the error and correct it.
CNCE0001E | CYCLING DOWN DUE TO EXCESSIVE CHANNEL CHECKS |
Explanation: The channel check handler (CNCEX1) issues this message when the threshold for channel checks is reached, the TPF system is above 1052 state, and cycling is enabled.
System Action: The TPF system is cycled down by CNCEX1.
User Response: Do the following:
See TPF Main Supervisor Reference and ESA/390 Principles of Operation for more information about machine check handling.
CNCE0002E | aaaa DEVICES ADDED, bbbb DEVICES DELETED |
Where:
Explanation: The channel report word handler (CNCEX9) issues this message when one or more channel report words report one or more devices added or deleted from the I/O configuration.
System Action: None.
User Response: None.
See TPF Main Supervisor Reference and ESA/390 Principles of Operation for more information about machine check handling.
CNCE0003E | OVERRAN CRWS |
Explanation: The channel report word handler (CNCEX9) issues this message when CRWs are reported overrun. This is noteworthy because:
System Action: None.
User Response: None.
See TPF Main Supervisor Reference and ESA/390 Principles of Operation for more information about machine check handling.
CNE00101E | LEID xxxxxx IS UNKNOWN |
Where:
Explanation: The TPF system received a message from a NEF, the AX.25, or the XALCI device whose logical end-point identifier (LEID) is not in the WGTA.
System Action: An OPR-1E8 dump is issued and the ECB is exited.
User Response: Have your system programmer review the system error dump to determine the cause of the error and to correct it.
CNFC0001E | LEID xxxxxx IS UNKNOWN |
Where:
Explanation: The TPF system received an error report from NEF indicating that a message was sent to a logical end-point identifier (LEID) that is not defined in the network control program (NCP) NEF tables.
System Action: Indicates that the terminal is not in service.
User Response: Have your system programmer review the system error dump to determine the cause of the error and to correct it.
CNFC0002I | LEID xxxxxx IS INACTIVE |
Where:
Explanation: The TPF system is trying to send a message to a NEF2 logical end-point identifier (LEID) that is not active.
System Action: Indicates that the terminal is not in service.
User Response: Determine whether the terminal is powered on or whether there is any other malfunction.
CNFC0003I | LEID xxxxxx WAS PREVIOUSLY ASSOCIATED WITH ANOTHER LU |
Where:
Explanation: The terminals associated with a SNA logical unit (LU) have changed.
System Action: None.
User Response: Enter the ZTERM command to see whether this LEID is switched to another NEF LU.
CNIS0001I | UP MODE IS SET FOR NEXT IPL |
Explanation: Only one I-stream in the processor is set to be active for the next IPL.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZCNIS command.
CNIS0002I | MP MODE IS SET FOR NEXT IPL |
Explanation: All of the I-streams in the processor are set to be active for the next IPL.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZCNIS command.
CNIS0003I | CURRENTLY RUNNING IN MP MODE |
Explanation: All I-streams in the processor are active.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZCNIS command.
CNIS0004I | CURRENTLY RUNNING IN UP MODE |
Explanation: Only one I-stream in the processor is active.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZCNIS command.
CNIS0020W | MP REQUEST INVALID FOR UNI PROCESSOR SYSTEM |
Explanation: The operator requested for all (more than one) I-streams to be active for the next IPL. However, there is only one I-stream in the processor capable of being activated by the TPF system. Therefore, the MP mode request is not valid.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZCNIS command.
CNIS0051E | INVALID INPUT FORMAT -- ENTER '?' OR 'HELP' FOR VALID PARAMS |
Explanation: None.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZCNIS command.
CNIS0052E | PTV ACTIVE - CANNOT PROCESS MP REQUEST |
Explanation: MP mode was requested by the operator while the program test vehicle (PTV) was still active. PTV can only run in UP mode.
System Action: None.
User Response: Do the following:
See TPF Operations for more information about the ZCNIS command.
CNIS0053E | CTKI RETRIEVAL TIMEOUT, DASD RECORD HOLD TABLE |
Explanation: CNBA failed to retrieve CTKI with HOLD after 2 seconds. Therefore, CTKI is assumed to be held already, probably by some other processor in the complex.
System Action: None.
User Response: Enter the ZRHLD DISPLAY command to display the control locks to determine who is holding CTKI and then try to clear the hold.
If some other processor is hung while holding the keypoint, then that processor should be deactivated by entering the ZPSMS PR DEACTIVATE pr command.
See TPF Operations for more information about the ZCNIS and ZPSMS commands.
CNIS0054E | UNABLE TO RETRIEVE CTKI -- REQUEST NOT PROCESSED |
Explanation: Keypoint I could not be retrieved by using the CYYC keypoint retrieval program to update the CPU field to indicate UP or MP mode for the next IPL.
System Action: A system error is issued.
User Response: Give the system console sheet and dump to your system support personnel.
See TPF Operations for more information about the ZCNIS command.
CNIS0055E | CTKI I/O ERROR -- REQUEST NOT PROCESSED |
Explanation: An input/output (I/O) error occurred when trying to retrieve CTKI to update the CPU field to indicate UP or MP mode for the next IPL.
System Action: A system error is issued.
User Response: Give the system console sheet and system error dump your system support personnel.
See TPF Operations for more information about the ZCNIS command.
CNIS0056E | UNABLE TO FILE CTKI -- REQUEST NOT PROCESSED |
Explanation: An error occurred while filing CTKI with the updated CPU field. Therefore, the CPU field in CTKI did not get updated.
System Action: A system error is issued.
User Response: Review the entry control block (ECB) SUD flag byte for data level 1 and determine the reason for the failure.
See TPF Operations for more information about the ZCNIS command.
CNIS0060E | UNABLE TO RETRIEVE CTKA - REQUEST NOT PROCESSED |
Explanation: Keypoint A could not be retrieved by using the CYYC keypoint retrieval program. Keypoint A was retrieved to update or display the I-stream scheduler constants.
System Action: A system error is issued.
User Response: Give the system console sheet and dump to your system support personnel.
See TPF Operations for more information about the ZCNIS command.
CNIS0061E | UNABLE TO FILE CTKA -- REQUEST NOT PROCESSED |
Explanation: An error occurred while filing CTKA with the updated MAXQ or REACT parameter. This prevents updating of the file copy of the parameter. The main storage copy of the field is, however, updated with the new data.
System Action: A system error is issued.
User Response: Review the entry control block (ECB) SUD flag byte for data level 1 and determine the reason for the failure.
See TPF Operations for more information about the ZCNIS command.
CNIS0062I | I-STREAM SCHEDULER CONSTANTS: REACT-nn, MAXQ-nn |
Explanation: This is an informational display of the I-stream scheduler constants. It was caused by a ZCNIS DISPLAY, ZCNIS MAXQ-, or ZCNIS REACT- command.
Where:
System Action: None.
User Response: None.
See TPF Operations for more information about the ZCNIS command.
CNOM0001E | IPC WAIT ERROR, XMIT TO PROC x |
Where:
Explanation: The timeout period for the queued output messages expired. Connections were not established with interprocessor communications (IPC) in an active processor.
System Action: All queued system interprocessor communications (SPIC) items for that processor are returned to the originating user or discarded.
User Response: Determine why there was a failure to establish the connections.
CNOM0002W | IPC QUEUE TO PROC x HAS REACHED A HIGH LEVEL, CURRENT LEVEL =xxxxx |
Where:
Explanation: The interprocessor communications (IPC) output queue contains greater than a multiple of CNOSWRN messages since the last time a multiple of CNOSWRN was reached or dropped to (CNOSWRN is defined in the change number of sessions (CNOS) segment). The current level of the queue is referenced in the message.
System Action: A warning message is issued.
User Response: Determine why messages are being placed on the IPC queue and provide an opportunity to detect stalled IPC traffic to a processor.
CNON0001I | IPC RESTART COMPLETED. |
Explanation: Interprocessor communications (IPC) restart processing completed.
System Action: Control is returned to the Restart Scheduler (CTKS).
User Response: None.
CNOP0002I | IPC WAITING FOR CONNECTIONS TO ALL L/C PROCS |
Explanation: This is an informational message. It indicates that restart processing is waiting until interprocessor communications (IPC) have established connections with all the processors in the loosely coupled complex.
System Action: When all required connections are established, CNOQ or CNOR runs POSTC to reinitiate restart processing.
User Response: None.
CNOP0051E | IPC TIMEOUT -- CONNECTIONS NOT COMPLETED TO ALL L/C PROCESSORS |
Explanation: This error occurs during restart if the connections for all loosely coupled processors in the complex were not completed within the time specified on the ZSIPC ALTER RESTART command.
System Action: Restart is continued.
User Response: None.
CNOQ0002I | IPC CONNECTION ESTABLISHED TO PROCESSOR x |
Where:
Explanation: This is an informational message. It indicates that a connection was established with the specified processor.
System Action: The interprocessor communications (IPC) processor activation is completed.
User Response: None.
CNOR0002I | IPC CONNECTION ESTABLISHED TO PROCESSOR x |
Where:
Explanation: This is an informational message. It indicates that a connection was established with the specified processor.
System Action: The interprocessor communications (IPC) processor activation is completed.
User Response: None.
CNOR0050E | IPC CONNECTION REQUEST TO SYSTEM ssssssss FAILED WITH ERROR CODE xxxxxxx |
Where:
Explanation: The CONNECT request was not accepted by the TPF systemnamed in the message.
System Action: The TPF system resources associated with the CONNECT attempt are released.
User Response: Determine why there was a failure to establish the connections.
CNOS0050E | IPC WAIT ERROR, XMIT TO PROC x |
Where:
Explanation: The timeout period for queued output messages expired. Connections were not established with the interprocessor communications (IPC) in an active processor.
System Action: All queued system interprocessor communications (IPC) items for that processor are returned to the originating user or discarded.
User Response: Determine why there was a failure to establish the connections.