gtpm4m1a | Messages (System Error and Offline) |
Program: Displayed on the console and in the dump
Error Message: None.
Explanation: The conversation ID passed in the routing control parameter list (RCPL), which is defined in the RCPL6CID field of the RC0PL data area, does not match the conversation ID of the conversation control block (CCB) to which it points.
System Action: A system error is issued and the program is exited.
User Response: Review the system error dump to determine why the conversation IDs are not equal.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: The conversation ID passed in the routing control parameter list (RCPL), which is defined by the RCPL6CID field of the RC0PL data area, contained zeros.
System Action: A system error is issued and the program is exited.
User Response: Review the system error dump to determine why the RCPL was not set up correctly.
Program: Displayed on the console and in the dump
Error Message: None.
Explanation: The session control block identifier (SCBID) in the routing control parameter list (RCPL) which is defined by the RCPLORGR field of the RC0PL data area, does not match the SCBID in the conversation control block (CCB).
System Action: A system error is issued and the program is exited.
User Response: Review the system error dump to determine why the SCBIDs are not equal.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: The conversation control block (CCB) pointed to by the conversation ID in the routing control parameter list (RCPL), which is defined in the RCPL6CID field of the RC0PL data area, is marked as not in use.
System Action: A system error is issued and the program is exited.
User Response: Review the system error dump to determine whether that CCB is actually in use and if not, why the RCPL6CID field is pointing to it.
Program: Displayed on the console and in the dump
Error Message: None.
Explanation: The required request block on data level 14 (D14) was not passed.
System Action: The DEALLOCATE_CLEANUP (CHQF) process is activated.
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 required functional management header (FMH) was not passed in the request block on data level 14 (D14).
System Action: The DEALLOCATE_CLEANUP (CHQF) process is activated.
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: CHDR issues this error when a segment in the presentation services (PS) layer requests a half-session function that is not valid.
Valid half-session functions are:
System Action: The DEALLOCATE_CLEANUP (CHQF) process is activated.
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: CHDR issues this error when a segment in the presentation services (PS) layer requests a send data record function but the data type is not valid.
System Action: The DEALLOCATE_CLEANUP (CHQF) process is activated.
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: CHDR issues this error when a segment in the resource manager (RM) layer requests a half-session function that is not valid.
System Action: The DEALLOCATE_CLEANUP (CHQF) process is activated.
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: CHDR issues this error when a segment in the half-session (HS) requests a half-session function that is not valid.
System Action: The DEALLOCATE_CLEANUP (CHQF) process is activated.
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 error finite state machine is in an illogical state.
System Action: The DEALLOCATE_CLEANUP (CHQF) process is activated.
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: While processing the WAIT verb, an error occurred during an attempt to find a conversation control block (CCB) ID in the TP_TO_PS_WAIT_RESID_LIST.
System Action: Returns to the TPF transaction program with a parameter error return code.
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 conversation finite state machine is in an illogical state.
System Action: The DEALLOCATE_CLEANUP (CHQF) process is activated.
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: A verb that is not valid or is not implemented was issued.
System Action: The DEALLOCATE_CLEANUP (CHQF) process is activated.
User Response: Review the system error dump to determine the cause of the error and to correct it.
Program: C266, C267, C268, or C278
Error Message: INVALID MAPPED CONVERSATION SUPPORT VERB
Explanation: A mapped conversation macro passed a verb parameter that is not valid to a C library function.
System Action: If an active conversation exists for the conversation control block (CCB), the conversation is abended (DEALLOCATE TYPE=DEALLOCATE_SVC). The Mapped Conversation Support API sets the return code to CM_PRODUCT_SPECIFIC_ERROR and returns to the calling function.
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 PREPARE_TO_RECEIVE verb was issued with TYPE=CONFIRM while the synchronization level (SYNC) was NONE.
System Action: The DEALLOCATE_CLEANUP (CHQF) process is activated.
User Response: Check the transaction program that issued the verb.
Program: Displayed on the console and in the dump
Error Message: None.
Explanation: An error occurred while trying to find (the FINWC macro) a SEND_DATA record.
System Action: The system DEALLOCATE_CLEANUP (CHQF) process is activated.
User Response: Do one of the following:
Program: Displayed on the console and in the dump
Error Message: None.
Explanation: A remote transaction program issued an ALLOCATE request, but the name of the transaction program to be activated is not valid. The transaction program name is in the functional management header type 5 that is the ATTACH header. See the IFMH5 DSECT for more information.
System Action: The ATTACH_ERROR (CHQD) process is activated.
User Response: Do one of the following:
Explanation: A local TPF transaction program issued an ALLOCATE request, but the length of the transaction program name specified on the ALLOCATE verb is not valid. The length must be between 1 and 64.
System Action: The TPF system returns to the transaction program with a parameter check.
User Response: Correct the transaction program that issued the ALLOCATE verb.
Program: Displayed on the console and in the dump
Error Message: None.
Explanation: CHRA issues this error when the work buffer (DSECT IWBL) owner is not presentation services (PS) or half-session (HS).
System Action: The DEALLOCATE_CLEANUP (CHQF) process.
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 TPF system issues this error when the SYNC_LEVEL on the ALLOCATE verb that was passed from the presentation services (PS) layer to the resource manager (RM) layer is not valid.
System Action: The DEALLOCATE_CLEANUP (CHQF) process is activated.
User Response: Check the transaction program that issued this verb.
Program: Displayed on the console and in the dump
Error Message: None.
Explanation: CHRD issues this error when a segment in the presentation services (PS) layer requests a resource manager (RM) function that is not valid.
System Action: The DEALLOCATE_CLEANUP (CHQF) process is activated.
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: CHRD issues this error when a segment in the half-session (HS) layer requests a resource manager (RM) that is not valid.
System Action: The DEALLOCATE_CLEANUP (CHQF) process is activated.
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: An ATTACH header (DSECT IFMH5) that is not valid was received.
System Action: Calls the ATTACH_ERROR procedure (CHQD).
User Response: Check that the remote logical unit (LU) sent out the ATTACH.
Program: Displayed on the console and in the dump
Error Message: None.
Explanation: When requesting a session, this error occurs when the destination LU_NAME passed is not a valid LU 6.2 node defined by OSTG or when the LU_NAME is not unique.
If the LU_NAME is not unique, it must be qualified with a network identifier (NETID).
System Action: The TPF system returns control to the previous segment (through the BACKC macro).
User Response: Check the transaction program that requested the session.
Program: Displayed on the console and in the dump
Error Message: None.
Explanation: A protocol error occurred. The remote transaction program issued a SEND_ERROR and sent a sense code of X'0846', but did not follow it with the required FMH7 error record. See the IFMH7 DSECT for more information.
System Action: The PS_PROTOCOL_ERROR (CHQH) process is activated.
User Response: Check the transaction program and the logical unit (LU) that caused the protocol error.
Program: Displayed on the console and in the dump
Error Message: None.
Explanation: An error occurred while trying a find (the FINWC macro) on a record in the conversation control block (CCB) inbound queue.
System Action: The DEALLOCATE_CLEANUP (CHQF) process is activated.
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 transaction program found an error and sent a negative response. The TPF system issues this system error when it times out while waiting for an end-of-chain, which indicates that it is fine to send the FMH7.
System Action: The DEALLOCATE_CLEANUP (CHQF) process is activated.
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: A data type record that was not valid was received.
System Action: The DEALLOCATE_CLEANUP (CHQF) process.
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 EVNTC macro was issued with a duplicate name.
System Action: The DEALLOCATE_CLEANUP (CHQF) process is activated.
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 TPF system issued the IFSMC macro and a logic error occurred due to a state condition that is not valid when updating the conversation finite state machine.
System Action: The DEALLOCATE_CLEANUP (CHQF) process is activated.
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: A logic error occurred due to an illogical state condition when updating the error finite state machine.
System Action: The DEALLOCATE_CLEANUP (CHQF) process is activated.
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: A logic error occurred due to an illogical state condition when updating the post finite state machine.
System Action: The DEALLOCATE_CLEANUP (CHQF) process is activated.
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: A routing control parameter list (RCPL) that was not valid was received. The RCPL indicated a begin bracket (BB) but the ATTACH header (DSECT IFMH5) was not valid or was missing.
System Action: A system error is issued and the program is exited.
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: A functional management header type 5 (the ATTACH header; the IFMH5 DSECT) is required but was not provided.
System Action: The DEALLOCATE_CLEANUP (CHQF) process is activated.
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: A functional management header type 7 (the IFMH7 DSECT) error record is required but was not provided.
System Action: The DEALLOCATE_CLEANUP (CHQF) process is deactivated.
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 following conditions may cause this error:
System Action: The TPF system brings down the session with the remote logical unit (LU) and issues the C62031 system error.
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 remote logical unit (LU) sent a functional management header type 7 (the IFMH7 DSECT) error record that is not valid.
System Action: The PS_PROTOCOL_ERROR (CHQH) process is activated.
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: An I/O error occurred attempting to add a record to the conversation control block (CCB) inbound queue for a conversation.
System Action: The TPF system unbinds the session.
User Response: None.
Program: Displayed on the console and in the dump
Error Message: None.
Explanation: The EVNWC macro returned with an error.
System Action: The DEALLOCATE_CLEANUP (CHQF) process is activated.
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: This error occurs when there is a return code from INQRC or RIDCC that indicates the TPF system was unable to do a RID to LUNAME conversion.
System Action: A system error is issued and the program is exited.
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: This error is issued when there is an error return code from POSTC because the event name was not found.
System Action: If the error occurs in the CHDF segment, the TPF system exits. Otherwise, the DEALLOCATE_CLEANUP (CHQF) process is activated.
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: This error occurs when the destination session control block identifier (SCBID) in the conversation control block (CCB) is not valid.
System Action: Control is returned to the previous segment through the BACKC macro.
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: This error occurs when there is a time out during an EVNWC.
System Action: The DEALLOCATE_CLEANUP (CHQF) process is activated.
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: This error is issued when a program issues an ALLOCATE request but no conversation control control blocks (CCBs) are defined to the TPF system.
System Action: Control is returned to the previous segment through the BACKC macro.
User Response: CCBs are defined to the TPF system with the MAXCCB field in the Systems Network Architecture (SNA) keypoint (DSECT CK2SN). The value must be greater than two to use the TPF/APPC functions.
Error Message: ALL CCB BLOCKS IN USE -- ADVISE COVERAGE TO CHECK CCB CORE ALLOCATION
Explanation: This error is issued when a program issues an ALLOCATE request but all the conversation control blocks (CCBs) are in use.
System Action: Control is returned to the previous segment through the BACKC macro.
User Response: To define more CCBs to the TPF system, increase the value of MAXCCB in the SNA keypoint (DSECT CK2SN).
Program: Displayed on the console and in the dump
Error Message: None.
Explanation: This occurs when the DEALLOCATE_CLEANUP procedure is unable to return the conversation control block (CCB) to the available list because CCB ID in the work buffer (which is defined by the IWBL data macro) is not valid.
System Action: Control is returned to the previous segment through the BACKC macro.
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 TPF system issues this error when an error is received from the EVNWC macro because the event name was not found.
System Action: The DEALLOCATE_CLEANUP (CHQF) process is activated.
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: A protocol error was detected but TPF was unable to terminate the session.
System Action: The TPF system returns control to the previous segment through the BACKC macro.
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 TPF system issued the ILCKCB macro but this ECB already holds a lock for the specified control block area.
System Action: A SERRC macro is issued and processing is continued.
User Response: Review the system error dump to determine the cause of the error and to correct it. If necessary, see your IBM service representative.
Program: Displayed on the console and in the dump
Error Message: None.
Explanation: The TPF system issued the IULKCB macro but the control block area is not locked.
System Action: A system error is issued and processing is continued.
User Response: Review the system error dump to determine the cause of the error and to correct it. If necessary, see your IBM service representative.
Program: Displayed on the console and in the dump
Error Message: None.
Explanation: The TPF system issued the IULKCB macro but the lock is held by a different ECB. An IULKCB macro can only be issued by the ECB that issued the ILCKCB for that control block.
System Action: A system error is issued and processing is continued.
User Response: Review the system error dump to determine the cause of the error and to correct it. If necessary, see your IBM service representative.
Program: Displayed on the console and in the dump
Error Message: None.
Explanation: The transaction program issued a WAIT verb with more than the maximum number of entries allowed in the resource identifier (RID) list.
System Action: Processing is continued ignoring any entries above the maximum number.
User Response: Check the transaction program that issued the WAIT verb. Correct the logic that produces more than the maximum number of entries in the resource identifier (RID) list.
Program: Displayed on the console and in the dump
Error Message: None.
Explanation: The transaction program issued a WAIT verb with no conversation control block (CCB) IDs in the resource identifier (RID) list.
System Action: A return code is set and control is returned to the transaction program.
User Response: Check the transaction program that issued the WAIT verb. Correct the logic that results in no entries in the resource identifier (RID) list.
Program: Displayed on the console and in the dump
Error Message: None.
Explanation: This error occurs when the TPF system cannot activate the program name specified on the ACTIVATE_ON_RECEIPT or ACTIVATE_ON_CONFIRMATION verb (the PGM parameter). This indicates that the program name saved in the conversation control block (CCB) was corrupted and is no longer valid.
System Action: A SERRC macro is issued and the program is exited. The SERRC processing invokes the abend processor segment (CHDE) to send out a DEALLOCATE_ABEND for all conversations associated with this transaction program.
User Response: Review the system error dump to determine why the program name saved in the CCB is not valid.
Program: CHRA
Error Message: ALL TPICBS IN USE -- CHECK TPICB CORE ALLOCATION
Explanation: A transaction program called the TPPCC ALLOCATE macro and the ALLOCATE processing requires allocation of a transaction program instance control block (TPICB) but all of the TPICBs are already in use.
System Action: Control returns to the transaction program with the storage specified by the RCODE macro parameter set to LU62RC_ALLOC_ERROR, LU62RC_ALLOCERR_NORETRY.
User Response: Define sufficient TPICBs in the TPF system by increasing the value of MAXTPI in the Systems Network Architecture (SNA) keypoint (CTK2).
Program: CCEB
Error Message: TPICB ORDINAL NUMBER GREATER THAN MAXTPI
Explanation: The transaction program instance control block (TPICB) ordinal number in the exiting ECB is greater than the number of TPICBs defined in the TPF system by MAXTPI.
System Action: Exit processing is continued for the ECB.
User Response: Review the system error dump to determine the cause of the error and to correct it. If necessary, see your IBM service representative.
Error Message: UNABLE to RELEASE TPICB
Explanation: The transaction program instance control block (TPICB) ordinal number in the exiting ECB is not zero. This indicates that a TPICB is assigned to the ECB but the ITPICB header indicates that no TPICBs are currently assigned.
System Action: Exit processing is continued for the ECB.
User Response: Review the system error dump to determine the cause of the error and to correct it. If necessary, see your IBM service representative.
Program: CHRG
Error Message: ALL SCB BLOCKS IN USE
Explanation: A request was made to get a session control block (SCB) entry but all SCB entries are in use.
System Action: None.
User Response: Do the following:
See TPF ACF/SNA Network Generation for more information about the SNAKEY macro.
Program: CHRG
Error Message: None.
Explanation: A request was made to get a session control block (SCB) entry for a logical unit (LU) but the resource identifier (RID) was not correct.
System Action: None.
User Response: Review the system error dump to determine why the RID passed to CHRG was not correct and correct the error.
Program: CHRR
Error Message: None.
Explanation: A request was made to return a session control block (SCB) entry for a logical unit (LU) but the SCBID was not correct.
System Action: None.
User Response: Review the system error dump to determine why the SCBID passed to CHRR was not correct and correct the error.
Program: CHRS
Error Message: None.
Explanation: One of the following errors occurred:
System Action: The entry control block (ECB) exits.
User Response: Review the system error dump to determine the cause of the error and to correct it.
Program: CHKR
Error Message: SCB CHAIN ERROR FOUND IN LU=luname
Explanation: A chain error was detected during restart while verifying the session control block (SCB) chain for a particular logical unit (LU).
System Action: All SCBs for this LU are returned to the pool of available SCBs and processing is continued.
User Response: Review the system error dump to determine why the SCB chain was not correct and correct the error. The dump contains the LU RVT1 entry and the entire SCB1 area to aid in finding the chain error.
Program: CHZU or CHZW
Error Message: FIND FAILURE ON SIDE INFORMATION TABLE FIXED FILE RECORD
Explanation: An error occurred while executing a FIND macro against the online side information table during ZNSID command processing.
System Action: The entry control block (ECB) for the ZNSID command is exited.
User Response: Review the system error dump to determine why the FIND macro failed and correct the error.
Program: CHZU or CHZW
Error Message: FILE FAILURE ON SIDE INFORMATION TABLE FIXED FILE RECORD
Explanation: An error occurred while executing a FILE macro against the online side information table during ZNSID command processing.
System Action: The entry control block (ECB) for the ZNSID command is exited.
User Response: Review the system error dump to determine why the FILE macro failed and correct the error.
Program: C269
Error Message: INVALID MAPPED CONVERSATION SUPPORT CCB
Explanation: The conversation control block (CCB) ID for a nonmapped conversation was passed to a mapped conversation verb or the CCB was corrupted.
System Action: If an active conversation exists for the CCB, the conversation is abended (DEALLOCATE TYPE=DEALLOCATE_SVC). The Mapped Conversation Support API sets the return code to CM_PRODUCT_SPECIFIC_ERROR and returns to the calling function.
User Response: Review the system error dump and the program segment that issued the mapped conversation verb to determine the cause of the error and correct it.
Program: C269
Error Message: UNKNOWN TPPC RCODE RETURNED TO MAPPED SUPPORT
Explanation: A TPF/APPC basic verb called by mapped conversation support returned a return code value that mapped conversation support does not recognize.
System Action: If an active conversation exists for the CCB, the conversation is abended (DEALLOCATE TYPE=DEALLOCATE_SVC). The Mapped Conversation Support API sets the return code to CM_PRODUCT_SPECIFIC_ERROR and returns to the calling function.
User Response: 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: An output message in AM0SG format was passed to the SEND_DATA verb, but the
character count field (AM0CCT) of the output message exceeds the logical block
size.
System Action: The DEALLOCATE_CLEANUP (CHQF) process is activated.
User Response: Do the following:
Program: C264
Error Message: EITHER FIELD OR LEVEL ARE NEEDED FOR ACTIVATE ON CONFIRMATION
Explanation: The TPF/APPC tppc_activate_on_confirmation function was passed a FIELD parameter of NULL and a LEVEL parameter of AOC_NO_DL.
System Action: Control is returned to the caller with the RCODE parameter set to LU62RC_PARAMETER_CHECK, LU62RC_PK_BAD_OPTION.
User Response: Correct the error in the function call.
See TPF C/C++ Language Support User's Guide for more information about the tppc_activate_on_confirmation function and its parameters.
Program: C265
Error Message: EITHER FIELD OR LEVEL ARE NEEDED FOR ACTIVATE ON RECEIPT
Explanation: The TPF/APPC tppc_activate_on_receipt function was passed a FIELD parameter of NULL and a LEVEL parameter of AOR_NO_DL.
System Action: Control is returned to the caller with the RCODE parameter set to LU62RC_PARAMETER_CHECK, LU62RC_PK_BAD_OPTION.
User Response: Correct the error in the function call.
See TPF C/C++ Language Support User's Guide for more information about the tppc_activate_on_receipt function and its parameters.
Program: C255
Error Message: GET ATTRIBUTE PARAMETERS OWNNAME, PLUNAME, MODE AND SYNC ARE ALL NULL
Explanation: The TPF/APPC tppc_get_attributes function was passed as NULLs in the OWNNAME, PLUNAME, MODE, and SYNC parameters. At least one of these parameters must be non-NULL.
System Action: Control is returned to the caller with the RCODE parameter set to LU62RC_PARAMETER_CHECK, LU62RC_PK_BAD_OPTION.
User Response: Correct the error in the function call.
See TPF C/C++ Language Support User's Guide for more information about the tppc_get_attributes function and its parameters.
Program: C256
Error Message: INVALID FILL OPTION PASSED TO TPPC POST ON RECEIPT FUNCTION
Explanation: The TPF/APPC tppc_post_on_receipt function was passed a FILL parameter value other than POST_ON_RECEIPT_FILL_LL.
System Action: Control is returned to the caller with the RCODE parameter set to LU62RC_PARAMETER_CHECK, LU62RC_PK_BAD_OPTION.
User Response: Correct the error in the function call. See TPF C/C++ Language Support User's Guide for more information about the tppc_post_on_receipt function and its parameters.
Program: C258
Error Message: INVALID FILL OPTION PASSED TO TPPC RECEIVE FUNCTION
Explanation: The TPF/APPC tppc_receive function was passed a FILL parameter value other than RECEIVE_FILL_LL.
System Action: Control is returned to the caller with the RCODE parameter set to LU62RC_PARAMETER_CHECK, LU62RC_PKBAD_OPTION.
User Response: Correct the error in the function call.
See TPF C/C++ Language Support User's Guide for more information about the tppc_receive function and its parameters.
Program: C264
Error Message: INVALID LEVEL OPTION PASSED TO TPPC ACTIVATE ON CONFIRMATION FUNCTION
Explanation: The TPF/APPC tppc_activate_on_confirmation function was passed a LEVEL parameter value other than AOC_D0, AOC_D1, AOC_D2, AOC_D3, AOC_D4, AOC_D5, AOC_D6, AOC_D7, AOC_D8, AOC_D9, AOC_DA, or AOC_NO_DL.
System Action: Control is returned to the caller with the RCODE parameter set to LU62RC_PARAMETER_CHECK, LU62RC_PK_BAD_OPTION.
User Response: Correct the error in the function call.
See TPF C/C++ Language Support User's Guide for information about the tppc_activate_on_confirmation function and its parameters.
Program: C265
Error Message: INVALID LEVEL OPTION PASSED TO TPPC ACTIVATE ON RECEIPT FUNCTION
Explanation: The TPF/APPC tppc_activate_on_receipt function was passed a LEVEL parameter value other than AOR_D1, AOR_D2, AOR_D3, AOR_D4, AOR_D5, AOR_D6, AOR_D7, AOR_D8, AOR_D9, AOR_DA, or AOR_NO_DL.
System Action: Control is returned to the caller with the RCODE parameter set to LU62RC_PARAMETER_CHECK, LU62RC_PK_BAD_OPTION.
User Response: Correct the error in the function call.
See TPF C/C++ Language Support User's Guide for more information about the tppc_activate_on_receipt function and its parameters.
Program: C257
Error Message: INVALID LOCKS OPTION PASSED TO TPPC PREPARE TO RECEIVE FUNCTION
Explanation: The TPF/APPC tppc_prepare_to_receive function was passed a LOCKS parameter value other than PREP_TO_RECEIVE_LOCKS_SHORT.
System Action: Control is returned to the caller with the RCODE parameter set to LU62RC_PARAMETER_CHECK, LU62RC_PK_BAD_OPTION.
User Response: Correct the error in the function call. See TPF C/C++ Language Support User's Guide for more information about the tppc_prepare_to_receive function and its parameters.
Program: C253
Error Message: INVALID LOGDATA OPTION PASSED TO TPPC DEALLOCATE FUNCTION
Explanation: The TPF/APPC tppc_deallocate function was passed a LOGDATA parameter value other than DEALLOCATE_LOGDATA_NO.
System Action: Control is returned to the caller with the RCODE parameter set to LU62RC_PARAMETER_CHECK, LU62RC_PK_BAD_OPTION.
User Response: Correct the error in the function call.
See TPF C/C++ Language Support User's Guide for more information about the tppc_deallocate function and its parameters.
Program: C261
Error Message: INVALID LOGDATA OPTION PASSED TO TPPC SEND ERROR FUNCTION
Explanation: The TPF/APPC tppc_send_error function was passed a LOGDATA parameter value other than SEND_ERROR_LOGDATA_NO.
System Action: Control is returned to the caller with the RCODE parameter set to LU62RC_PARAMETER_CHECK, LU62RC_PK_BAD_OPTION.
User Response: Correct the error in the function call.
See TPF C/C++ Language Support User's Guide for more information about the tppc_send_error function and its parameters.
Program: C250
Error Message: INVALID PIP OPTION PASSED TO TPPC ALLOCATE FUNCTION
Explanation: The TPF/APPC tppc_allocate function was passed a PIP parameter value other than ALLOCATE_PIP_NO.
System Action: Control is returned to the caller with the RCODE parameter set to LU62RC_PARAMETER_CHECK, LU62RC_PK_BAD_OPTION.
User Response: Correct the error in the function call.
See TPF C/C++ Language Support User's Guide for more information about the tppc_allocate function and its parameters.
Program: C250
Error Message: INVALID RCONTROL OPTION PASSED TO TPPC ALLOCATE FUNCTION
Explanation: The TPF/APPC tppc_allocate function was passed an RCONTROL parameter value other than ALLOCATE_RCONTROL_WSA or ALLOCATE_RCONTROL_IMM.
System Action: Control is returned to the caller with the RCODE parameter set to LU62RC_PARAMETER_CHECK, LU62RC_PK_BAD_OPTION.
User Response: Correct the error in the function call.
See TPF C/C++ Language Support User's Guide for more information about the tppc_allocate function and its parameters.
Program: C250
Error Message: INVALID SECURITY OPTION PASSED TO TPPC ALLOCATE FUNCTION
Explanation: The TPF/APPC tppc_allocate function was passed a SECURITY parameter value other than ALLOCATE_SECURITY_NO.
System Action: Control is returned to the caller with the RCODE parameter set to LU62RC_PARAMETER_CHECK, LU62RC_PK_BAD_OPTION.
User Response: Correct the error in the function call.
See TPF C/C++ Language Support User's Guide for more information about the tppc_allocate function and its parameters.
Program: C250
Error Message: INVALID SYNC OPTION PASSED TO TPPC ALLOCATE FUNCTION
Explanation: The TPF/APPC tppc_allocate function was passed a SYNC parameter value other than ALLOCATE_SYNC_NONE or ALLOCATE_SYNC_CONFIRM.
System Action: Control is returned to the caller with the RCODE parameter set to LU62RC_PARAMETER_CHECK, LU62RC_PK_BAD_OPTION.
User Response: Correct the error in the function call.
See TPF C/C++ Language Support User's Guide for more information about the tppc_allocate function and its parameters.
Program: C262
Error Message: INVALID TEST OPTION PASSED TO TPPC TEST FUNCTION
Explanation: The TPF/APPC tppc_test function was passed a TEST parameter value other than TEST_TEST_POSTED or TEST_TEST_RTSRCVD.
System Action: Control is returned to the caller with the RCODE parameter set to LU62RC_PARAMETER_CHECK, LU62RC_PK_BAD_OPTION.
User Response: Correct the error in the function call.
See TPF C/C++ Language Support User's Guide for more information about the tppc_test function and its parameters.
Program: C250
Error Message: INVALID TYPE OPTION PASSED TO TPPC ALLOCATE FUNCTION
Explanation: The TPF/APPC tppc_allocate function was passed a TYPE parameter value other than ALLOCATE_TYPE_BASIC, or ALLOCATE_TYPE_MAPPED.
System Action: Control is returned to the caller with the RCODE parameter set to LU62RC_PARAMETER_CHECK, LU62RC_PK_BAD_OPTION.
User Response: Correct the error in the function call.
See TPF C/C++ Language Support User's Guide for more information about the tppc_allocate function and its parameters.
Program: C253
Error Message: INVALID TYPE OPTION PASSED TO TPPC DEALLOCATE FUNCTION
Explanation: The TPF/APPC tppc_deallocate function was passed a TYPE parameter value other than:
System Action: Control is returned to the caller with the RCODE parameter set to LU62RC_PARAMETER_CHECK, LU62RC_PK_BAD_OPTION.
User Response: Correct the error in the function call.
See TPF C/C++ Language Support User's Guide for more information about the tppc_deallocate function and its parameters.
Program: C257
Error Message: INVALID TYPE OPTION PASSED TO TPPC PREPARE TO RECEIVE FUNCTION
Explanation: The TPF/APPC tppc_prepare_to_receive function was passed a TYPE parameter value other than PREP_TO_RECEIVE_TYPE_CONFIRM, PREP_TO_RECEIVE_TYPE_FLUSH, or PREP_TO_RECEIVE_TYPE_SYNC.
System Action: Control is returned to the caller with the RCODE parameter set to LU62RC_PARAMETER_CHECK, LU62RC_PK_BAD_OPTION.
User Response: Correct the error in the function call.
See TPF C/C++ Language Support User's Guide for more information about the tppc_prepare_to_receive function and its parameters.
Program: C261
Error Message: INVALID TYPE OPTION PASSED TO TPPC SEND ERROR FUNCTION
Explanation: The TPF/APPC tppc_send_error function was passed a TYPE parameter value other than SEND_ERROR_TYPE_PROG or SEND_ERROR_TYPE_SVC.
System Action: Control is returned to the caller with the RCODE parameter set to LU62RC_PARAMETER_CHECK, LU62RC_PK_BAD_OPTION.
User Response: Correct the error in the function call.
See TPF C/C++ Language Support User's Guide for more information about the tppc_send_error function and its parameters.
Program: C264
Error Message: INVALID VERB OPTION PASSED TO TPPC ACTIVATE ON CONFIRMATION FUNCTION
Explanation: The TPF/APPC tppc_activate_on_confirmation function was passed a VERB parameter value other than AOC_CONFIRM, AOC_DEALLOC or AOC_P_T_R.
System Action: Control is returned to the caller with the RCODE parameter set to LU62RC_PARAMETER_CHECK, LU62RC_PK_BA_OPTION.
User Response: Correct the error in the function call.
See TPF C/C++ Language Support User's Guide for more information about the tppc_activate_on_confirmation function and its parameters.
Program: C258
Error Message: INVALID WAIT OPTION PASSED TO TPPC RECEIVE FUNCTION
Explanation: The TPF/APPC tppc_receive function was passed a WAIT parameter value other than RECEIVE_WAIT_YES.
System Action: Control is returned to the caller with the RCODE parameter set to LU62RC_PARAMETER_CHECK, LU62RC_PK_BAD_OPTION.
User Response: Correct the error in the function call.
See TPF C/C++ Language Support User's Guide for more information about the tppc_receive function and its parameters.
Program: C264
Error Message: ONLY ONE OF FIELD OR LEVEL MAY BE USED FOR ACTIVATE ON CONFIRMATION
Explanation: The TPF/APPC tppc_activate_on_confirmation function was passed a non-NULL FIELD parameter and a LEVEL parameter option specifying a data level (for example, one of AOC_D0 to AOC_DA; AOC_NO_DL must be coded with a non-NULL FIELD).
System Action: Control is returned to the caller with the RCODE parameter set to LU62RC_PARAMETER_CHECK, LU62RC_PK_BAD_OPTION.
User Response: Correct the error in the function call.
See TPF C/C++ Language Support User's Guide for more information about the tppc_activate_on_confirmation function and its parameters.
Program: C265
Error Message: ONLY ONE OF FIELD OR LEVEL MAY BE USED FOR ACTIVATE ON RECEIPT
Explanation: The TPF/APPC tppc_activate_on_receipt function was passed a non-NULL FIELD parameter and a LEVEL parameter option specifying a data level (for example, AOR_D1 to AOR_DA; AOR_NO_DL must be coded with a non-NULL FIELD).
System Action: Control is returned to the caller with the RCODE parameter set to LU62RC_PARAMETER_CHECK, LU62RC_PK_BAD_OPTION.
User Response: Correct the error in the function call.
See TPF C/C++ Language Support User's Guide for more information about the tppc_activate_on_receipt function and its parameters.
Program: C258
Error Message: RECEIVE LENGTH AND DATA MUST BE EITHER BOTH NULL OR BOTH NOT NULL
Explanation: The TPF/APPC tppc_receive function was passed either NULL LENGTH with non-NULL DATA, or non-NULL LENGTH with NULL DATA.
System Action: Control is returned to the caller with the RCODE parameter set to LU62RC_PARAMETER_CHECK, LU62RC_PK_BAD_OPTION.
User Response: Correct the error in the function call.
See TPF C/C++ Language Support User's Guide for more information about the tppc_receive function and its parameters.
Program: C260
Error Message: SEND DATA LENGTH AND DATA MUST BE EITHER BOTH NULL OR BOTH NOT NULL
Explanation: The TPF/APPC tppc_send_data function was passed either NULL LENGTH with non-NULL DATA, or non-NULL LENGTH with NULL DATA.
System Action: Control is returned to the caller with the RCODE parameter set to LU62RC_PARAMETER_CHECK, LU62RC_PK_BAD_OPTION.
User Response: Correct the error in the function call.
See TPF C/C++ Language Support User's Guide for more information about the tppc_send_data function and its parameters.
Program: Displayed on the console and in the dump
Error Message: FACS ERROR ON APPN TAPST RECORD
Explanation: While trying to calculate the file address of the Advanced Peer-to-Peer Networking (APPN) TAPST record, an error was returned by the FACS program.
System Action: The APPN or high-performance routing (HPR) function ends.
User Response: Ensure that the #IBMM4 record representing the APPN TAPST record is defined.
Program: Displayed on the console and in the dump
Error Message: FIND ERROR ON APPN TAPST RECORD
Explanation: While trying to retrieve the Advanced Peer-to-Peer Networking (APPN) TAPST record from file, an I/O error occurred.
System Action: The APPN or high-performance routing (HPR) function ends.
User Response: Review the system error dump to determine the cause of the input/output (I/O) error.
Program: CSBJ
Error Message: INVALID APPN REGISTER REPLY RECEIVED
Explanation: While performing the APPN LU registration process, the remote CP sent the TPF system a register reply containing data that is not valid.
System Action: The LU registration process is ended.
User Response: Review the register request and register reply included with the dump to determine the cause of the error.
Program: CSBE
Error Message: INVALID CPU ID FOR TAPST FUNCTION
Explanation: A request was made to update the in-core TAPST, but the requested CPU ID passed as input to CSBE was not valid.
System Action: The TAPST request is rejected.
User Response: Review the system error dump to determine why the CPU ID is not valid.
Program: CSBE
Error Message: NO SPACE AVAILABLE IN TAPST
Explanation: A request was made to add a link to the in-core TAPST, but the TAPST was full.
System Action: The TAPST request is rejected and the link is deactivated.
User Response: Do the following:
See TPF Operations for more information about the ZNAPN command.
Program: CSBF
Error Message: INVALID APPN FUNCTION CODE
Explanation: A function code that is not valid was passed to the CSBF segment.
System Action: The request is rejected.
User Response: Review the system error dump to determine why the function code is not valid.
Program: CSBK
Error Message: INVALID CPUID PASSED FOR TG REGISTRATION
Explanation: A request was made to register the transmission groups (TGs) for a given TPF processor, but the CPU ID passed to the CSBK segment was not valid.
System Action: The request is rejected.
User Response: Review the system error dump to determine why the CPU ID is not valid.
Program: CSBI
Error Message: NCB CONTAINS INVALID CPU ID
Explanation: The node control block (NCB) associated with a remote resource was retrieved to determine which TPF processor owned the session with that resource. The CPU ID found in the NCB was not a valid CPU ID.
System Action: The TPF system rejects the APPN LOCATE request.
User Response: Review the system error dump to determine the cause of the error.
Program: CSBI
Error Message: MISSING REQUIRED LOCATE GDS IN LOCATE PIU
Explanation: A LOCATE PIU received by the TPF system did not contain the required LOCATE GDS variable.
System Action: The TPF system rejects the LOCATE request.
User Response: Review the system error dump to determine the cause of the error.
Program: CSBI
Error Message: UNABLE TO FIND FULLY QUALIFIED PCID CONTROL VECTOR
Explanation: A LOCATE PIU received by the TPF system does not contain a fully qualified PCID control vector (CV X'60'). A LOCATE PIU, by definition, must contain a fully qualified PCID control vector.
System Action: The TPF system rejects the LOCATE request.
User Response: Review the system error dump to determine the cause of the error.
Program: CSBI
Error Message: UNABLE TO FIND CD-TERMINATE PARAMETERS CONTROL VECTOR
Explanation: A CD-TERMINATE NOTIFY GDS variable was received by the TPF system as part of a LOCATE PIU. The NOTIFY(CDTERM) GDS received by the TPF system did not contain a CD-terminate parameters control vector (CV X'80'). A NOTIFY(CDTERM) GDS must, by definition, contain a CD-TERMINATE parameters control vector.
System Action: The TPF system rejects the LOCATE request.
User Response: Review the system error dump to determine the cause of the error.
Program: CSBI
Error Message: UNABLE TO FIND SEARCH ARGUMENT CONTROL VECTOR
Explanation: A FIND GDS variable was received by the TPF system as part of a LOCATE PIU. The FIND GDS received by the TPF system did not contain a search argument directory entry control vector (CV X'82'). A FIND GDS must, by definition, contain a search argument directory entry control vector.
System Action: The TPF system rejects the LOCATE request.
User Response: Review the system error dump to determine the cause of the error.
Program: CSBP
Error Message: UNABLE TO FIND PCID MODIFIER CONTROL VECTOR
Explanation: A LOCATE PIU received by the TPF system did not contain a PCID modifier control vector (CV X'81'). A LOCATE PIU must, by definition, contain a PCID modifier control vector.
System Action: The TPF system rejects the LOCATE request.
User Response: Review the system error dump to determine the cause of the error.
Program: CSBL, CSBP
Error Message: UNABLE TO FIND COS/TPF CONTROL VECTOR
Explanation: A LOCATE request received by the TPF system did not contain a class of service control vector (CV X'2C') in the CDINIT GDS variable.
System Action: The TPF system rejects the LOCATE request.
User Response: Review the system error dump to determine the cause of the error.
Program: CSBQ
Error Message: UNABLE TO FIND ROUTE SELECTION CONTROL VECTOR
Explanation: A LOCATE reply received by the TPF system did not contain a route selection control vector (CV X'2B') in the CDINIT GDS variable.
System Action: The TPF system rejects the LOCATE reply.
User Response: Review the system error dump to determine the cause of the error.
Program: CSBQ
Error Message: UNABLE TO FIND BIND IMAGE CONTROL VECTOR
Explanation: A LOCATE PIU received by the TPF system did not contain a BIND image control vector (CV X'31') in the CDINIT GDS variable. For LU-LU session requests where the remote LU is the secondary LU (SLU), the CDINIT GDS variable must contain a BIND image control vector.
System Action: The TPF system rejects the LOCATE PIU.
User Response: Review the system error dump to determine the cause of the error.
Program: CSBQ
Error Message: UNABLE TO FIND TG DESCRIPTOR CONTROL VECTOR
Explanation: A LOCATE PIU received by the TPF system included a route selection control vector (CV X'2B') that did not contain any transmission group (TG) descriptor control vectors (CV X'46'). TG descriptor control vectors are required fields in a route selection control vector.
System Action: The TPF system rejects the LOCATE PIU.
User Response: Review the system error dump to determine the cause of the error.
Program: CSBQ
Error Message: UNABLE TO FIND COMMAND PARAMETERS CONTROL VECTOR
Explanation: A LOCATE reply received by the TPF system included a FOUND GDS variable that did not contain a command parameters control vector (CV X'80'). The command parameters control vector is a required field in a FOUND GDS variable.
System Action: The TPF system rejects the LOCATE PIU.
User Response: Review the system error dump to determine the cause of the error.
Program: CSBQ
Error Message: UNABLE TO FIND TG IDENTIFIER SUBFIELD
Explanation: A LOCATE PIU received by the TPF system included a route selection control vector (CV X'2B'). One of the transmission group (TG) descriptor control vectors (CV X'46') within the route selection control vector did not contain a TG identifier subfield (SF X'80'). A TG descriptor control vector must, by definition, include a TG identifier subfield.
System Action: The TPF system rejects the LOCATE PIU.
User Response: Review the system error dump to determine the cause of the error.
Program: CSBQ
Error Message: UNABLE TO READ IN SAVED LOCATE REPLY
Explanation: A LOCATE dequeue request was received, but an I/O error occurred when the TPF system tried to read in the previous LOCATE PIU that was saved on DASD.
System Action: The TPF system rejects the LOCATE PIU.
User Response: Review the system error dump to determine the cause of the error.
Program: CSBW
Error Message: TAPST CONTAINS INVALID CPU ID
Explanation: When building a LOCATE, or processing a LOCATE that contains a route selection control vector (CV X'2B'), an entry in the in-core TAPST was found to have a CPU ID that is not valid.
System Action: The TPF system rejects the LOCATE PIU.
User Response: Review the system error dump to determine the cause of the error.
Program: CSBQ
Error Message: ERROR FROM MALOC MACRO
Explanation: The TPF system could not allocate enough space to process an incoming LOCATE PIU.
System Action: The TPF system rejects the LOCATE request.
User Response: See your system programmer for more information.
Program: CSGJ
Error Message: HPRMT QUEUE IS NOT VALID FOR RTPCB rtpcb
Where:
Explanation: The chain pointers in the high-performance routing message table (HPRMT) queue for the specified RTP connection are not valid.
System Action: A system error dump is issued and the HPRMT queue for the specified RTP connection is cleared.
User Response: Review the system error dump to determine the cause of the error.
See TPF ACF/SNA Data Communications Reference for more information about the HPRMT and RTP connections.
Program: CSGJ
Error Message: HPRMT QUEUE IS NOT VALID FOR RTPCB rtpcb
Where:
Explanation: This system error is displayed if more than one RTP connection has a high-performance routing message table (HPRMT) queue with chain pointers that are not valid.
System Action: The HPRMT queue for the specified RTP connection is cleared.
User Response: Review system error C62200, which was issued previously, to determine the cause of the error.
See TPF ACF/SNA Data Communications Reference for more information about the HPRMT and RTP connections.
Program: CSHS
Error Message: FORMAT OF ROUTE SETUP PIU IS NOT VALID
Explanation: The TPF system received a ROUTE_SETUP command that did not contain a ROUTE_SETUP (X'12CE') general data stream (GDS) variable, or the ROUTE_SETUP command was a reply that did not contain control vector X'60'.
System Action: The TPF system discards the ROUTE_SETUP command.
User Response: Review the system error dump to determine the cause of the error.
See TPF ACF/SNA Data Communications Reference for more information about ROUTE_SETUP commands.
Program: CSH4
Error Message: MISSING REQUIRED DATA IN ROUTE SETUP REQUEST
Explanation: The TPF system received a ROUTE_SETUP request that did not contain all of the required control vectors.
System Action: The TPF system sends a negative ROUTE_SETUP reply.
User Response: Review the system error dump to determine the cause of the error.
See TPF ACF/SNA Data Communications Reference for more information about ROUTE_SETUP commands.
Program: CSHS
Error Message: MISSING REQUIRED DATA IN ROUTE SETUP REPLY
Explanation: The TPF system received a ROUTE_SETUP reply that did not contain all of the required control vectors, or a specific control vector in the ROUTE_SETUP reply did not contain the required information.
System Action: The TPF system cleans up the rapid transport protocol (RTP) connection.
User Response: Review the system error dump to determine the cause of the error.
See TPF ACF/SNA Data Communications Reference for more information about ROUTE_SETUP commands and RTP connections.
Program: CSHP, CS0P
Error Message: ALL RTPCB ENTRIES IN USE
Explanation: A request was made to get a rapid transport protocol control block (RTPCB) table entry, but all RTPCB table entries are in use.
System Action: If the dump is issued from the CSHP segment, the TPF system starts the LU-LU session using base Advanced Peer-to-Peer Networking (APPN) protocols.
If the dump is issued from the CS0P segment, the TPF system rejects the session activation request that was received.
User Response: Do the following:
See TPF ACF/SNA Network Generation for more information about the SNAKEY macro. See TPF ACF/SNA Data Communications Reference for more information about the RTPCB table.
Program: CSG7
Error Message: HPRSAT IS FULL
Explanation: During Systems Network Architecture (SNA) restart, the TPF system tried to get an entry in the high-performance routing session address table (HPRSAT) for a high-performance routing (HPR) LU-LU session, but the HPRSAT was full.
System Action: A SNAPC dump is issued. SNA restart ends and state change is disabled in the TPF system.
User Response: Do the following:
See TPF ACF/SNA Network Generation for more information about the SNAKEY macro. See TPF ACF/SNA Data Communications Reference for more information about the HPRSAT.
Program: CS0R
Error Message: AN INCORRECT SOUTC TYPE=H MACRO CALL WAS ISSUED
Explanation: The SOUTC macro was issued with the TYPE=H parameter specified. However, the value specified for the NLP1SOUTC_H field in the message block was not correct.
System Action: The message block is released and control is returned to the calling segment.
User Response: Review the program that issued the SOUTC macro to determine the cause of the error.
See TPF System Macros for more information about the SOUTC macro.
Program: CS0P
Error Message: MISSING REQUIRED DATA IN SWITCHING INFORMATION SEGMENT
Explanation: The TPF system received a network layer packet (NLP) containing the Switching Information (SI) segment, but the SI segment did not contain all of the required information.
System Action: The TPF system ends the rapid transport protocol (RTP) connection.
User Response: Review the system error dump to determine the cause of the error.
See TPF ACF/SNA Data Communications Reference for more information about RTP connections.
Program: CS0P
Error Message: MAXIMUM PACKET SIZE IS NOT VALID
Explanation: The TPF system received a network layer packet (NLP) containing the Switching Information (SI) segment, but the maximum packet size specified was not valid.
System Action: The TPF system ends the rapid transport protocol (RTP) connection.
User Response: Review the system error dump to determine the cause of the error.
See TPF ACF/SNA Data Communications Reference for more information about RTP connections.
Program: CSKH
Error Message: FACS OR FILE ERROR ON RECORD rectype ORDINAL NUMBER ordnum
Where:
Explanation: While keypointing the rapid transport protocol control block (RTPCB) table, an error was returned by the file address retrieval program (FACS), or an input/output (I/O) error occurred while filing the record to DASD.
System Action: The TPF system stops keypointing the RTPCB table.
User Response: Review the system error dump to determine the cause of the error.
See TPF ACF/SNA Data Communications Reference for more information about the RTPCB table.
Program: CSKH
Error Message: VALIDITY BIT ERROR IN RTPCB TABLE
Explanation: While keypointing the rapid transport protocol control block (RTPCB) table, the TPF system determined that the validity bit in an RTPCB table entry was not valid.
System Action: A catastrophic system error is issued.
User Response: Review the system error dump to determine the cause of the error.
See TPF ACF/SNA Data Communications Reference for more information about the RTPCB table.