gtpm4m0j | Messages (System Error and Offline) |
Program: CJIQ
Error Message: THIS PROCESSOR IS LOCK FENCED
Explanation: During processing of a concurrency filter lock facility (CFLF) lock or unlock operation, this processor is deactivated and removed from the loosely coupled complex.
System Action: This processor is brought offline immediately and a catastrophic system error occurs.
User Response: Do the following:
Program: CJIE
Error Message: PERMANENT SUBSYSTEM ERROR
Explanation: During processing of a concurrency filter lock facility (CFLF) lock or unlock operation, a hardware error occurred.
System Action: All modules on the affected subsystem are brought offline.
User Response: Do the following:
If the problem continues, see your IBM service representative.
See TPF Operations for more information about the ZAMOD and ZMCPY UP commands.
Program: CJIE
Error Message: CFLF PARAMETER/FORMAT ERROR
Explanation: During unit exception processing, a parameter that is not valid was issued in a concurrency filter lock facility (CFLF) perform subsystem function (PSF) order. This was probably caused. by an overlaid parameter list.
System Action: A catastrophic system error occurs.
User Response: In the dump, the right-most 3 bytes of R7 contain the CFLF partition number, the PSF order number, and the CFLF return code. Inspect the return code to determine the cause of the error. For a list of the return codes, see 3990 Transaction Processing Facility Support RPQs for more information.
Program: CJIE
Error Message: CFLF LOGIC ERROR
Explanation: During unit exception processing, a concurrency filter lock facility (CFLF) return code is detected that is unrelated to current processing. This indicates that an internal TPF logic error has occurred.
System Action: A catastrophic system error occurs.
User Response: See your IBM service representative for more information.
Program: CJIE
Error Message: UNDEFINED CFLF ERROR RETURN CODE
Explanation: During unit exception processing, an undefined return code was returned from a multi-path lock facility (MPLF) subsystem.
System Action: The system brings the modules offline.
User Response: In the dump, the right-most 3 bytes of R7 contain the CFLF partition number, the PSF order number, and the CFLF return code. Inspect the return code to determine the cause of the error. For a list of the return codes, see 3990 Transaction Processing Facility Support RPQs for more information.
Program: CLM1
Error Message: CFLF RESTART FAILED
Explanation: Lock restart failed or was not attempted on a processor other than the first processor to IPL.
System Action: A catastrophic system error occurs.
User Response: Re-IPL after the first processor completes restart.
Program: CLHV, CCSTOR
Error Message: RELBC -- NO ECB, FRAME NOT IN USE
Explanation: The $RELBC macro determined that the frame associated with the block address being returned is not in use.
System Action: The entry is exited and a error recovery is initiated.
User Response: None.
Program: CLHV, CCSTOR
Error Message: RELBC -- NO ECB, BAD OFFSET INTO FRAME
Explanation: The $RELBC macro determined that the block address being returned does not fall on a block boundary.
System Action: The entry is exited and error recovery is initiated.
User Response: None.
Program: CLHV, CCSTOR
Error Message: RELBC -- NO ECB, BLOCK NOT IN USE
Explanation: The $RELBC macro determined that the block address being returned is not a block that is in use.
System Action: The entry is exited and error recovery is initiated.
User Response: None.
Program: CLHV, CCSTOR
Error Message: RELBC -- NO ECB, FRAME IS CONNECTED
Explanation: The $RELBC macro determined that the frame associated with the block address being returned is connected to an ECB.
System Action: The entry is exited and error recovery is initiated.
User Response: None.
Program: CLHV, CCSTOR
Error Message: RELBC -- WITH ECB, BLOCK NOT OWNED BY THIS ECB
Explanation: The $RELBC macro determined that the block address being returned is not owned by the calling ECB.
System Action: The entry is exited and error recovery is initiated.
User Response: Ensure that the blocks are returned only by the ECB that previously had the block.
Program: CLHV, CCSTOR
Error Message: ILLEGAL BLOCK SHARING DETECTED
Explanation: The SCRUB internal routine determined that the block being released is being shared among ECBs when that block is not a common block.
System Action: The entry is exited and error recovery is initiated.
User Response: Analyze the failing application program to determine why blocks are being shared between ECBs. You should change the code, where necessary, to use common blocks for this purpose.
Program: CLHV, CCSTOR
Error Message: DISBC -- BLOCK IS INVALID
Explanation: The $DISBC macro determined that the block address to be disconnected is not a valid block address.
System Action: The entry is exited and error recovery is initiated.
User Response: None.
Program: CLHV, CCSTOR
Error Message: DISBC -- BLOCK OR FRAME IS NOT IN USE
Explanation: The $DISBC macro determined that either the frame associated with the block or the block itself is not flagged as in use.
System Action: The entry is exited and error recovery is initiated.
User Response: None.
Program: CLHV, CCSTOR
Error Message: DISBC -- SVAT ENTRY IS ZERO
Explanation: The $DISBC macro determined that the SVAT entry that points to the frame associated with the block is zero. Therefore, it is not valid.
System Action: The entry is exited and error recovery is initiated.
User Response: None.
Program: CLHV, CCSTOR
Error Message: DISBC -- ATTEMPT TO DISCONNECT AN ECB
Explanation: The $DISBC macro determined that the block address to be disconnected is the address of the ECB. Therefore, it cannot be disconnected.
System Action: The entry is exited and error recovery is initiated.
User Response: None.
Program: CLHV, CCSTOR
Error Message: REMOVFRM -- FRAME NOT ON ECB'S FRAME CHAIN
Explanation: The CLH internal routine REMOVFRM determined that the frame to be removed from this ECB is not seen in the frame chain for that ECB.
System Action: The entry is exited and error recovery is initiated.
User Response: None.
Program: CLHV, CCSTOR
Error Message: CONBC -- FRAME NOT IN USE
Explanation: The $CONBC macro determined that the frame associated with the block address to be connected to the ECB is not flagged as in use. Therefore, it cannot be connected to the ECB.
System Action: The entry is exited and error recovery is initiated.
User Response: None.
Program: CLHV, CCSTOR
Error Message: CONBC -- INVALID BLOCK ADDRESS
Explanation: The $CONBC macro determined that the block address to be connected to the ECB is not valid. Therefore, it cannot be connected to the ECB.
System Action: The entry is exited and error recovery is initiated.
User Response: None.
Program: CLHV, CCSTOR
Error Message: CONBC -- BLOCK NOT IN USE
Explanation: The $CONBC macro determined that the block address to be connected to the ECB is not in use. Therefore, it cannot be connected to the ECB.
System Action: The entry is exited and a error recovery is initiated.
User Response: None.
Program: CLHV, CCSTOR
Error Message: CONBC -- ADDRESS ABOVE FRAMES (VEQR)
Explanation: The $CONBC macro determined that the block address to be connected to the ECB is above the highest frame address. In virtual-equals-real (VEQR) mode, this implies a block type that should not be connected to the ECB.
System Action: The entry is exited and error recovery is initiated.
User Response: None.
Program: CLHV, CCSTOR
Error Message: CONBC -- FRAME ALREADY CONNECTED
Explanation: The $CONBC macro determined that the frame associated with the block address to be connected is already connected to the ECB.
System Action: The entry is exited and error recovery is initiated.
User Response: None.
Program: CLHV, CCSTOR
Error Message: GECBC -- EVA ADDRESS BELOW PRIVATE AREA
Explanation: The GECBC internal routine determined that a request for an attached block cannot be satisfied because the ECB virtual memory (EVM) address of the block to be attached is below the start of the ECB private area.
System Action: The entry is exited and error recovery is initiated.
User Response: None.
Program: CLHV, CCSTOR
Error Message: GECBC -- EVA ADDRESS ABOVE PRIVATE AREA
Explanation: The $GECBC internal routine determined that a request for an attached block cannot be satisfied because the ECB virtual memory (EVM) address of the block to be attached is above the end of the ECB private area.
System Action: The entry is exited and error recovery is initiated.
User Response: None.
Program: CLHV, CCSTOR
Error Message: GECBC -- EVA DOES NOT EQUAL SVA (VEQR)
Explanation: The $GECBC internal routine determined that a request for an attached block cannot be satisfied because the ECB virtual memory (EVM) address does not match the system virtual memory (SVM) address of the block. The virtual-equals-real (VEQR) mode requires that these addresses match.
System Action: The entry is exited and error recovery is initiated.
User Response: None.
Program: CLHV, CCSTOR
Error Message: RECBC -- R9 IS ABOVE LAST ECB ADDRESS
Explanation: The $RECBC internal routine determined that R9, the SVA pointer to the ECB, is beyond the end of the ECB area. Therefore, it cannot release the ECB.
System Action: The entry is exited and error recovery is initiated.
User Response: None.
Program: CLHV, CCSTOR
Error Message: RECBC -- R9 IS BELOW FIRST ECB ADDRESS
Explanation: The $RECBC internal routine determined that R9, the SVA pointer to the ECB, is below the start of the ECB area. Therefore, it cannot release the ECB.
System Action: The entry is exited and error recovery is initiated.
User Response: None.
Program: CLHV, CCSTOR
Error Message: RECBC -- R9 NOT ON AN ECB BOUNDARY
Explanation: The $RECBC internal routine determined that R9, the SVA pointer to the ECB, is not the starting address of an ECB. Therefore, it cannot be released.
System Action: The entry is exited and error recovery is initiated.
User Response: None.
Program: CLHV, CCSTOR
Error Message: RECBC -- ECB NOT IN USE
Explanation: The $RECBC internal routine determined that the ECB to be released is not in use. Therefore, it cannot be released.
System Action: The entry is exited and error recovery is initiated.
User Response: None.
Program: CLHV, CCSTOR
Error Message: RECBC -- LOST BLOCK AT ECB EXIT TIME
Explanation: The $RECBC internal routine determined that the ECB is being exited and some blocks are still flagged as in use when running in block-checking mode.
System Action: A system error is issued with a return. Control is passed back to the caller.
User Response: R6 will point to the lost block, and the CTL-749 dump will contain the frame the contained the block and the control table entry for the frame. The data can be found in the dump as LISTC data labeled FRAME and FCTENTRY. Verify that the failing application program is using blocks in an appropriate manner for the TPF 4.1 environment.
Program: Displayed on the console and in the dump.
Error Message: PHYBC -- INVALID TYPE SPECIFIED
Explanation: The PHYBC macro detected a type that is not valid. The PHYBC macro accepts any physical or logical block type as valid.
System Action: The entry is exited and error recovery is initiated.
User Response: The PHYBC macro can be called with any physical or logical block type as defined in CLHEQ.
Program: Displayed on the console and in the dump.
Error Message: SIZBC -- INVALID TYPE SPECIFIED
Explanation: The SIZBC macro detected a type that is not valid. The SIZBC macro accepts any physical or logical block type as valid.
System Action: The entry is exited and error recovery is initiated.
User Response: The SIZBC macro can be called with any physical or logical block type as defined in CLHEQ.
Program: Displayed on the console and in the dump.
Error Message: TYPBC -- INVALID TYPE SPECIFIED
Explanation: The TYPBC macro detected a type that is not valid. The TYPBC macro accepts only logical block types as valid.
System Action: The entry is exited and error recovery is initiated.
User Response: The TYPBC macro can be called with any logical block type as defined in CLHEQ.
Program: Displayed on the console and in the dump.
Error Message: MAXBC -- INVALID TYPE SPECIFIED
Explanation: The MAXBC macro detected a type that is not valid. The MAXBC macro accepts only physical block types as valid.
System Action: The entry is exited and error recovery is initiated.
User Response: The MAXBC macro can be called with any physical block type as defined in CLHEQ.
Program: Displayed on the console and in the dump.
Error Message: NUMBC -- INVALID TYPE SPECIFIED
Explanation: The NUMBC macro detected a type that is not valid. The NUMBC macro accepts only physical block types as valid.
System Action: The entry is exited and error recovery is initiated.
User Response: The NUMBC macro can be called with any physical block type as defined in CLHEQ.
Program: Displayed on the console and in the dump.
Error Message: FREEC -- INVALID BLOCK ADDRESS SPECIFIED
Explanation: The FREEC macro detected a block address that is not valid. The FREEC macro accepts only addresses that are within the heap and that can be translated within this address space.
System Action: The entry is exited and error recovery is initiated.
User Response: The FREEC macro should only be called with the block address returned from a macro that allocates storage from the heap (MALOC, RALOC, or CALOC macros). The appended message indicates whether the block address is valid because it is not an address in the heap area or whether it is an address within the heap that could not be translated.
Program: CLHV, CCSTOR
Error Message: CONBC -- NO SVA TRANSLATION AVAILABLE
Explanation: The $CONBC macro determined that the block cannot be connected to the ECB because the system virtual address (SVA) of the block is not valid. The SVA is above the range of addresses of the frames but it cannot be translated to a real address. It is likely that a bad address was passed to the $CONBC macro.
System Action: The entry is exited and error recovery is initiated.
User Response: None.
Program: CICR, CCNUCL
Error Message: One of the following:
Explanation: One of the following errors occurred:
System Action: A system error is issued and the entry control block (ECB) exits.
User Response: Do the following:
Program: COS5
Error Message: None.
Appended Message: None.
Explanation: COS5 was entered with a request table pointer of 0.
System Action: The ECB is exited.
User Response: Do the following:
Program: COS5
Error Message: None.
Appended Message: None.
Explanation: COS5 was entered with a request table that is not valid.
System Action: The ECB is exited and the request table is displayed.
User Response: Do the following:
Program: Displayed on the console and in the dump.
Error Message: ERROR RETRIEVING TAPE GROUP DEFINITION TABLE
Appended Message: None.
Explanation: An error occurred while trying to read the tape group definition table.
System Action: The ECB is exited.
User Response: Ensure that the proper number of #IBMMP4 records were allocated to accommodate the requirements of the tape group definition table.
If the proper number of records were allocated, then this probably represents a hardware error. 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: ERROR FILING TAPE GROUP DEFINITION TABLE
Appended Message: None.
Explanation: An error occurred while trying to file the tape group definition table.
System Action: The entry control block (ECB) exits.
User Response: Review the information displayed on the console and in 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: ERROR RETRIEVING DEFINED TAPE DEVICE ASSIGNMENT TABLE
Appended Message: None.
Explanation: An error occurred while trying to read the tape device assignment table.
System Action: The entry control block (ECB) exits.
User Response: Ensure that the proper number of #TDTDR records were allocated to accommodate the requirements of the tape device assignment table.
If the proper number of records were allocated, then this error probably represents a hardware error. 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: ERROR FILING DEFINED TAPE DEVICE ASSIGNMENT TABLE
Appended Message: None.
Explanation: An error occurred while trying to file the tape device assignment table.
System Action: The entry control block (ECB) exits.
User Response: Review the information displayed on the console and in the system error dump to determine the cause of the error and to correct it.
Program: CCTAPE (CEFE)
Error Message: SDA NOT IN TAPE STATUS TABLE
Explanation: A TDCTC macro was issued to a specific device address, and the device address was not found in the tape status table.
System Action: The symbolic device address (SDA) that could not be found in the tape status table is placed in R14.
The entry control block (ECB) ends.
User Response: Have your system programmer review the system error dump to determine why a device-specific input/output (I/O) request was attempted to a device that is not in the tape status table.
Program: CORC
Error Message: TAPE LIBRARY READ DEVICE DATA FAILED
Explanation: A perform library function channel command word (CCW) to read device data failed.
System Action: The entry control block (ECB) ends.
User Response: Have your system programmer review the system error dump to check the CCW that was used to read the device data.
If the CCW is correct, the problem may be hardware related. If the problem is hardware related, see your IBM service representative.
Program: CORB, CORC, CORE
Error Message: TAPE LIBRARY OPERATION STATUS UNKNOWN
Explanation: A tape library event timeout occurred and the device address is no longer in the tape status table or the Library Manager has no pending status for the operation.
System Action: If issued from CORB or CORE, the ECB is allowed to continue processing.
If issued from CORC, the ECB is exited.
User Response: Do the following:
Program: CORB, CORE
Error Message: TAPE LIBRARY READ DEVICE DATA FAILED
Explanation: A perform library function channel command word (CCW) to read device data failed.
System Action: If issued from CORB, the entry control block (ECB) is allowed to continue processing.
If issued from CORE, the ECB is exited.
User Response: Have your system programmer review the system error dump to check the CCW that was used to read the device data.
If the CCW is correct, the problem may be hardware related. If the problem is hardware related, see your IBM service representative.
Program: CORB, CORC
Error Message: TAPE LIBRARY SET VOLUME CATEGORY FAILED
Explanation: A perform library function channel command word (CCW) to set a volume category failed.
System Action: If issued from CORB, the entry control block (ECB) is allowed to continue processing.
If issued from CORC, the ECB is exited.
User Response: Have your system programmer review the system error dump to check the CCW that was used to set the volume category.
If the CCW is correct, the problem may be hardware related. If the problem is hardware related, see your IBM service representative.
Program: CCTAPE (CEFA)
Error Message: None.
Explanation: A device-specific input/output (I/O) request initiated through CEFA was returned with the error index indicating a tape switch had taken place, but the original device address was no longer in the tape status table.
System Action: The entry control block (ECB) ends.
User Response: Have your system programmer review the system error dump to determine why the original device address was no longer in the tape status table.
Program: CORE
Error Message: TAPE LIBRARY SET DEVICE CATEGORY FAILED
Explanation: A perform library function channel command word (CCW) to set a device category failed.
System Action: The entry control block (ECB) ends.
User Response: Have your system programmer review the system error dump to check the CCW that was used to set the device category.
If the CCW is correct, the problem may be hardware related. If the problem is hardware related, see your IBM service representative.
Program: CORB
Error Message: TAPE LIBRARY RESERVE CATEGORY FAILED
Explanation: A perform library function channel command word (CCW) used to retrieve the reserved categories for a complex failed.
System Action: The entry control block (ECB) is allowed to continue processing.
User Response: Have your system programmer review the system error dump to check the CCW that was used to prepare to read subsystem data.
If the CCW is correct, the problem may be hardware related. If the problem is hardware related, see your IBM service representative.
Program: CORB
Error Message: INVALID NUMBER OF CATEGORIES RESERVED
Explanation: More than one, but fewer than eight, categories were reserved by a complex.
This error also indicates that the default category of other devices in the complex may change following the next IPL or ZTVAR DELETE or ZTVAR ADD command sequence.
System Action: Additional categories are obtained to bring the total number of categories to eight. The entry control block (ECB) is allowed to continue processing.
User Response: Have your system programmer review the Library Manager logs to determine how the previously reserved categories were released.
Program: CORA, CORB, CORC
Error Message: INVALID BRANCH VECTOR
Explanation: A subroutine branch vector that is not valid was passed to a program.
System Action: The entry control block (ECB) ends.
User Response: Have your system programmer review the system error dump to determine how the branch vector that is not valid was passed.
Program: CORB, CORC, CORE
Error Message: TAPE LIBRARY EVENT UNSUCCESSFUL
Explanation: One of the following errors occurred:
System Action: The entry control block (ECB) is allowed to continue processing.
User Response: Have your system programmer review the system error dump to determine how a duplicate name was defined in the event table or why there was no event when there should have been.
Do the following:
Program: CORB
Error Message: TAPE LIBRARY CANCEL FAILED
Explanation: A perform library function channel command word (CCW) to cancel a library function failed.
System Action: The entry control block (ECB) is allowed to continue processing.
User Response: Have your system programmer review the system error dump to check the CCW that was used to cancel a library function.
If the CCW is correct, the problem may be hardware related. If the problem is hardware related, see your IBM service representative.
Program: CORB, CORC, CORE
Error Message: TAPE LIBRARY QUERY FAILED
Explanation: A perform library function channel command word (CCW) to retrieve message status failed.
System Action: The entry control block (ECB) is allowed to continue processing.
User Response: Have your system programmer review the system error dump to check the CCW that was used to prepare to read subsystem data.
If the CCW is correct, the problem may be hardware related. If the problem is hardware related, see your IBM service representative.
Program: CORE
Error Message: UNABLE TO RETRIEVE TAPE CATEGORY DATA
Explanation: A perform library function command that specified a prepare for read subsystem data failed while trying to retrieve the category inventory data.
System Action: The entry control block (ECB) ends.
User Response: Have your system programmer review the system error dump to check the CCW that was used to prepare to read subsystem data.
If the CCW is correct, the problem may be hardware related. If the problem is hardware related, see your IBM service representative.
Program: CREB
Error Message: TPFAR SQLH ERROR, DIST. PROTOCOL ERROR- PERMANENT AGENT ERROR. SQLCODE xxxxxx, SQLSTATE yyyyy
Where:
Explanation: Process failed because of a distributed relational data architecture (DRDA) error. A permanent agent error was received by the TPF Application Requester (TPFAR) feature.
System Action: A dump is issued and the SQLCODE and SQLSTATE are returned to the application program.
User Response: None.
Program: CREB
Error Message: TPFAR SQLH ERROR, DIST. PROTOCOL ERROR- CONV. PROTOCOL ERROR. SQLCODE xxxxxx, SQLSTATE yyyyy
Where:
Explanation: Processing failed because of a distributed relational data architecture (DRDA) error. A conversational protocol error was received by the TPF Application Requester (TPFAR) feature.
System Action: A dump is issued and the SQLCODE and SQLSTATE are returned to the application program.
User Response: None.
Program: CREB
Error Message: TPFAR SQLH ERROR, DIST. PROTOCOL ERROR- MANAGER DEPENDENCY ERROR. SQLCODE xxxxxx, SQLSTATE yyyyy
Where:
Explanation: Processing failed because of a distributed distributed relational data architecture (DRDA) error. A manager dependency error was received by the TPF Application Requester (TPFAR) feature.
System Action: A dump is issued and the SQLCODE and SQLSTATE are returned to the application program.
User Response: None.
Program: CREB
Error Message: TPFAR SQLH ERROR, DIST. PROTOCOL ERROR- COMMAND CHECK. SQLCODE xxxxxx, SQLSTATE yyyyy
Where:
Explanation: Processing failed because of a distributed relational data architecture (DRDA) error. A command check was received by the TPF Application Requester (TPFAR) feature.
System Action: A dump is issued and the SQLCODE and SQLSTATE are returned to the application program.
User Response: None.
Program: CREB
Error Message: TPFAR SQLH ERROR, MANAGER LEVEL CONFLICT. SQLCODE xxxxxx, SQLSTATE yyyyy
Where:
Explanation: A distributed relational data architecture (DRDA) protocol error was received by the TPF Application Requester (TPFAR) feature. The remote relational database (RDB) application server does not support the specified manager and level combination.
System Action: A dump is issued and the SQLCODE and SQLSTATE are returned to the application program.
User Response: None.
Program: CREB
Error Message: TPFAR SQLH ERROR, DIST. PROTOCOL ERROR- NOT AUTHORIZED TO COMMAND. SQLCODE xxxxxx, SQLSTATE yyyyy
Where:
Explanation: A distributed relational data data architecture (DRDA) protocol error was received by the TPF Application Requester (TPFAR) feature. The TPFAR feature issued an unauthorized command.
System Action: A dump is issued and the SQLCODE and SQLSTATE are returned to the application program.
User Response: None.
Program: CREB
Error Message: TPFAR SQLH ERROR, DIST. PROTOCOL ERROR- COMMAND CHECK. SQLCODE xxxxxx, SQLSTATE yyyyy
Where:
Explanation: A distributed relational data architecture (DRDA) protocol error was received by the TPF Application Requester (TPFAR) feature. The TPFAR feature issued an unknown command.
System Action: A dump is issued and the SQLCODE and SQLSTATE are returned to the application program.
User Response: None.
Program: CREB
Error Message: TPFAR SQLH ERROR, DIST. PROTOCOL ERROR- INVALID DESCRIPTION. SQLCODE xxxxxx, SQLSTATE yyyyy
Where:
Explanation: The TPF Application Requester (TPFAR) feature issued a formatted data object content architecture (FDOCA) descriptor that is not valid.
System Action: A dump is issued and the SQLCODE and SQLSTATE are returned to the application program.
User Response: None.
Program: CREB
Error Message: TPFAR SQLH ERROR, DIST. PROTOCOL ERROR- DATA DESCRIPTOR MISMATCH. SQLCODE xxxxxx, SQLSTATE yyyyy
Where:
Explanation: The TPF Application Requester (TPFAR) feature issued data that is not valid for the descriptor sent.
System Action: A dump is issued and the SQLCODE and SQLSTATE are returned to the application program.
User Response: None.
Program: CREB
Error Message: TPFAR SQLH ERROR, DIST. PROTOCOL ERROR- QUERY NOT OPEN. SQLCODE xxxxxx, SQLSTATE yyyyy
Where:
Explanation: The TPF Application Requester (TPFAR) feature issued a continue query command when the remote application server thought a query was closed.
System Action: A dump is issued and the SQLCODE and SQLSTATE are returned to the application program.
User Response: None.
Program: CREB
Error Message: TPFAR SQLH ERROR, DIST. PROTOCOL ERROR- QUERY PREVIOUSLY OPENED. SQLCODE xxxxxx, SQLSTATE yyyyy
Where:
Explanation: The TPF Application Requester (TPFAR) feature issued an open query command for a query that the remote application server thought was previously opened.
System Action: A dump is issued and the SQLCODE and SQLSTATE are returned to the application program.
User Response: None.
Program: CREB
Error Message: TPFAR SQLH ERROR, DIST. PROTOCOL ERROR- RDB CURRENTLY ACCESSED. SQLCODE xxxxxx, SQLSTATE yyyyy
Where:
Explanation: The TPF Application Requester (TPFAR) feature issued an access relational database (RDB) command for an RDB that the application server thought was previously accessed.
System Action: A dump is issued and the SQLCODE and SQLSTATE are returned to the application program.
User Response: None.
Program: CREB
Error Message: TPFAR SQLH ERROR, DIST. PROTOCOL ERROR- RDB NOT ACCESSED. SQLCODE xxxxxx, SQLSTATE yyyyy
Where:
Explanation: A command was issued by the remote application server before an access relational database (RDB) command was issued by the TPF Application Requester (TPFAR) feature.
System Action: A dump is issued and the SQLCODE and SQLSTATE are returned to the application program.
User Response: None.
Program: CREB
Error Message: TPFAR SQLH ERROR, DIST. PROTOCOL ERROR-- SYNTAX ERROR. SQLCODE xxxxxx, SQLSTATE yyyyy
Where:
Explanation: The TPF Application Requester (TPFAR) feature issued a command that did not conform to the distributed data management (DDM) architecture.
System Action: A dump is issued and the SQLCODE and SQLSTATE are returned to the application program.
User Response: None.
Program: CREB
Error Message: TPFAR SQLH ERROR, DIST. PROTOCOL ERROR- TARGET NOT SUPPORTED. SQLCODE xxxxxx, SQLSTATE yyyyy
Where:
Explanation: The TPF Application Requester (TPFAR) feature specified an object in a command target that is not supported by the remote application server.
System Action: A dump is issued and the SQLCODE and SQLSTATE are returned to the application program.
User Response: None.
Program: CREB
Error Message: TPFAR SQLH ERROR, DDM COMMAND NOT SUPPORTED BY REMOTE APPL SERVER. SQLCODE xxxxxx, SQLSTATE yyyyy
Where:
Explanation: The SQL return code indicates that the application server does not support a particular distributed data management (DDM) command issued by the TPF Application Requester (TPFAR) feature.
System Action: A dump is issued and the SQLCODE and SQLSTATE are returned to the application program.
User Response: None.
Program: CREB
Error Message: TPFAR SQLH ERROR, OBJECT NOT SUPPORTED. SQLCODE xxxxxx, SQLSTATE yyyyy
Where:
Explanation: The SQL return code indicates that the application server does not support the TPF Application Requester (TPFAR) object specified as data in an object data stream for the command associated with the object.
System Action: A dump is issued and the SQLCODE and SQLSTATE are returned to the application program.
User Response: None.
Program: CREB
Error Message: TPFAR SQLH ERROR, PARAMETER NOT SUPPORTED. SQLCODE xxxxxx, SQLSTATE yyyyy
Where:
Explanation: The SQL return code indicates that the application server does not support the specified parameter by the TPF Application Requester (TPFAR) feature for the specified command.
System Action: A dump is issued and the SQLCODE and SQLSTATE are returned to the application program.
User Response: None.
Program: CREB
Error Message: TPFAR SQLH ERROR, PARAMETER VALUE NOT SUPPORTED. SQLCODE xxxxxx, SQLSTATE yyyyy
Where:
Explanation: The application server does not support or recognize the specified the TPF Application Requester (TPFAR) parameter value or that the TPFAR feature does not support or recognize the specified server parameter value.
System Action: A dump is issued and the SQLCODE and SQLSTATE are returned to the application program.
User Response: None.
Program: CREB
Error Message: TPFAR SQLH ERROR. SEVERITY CODE INVALID FOR REPLY MESSAGE. SQLCODE xxxxxx, SQLSTATE yyyyy
Where:
Explanation: The TPF Application Requester (TPFAR) feature received a reply message with a severity code (SVRCODE) value that the application server did not recognize. The cause of the error may be a mismatch in the application server or TPFAR manager levels or this may be an internal error.
System Action: A dump is issued and the SQLCODE and SQLSTATE are returned to the application program.
User Response: None.
Program: CREB
Error Message: TPFAR SQLH ERROR, RQSCRR ERROR - MISSING REQUEST CORRELATION ID. SQLCODE xxxxxx, SQLSTATE yyyyy
Where:
Explanation: The TPF Application Requester (TPFAR) feature detected an error when correlating the requests sent with the responses received. There is a missing correlation ID.
System Action: A dump is issued and the SQLCODE and SQLSTATE are returned to the application program.
User Response: None.
Program: CREB
Error Message: TPFAR SQLH ERROR, RQSCRR ERROR - REQ. CORRELATION ID OUT OF ORDER. SQLCODE xxxxxx, SQLSTATE yyyyy
Where:
Explanation: The TPF Application Requester (TPFAR) feature detected an error when correlating the requests sent with the responses received. There is a request correlation ID out of order.
System Action: A dump is issued and the SQLCODE and SQLSTATE are returned to the application program.
User Response: None.
Program: CREB
Error Message: TPFAR SQLH ERROR, RQSCRR ERROR - INVALID REQUEST CORRELATION ID. SQLCODE xxxxxx, SQLSTATE yyyyy
Where:
Explanation: The TPF Application Requester (TPFAR) feature detected an error when correlating the requests sent with the responses received. There is a request correlation ID that is not valid.
System Action: A dump is issued and the SQLCODE and SQLSTATE are returned to the application program.
User Response: None.
Program: CREB
Error Message: TPFAR SQLH ERROR, RQSCRR ERROR - PREMATURE END OF REPLY BLOCK. SQLCODE xxxxxx, SQLSTATE yyyyy
Where:
Explanation: The TPF Application Requester (TPFAR) feature detected an error when correlating the requests sent with the responses received. There is a premature end of reply block.
System Action: A dump is issued and the SQLCODE and SQLSTATE are returned to the application program.
User Response: None.
Program: CREB
Error Message: TPFAR SQLH ERROR, IMPLIED COMMIT FAILED. SQLCODE xxxxxx, SQLSTATE yyyyy
Where:
Explanation: The SQL database directory count of TPF Application Requester (TPFAR) hot conversations indicates that there are conversations available. However, the actual list of hot conversations is empty.
System Action: A dump is issued and the SQLCODE and SQLSTATE are returned to the application program.
User Response: None.
Program: CREB
Error Message: TPFAR SQLH ERROR, DIST. PROTOCOL ERROR- MISSING SQLCARD. SQLCODE xxxxxx, SQLSTATE yyyyy
Where:
Explanation: A structured query language communications area reply data (SQLCARD) was expected in a response from the application server, but was not included.
System Action: A dump is issued and the SQLCODE and SQLSTATE are returned to the application program.
User Response: None.
Program: CREB
Error Message: TPFAR SQLH ERROR, DIST. PROTOCOL ERROR- RDB ACCESS FAILED. SQLCODE xxxxxx, SQLSTATE yyyyy
Where:
Explanation: A relational database access failed reply message (RDBAFLRM) was received from the application server.
System Action: A dump is issued and the SQLCODE and SQLSTATE are returned to the application program.
User Response: None.
Program: CREB
Error Message: TPFAR SQLH ERROR, REPLY MESSAGE NOT SUPPORTED. SQLCODE xxxxxx, SQLSTATE yyyyy
Where:
Explanation: An unsupported reply message from the application server was received the by TPF Application Requester (TPFAR) SQL Handler (SQLH).
System Action: A dump is issued and the SQLCODE and SQLSTATE are returned to the application program.
User Response: None.