gtpm4m0d | Messages (System Error and Offline) |
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: BSC RTR -- Too many slots were found in the BSC station name conversion table (SN0CT) for a station name while building a list of paths for routing a message to a station.
System Action: Processing continues. Excess slots are ignored.
User Response: Have your system programmer correct SN0CT for the station name involved. EBW000-011 -- RCPL.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: A CPU ID in the routing control application table (RCAT) status message is not valid.
System Action: A system error is issued and the program is exited.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: BSC RTR -- The byte count in the prime message block of an output message to a BSC station is too large to allow insertion of the routing control parameter list (RCPL) into the message block.
System Action: The output message is discarded.
User Response: Have your system programmer or application programmer correct the originating application program. EBW000-O11 of the dump contains the routing control parameter list (RCPL) associated with the error.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: BSC RTR -- while attempting to validate a binary synchronous communication (BSC) station address, a symbolic line number was found that is too large for the TPF system.
System Action: If the line number was specified as a specific BSC station address in the routing control parameter list (RPCL), the message is discarded. If the line number was obtained from the SN0CT record while processing a station name destination, the processing continues and ignores the bad line.
User Response: Have your system programmer correct the originating application program or the SN0CT record. EBW000-011 contains the routing control parameter list (RCPL).
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: BSC RTR -- while trying to validate a binary synchronous communication (BSC) station address, a symbolic line number was found that was not a BSC line.
System Action: See the 000354 message for more information.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: BSC RTR -- while trying to validate a binary synchronous communication (BSC) station address, a station number was found that was greater than the number of terminal interchange status table entries for the associated line.
System Action: If the station number was specified as a specific BSC station address in the routing control parameter list (RCPL) associated with the output message, the message is discarded.
If the station number was obtained from the station name conversion table record while processing a station name destination, the processing continues and ignores the bad station number entry.
User Response: Have your system programmer correct the originating application program or the SN0CT record. EBW000-011 contains the routing control parameter list (RCPL).
Program: COUM, COUR, COUX
Error Message: None.
Explanation: While attempting to send an unsolicited message to a terminal, a line number, interchange address, and terminal address (LNIATA) for a non-SNA terminal or a RID for a SNA terminal that is not valid was found.
System Action: The message is not delivered and the program is exited.
User Response: Review the dump to determine the cause of the error and to correct it. The RID/LNIATA of the destination terminal is located at EBW000.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: There was an unsolicited read error for the routing control block (RCB).
System Action: Processing is ended. If this is a prime computer room agent set (CRAS) entry, the message that is unable to process is sent to the prime CRAS console. The request may be issued again.
If this is a remote CPU entry, the program is exited.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: There was a file error on the Copy Message utility in a MASS environment.
System Action: The message is returned to the originator.
User Response: Have your system programmer check the system error dump to find out why the COBD copy segment returned an error condition.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: There was a transfer vector for the remote router that is not valid or the activation of the Router option was not valid.
System Action: The processing is ended.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: The remote router increments the resource count for input messages received from a remote processor. This error is indicated when the maximum node count limit is exceeded.
System Action: The message is returned to the originator.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: There was no direct routing path found to a remote application program.
System Action: The message is returned to the originator.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: There was no direct Line/Link path to the remote application program found.
System Action: The message is returned to the originator.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: The router found a line number for the destination path that is not valid.
System Action: The message is returned to the originator.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: There are no eligible line available to route the message to the remote destination.
System Action: The message is returned to the originator.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: INVALID SNA ROUTC ENTRY -- POSSIBLE CORRUPTED RCPL.
Explanation: The ECB-driven router received control of a message destined for a SNA terminal. With the exception of unsolicited messages, messages destined for SNA nodes should be processed by CS96 (CCSNA3). This dump indicates a corrupted routing control parameter list (RCPL).
System Action: A system error is issued and the program is exited.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: LU62 -- INVALID ROUTC SEQUENCE OR PARMS
Explanation: The ROUTC entered the LU62 queue control segment to process a queue request and one of the following error conditions occurred:
System Action: A system error is issued and the program is exited.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: The Router was unable to deliver a message from a binary synchronous communication (BSC) station.
System Action: A system error is issued and the program is exited.
User Response: The path to the destination should be activated or the BSC station should be shut down.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: There was a FINWC error while retrieving an unsolicited Notification List record.
System Action: The processing is ended.
User Response: Have your system programmer review the system error dump to determine the cause of the error and correct it.
Program: Displayed on the console and in the dump.
Error Message: ROUTER ERROR IN LINE SELECTION
Explanation: The Line/Link selected to send a message to a remote processor is not binary synchronous communication (BSC) or synchronous link control (SLC).
System Action: The message is discarded.
User Response: Have your system programmer review the system error dump and check the Line/Link selection.
Program: Displayed on the console and in the dump.
Error Message: ERROR RETURN FROM SENDC/B MACRO
Explanation: The SENDC/B failed while sending a message on a binary synchronous communication (BSC) line to a remote processor.
System Action: The message is discarded.
User Response: Have your system programmer review the system error dump to determine the cause of the error and correct it.
Program: Displayed on the console and in the dump.
Error Message: UNABLE TO PROCESS
Explanation: There was an FIWHC error while retrieving a prime Unsolicited Message Directory record.
System Action: Processing is continued while the unsolicited messages are being policed. Otherwise, the processing is ended.
User Response: Have your system programmer review the system error dump to determine the cause of the error and correct it.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: There was a failure on the file of a primary message block.
System Action: The message is returned to the originator.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: An alternate line selection is an active route for the message to a remote destination but the router is unable to route the message with alternate lines.
System Action: The message is returned to the originator.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: A symbolic line number that is not valid was found.
System Action: The TPF system continues the search for the next alternate line.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: A line number that is not valid was found for the remote destination path.
System Action: The message is returned to the originator.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: A byte count that is not valid was found for the message to a remote destination.
System Action: The message is returned to the originator.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: A transfer vector that is not valid or activation of a Router option that is not valid was found.
System Action: The processing is ended.
User Response: Restart.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: There was an FINWC error while retrieving an overflow Unsolicited Message Directory record.
System Action: The processing continues. Have your system programmer determine the error and to correct it.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: There was an FIWHC error while retrieving a prime Application Terminal Directory record.
System Action: The processing is continued if the calling program expects a return (with an error indication). Otherwise, the processing is ended.
User Response: Have your system programmer review the system error dump to determine the cause of the error and to correct it.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: There was an FINWC error while retrieving an Application Terminal directory record.
System Action: The processing is continued if the calling program expects a return (with an error indication).
User Response: Have your system programmer review the system error dump to determine the cause of the error and to correct it.
Program: Displayed on the console and in the dump.
Error Message: UNABLE TO PROCESS
Explanation: There was an unsolicited read error retrieving CTKC (keypoint C) in order to set or check the Unsolicited Message Directory record initialization bits.
System Action: The processing is continued if there is a Restart entry. Otherwise, the message is sent to the operator and processing is ended.
User Response: Have your system programmer should review the system error dump to determine the cause of the error and to correct it.
Program: Displayed on the console and in the dump.
Error Message: UNABLE TO PROCESS
Explanation: There was a file address compute program (FACE) error while retrieving the file address of a prime Unsolicited Message Directory record.
System Action: The processing is ended.
User Response: Have your system programmer review the system error dump to determine the cause of the error and to correct it.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: There was an Unsolicited Broadcast request that was not valid. The message erroneously consisted of a LOGI request or a canned message.
System Action: The processing is ended.
User Response: Have your system programmer review the system error dump to determine the cause of the error and to correct it.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: Upon entry to perform an application broadcast, the program cannot locate the application name passed from the calling module in the routing control application table.
System Action: The processing is continued if the calling program expects a return (with an error indication). Otherwise, the processing is ended.
User Response: Have your system programmer review the system error dump to determine if a valid application program was specified or if its routing control application table (RCAT) residency was in error.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: There was an unsolicited message from the application program that is too long.
System Action: The processing is ended.
User Response: Have your system programmer review the system error dump to determine the cause of the error and to correct it.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: The format of an unsolicited message was not legal.
System Action: The processing is ended.
User Response: The operator should issue the message again by using the correct format.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: There was an unsolicited Message Directory record initialization file (FILNC) error.
System Action: The processing is ended.
User Response: Have your system programmer review the system error dump to determine the cause of the error and to correct it.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: There was an unsolicited message directory record ID error from the file address compute program (FACE) program.
System Action: The processing is ended.
User Response: Have your system programmer review the system error dump to determine the cause of the error and to correct it.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: The broadcast request sent by the application program is not formatted correctly.
System Action: The processing is ended.
User Response: Have your system programmer review the system error dump to determine the reason for the format error and to correct it. The application program must be change to build a request in the correct format.
Program: Displayed on the console and in the dump.
Error Message: UNABLE TO PROCESS
Explanation: There was an unsolicited file error -- unable to file an Application Message Format record when trying to send a message to a single logical unit (LU) (not 3270 SDLC or NEF). The message is the following:
System Action: The processing is ended when an UNABLE TO PROCESS message is sent to the operator.
User Response: Have your system programmer review the system error dump to determine the cause of the error and to correct it.
Program: Displayed on the console and in the dump.
Error Message: UNSOLICITED ERROR IN READ OF MESSAGE.
Explanation: There was an FINWC error while retrieving the unsolicited message record.
System Action: The processing is ended and an error message is sent to the operator.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: UNABLE TO RETRIEVE IFMSG TABLE
Explanation: An error occurred during retrieval of the file address of the prime or overflow IFMSG record.
System Action: If the error occurs on the the prime record, the TPF system sends an error message to the operator and processing ends.
If the error occurs on the overflow record and the request is a display, processing continues with the prime record. Otherwise, the TPF system sends an error message to the operator and processing ends.
User Response: Have your system programmer review the system error dump to determine the cause of the error and to correct it.
Program: Displayed on the console and in the dump.
Error Message: UNABLE TO RETRIEVE IFMSG TABLE
Explanation: A FIND error occurred during retrieval of the prime or overflow IFMSG record.
System Action: If the error occurs on the the prime record, the TPF system sends an error message to the operator and processing ends.
If the error occurs on the overflow record, the TPF system performs one of the following:
User Response: Have your system programmer review the system error dump to determine the cause of the error and to correct it. The system error dump shows the following:
Program: Displayed on the console and in the dump.
Error Message: FACE/FIND ERROR ON ZPTCH ROOT FILE
Explanation: An error occurred during retrieval of the ZPTCH root fixed-file record.
System Action: A system error dump is issued and processing is ended.
User Response: Have your system programmer review the system error dump to determine the cause of the error and to correct it. The system error dump shows the following:
To force the ZPTCH root fixed-file record to be re-initialized, enter ZIFIL IBMMS/00E7/00/23/23/NNN/N.
See TPF Operations for more information about the ZPTCH command.
Program: Displayed on the console and in the dump.
Error Message: FIND ERROR ON ZPTCH PATCH DECK
Explanation: An error occurred during retrieval of the patch deck pool record.
System Action: A system error dump is issued and processing is ended.
User Response: Have your system programmer review the system error dump to determine the cause of the error and to correct it. The system error dump shows the following:
Program: Displayed on the console and in the dump.
Error Message: FIND ERROR ON KEYPOINT E.
Explanation: A FIND error was found while trying to retrieve the address of the keypoint.
System Action: A system error is issued and the entry control block (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.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: The TPF system is unable to find a Conversion Resource Vector entry for a given resource ID.
System Action: A system error dump is issued and the entry control block (ECB) is ended.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: BSC STATION ADDR TABLE LOAD FAIL
Explanation: The BSAT load was not successful.
System Action: Restart processing is continued.
User Response: Have your system programmer determine why the load was not successful and correct it.
Program: Displayed on the console and in the dump.
Error Message: SNCT LOAD FAILED (SN0CT)
Explanation: The binary synchronous communication (BSC) station name conversion table load was not successful.
System Action: Processing is continued.
User Response: Have your system programmer determine why the load was not successful and correct it.
Program: Displayed on the console and in the dump.
Error Message: CVLD -- INVALID INPUT PARAMETER
Explanation: SLN is out of range of valid lines for 3270 Local.
System Action: A SERRC macro is issued and BACKC is issued to calling program.
User Response: Review the system error dump for database problems or user error on input.
Program: Displayed on the console and in the dump.
Error Message: CVLx -- INVALID SLST ENTRY .hh.mm.ss (LSON/LSOF)80HS(xx/ALL) INVALID SLST ENTRY
Where:
Explanation: The 3270 local (-CTLLC) start a line (CVLC), restart (CVLD), stop a line (CVLG), or start/stop TPNS(CVLP) determined that the symbolic line status table entry for the specific line number was not a 3270 local device (fields: SLSTTYP and SLSTTPNS).
System Action: A system error is issued and the function continues for the next SLN or in the case of CVLP the error message is issued and then it is exited.
User Response: Review the system error dump to determine the incompatibility between the system communication configuration table (CK6KE) and the symbolic line status table (SLSTL).
The system initialization program (SIP) creates the system communication configuration table and the 3270 local SLN range, and system communication keypoint (SCK) generation creates the symbolic line status table.
See TPF System Generation for more information about these procedures.
The SLN in question is in EBW008-009 in CVLC, CVLG, and CVLP, and it is in EBW022-023 for CVLD. R2 points to CK6KE and R3 to the SLSTL entry for the SLN.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: This error is issued by 1052 fallback for one of the following conditions:
System Action: A dump is issued and processing is continued.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: CVLx -- SUB CHN EQUAL TO ZERO
Where:
Explanation: The 3270 local start a line (CVLC), restart (CVLD), or stop a line (CVLG) determined that the subchannel address in the line status table is zero (field: CPMVSC).
System Action: A system error is issued and the function continues for the next SLN.
User Response: Review the system error dump to deterine which symbolic line has the error.
System communication keypoint (SCK) generation creates the line status table. The SLN in question is in EBW008-009 in both CVLC and CVLG, and it is in EBW022-023 for CVLD. R5 points to LSTB entry for the SLN in question.
Program: Displayed on the console and in the dump.
Error Message: CVLL -- INVALID APPLICATION NAME
Explanation: After a write I/O error to a 3270 local CRT device is corrected, the content of the device buffer is unknown (the 3270 local I/O program clears the buffer as part of error correction procedure). The CVLB segment activated CVLL when it could not reformat the buffer.
System Action: A system error dump is issued and the device queue of all pending messages for the device are cleared.
User Response: Review the system error dump to determine the symbolic line number (SLN) of the device in error. One possible action is to stop the device or to have the operator retry the input message that caused the suspect output message.
The EBROUT field of the ECB contains the SLN of the device in error. The CCP CCW areas for the SLN contains the address of the bad message as the first entry on the write queue (CXQTOP).
See TPF Operations for more information about the ZLSTP command.
Program: Displayed on the console and in the dump.
Error Message: CVLx -- DUPLICATE INTERNAL LINE NUMBER IN ITLT
Where:
Explanation: The 3270 local start a line (CVLC), restart (CVLD), or stop a line (CVLG) determined that the slot in the internal line number table was not equal to zero when it should have been based on the device status.
This dump is most commonly caused when fallback prime computer room agent set (CRAS) consoles are not defined in the SIP generation or those defined in the SIP generation are not available. In such a case, if the prime CRAS console goes through fallback, an alternate CRAS console is chosen to be the fallback prime CRAS console If the TPF system goes through re-IPL before the original prime CRAS console is restored, a 3C5 dump results to indicate an alternate CRAS console is being used as the prime CRAS console. This configuration is not supported by the TPF system since it is very easy to hang the TPF system consoles with an alternate CRAS console defined as the prime CRAS console. The recommended configuration is to have a fallback CRAS available on a control unit other than the control unit used for alternate CRASs. The fallback CRAS can then be defined in the SIP generation.
System Action: A system error is issued and the function continues with the next SLN.
User Response: Review the system error dump to determine which symbolic line number (SLN) is in error.
The SLN in question is in EBW008-009 in both CVLC and CVLG, whereas it is in EBW022-023 for CVLD. R14 contains the entry number into the internal line number table of the SLN in question.
Program: CCCCP4 (CLOE, CLOG)
Error Message: One of the following:
Where:
Explanation: The 3270 local I/O program, Write (CLOE), or Asynchronous Write (CLOG) received a command reject status from the control unit (3272) because the Write command is not valid or a command that is not valid was detected at SEND macro time.
System Action: A system error is issued and processing is continued with the next entry on the device queue or goes to the I/O exit if detected at interrupt time.
If detected at SEND macro time, then a system error is issued and exits the ECB.
User Response: Review the system error dump to determine who requested the output operation with a command that is not valid.
There may have been an application package error while formatting the output message. R1 is a pointer to the output message.
Program: CCCCP4 (CLOE, CLOG)
Error Message: CLOx -- 3270 LOCAL OPERATION CHECK
Where:
Explanation: The 3720 local I/O program, Write (CLOE), or Asynchronous Write (CLOG) received an operation check status from the control unit (3272) because of an error within the output message.
System Action: A system error is issued and processing is continued with the next entry on the device queue or goes to the I/O exit.
User Response: Review the system error dump to determine who sent the output message with data that is not valid (for example, a buffer address that is not valid after an SBA order).
An example of a typical error would be the use of a cursor address for a Model 2 device when the device is really a Model 1. R1 is a pointer to the output message.
Program: CCCCP4 (CLOA)
Error Message: CLOA -- NO MAIN STORAGE AVAILABLE
Explanation: A 3270 local I/O attention routine determined that there are no IOCBs available to perform a read operation.
System Action: A catastrophic system error is issued.
User Response: Restart the TPF system.
Determine why the IOCB pool is being depleted and correct it or increase the number of IOCBs.
Program: CCCCP1 (CLVG)
Error Message: CLVG -- INVALID SENDL TO 3270 LOCAL
Explanation: There was an attempt to issue an SENDL (SEND) to a 3270 local device when the long message transmitter (LMT) is not active and the message consisted of multiple segments.
System Action: A system error is issued and only the prime output message blocked is sent to the device.
User Response: The program that issued the SENDL should be modified to check for an LMT that is active before sending a multiple segment output message. The message can only be sent as separate and distinct output messages via through SENDA or ROUTC.
R8 points to the program that issued SEND and R1 points to the prime message block.
Program: Displayed on the console and in the dump.
Error Message: INVALID PKSTG RECORD
Explanation: CVLM was unable to use the PKSTG record for a 3270 local control unit.
System Action: The control unit buses are not supported for the control unit in question. Other than that, the SERR has no effect.
User Response: Rebuild the TPF system, if necessary.
Program: Displayed on the console and in the dump.
Error Message: CVLG - TIMED OUT ON STOPPING LINE
Explanation: While processing a ZLSTP command, the CVLG segment waited more than 60 seconds for core-queue messages to be written to a 3270 local device. This is usually caused by a hardware error on the 3270 local device or control unit.
System Action: The line to the 3270 local device is stopped. If ZLSTP LC ALL was entered, processing continues to write core-queue messages to the next 3270 local device.
User Response: Do the following:
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: The node name in the input load image record is not valid.
System Action: The processing continues with the next record.
User Response: Have your system programmer determine the cause of the system error dump and correct it. Level 0 contains the tape record with the node name that is not valid.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: A file error occurred while trying to file a 3600 load image to pool storage.
System Action: The entry control block (EDB) is exited and the tape load function is aborted.
User Response: Have your system programmer review the system error dump to determine cause of the error and correct it.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: A tape read error occurred while trying to read a 3600 load image.
System Action: The entry control block (ECB) is exited and the tape load function is aborted.
User Response: Have your system programmer review the system error dump to determine the cause of the error and correct it
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: A problem was found with the input command. The message was not attached, contained a bad ID, or was not ZNLDC.
System Action: The entry control block (ECB) is exited.
User Response: Have your system programmer review the system error dump to determine the cause of the error and correct it.
Program: CCENBK(CCEB), CCENBK(CCEF)
Error Message: PROGRAM FORMAT DOES NOT MATCH ALLOCATION
Explanation: The content of a program record field is incorrect.
The format of program records is different between an ISO-C DLM and a non-DLM (for example, a Basic Assembler Language (BAL) program). The program linkage type for the program in the Program Allocation Table (PAT) slot is inconsistent with the format of the program record.
One of the following errors occurred:
System Action: The entry control block (ECB) is exited.
User Response: Have your system programmer review the system error dump to determine the cause of the error and correct it.