gtpm4m0c | Messages (System Error and Offline) |
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: The block type code for the TWRTC macro was not valid.
System Action: The program is exited.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: There was a FIND error on the alarm message segment.
System Action: No alarm is SETN. The program backs or exits according to the option specified.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: The alarm message number is not valid.
System Action: No alarm is sent. The program backs or exits according to the option specified.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: There is no own text for the alarm message.
System Action: No alarm is sent. The program backs or exits according to the option specified.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: There are not enough substitution characters supplied.
System Action: No alarm is sent. The program backs or exits according to the option specified.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: There an odd number of substitution characters specifying hexadecimal data.
System Action: No alarm is sent. The program backs or exits according to the option specified.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: There is no address supplied for the alarm message.
System Action: No alarm is sent. The program backs or exits according to the option specified.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: The item on the input LDB queue is neither an LCB or a time out.
System Action: The item is ignored. The next item, if any, is processed.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: The AI line number in EBWSLN is not valid.
System Action: The program is exited.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: The indicator passed by CMR is not valid.
System Action: The program is exited.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: An STP/RSM was received for a nonexistent channel.
System Action: The line control block (LCB) is ignored.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: A subsequent ENQ was requested -- the line is not in the ENQ procedure.
System Action: The request is treated as a first ENQ request.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: There was a FIND error while retrieving a type B messaged saved by CPSF.
System Action: The message is lost. Processing is continued.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: There was an error while retrieving a message referenced from the MBI slot.
System Action: An internal indicator is set and processing continues. The file address is set as available in the link pool directory.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: There was a file address compute program (FACE) error on the message and the ordinal number was calculated from FPD.
System Action: The file address is set as available in the link pool directory and processing is continued.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: There was an error retrieving a message using the ordinal number from the FPD.
System Action: The file address is set as available in the link pool directory and processing is continued.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: There was an error while retrieving a message and the address is saved in the ECB work area.
System Action: The file address is set as available in the link pool directory and processing is continued.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: NO MESSAGES ON QUEUE DESPITE LK5LQB
Explanation: There are no messages on the channel queue that is being processed currently even though LK5LQB indicates that there are messages on the queue.
System Action: Processing is continued.
User Response: Look for the lost chain of messages.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: There is a multiblock message back but the message block identifier (MBI) is not in use.
System Action: Processing is continued.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: There are too many syns specified in the keypoint.
System Action: The number of extra syns is set to the maximum CXJMXS value and processing is continued.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: There was an error retrieving the message referenced from the AMQ SAVE LK4BQR area.
System Action: The current save area slot is set as inactive and processing is continued.
User Response: None.
Program: CML2
Error Message: SUBCHANNEL HANG PROBLEM
Explanation: No response is received from the line after an ENABLE/DISABLE command is issued. The hardware may be malfunctioning.
System Action: No further initialization of the line takes place.
User Response: Check the hardware.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: There is no ETB in the message.
System Action: The program is exited.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: There was a FACE error while calculating the file addressing an ordinal number from FPD.
System Action: The program is exited.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: There is no file space available in FPD.
System Action: The program is exited.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: There was an error while retrieving a message in CMR3 during message reassembly.
System Action: If block 0 is already retrieved, the message is handled as if an end of chain is found. Otherwise, an attempt is made to retrieve block 0. If that fails, the program is exited.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: There was a file address compute program (FACE) error while using an ordinal number of block 0 during error correction procedures.
System Action: The program is exited.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: A link routing table search was not successful.
System Action: The message is discarded and the program is exited.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: There were link envelope format errors on the LCI and the ACI.
System Action: Return is made to the CMR1, which then exits.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: There were link envelope format errors on the LCI and the ACI.
System Action: The program is exited.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: There was an error while retrieving a message during message throwaway.
System Action: Processing is continued with any other message blocks, if there are any.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: An end-of-message-complete (EOM) was found that is not the last character.
System Action: The characters beyond the EOM are ignored and processing is continued.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: An end-of-message-complete (EOM) was found in the last character of the message block but no more blocks exist.
System Action: The remaining blocks are discarded and processing is continued.
User Response: None.
Program: CILM
Error Message: None.
Explanation: A message was found that was destined for a user type-A nonterminal-oriented application package that is not defined.
System Action: The ECB is exited.
User Response: The SERRC macro should be replaced by an ENTC to the USERS type-A nonterminal-oriented application package.
Program: Displayed on the console and in the dump.
Error Message: INCOMPLETE TYPE A MESSAGE
Explanation: The last message block on the AMQ was not indicated as being the last of a message.
System Action: The type-A output sender active switch is turned off and the program exits.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: The type-A AMQ is empty so the second block is searched.
System Action: The message is discarded and processing is continued.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: The type-A AMQ is empty so the third block is searched.
System Action: The message is discarded and processing continues.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: The third block of a message from type-A AMQ is not last.
System Action: The message is discarded and also further blocks on the AMQ until either a last block is found or the AMQ is empty when error 000324 occurs.
User Response: None.
Program: CMSL CMSM
Error Message: Error retrieving message from file.
Explanation: A master control record (MCR) slot contains information about a given message including its file address. When the TPF system is ready to send that message, the message is read in from file. An error occurred during the read.
System Action: This message is skipped by marking its slot in the MCR as inactive. Processing is continued with the next message.
User Response: None.
Program: CMSM CMSL CMCK
Error Message: ERROR RETRIEVING MCR RECORD
Explanation: The master control record (MCR) is maintained on file. It must be read in from file to:
An error occurred while reading the MCR from file.
System Action: The last MCR record is used when adding messages. If an error occurs reading this record, an attempt is made to reconstruct the chain by starting with the first record and reading as many of the records as possible. The new last MCR will then be used.
The first MCR record is used when dequeuing messages or marking message slots as inactive. If this first MCR record cannot be read, there is nothing that can be done. Processing of the MCR does not continue and return is made to the caller.
User Response: The pointers to the file copy of the first and last MCR records are in the link LK4KC keypoint at labels LK4MCA and LK4MFL respectively. The address of the link keypoint is in R4. These can be used to examine the file copies of the MCR records. Examination of the data levels in the ECB (which data level varies based on where the error occurred) can provide information about which MCR was being retrieved.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: There was an error retrieving the prime block of a partially transmitted type-B message.
System Action: If one or more blocks were transmitted already, a QTB-QTB-QTB sequence is sent to complete the message.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: There was an error while retrieving the overflow message block from file.
System Action: For type-A, the sequence ***XMIT Err*** is set up in a block. For type-B, the sequence QTB-QTB-QTB is set up. This is then treated as the last block of the message.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: There was no regenerated type-A message on the AMQ following the NAK process.
System Action: For type-A, the sequence ***XMIT error*** is set up in a block. For type-B, the sequence QTB-QTB-QTB is set up. This is then treated as the last block of the message.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: There were too many regenerated type-A message blocks on the AMQ following the NAK process.
System Action: All blocks are discard and the next NAK item (if there is any) is processed.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: There was an error while retrieving the agent assembly area (AAA) or the routing control block (RCB) for type-A NAK processing.
System Action: See the 00032C system error message for more information.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: The message saved in the agent assembly area (AAA) or the routing control bock (RCB) was overlaid by subsequent input.
System Action: See the 00032C system error message for more information.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: There was no message saved in the agent assembly area (AAA) or the routing control block (ECB) despite the reference.
System Action: See the 00032C system error message for more information.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: There was error while retrieving a nonterminal message from file.
System Action: See the 00032C system error message for more information.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: There was an error while retrieving XLMA for type-A NAK processing.
System Action: See the 00032C system error message for more information.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: There was an error while retrieving the prime message block for NAK processing.
System Action: See the 00032C system error message for more information.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: The TPF system was unable to find the highest TSI used when trying to recover from an error situation.
System Action: Processing is continued with the next NAK item, if there is any.
User Response: None.
Program: CMSM CMCK
Error Message: Error filing MCR record.
Explanation: An error occurred while filing a master control record (MCR).
System Action: Each time the MCR is updated it is written to file. An error occurred while writing an updated MCR to file. The update that was just made is lost. No further processing of the MCR takes place at this time.
If the update was a new message added, the message is lost.
If the update was a message deleted, it remains in the MCR and will be dequeued the next time CMSM is entered to dequeue a message from the MCR.
If the update was a pointer to a new MCR, it is lost and a new MCR is obtained the next time CMSM is called to add messages to the MCR.
If the update was marking a slot inactive because an acknowledgement was received, it remains an unacknowledged message and may be resent at some future time.
User Response: The pointers to the file copy of the first and last MCR records are in the link KL4KC keypoint at labels LK4MCA and LK4MFL respectively. The address of the link keypoint is in R4. These can be used to examine the file copies of the MCR records. Examination of the data levels in the ECB (which data level varies based on where the error occurred) can provide information about which MCR was being filed.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: There was an error while retrieving the prime message block with a file address obtained from the MCR.
System Action: The message is lost. Processing is continued with the next MCR item, if there is any.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: There was an error while retrieving the prime block of a message that is to be rerouted.
System Action: The message is lost and the program is exited.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: The character count in the prime block of a multiblock type-A or type-B message is not valid. The character count must be greater than the value defined in LK4MXT in the link keypoint.
System Action: The prime block is released and error text is set up in a block.
User Response: For type-A, the sequence ***XMIT error*** is used. For type-B, the sequence QTB-QTB-QTB is used. This program then sets an error indicator and returns to the calling segment through the BACKC.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: There was an error retrieving the agent assembly area (AAA) or the routing control block (RCB) while trying to retransmit a multiblock message as a new message.
System Action: The block on level 1, if present, is released and the program is exited.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: There was an error while retrieving a nonterminal-oriented message from file while trying to retransmit a message as a new message.
System Action: The program is exited.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: There was an error retrieving an agent assembly area (AAA) or a routing control block (RCB) referenced prime message block from file while trying to retransmit a message as a new message.
System Action: The block on level 2, if present, is released. The agent assembly area (AAA) or the routing control block (RCB) is released and the program is exited.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: There was an XLMA retrieval error while attempting to retransmit a multiblock message as a new message.
System Action: The block on level 1, if present, is released and the program is exited.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: There was an error while retrieving a block of a partially received message while attempting to release file space during message discard processing.
System Action: The program is exited.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: UNSOLICITED MESSAGE NOT ALLOWED
Explanation: COUB received an unsolicited message from an application program that cannot be delivered because the device is defined (RVT1) as unable to receive unsolicited messages. This error can only occur for 3270-type SDLC devices referenced by pseudo line number, interchange address, and terminal address (LNIATA).
System Action: A system error is issued and is exited.
User Response: The application program that originated the message should be reviewed and possibly modified to ensure that the device is defined as able to receive unsolicited messages.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: LOC. RTR -- there are too many blocks in the message.
System Action: The router error message processor is entered to send an error message to the console.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: LOC. RTR -- INVALID FILE ADDRESS IN MESSAGE
Explanation: LOC. RTR -- There is a file address that is not valid in the message.
System Action: The router error message processor is entered to send an error message to the console.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: The LOC. RTR-INV record is in the message chain.
System Action: The router error message processor is entered to send an error message to the console.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: LOC. RTR -- There is a hardware error on the message chain.
System Action: The router error message processor is entered to send an error message to the console.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: LOC. RTR -- There is an undetermined FIND error.
System Action: The router error message processor is entered to send an error message to the console.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: LOC. RTR -- There is a FILE error on the first block.
System Action: The router error message processor is entered to send an error message to the console.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: WGTAC ERROR RETURN
Explanation: While attempting to locate a WGTA slot for an input line number, interchange address, and terminal address (LNIATA), the WGTAC macro found an error.
System Action: A system error is issued and the program is exited. In addition, the message is discarded.
User Response: The address (LNIATA) contained in the output message is used as input to the WGTAC macro. The given LNIATA is in error.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: LOC. RTR -- There is a line number in the RCAT that is not valid.
System Action: The program is exited.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: UNABLE TO RETURN MSG TO ORIGINATOR
Explanation: The returned message cannot be routed.
System Action: The message prime core block and chained pool records are released. The program either is exited or does a BACK, depending upon the return indicated in the entry control block (ECB).
User Response: Determine why the TPF system does not return the message, for example, the lines may be down or the application program may not be active.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: An error was found on input that originated from an application program destined to another application program but the Message Router is unavailable to CSMP to route the message back to the originating application program.
System Action: A SERRC macro is issued and the program is exited.
User Response: None.
Program: CLGA, CVAA
Error Message: None.
Explanation: A message that was unable to be transmitted by the Message Router was returned to CSMP.
System Action: The message is released, a SERRC macro is issued, and the program is exited.
User Response: See your system programmer to check the following areas:
Program: COBB
Error Message: None.
Explanation: LOC. RTR-INV -- pseudo IA TA.
System Action: The program is exited.
User Response: None.
Program: COBB
Error Message: None.
Explanation: LOC. RTR-INV -- SKN in LRT.
System Action: The program is exited.
User Response: None.
Program: COQQ
Error Message: None.
Explanation: COQQ-ERR -- return from CVIO/CVIP.
System Action: The terminal error response message is not sent to the originating terminal and the program is either exited or returned to the caller.
User Response: Have your system programmer verify the status of the predefined message formats in CVIP and face is satisfied.