gtpm4m0f | Messages (System Error and Offline) |
Program: CCSNA2(CS80)
Error Message: None.
Explanation: Segment CS80 was unable to send error sense data in response to a request.
System Action: The entry control block (ECB) is ended.
User Response: Have your system programmer review the system error dump for a response protocol that is not valid.
Program: CCSNAF(CS9A)
Error Message: ROUTC ISSUED WITH INVALID LU62 CID
Explanation: This message occurs when a ROUTC macro is issued with a conversation identifier (CID) of X'00000000' or X'FFFFFFFF'. The value X'00000000' is used when a remote logical unit (LU) allocates the conversation, and the TPF system uses the value X'FFFFFFFF' to indicate an idle session. Each conversation should be assigned a unique ID that is not one of these values.
System Action: The entry control block (ECB) is ended.
User Response: Have your system programmer review the system error dump to determine the cause of the error and to correct it.
Error Message: ROUTC STATE CHECK -- REQUEST NOT AN ALLOCATE
Explanation: Only an ALLOCATE request can be made when in Between-Bracket state. This message occurs when some other request was made.
System Action: The entry control block (ECB) is ended.
User Response: Have your system programmer review the system error dump to determine the cause of the error and to correct it.
Error Message: ROUTC ALLOCATE REQUEST MISSING FMH5
Explanation: This message occurs when an ALLOCATE request is made but the functional management header is missing.
System Action: The entry control block (ECB) is ended.
User Response: Have your system programmer review the system error dump to determine the cause of the error and to correct it.
Error Message: ROUTC IN RCV_PENDING STATE HAS INVALID REQ
Explanation: A request that is not valid was made while the transaction program was waiting for confirmation. Only a CONFIRMED, SEND_ERROR, or DEALLOCATE ABEND request is permitted.
System Action: The entry control block (ECB) is ended.
User Response: Have your system programmer review the system error dump to determine the cause of the error and to correct it.
Error Message: ROUTC RECEIVE STATE -- INCONSISTENT REQUEST
Explanation: A request that is not valid was made while the transaction program was in receive state. Only a SEND_ERROR, DEALLOCATE ABEND, or REQUEST_TO_SEND request is permitted.
System Action: The entry control block (ECB) is ended.
User Response: Have your system programmer review the system error dump to determine the cause of the error and to correct it.
Error Message: ROUTC LUSTAT NOT BID, CD OR DEALLOCATE
Explanation: A null message (LUSTAT) can only be sent with a BID, change direction (CD), or DEALLOCATE request. This message occurs when some other request is made.
System Action: The entry control block (ECB) is ended.
User Response: Have your system programmer review the system error dump to determine the cause of the error and to correct it.
Error Message: ROUTC SEND STATE -- INCONSISTENT REQUEST
Explanation: This message occurs when a request that is not valid or is not consistent is made while the program is in send state.
System Action: The entry control block (ECB) 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: CCSNA2(CS10)
Error Message: INVALID OAF IN PIU
Explanation: The TPF system receive a Systems Network Architecture (SNA) input message where the origin address field (OAF) of the transmission header (TH) in the path information unit (PIU) is not one of those recognized by the TPF system.
System Action: The entry control block (ECB) is exited.
User Response: Have your system programmer review the system error dump for the origin address field (OAF).
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: The requested command is not valid. CSCD determined that the requested command was not valid for one of these reasons:
System Action: A system error is issued and is returned to the calling module with the error indicator set.
User Response: Review the system error dump for a command that is not valid.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: The device is not active or is in a state that is not consistent with the requested command.
System Action: A system error is issued and is returned to the calling module with the error indicator set.
User Response: 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 resource identifier (RID) was found not to be valid when trying to access a node control block.
System Action: If you request it, the TPF system returns with the error indicator set. Otherwise, the ECB 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: A data level error was found while trying to access a node control block.
System Action: If you request it, the TPF system returns with the error indicator set. Otherwise, the entry control block (ECB) is ended.
User Response: Have your system programmer review the system error dump to determine the cause of the error and to correct it. Either the parameter list pointed to by R1 indicates a data level that is not valid or the data level is not free.
Program: Displayed on the console and in the dump.
Error Message: VALIDATION ERROR IN RVT1,RVT2,SAT,SRT,CCB,SCB1, OR SCB2
Explanation: The Systems Network Architecture (SNA) keypoint program detected that the validity pattern in a SNA record is broken. This is a serious error since a crucial system record was altered inadvertently.
System Action: The TPF system is IPLed again.
User Response: Do the following:
Program: Displayed on the console and in the dump.
Error Message: One of the following:
Where:
Explanation: One of the Systems Network Architecture (SNA) keypoint programs detected an error due to:
System Action: The processing continues with the next record.
User Response: Do one of the following:
You can use the macro trace table in the dump to determine whether the error was due to an address retrieval or record file problem.
Program: Displayed on the console and in the dump.
Error Message: INSUFFICIENT SPACE IN CORE FOR xxxx
Where:
Explanation: The communications restart programs detected one of the following conditions:
System Action: A system error is issued and processing for this record type is ended. The RESTART ABORTED STATE CHANGE DISABLED message may be printed and the restart schedule is abnormally ended.
If the error occurred during system recovery table (SRT) processing, fresh load processing is activated immediately, allowing the restart schedule to complete normally.
User Response: Do one of the following:
See TPF ACF/SNA Data Communications Reference for more information about performing a fresh load. See TPF ACF/SNA Network Generation for more information about the SNAKEY macro.
Program: Displayed on the console and in the dump.
Error Message: One of the following:
VALIDATION ERROR IN xxxx
NO AVAILABLE SLOTS IN xxxx
Where:
Explanation: Each entry in the Systems Network Architecture (SNA) tables that were previously listed has a bit referred to as the validity bit. The pattern for these bits is an ON/OFF alternating sequence for each entry. These bits are used to detect the inadvertent alteration of any of the SNA tables. The error occurred when the broken bit pattern was found while the SNA restart programs read that table into main storage.
System Action: If an error occurs during system recovery table (SRT) processing (due to validity checking or because no SRT slots are available), fresh load processing is activated immediately, which allows the restart schedule to complete. In either case, recoverable messages and file records associated with those messages are lost.
For all other conditions, the fresh load indicator is set and the restart schedule is ended. The fresh load process is activated again with the next IPL.
User Response: Review the system error dump to determine the cause of the error and correct it.
R3 on the dump contains the starting address of the entry whose validity bit was altered. If file corruption is involved, it may be necessary to reload the SNA data pilot tape.
When the NO AVAILABLE SLOTS IN THE SR0RT condition is detected, one or more of the following actions may be necessary:
Program: Displayed on the console and in the dump.
Error Message: FACE/FILE/FIND ERROR IN xxxx ORDINAL NUMBER yyy
Where:
Explanation: The Systems Network Architecture (SNA) restart programs detected an error because one of the following errors occurred:
System Action: A system error is issued and processing for this record type is ended. The RESTART ABORTED STATE CHANGE DISABLED message may be printed and the restart schedule is ended abnormally. An indicator is set to force restart to process fresh load processing during the next IPL.
If the error occurred during SRT processing, fresh load processing is activated immediately, which allows the restart schedule to complete normally.
User Response: Do one of the following:
Use the macro trace table in the dump to determine the cause of the error.
Program: Displayed on the console and in the dump.
Error Message: FIND ERROR IN RCIT
Explanation: The application name table (ANT) load program found an error while trying to retrieve the routing control initialization (RCIT) records residing within the COHA program segment and its associated program segments.
System Action: A system error is issued and the restart schedule 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: CCSNA2 (CS10)
Error Message: INPUT PIU INVALID -- INVALID FID TYPE
Explanation: The Systems Network Architecture (SNA) read a path information unit (PIU) from a 37x5 that has a format identification field (FID) type other than FID2, or FID4.
System Action: A system error is issued, the main storage blocks that contain the PIU are returned to the TPF system, and the read is ignored.
User Response: None.
Error Message: INPUT PIU INVALID -- GREATER THAN 4K
Explanation: The Systems Network Architecture (SNA) read a path information unit (PIU) from a 37x5 that was larger than the largest message that could fit into a 4K block.
System Action: A system error is issued, the main storage blocks that contain the PIU are returned to the TPF system, and the read is ignored.
User Response: The bind image for a logical unit (LU) should not exceed 4K bytes.
R4 contains the PIU size that is not valid and R1 contains a pointer to the PIU itself.
Error Message: INPUT PIU INVALID -- DCF EQUAL 0
Explanation: The Systems Network Architecture (SNA) read a path information unit (PIU) from a 37x5 that has a data count field equal to zero.
System Action: A system error is issued, the main storage blocks containing the PIU are returned to the TPF system, and the read is ignored.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: SYSGEN/OSTG ERROR -- NO RVT ENTRY FOR THIS HOST
Explanation: The Systems Network Architecture (SNA) restart processing was unable to find the RVT1 entry for this host. This is a serious error since without the host RVT, the system services control point (SSCP) network address cannot be obtained.
System Action: A system error is issued and processing is continued.
User Response: Have your system programmer review the system error dump and the output from the offline SNA table generation (OSTG) program to determine the cause of the error and to correct it. It may be necessary to run the OSTG program again and to load the resulting SNA pilot tape.
Program: CCSNA3 (CS96)
Error Message: ROUTC ISSUED TO NON-LU NODE
Explanation: The ROUTC macro was issued to a non-logical unit (LU) node.
System Action: The program is exited.
User Response: None.
Program: CCSNA3 (CS96), CCSNA1 (CS06)
Error Message: INVALID PIU LENGTH
Explanation: The length of the path information unit (PIU) is not valid.
System Action: The program is exited.
User Response: None.
Program: CCSNA3(CS96), CCCCP1(CLXA)
Error Message: INVALID NCP OR RID
Explanation: The Network Control Program (NCP) or the resource identifier (RID) is not valid.
System Action: The program is exited.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: MESSAGE DOES NOT FIT INTO MESSAGE BLOCK
Explanation: The message does not fit into the message block.
System Action: The program is exited.
User Response: None.
Error Message: INVALID MESSAGE SIZE
Explanation: The message size is below the allowable minimum message size.
System Action: The TPF system issues the system error and the program is exited.
User Response: Have your system programmer review the system error dump to determine which application is sending the wrong size message.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: The TPF system is unable to update keypoint E to reflect the altered poll values or START/STOP of a 3705.
System Action: The program updates the core copy of the network polling table (NPT) and continues processing.
User Response: None.
Program: CCSNA3 (CS96), CMTD
Error Message: SNA/ROUTC -- INV MSG FMT FOR NPSI
Explanation: This error occurs when an application program tries to send one of the following to an NSPI logical unit (LU):
System Action: The message is discarded.
User Response: The application program must be changed to send out messages with less than 4027 bytes of data.
Program: CCSNA3 (CS96)
Error Message: OUTPUT SENT WITH NO INPUT IN SRT
Explanation: This message is self-explanatory.
System Action: The message is discarded.
User Response: The program must be changed to zero the system recovery table (SRT) reference number in the routing control parameter list (RCPL).
Program: CCSNA3 (CS96)
Error Message: TWO ROUTC'S WITH RELEASE INPUT ISSUED
Explanation: The program should not issue two release input ROUTCs for one input message.
System Action: The message is discarded.
User Response: Correct the program.
Program: Displayed on the console and in the dump.
Error Message: CANNOT READ MESSAGE ON FILE
Explanation: There was an error because the TPF system could not read the message on file.
System Action: The logical unit (LU) is stopped by the program.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: OUTPUT WAS NOT FILED
Explanation: There was an error because the output was not filed.
System Action: The logical unit (LU) is stopped by the program.
User Response: None.
Program: CCSNA3 (CS96)
Error Message: INVALID 3614 MESSAGE
Explanation: The 3614 message is not valid.
System Action: The message is discarded.
User Response: Ensure your program is building the 3614 message to be less than the maximum data.
Program: CCSNA3 (CS96)
Error Message: INVALID FARW SUPPLIED W/ROUTC
Explanation: A user issued the ROUTC macro and the routing control parameter list (RCPL) indicates that a file address was supplied in the file address reference word (FARW) on the specified level. The control program (CP) CLXA segment checked the FARW and found it to be zero (O).
System Action: The previous system error is issued and the entry control block (ECB) is exited.
User Response: Review the system error dump to determine the cause of the error and to correct it.
You can use the system error dump to determine which program issued the ROUTC macro that caused the system error. This program should be checked to determine the reason for the condition that is not valid.
Program: CCSNA3 (CS96)
Error Message: INVALID CORE BLOCK SIZE SUPPLIED W/ROUTC
Explanation: A user issued the ROUTC macro and the routing control parameter list (RCPL) indicates a file address was supplied in the file address reference word (FARW) on the specified level. The control program (CP) CLXA segment checked the associated CBRW and found that it contains a 128-byte main storage block.
System Action: The previous system error is issued and the ECB is exited.
User Response: Review the system error dump to determine the cause of the error and to correct it. You can use the system error dump to determine which program issued the ROUTC macro that caused the system error. This program should be checked to determine and correct the reason for the condition that is not valid.
Program: CCSNA3 (CS96)
Error Message: INVALID RCPL FORMAT
Explanation: An application program segment that issued a ROUTC macro to a node that was defined as a batch logical unit (LU) failed to provide a routing control parameter list (RCPL) in the expanded format.
System Action: A system error is issued and is exited.
User Response: Review the system error dump to determine the cause of the error and to correct it. Bit 7 of control byte 0 (RCPLCTL0) of the RCPL indicates the format state. If this bit is on (set to 1), then the RCPL is in the expanded format.
The application programmer must review and update the source code so that the 16-byte RCPL is used and bit 7 of RCPLCTL0 is initialized correctly to indicate this condition.
Program: CCSNA3 (CS96)
Error Message: INVALID SRT SLOT RELEASE
Explanation: A request to delete an input system recovery table (SRT) slot without any associated output text was detected for a logical unit (LU) defined as a 3270 SDLC device. This condition is not valid.
System Action: The SRT slot is released, a system error with return is issued, the associated block is released, and control is returned to the segment that issued the ROUTC macro.
User Response: Review the system error dump to determine the cause of the error and to correct it.
An examination of the system error dump will reveal Control Byte 2 that control byte 2 (RCPLCTL2) of the routing control parameter list (RCPL) is set to release the input and the functional management header that is present, and the first byte of text (AM0TXT) that is set to a X'00'. These represent a combination of conditions that are not valid for a 3270 SDLC logical unit (LU).
Program: Displayed on the console and in the dump.
Error Message: No message or one of the following:
Explanation: A FACE, FIND, or parameter error was detected during the retrieval of a network control block (NCB) by the Systems Network Architecture SNA GETNCB segment.
System Action: GET NCB processing for this record is ended. Processing continues or ends depending on the function being performed.
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 or FACE ERROR
Explanation: The Systems Network Architecture (SNA) GETNCB segment found a file address compute program (FACE) error while trying to retrieve a network control block record.
System Action: GET NCB processing for this record is ended. Processing continues or ends depending on the function being performed.
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: LEVEL 6 NOT HOLDING 381-BYTE BLOCK OR MESSAGE TEXT TOO LONG.
Explanation: On input to CSNW, level 6 must have a 381-byte message block. In addition, the message count (AM0CCT) cannot exceed 257 + the length of the functional management header (AM0FMH).
System Action: A system error is issued and then is exited (EXITC) or is returned to the calling program (BACKC) as specified by the user on input (EBRS01). The user registers are restored (R0 through R7) and the message block released.
User Response: Review the system error dump to determine the cause of the error and to correct it.
R14=1 if level 0 was not holding a block or the block was other than 381 bytes.
R14=2 if the message text was too long.
Program: Displayed on the console and in the dump.
Error Message: INVALID RID
Explanation: The system message must be for a Systems Network Architecture (SNA) logical unit (LU). If the destination resource identifier (RID) is either undefined or for a node other than an SNA LU, it is not valid.
System Action: A system error (4C4) is issued and then is exited (EXITC) or returned to the calling program (BACKC), as specified by the user on input (EBRS01). The user registers (R0 through R4) are restored and the message block released.
User Response: Review the system error dump to determine the cause of the error and to correct it.
R14=1 if there was a resource identifier (RID) conversion error, for example, the RID was not defined.
R14=2 if the RID was for a node other than an SNA logical unit (LU).
Program: Displayed on the console and in the dump.
Error Message: DESTINATION CPU IS NOT 'THIS' CPU.
Explanation: The Systems Network Architecture (SNA) output message writer (CSNW) is responsible for sending user-defined system messages to SNA logical units (LUs). These LUs must be attached to the host central processing unit (CPU).
System Action: A system error is issued and CSNW is exited (EXITC) or control is returned to the user (BACKC) as specified by the user on input (EBRS01). The user registers are the same as on input. The message block was released (D6).
User Response: Review the system error dump to determine the cause of the error and to correct it. Also look at EBROUT to determine the CPU ID of the destination CPU.
Program: Displayed on the console and in the dump.
Error Message: MORE THAN 39 CHARACTERS PER LINE.
Explanation: The CSNW multiple-line messages (messages with new line characters embedded in the text rather than just at the end of text) can have only 39 characters to a line.
New line character = X'15'
System Action: A system error is issued and the CSNW is exited (EXITC) or control is returned to the user (BACKC) as specified by the user on input (EBRS01). The user registers are the same as on input. The message block is released.
User Response: Review the system error dump to determine the cause of the error and to correct it. Also review the user-defined message (D6).
Program: Displayed on the console and in the dump.
Error Message: CVIO ERROR.
Explanation: CSNW enters CVIO to have system messages bound for Systems Network Architecture (SNA) logical units (LUs) reformatted as SNA data streams. In case of a CVIO error, control is returned to CSNW with an error indicator set (R0=0).
System Action: A system error is issued and the CSNW is exited (EXITC) or control is returned to the user (BACKC) as specified by the user on input (EBRS01). The user registers are the same as on input. The message block is released.
User Response: Review the system error dump to determine the cause of the error and to correct it. Also review the message and control information passed to CVIO (D0).
Program: CCSNA2 (CS90)
Error Message: LU EXCEEDS 256 SRT SLOTS.
Explanation: The processing of a recoverable Systems Network Architecture (SNA) message for a multi-thread logical unit (LU) in CS09 has determined that the maximum number of SRT slots for this LU system recover table (SRT) slots for this LU was reached.
System Action: The entry control block (ECB) is exited.
User Response: Review the system error dump to determine the cause of the problem and to correct it. Have your system programmer check the output queues to determine whether processing is being delayed by a line failure or a problem segment. Also, be aware of shutdown levels.
Program: CCSNA2 (CS90)
Error Message: NO SRT SLOTS AVAILABLE.
Explanation: In processing a Systems Network Architecture (SNA) recoverable message, the system recovery table (SRT) reached its limit. The error cause may be that the number of slots in the SRT is too low for the current level of system activity or that recoverable messages are not being processed to completion and the SRT slots are not being returned.
System Action: The current entry control block (ECB) is exited and the message is lost.
User Response: Have your sytem programmer review the system error dump to determine the cause of the error and to correct it.
One or more of the following actions may be necessary:
If the condition continues and the SRT does not have any available slots at the next IPL, the SRT and RVT are re-synchronized during SNA restart. Recoverable messages are lost at that time.
Program: CCSNA2 (CS10)
Error Message: INVALID DAF IN PIU.
Explanation: The TPF system received a Systems Network Architecture (SNA) input message where the destination address field (DAF) of the transmission header in the path information unit (PIU) is not one of those recognized by the TPF system.
System Action: A negative response with a sense code of X'8004' is returned to the originating logical unit (LU) if a response is allowed.
User Response: Have your system programmer review the system error dump to determine the cause of the error and to correct it.
The only DAF values that are acceptable to the TPF system are the TPF CDRM and the session partner.
Have your system programmer also check the data in the main storage block since it may be possible that another program is storing data erroneously in this main storage block. The address of the PIU in error is contained in the CE1CR0 field of the ECB.
Program: CCSNA2 (CS55)
Error Message: DIRECTION ERROR ON INCOMING MESSAGE (PIU) FROM 3276/3278
Explanation: An input message was received from a 3270 logical unit (LU) that has output pending from a previous input request. Since a true direction is not possible for 3276 LUs, the problem is most probably caused by not resetting the output pending indicator in RVT2.
System Action: The incoming message is accepted and processing is continued.
User Response: Have your system programmer review the output pending indicator in RVT2 and correct the cause of the problem.
Program: CCSNA2 (CS65)
Error Message: None.
Explanation: A bracket protocol error was found on an incoming 3276/3278 message (PIU).
A 3276 input message was received with Begin Brackets in RH, while End Brackets are owed. This condition is probably caused by the TPF system not resetting the Brackets Owed indicator when an output message with End Brackets is transmitted.
System Action: The TPF system accepts the incoming bracket state and processes the input message.
User Response: Have your system programmer review whether the Brackets Owed indicator is being reset when an output message with End Brackets is transmitted.
Program: CCSNA1 (CS07)
Error Message: SOUTC ISSUED WITHOUT BLOCK BEING HELD.
Explanation: A message block must be held by the ECB at the same level as that indicated in the SOUTC macro statement.
System Action: A system error is issued and processing is continued.
User Response: None.
Program: CCSNA1 (CS03)
Error Message: POSSIBLE ERROR IN READ CHANNEL PROGRAM
Explanation: The TPF system issued a read channel program to a 37x5 and the interrupt was processed by the CCSNA1 CS03 copy segment.
The address field in the CSW points to the second read CCW rather than the first. This indicates that one CCW was processed. However, the residual byte count is equal to the TPF UNITSZ (the size of a block for data transfer from the Network Control Program (NCP)) indicating that no data was read in.
If the first CCW of the read channel program, as indicated by information in the device operation request (DOR) block is a read (X'02') instead of a read start (X'32' or X'52'), this could be an error in the read channel program of the TPF system. Another possible cause for the error is that the address of the read channel program in the DOR block is corrupted or changed by an error in the TPF system.
System Action: Processing is continued as if no read CCWs were processed.
User Response: You must determine whether anything is wrong with the read channel program or whether the CCW area or the DOR block was corrupted or changed by erroneous software. An indication of what the channel program looked like when the start I/O was issued can be obtained from the SNADOR@ field in the CCW area. This contains the address of the DOR block. The contents of DORCAW is the channel address word of the last channel program issued. You need to review that the channel program pointed to by this address is accurate.
Program: CCSNA1 (CS05, CS0H)
Error Message: CHANNEL PROGRAM ERROR - SDA x
Where:
Explanation: A channel program check is recognized.
System Action: A catastrophic system error is issued.
User Response: Your system programmer should look at the dump to determine the cause of the channel program error and to correct it. The I/O trace table indicates the CSW status. The CCW area pointed to by R2 is also helpful for diagnosis.
Program: CCSNA1 (CS0A)
Error Message: RETRY OF SENSE ERROR UNSUCCESSFUL.
Explanation: Five attempts were made to get past a sense error that still persists.
System Action: The Load/Dump is called, blocks are returned to the TPF system, and control is returned to the interrupt handler.
User Response: None.
Program: CCSNA1 (CS0A)
Error Message: COMMAND REJ -- ACTUAL COM INVALID.
Explanation: The channel command received was not valid.
System Action: A catastrophic system error is issued.
User Response: IPL the TPF system again.
Program: CCSNA1 (CS05)
Error Message: 3705 CHAN ERROR -- CANNOT RECOVER.
Explanation: An unrecoverable MPX channel error occurred.
System Action: A system error is issued and control is returned to the interrupt handler.
User Response: None.
Program: CCSNA1 (CS07)
Error Message: SUBAREA ADDRESS IN RVT OR SCB IS 0
Explanation: The subarea address of a resource vector table (RVT) or a session control block (SCB) for a path information unit (PIU) is zero.
System Action: PIU core blocks are released to the TPF system and processing is continued.
User Response: Have your system programmer review the system error dump to determine the cause of the error and to correct it.
Error Message: DESTINATION SA AND SA IN RVT DO NOT MATCH
Explanation: The TPF system recognized an attempt to send a path information unit (PIU) to the wrong Network Control Program (NCP)/CTC. The destination resource does not have the same network subarea address as the NCP/CTC being used during SOUTC processing of the PIU.
System Action: PIU core blocks are released to the TPF system and processing is continued.
User Response: Have your system programmer review the system error dump to determine the cause of the error and to correct it.
Program: CCSNA1 (CS07)
Error Message: NUMBER OF CHAINED BLOCKS EXCEEDED 8. PIU DISCARDED.
Explanation: The 37X5 Network Control Program (NCP) I/O support for Systems Network Architecture (SNA) can send a maximum of eight CCWs to the NCP with each start I/O.
If the user has a path information unit (PIU) that is main storage chained using more than eight main storage blocks, the TPF system cannot build the CCW to send it.
System Action: A system error is issued and the main storage blocks that constitute the PIU are returned to the TPF system and normal processing is continued.
User Response: If the user is already using eight 1055-byte blocks, resegmenting of the output message should be done and a separate ROUTC macro issued. If the main storage blocks are 381 or 128 in size, a larger main storage block size may be used to contain the PIU.
R3 in the dump points to the beginning of the first block of the PIU. The chaining convention used is described in (SOUTC).
Program: Displayed on the console and in the dump.
Error Message: CHAIN OF AVAILABLE SRT ENTRIES IS NOT VALID.
Explanation: During a system services control point (SSCP) restart, the chain of system recovery table (SRT) entries were identified as not valid. Either the end of the chain was not delineated or one of the pointers to the next entry in the chain was set to an incorrect value.
System Action: A system error is issued and a fresh copy of the Systems Network Architecture (SNA) tables is loaded. All messages that were previously in the SRT are lost.
User Response: Have your system programmer review the system error dump to determine the cause of the error and to correct it.
Program: CCSNAB (CS70)
Error Message: BRACKET PROTOCOL VIOLATION - SESSION TERMINATED
Explanation: An error occurred because the begin and end brackets are unmatched.
System Action: The communication session is ended.
User Response: Do the following:
Program: CSX3
Error Message: CONTROL VECTOR 22 SENT/RECEIVED DURING XID
Explanation: During adjacent link station (ALS) channel contact processing, an XID format 3 I-field was received from the Network Control Program (NCP) with XID Negotiation Error control vector X'22'. It is probable that there is a mismatch between the TPF definition and the NCP generation on the host parameters.
System Action: A system error is issued. The channel contact sequence is ended and the ECB is exited.
User Response: Have your system programmer review the system error dump for control vector 22 in the XID 3 I-field to determine the cause of the error and to correct it.
Program: CSX5
Error Message: ERROR RECEIVED DURING XID.
Explanation: During the Network Control Program (NCP) channel contact processing, an XID format 2 I-field was received from NCP with an error indicator set. It is probable that there is a mismatch between the TPF definition and the NCP generation on the host parameters.
System Action: A system error is issued. The channel contact sequence is ended.
User Response: Have your system programmer review the system error dump for the error status (byte 18) in the XID 2 I-field to determine the cause of the error and to correct it.
See TPF ACF/SNA Data Communications Reference for more information about the FID4 considerations and a description of the TPF XID.
Program: CSX6
Error Message: ERROR RECEIVED DURING CTC XID.
Explanation: During CTC channel contact processing, one of the following errors occurred:
It is probable that there is a mismatch between the TPF definitions and the VTAM definitions or differences between definitions in this TPF system and the other TPF system, if the connection is a TPF-to-TPF connection. The content of the XID I-field and the read header are dumped as SLIST parameters in this dump. These fields show up as USER SPECIFIED AREAS.
System Action: A system error is issued. The channel contact sequence is ended.
User Response: Have your system programmer review the system error dump for the error status (byte 18) in the XID 2 I-field to determine the cause of the error and to correct it.
If the I-field does not indicate the error, then review the SAT, the RVT, and so on of the CTC link as a possible cause of the error. The I/O trace table entries indicate that the CSW status returned. The CCW area pointed to by R2 also helps in the diagnosis.
Program: Displayed on the console and in the dump.
Error Message: OMT -- NCB FIND/FILE ERR (NC0CB)
Explanation: An I/O error occurred following a find or file request for the node control block.
System Action: A system error is issued and the active session is ended.
User Response: Move the DASD packs involved and start the nodes affected. For persistent errors, a copy pack operation should be performed and the node control block (NCB) for the affected nodes initialized with the ZNNCB command without the purge options. The nodes should then be started.
Program: Displayed on the console and in the dump.
Error Message: PACING COUNT ERROR.
Explanation: The next window size (RV2NWS) and residual pacing count (RV2RPC) are both zero.
System Action: A system error is issued and control is returned to the next sequence instruction.
User Response: Have your system programmer review the system error dump to determine the cause of the error and to correct it. The resource vector table (RVT) entries and the path information unit (PIU) trace table are included in the dump for problem determination.
Program: Displayed on the console and in the dump.
Error Message: OMT -- NCB O/P MSG QUEUE BAD
Explanation: The output message transmission logic is unable to dequeue the first message from queue for a node.
System Action: A system error is issued and the node control block (NCB) section 1 is initialized.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: A software I/O error occurred following a find request for an overflow segment of a multi-segment message.
System Action: A cancel is issued. The failing message is discarded and a system error is issued.
User Response: Have your system programmer review the system error dump to determine whether a software error occurred and then take the appropriate action.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: There are bad pointers in the node control block (NCB).
System Action: The program resets the queue of the NCB to zero.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: A message length that is not valid was detected in the message header.
System Action: The program discards the message and returns to the caller.
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: INVALID FUNCTION CODE.
Explanation: The CMT4 program was called with a function code that was greater than any currently supported.
System Action: The ECB is exited.
User Response: Identify which program called the CMT4 program and ensure that the requested function is available.
R1 points to the parameter area passed to the CMT4 program. Displacement 0 through 3 contains the function code.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: The TPF system was unable to get the resource vector table (RVT) address from the resource identifier (RID) routine.
System Action: None.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: PIU RETRIEVAL ERROR
Explanation: A FIND error was detected during the retrieval of the path information unit (PIU).
System Action: A system error is issued and the program 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: CCSNA1 (CSX2)
Error Message: NO CCW AREAS AVAILABLE FOR ALS
Explanation: When a valid XID I-field is received during prenegotiation XID processing, the CCW areas are scanned for an unused CCW area. If all the CCW areas are in use, this dump is issued.
System Action: None.
User Response: Have your system programmer review the coding of the SNAKEY macro for generation of keypoint 2 (CTK2). The MAXALS parameter determines the maximum number of Network Control Programs (NCPs) that can be active at any one time and, therefore, the number of CCW areas generated for the system. This parameter should be increased, the new keypoint should be loaded into the TPF system, and the TPF system IPLed before continuing.
Program: CCSNA3 (CS96, CS97)
Error Message: RVT LOCK TIME-OUT
Explanation: An application program issued a ROUTC macro to a Systems Network Architecture (SNA) resource and the I-stream upon which the request was issued waited more than 1 second to obtain the resource vector table (RVT) lock used to serialize SOUTC queuing.
System Action: A SNAP dump is issued and processing is continued without obtaining the RVT lock. The current ECB releases the lock when control is returned from SOUTC queuing. The RVT lock remains on when an ECB abends during SOUTC queuing.
User Response: Have your system programmer review the consoles for previous communications related errors.
Program: CCSNA4 (CS0E)
Error Message: CS0E RVT LOCK TIME-OUT.
Explanation: RVTSCAN processing attempted to build a Systems Network Architecture (SNA) path information unit (PIU) for a data flow control (DFC) command and waited more than 1 second to obtain the resource vector table (RVT) lock of the associated logical unit (LU) that is used to serialize SOUTC macro queuing.
System Action: A SNAP dump is issued and processing is continued without obtaining the RVT lock. The current ECB releases the lock when control is returned from SOUTC macro queuing. The RVT lock remains on when an ECB abends during SOUTC macro queuing.
User Response: Have your system programmer review the consoles for previous communications-related errors.
Program: Displayed on the console and in the dump.
Error Message: PROTOCOL VIOLATION ERROR
Explanation: There was a protocol violation (for example, sense data that is not valid), or the length in the 3614 message is not valid.
System Action: Do one of the following:
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: A transmission header that is not valid was recognized by the TPF system.
System Action: For a batch logical unit (LU), the message is sent again. Otherwise, control is returned to the interrupt handler.
User Response: None.
Program: Displayed on the console and in the dump.
Error Message: RTR RECEIVED FROM LU UNDER PTV.
Explanation: An RTR was received from a logical unit (LU) under the program test vehicle (PTV).
System Action: None.
User Response: None.
Program: CSX7
Error Message: REQUEST TO RELEASE INACTIVE CCW
Explanation: The address of a CCW area not in use was passed to the release CCW routine.
System Action: Control is returned to the calling program.
User Response: Have your system programmer review the system error dump to determine cause of the error and to correct it.
Error Message: INVALID CW0CC ADDRESS
Explanation: A Systems Network Architecture (SNA) channel command work area address that is not valid was passed to the release CW0CC routine.
System Action: Control is returned to the calling program.
User Response: Have your system programmer review the system error dump to determine cause of the error and to correct it.
Program: CSX7
Error Message: INVALID SNA BUFFER ADDRESS
Explanation: A Systems Network Architecture (SNA) buffer address that is not valid was passed to the release buffer routine.
System Action: Control is returned to the calling program.
User Response: Have your system programmer review the system error dump to determine cause of the error and to correct it.
Program: CS07
Error Message: OUTPUT PIU SIZE EXCEEDS CTC BUFFER
Explanation: The size of a chained output path information unit (PIU) exceeds the size of the channel-to-channel (CTC) link write buffer.
System Action: The output PIU is discarded.
User Response: Have your system programmer increase the size of the write buffer. The write buffer size, which equals the size of the remote system read buffer, is determined during XID processing.