gtpm4m0u | Messages (System Error and Offline) |
Program: Displayed on the console and in the dump.
Error Message: UNABLE TO GET CLAW CONTROL BLOCK
Explanation: A request to obtain a Common Link Access to Workstation (CLAW) control block was not successful.
System Action: A system error dump is issued and an error indicator is returned to the caller.
User Response: Do the following:
Program: CLW3
Error Message: ADAPTER BLOCK NOT FOUND ON ACTIVE QUEUE
Explanation: The adapter control block was not found on the adapter control block active queue when the claw_openadapter or claw_closeadapter function was in progress.
System Action: A catastrophic system error occurs.
User Response: None.
See TPF Transmission Control Protocol/Internet Protocol for more information about the claw_openadapter and claw_closeadapter functions.
Program: Displayed on the console and in the dump.
Error Message: UNABLE TO RELEASE CLAW CONTROL BLOCK
Explanation: The block type is inconsistent with the block address.
System Action: A dump is issued and the error code is returned to the caller in R0.
User Response: Do the following:
Program: Displayed on the console and in the dump.
Error Message: INSUFFICIENT SPACE IN CORE FOR SOCKET/CLAW TABLES, CLAW IS NOW INACTIVE
Explanation: There is not enough storage defined for the socket Common Link Access to Workstation (CLAW) data or the value of the CLAWADP parameter in the SNAKEY macro is too large.
System Action: Restart continues and TCP/IP offload support is disabled.
User Response: Do the following:
See TPF ACF/SNA Network Generation for more information about the SNAKEY macro.
Program: Displayed on the console and in the dump.
Error Message: INVALID BUFFER ADDRESS OR LENGTH
Explanation: The application ECB virtual memory (EVM) buffer address cannot be converted to the system virtual memory (SVM) address.
System Action: Processing returns back to the application with an error return code.
User Response: Do the following:
Program: CLA5
Error Message: NO CLAW EP PROGRAM FOR THIS MESSAGE TYPE
Explanation: An entry point (EP) that is not valid was provided by the program that entered CLA5.
System Action: A system error is issued and the function exits.
User Response: Do the following:
Program: Displayed on the console and in the dump.
Error Message: UNABLE TO PROCESS CLAW SEND REQUEST
Explanation: An error occurred while processing the claw_send function with the SEND_LIST value specified on the SEND_METHOD parameter. The array of descriptors passed from the application to the Common Link Access to Workstation (CLAW) device interface is not valid.
System Action: A system error is issued and the error code is returned to the caller.
User Response: Do the following:
See TPF Transmission Control Protocol/Internet Protocol for more information about the claw_send function.
Program: Displayed on the console and in the dump.
Error Message: INVALID INPUT DATA LENGTH
Explanation: An input data length that is not valid was received from the remote workstation.
System Action: A system error is issued and the function is exits.
User Response: Do the following:
Program: Displayed on the console and in the dump.
Error Message: RSYSC ERROR ON SYSTEM HEAP BUFFER
Explanation: A Transmission Control Protocol/Internet Protocol (TCP/IP) offload program attempted to issue an rsysc function call to release a system heap buffer, but the rsysc return code indicated that the buffer was not released.
System Action: A SNAP dump is issued that displays the address of the system heap buffer, the number of frames associated with the system heap buffer, and the 8-byte token used by the rsysc function call to release the system heap buffer.
User Response: See your IBM service representative to determine the cause of the error.
See TPF C/C++ Language Support User's Guide for more information about the rsysc function.
Program: Displayed on the console and in the dump.
Error Message: LOG INFORMATION SENT FROM DEVICE INTERFACE
Explanation: A subrequest ordinal was received that is not valid.
System Action: A system error is issued and the function is returned to the caller.
User Response: Do the following:
Program: Displayed on the console and in the dump.
Error Message: UNEXPECTED MESSAGE RECEIVED
Explanation: An unexpected socket accept, read, or recvfrom response was received.
System Action: None.
User Response: See your system programmer to determine the cause of the error and correct it.
See TPF Transmission Control Protocol/Internet Protocol for more information about the accept, read, and recvfrom functions.
Program: Displayed on the console and in the dump.
Error Message: CLA4 (NON-SOCKET MSG EP) PROCESSING ACTIVATED
Explanation: The CLA4 user exit is activated.
System Action: The nonsocket message is discarded.
User Response: Update the CLA4 user exit to process the nonsocket message.
See TPF System Installation Support Reference for more information about the CLA4 user exit.
Program: CLSX
Error Message: NO FILE DESCRIPTORS AVAILABLE
Explanation: The socket, accept, or bind function tried to obtain a file descriptor, but there were no file descriptors available.
System Action: A catastrophic system error occurs.
User Response: Do the following:
See TPF Transmission Control Protocol/Internet Protocol for more information about the socket, accept, and bind functions. See TPF ACF/SNA Network Generation for more information about the SNAKEY macro.
Program: Displayed on the console and in the dump.
Error Message: EVENT POST ERROR
Explanation: This error occurs when CLWP tries to post an event that does not exist.
System Action: The response is discarded.
User Response: Do the following:
Program: Displayed on the console and in the dump.
Error Message: INVALID IUCV MESSAGE TYPE RECEIVED
Explanation: A type of inter-user communication vehicle (IUCV) message that is not valid was received by CLWP.
System Action: The TPF system returns to the CPU loop.
User Response: Do the following:
Program: Displayed on the console and in the dump.
Error Message: UNABLE TO ALLOCATE APPLICATION BUFFER
Explanation: The socket API function failed to get the application entry control block (ECB) storage by using the MALOC or $GSYSC macros.
System Action: A system error is issued and the function exits.
User Response: Do the following:
Program: Displayed on the console and in the dump.
Error Message: PROGRAM DETECTED HOLDING A RESOURCE WHILE ATTEMPTING CLAW I/O.
Explanation: During the processing of a Common Link Access to Workstation (CLAW) function call, the TPF system is trying to suspend the entry control block (ECB) but the ECB is holding a resource.
System Action: A system error is issued and the program exits.
User Response: Do the following:
Program: Displayed on the console and in the dump.
Error Message: FACS ERROR ON TCP/IP CONFIGURATION TABLE
Explanation: During system restart, an error was returned from the file address compute program (FACS) while trying to calculate the file address of the Transmission Control Protocol/Internet Protocol (TCP/IP) configuration table.
System Action: The TPF system is placed in state change disabled mode.
User Response: Ensure that the #IBMM4 record representing the TCP/IP configuration table record is defined.
Program: Displayed on the console and in the dump.
Error Message: ERROR FILING TCP/IP CONFIGURATION TABLE
Explanation: An error occurred when the TPF system tried to file the Transmission Control Protocol/Internet Protocol (TCP/IP) configuration table during TPF system restart.
System Action: The TPF system is placed in state change disabled mode.
User Response: Have your system programmer determine the cause of the problem and correct the error.
Program: Displayed on the console and in the dump.
Error Message: ERROR FINDING TCP/IP CONFIGURATION TABLE
Explanation: An error occurred when the TPF system tried to find the Transmission Control Protocol/Internet Protocol (TCP/IP) configuration table during TPF system restart.
System Action: The TPF system is placed in state change disabled mode.
User Response: Have your system programmer determine the cause of the problem and correct the error.
Program: Displayed on the console and in the dump.
Error Message: NO SYSTEM HEAP FOR TCP/IP CONFIGURATION TABLE
Explanation: An error occurred because the TPF system did not obtain system heap storage for the Transmission Control Protocol/Internet Protocol (TCP/IP) configuration table during TPF system restart.
System Action: The TPF system is placed in state change disabled mode.
User Response: Do the following:
See TPF Operations for more information about the ZCTKA ALTER command.
Program: CMQS
Error Message: idnum COULD NOT GET STORAGE FOR object
Where:
Explanation: An attempt was made to allocate memory for the specified object, but the requested memory was not available.
System Action: A system error dump is issued and the application returns with an error code.
User Response: Do one of the following:
See TPF Operations for more information about the ZCTKA ALTER command.
Program: CMQS
Error Message: MQ ERROR - attribute ERROR
Where:
Explanation: This is a program logic error in TPF MQSeries. The program was attempting to assign a parameter to a queue that does not apply to the queue type.
System Action: A system error dump is issued and the entry control block (ECB) is exited.
User Response: See your IBM service representative to determine the cause of the error.
Program: CMQS
Error Message: RSYSC FAILED - ADDR heapaddr FOR frames FRAMES, TOKEN token
Where:
Explanation: This is a program logic error. The program attempted to release an area of system heap, but the attempt failed.
System Action: A system error dump is issued and the program continues.
User Response: See your IBM service representative to determine the cause of the error.
Program: CMQS
Error Message: NOT ENOUGH SYSTEM HEAP FOR MQSERIES RECOVERY
Explanation: During TPF system restart, or in response to the ZPSMS command with the PROCESSOR and DEACTIVATE parameters specified, the MQSeries resource manager (RM) attempted to build recovery tables that are necessary to recover outstanding MQSeries transaction branches. However, the TPF system did not have enough system heap to complete the requests.
System Action: One of the following occurs:
User Response: Do the following:
See TPF Operations for more information about the ZPSMS and ZCTKA ALTER commands.
Program: CMQS
Error Message: NOT ENOUGH SWBS FOR MQSERIES RECOVERY
Explanation: During TPF system restart, or in response to the ZPSMS command with the PROCESSOR and DEACTIVATE parameters specified, the MQSeries resource manager (RM) attempted to build recovery tables that are necessary to recover outstanding MQSeries transaction branches. However, the TPF system did not have enough system work blocks (SWBs) to complete the requests.
System Action: One of the following occurs:
User Response: Do the following:
See TPF Operations for more information about the ZPSMS and ZCTKA ALTER commands.
Program: CMQS
Error Message: NOT ENOUGH MALLOC FOR MQSERIES RECOVERY
Explanation: During TPF system restart, or in response to the ZPSMS command with the PROCESSOR and DEACTIVATE parameters specified, the MQSeries resource manager (RM) attempted to build recovery tables to recover outstanding MQSeries transaction branches. However, the TPF system did not have enough entry control block (ECB) malloc storage to complete the requests.
System Action: One of the following occurs:
User Response: Do the following:
See TPF Operations for more information about the ZPSMS and ZCTKA ALTER commands.
Program: CMQX
Error Message: UNKNOWN MQSERIES LOG RECORD
Explanation: During TPF system restart, or in response to the ZPSMS command with the PROCESSOR and DEACTIVATE parameters specified, the MQSeries resource manager (RM) was passed a recovery log record from the log manager (LM). However, the log record was of an unknown type.
System Action: The log record is ignored and recovery processing continues.
User Response: Do the following:
See TPF Operations for more information about the ZPSMS command.
Program: CMQM
Error Message: INCOMPLETE MQSERIES LOG RECORD CHAIN
Explanation: During TPF system restart or in response to the ZPSMS command with the PROCESSOR and DEACTIVATE parameters specified, the MQSeries resource manager (RM) attempted to recover a committed MQSeries transaction. However, the transaction event spanned multiple recovery log records and not all of the recovery log records were found on the system recovery log.
System Action: The transaction event is ignored and recovery processing continues.
User Response: Determine why the log manager (LM) is not passing a complete log record chain to the MQSeries RM and correct the problem.
See TPF Operations for more information about the ZPSMS command.
Program: CMQK
Error Message: ERROR READING IN MQSERIES FILE ADDRESS xxxxxxxx
Where:
Explanation: During TPF system restart, the MQSeries queue manager (QM) attempted to reconstruct the MQSeries memory tables from copies of the tables stored in the MQSeries checkpoint. However, an error occurred when reading in the file address indicated.
System Action: The restart entry control block (ECB) ends and state change is disabled.
User Response: Do the following:
See TPF Operations for more information about the ZRIPL command.
Program: CMQK
Error Message: ERROR REBUILDING MESSAGE QUEUE FOR QUEUE qname
Where:
Explanation: During TPF system restart, the MQSeries queue manager (QM) attempted to reconstruct the MQSeries memory tables from copies of the tables that were stored in the MQSeries checkpoint. When reading in the messages for the queue indicated, an error was detected.
System Action: The restart entry control block (ECB) ends and state change is disabled.
User Response: Do the following:
See TPF Operations for more information about the ZRIPL command.
Program: CMQS
Error Message: TRANSACTION IS NOT IN CORRECT STATE, function_name ADDING CCR TO TRANSACTION FAILED
Where:
Explanation: An MQSeries function such as MQPUT or MQGET performed a function call to copy or add a commit control record (CCR) into the MQSeries resource manager (RM), but the transaction was not in the correct state.
System Action: The entry control block (ECB) exits.
User Response: Ensure the ECB is in an active transaction and the transaction is not suspended when calling the build CCR service functions.
Program: CMQS
Error Message: MQSERIES PRECOMMIT ERROR
Explanation: An error occurred during pre-commit processing while adding a message to a processor shared queue.
System Action: A system error dump is issued, the entry control block (ECB) exits and the message is not added to the queue.
User Response: Do the following:
Program: CMQK
Error Message: MQSERIES MAXIMUM RECORD ORDINALS REDUCED TO newcount FROM oldcount
Where:
Explanation: During TPF system restart, or while processing the ZPSMS command with the PROCESSOR and DEACTIVATE parameters specified, an attempt was made to read in the MQSeries checkpoint control and availability records. During validation of the availability records, it was determined that the total number of #IMQCK-type records allocated had been reduced from a previous setting. However, at least one of the fixed file records that were deallocated is marked as in use by TPF MQSeries support.
System Action: A system dump is issued and one of the following occurs:
User Response: Do the following:
See TPF Operations for more information about the ZPSMS command.
Program: Displayed on the console and in the dump.
Error Message: NO MQSERIES RECORDS AVAILABLE TO COMPLETE MQSERIES CHECKPOINT
Explanation: An attempt was made to retrieve an unused #IMQCK fixed file record to save vital information in the MQSeries checkpoint. However, all records of this type are currently in use.
System Action: The integrity of the MQSeries data is compromised if processing continues. This is a catastrophic system dump.
User Response: Allocate more #IMQCK fixed file records in the TPF 4.1 system.
See TPF Database Reference for more information about the #IMQCK fixed file records.
Program: CMQS
Error Message: SWB IS CORRUPTED
Explanation: A corrupted system work block (SWB) was detected while moving messages from a TPF Collection Support (TPFCS) blob to memory.
System Action: The message is ignored and processing continues.
User Response: Do the following:
Program: CMQS
Error Message: MQ COMMIT LOGIC ERROR
Explanation: An internal logic error was detected during commit or rollback processing by the TPF MQSeries resouce manager.
System Action: The entry control block (ECB) exits and the transaction ends.
User Response: See your IBM service representative.
Program: CMQS
Error Message: MESSAGE NOT FOUND IN XMITQ - queue name
Where:
Explanation: This is a program logic error in TPF MQSeries. A sender channel was not able to find a message on a transmission queue that was assigned to a batch.
System Action: A system error dump is issued and the program continues.
User Response: See your IBM representative to determine the cause of the error.
Program: CMQS
Error Message: TO2 DATA CORRUPTION
Explanation: A corruption in a TPF collection support (TPFCS) binary large object (BLOB) was detected while moving messages from the BLOB to memory.
System Action: The process is stopped and the entry control block (ECB) returns to the caller.
User Response: Review the system error dump to determine the cause of the error.