| 1005
|
Invalid URL pointer sent with Connection thread stop command.
Explanation: The user issued a Connection stop command for a Connection Thread probably by a S7MA -connstop. The Master Thread received the command but could not find a Connection Thread with the URL. The Master Thread ignores the command and the system returns 1005 status.
User Response: Check that the system is running properly by issuing
S7MA commands and check the system log for other errors. The user must verify the state of the CEET system and issue a
S7MA command and/or review the CEET log to determine the reason for the Work Thread termination. Check to see if another program or person has issued the Connection stop command just before you, resulting in a timing situation rather than a real issue.
System Action: The Master Thread ignores the command. The
tibems_status (return code) is set to
1005.
|
| 1006
|
Invalid ACMEM pointer sent with Connection Thread debug start command.
Explanation: The user issued a debug on command for a Connection Thread, probably by a S7MA -conntrace. The Connection Thread received the command, but when testing the ACMEM pointer, found it invalid. The Connection Thread terminates and the system returns 1006 status.
User Response: Check that the system is running properly by issuing
S7MA commands and check the system log for other errors. This is an internal error, so the CEET should be stopped and restarted at the first opportunity. Issue a S7MA -masterstop followed by a S7MA -masterstart. The user must verify the state of the CEET system and issue a S7MA command and/or review the CEET log to determine the reason for the Work Thread Termination.
System Action: The Connection Thread is stopped as well as all Work Threads associated with the connection. The
tibems_status (return code) is set to
1006.
|
| 1007
|
Invalid ACMEM pointer sent with Connection Thread debug stop command.
Explanation: The user issued a debug on command for a Connection Thread, probably by a S7MA -conntrace. The Connection Thread received the command, but when testing the ACMEM pointer, found it invalid. The Connection Thread terminates and the system returns 1007 status.
User Response: Check that the system is running properly by issuing
S7MA commands and check the system log for other errors. This is an internal error, so the CEET should be stopped and restarted at the first opportunity. Issue a S7MA -masterstop followed by a S7MA -masterstart. The user must verify the state of the CEET system and issue a
S7MA command and/or review the CEET log to determine the reason for the Work Thread Termination.
System Action: The Connection Thread is stopped as well as all Work Threads associated with the connection. The
tibems_status (return code) is set to
1007.
|
| 1008
|
EMS API Function call to CEET cannot allocate a Work Thread.
Explanation: The user issued an EMS Library API call which must be sent to a Work Thread. Since a Work Thread has not been allocated to this CICS transaction, the system tries to allocate a free one or start a new one. Both allocation types have failed. If the EMS Library API call is a tibemsConnection_Create, the system returns 1008 status.
User Response: Check the number of Work Threads running using the S7MA transaction. Check the system log and CEET log to determine why the Work Thread could not be allocated. Possible reasons for this abend include the following reasons:
- The maximum of 127 Work Threads was reached so no further Work Threads can be started.
- The maximum of 16 Connection Threads was reached so no further Connection Threads can be started.
- A stop workthread or connection command was issued.
The user programs, when getting a 1008 tibems_status, must take whatever error processing needed and terminate – DO NOT issue any more EMS API calls since a Work Thread has not been allocated to the CICS transaction.
System Action: The function returns unsuccessfully to the application and the
tibems_status (return code) is set to
1008. No Work Thread is allocated to the CICS transaction.
|
| 1009
|
Invalid ACMEM pointer sent with Connection Thread stop command.
Explanation: The user issued a stop command for a Connection Thread, probably by a S7MA -connstop. The Connection Thread received the command, but when testing the ACMEM pointer, found it invalid. The Connection Thread terminates and the system returns 1009 status.
User Response: Check that the system is running properly by issuing
S7MA commands and check the system log for other errors. This is an internal error, so the CEET should be stopped and restarted at the first opportunity. Issue a S7MA -masterstop followed by a S7MA -masterstart. The users have to verify the state of the CEET system and issue a
S7MA command and/or review the CEET log to determine the reason for the Work Thread termination.
System Action: The Connection Thread is stopped, as well as all Work Threads associated with the connection. The
tibems_status (return code) is set to
1009.
|
| 1010
|
Invalid ACMEM pointer sent with Connection Thread start command.
Explanation: The user issued a start command for a Connection Thread, probably by a S7MA -connstart. The Connection Thread received the command, but when testing the ACMEM pointer, found it invalid. The Connection Thread terminates and the system returns 1010 status.
User Response: Check that the system is running properly by issuing
S7MA commands and check the system log for other errors. This is an internal error, so the CEET should be stopped and restarted at the first opportunity. Issue a S7MA -masterstop followed by a S7MA -masterstart. The user must verify the state of the CEET system and issue a S7MA command and/or review the CEET log to determine the reason for the Work Thread termination.
System Action: The Connection Thread is stopped, as well as all Work Threads associated with the connection. The
tibems_status (return code) is set to
1010.
|
| 1011
|
Invalid ACMEM pointer sent with Connection Thread ping command.
Explanation: The user issued a ping command for a Connection Thread, probably by a S7MA -connping. The Connection Thread received the command, but when testing the ACMEM pointer, found it invalid. The Connection Thread terminates and the system returns 1011 status.
User Response: Check that the system is running properly by issuing S7MA commands and check the system log for other errors. This is an internal error, so the CEET should be stopped and restarted at the first opportunity. Issue a S7MA -masterstop followed by a S7MA -masterstart. The users have to verify the state of the CEET system and issue a S7MA command and/or review the CEET log to determine the reason for the Work Thread termination.
System Action: The Connection Thread is stopped, as well as all Work Threads associated with the connection. The
tibems_status (return code) is set to
1011.
|
| 1012
|
Function call to CEET is not a Connection request or a Supervisory command.
Explanation: The user program issued an EMS Library API call to the CEET and did not have a Work Thread allocated to the CICS transaction. First time calls must be either a connection request or a supervisory command. This error code can also be received if the Work Thread allocated to the CICS transaction terminates (normally or ABENDS) while the CICS transaction is running.
User Response: The user must verify that the first EMS Library API functional call to CEET is a tibemsConnection_Create function with valid parameters, correct the program, and retry the transaction. The user programs, when getting a 1012 tibems_status, have to take whatever error processing needed and terminate – DO NOT issue any more EMS API calls since a Work Thread has not been allocated to the CICS transaction.
System Action: The function returns unsuccessfully to the application and the
tibems_status (return code) is set to
1012. No Work Thread is allocated to the CICS transaction.
|
| 1016
|
Function not found in command list.
Explanation: The program issued a EMS Library API call to the CEET that is not a supported EMS API function. The CEET does not forward the function call to the EMS Library. The CEET immediately returns a
tibems_status (return code) of
1016.
User Response: The users have to verify the TIBCO function being used, correct the program, and retry the transaction.
System Action: The function returns unsuccessfully to the application and the
tibems_status (return code) is set to
1016.
|
| 1024
|
Missing Work Thread pointer sent or Work Thread not found with Work Thread stop command.
Explanation: The user issued a stop command for a Work Thread, probably by a S7MA -workstop. The Connection Thread received the command, but when testing the pointer, found it invalid or could not find the Work Thread. The Connection Thread ignores the command and the system issues returns 1024 status.
User Response: Check that the system is running properly by issuing
S7MA commands and check the system log for other errors. The users have to verify the state of the CEET system and issue a
S7MA command and/or review the CEET log to determine the reason for the Work Thread termination.
System Action: The Work Thread is not stopped, the command is ignored. The
tibems_status (return code) is set to
1024.
|
| 1040
|
Missing URL.
Explanation: The program issued a tibemsConnection Create API to the EMS Library, but without a URL parameter (null pointer or null string).
User Response: The user must verify that the tibemsConnection_Create API has a valid URL string.
System Action: The function returns unsuccessfully to the application and the
tibems_status (return code) is set to
1040.
|
| 1041
|
Invalid control block in CICS Application Environment.
Explanation: An invalid control block pointer was found in the CICS Application Environment. The pointer to the control block is invalid or the start/end ID stored in the control block is invalid. There is one control block in the CICS Application Environment for each Connection and Work Thread in the CEET.
User Response: Contact TIBCO support and report the error. It is good practice to provide the CEET log, DDNAME CEEOUT output, and CICS SYSLOG.
System Action: The function returns unsuccessfully to the application and the
tibems_status (return code) is set to
1041.
|
| 1042
|
Invalid control block in the CEET.
Explanation: An invalid control block was found in the CEET. Either the pointer, start id, or end indicator of the control block is invalid. There is one control block for each Connection and Work Thread in the CEET.
User Response: Contact TIBCO support and report the error. It is good practice to provide the CEET log, DDNAME CEEOUT output, and CICS SYSLOG.
System Action: The function returns unsuccessfully to the application and the
tibems_status (return code) is set to
1042.
|
| 1043
|
The CEET is stopping.
Explanation: A S7MA -masterstop or S7MA -connstop was issued so the CEET does not honor any new Connection Thread Start, Work Thread Start or Work Thread Allocation requests directly or indirectly (tibemsConnection_Create causes the CEET to issue Connection Thread starts, Work Thread starts and/or Work Thread Allocation requests).
User Response: The user programs have to take the steps necessary to terminate the program either normally or abnormally. If you want to restart the CEET master, issue a S7MA -masterstart and reissue the transactions.
System Action: The function returns unsuccessfully to the application and the
tibems_status (return code) is set to
1043.
|
| 1044
|
The CEET stopped.
Explanation: A S7MA -masterstop was issued so the CEET master does not honor any new Connection Thread Start, Work Thread Start or Work Thread Allocation requests directly or indirectly (tibemsConnection_Create causes the CEET master to issue Connection Thread starts, Work Thread starts and/or Work Thread Allocation requests).
User Response: The user programs have to take the steps necessary to terminate the program either normally or abnormally. If you want to restart CEET master, issue a S7MA -masterstart and reissue the transactions.
System Action: The function returns unsuccessfully to the application and the
tibems_status (return code) is set to
1044.
|
| 1045
|
The Connection Thread could not be started.
Explanation: A S7MA -connstart or a tibemsConnection_Create was issued, so the CEET master is attempting to start a new Connection Thread. The Connection Thread could not be started. Messages in the system log should indicate why the Connection Thread was not started.
User Response: The user programs have to take the steps necessary to terminate the program either normally or abnormally. Check the CEET log for why the Connection Thread could not be started or the MAXCONN has been reached.
System Action: The function returns unsuccessfully to the application and the
tibems_status (return code) is set to
1045.
|
| 1046
|
The Work Thread could not be started.
Explanation: A S7MA -workstart or a tibemsConnection_Create was issued, so the CEET master does not have an open Work Thread for the URL attempting to start a new Work Thread. The Work Thread could not be started. Messages in the system log should indicate why the Connection Thread was not started. The possible reasons are as follows:
- Bad URL.
- The Master Thread was stopped.
- MAXWORK has been exceeded.
User Response: The user programs have to take the steps necessary to terminate the program either normally or abnormally. Check the CEET log for why the Work Thread could not be started.
System Action: The function returns unsuccessfully to the application and the
tibems_status (return code) is set to
1046.
|
| 1047
|
The Work Thread terminated while processing a tibems API function.
Explanation: The Work Thread terminated when processing a tibems API function. The Work Thread terminated while processing a tibems API function for the user transaction. Messages in the system log should indicate why the Work Thread was not started. The common reasons are as follows:
- The Work Thread was stopped.
- The Connection Thread was stopped.
- The Master Thread was stopped.
- Connection to the TIBCO EMS Server was lost.
- The Work Thread, Connection Thread or Master Thread had a Error Condition Raise (System exception like an S0Cx).
- Work Threads can get an S0Cx abend if an invalid address is passed to the EMS library by a tibems API call.
User Response: The user programs have to take the steps necessary to terminate the program either normally or abnormally. Check the system log for why the Work Thread could not be started.
System Action: The function returns unsuccessfully to the application and the
tibems_status (return code) is set to
1047.
|
| 1048
|
Invalid control block combination.
Explanation: A control block combination (one in the CICS Application Environment and one in the CEET) are out of synch.
User Response: Contact TIBCO support and report the error. You are required to provide the CEET log, DDNAME CEEOUT output, and CICS SYSLOG.
System Action: The function returns unsuccessfully to the application and the
tibems_status (return code) is set to
1048.
|
| 1050
|
Invalid anchor control block in CICS Application Environment.
Explanation: Invalid anchor control block in CICS Application Environment was discovered.
Either the pointer to the control block is not valid or the start ID of the control block is invalid or end indicator of the control block is invalid. There is one control block for the Master thread in the CICS Application Environment.
User Response: Contact TIBCO support and report the error. It is good practice to provide the CEET log, DDNAME CEEOUT output, and CICS SYSLOG.
System Action: The function returns unsuccessfully to the application and the
tibems_status (return code) is set to
1050.
|
| 1051
|
Invalid anchor control block in the CEET.
Explanation: Invalid anchor control block in the CEET was discovered.
Either the pointer to the control block is not valid or the start ID of the control block is invalid or end indicator of the control block is invalid. There is one control block for the Master thread in the CEET.
User Response: Contact TIBCO support and report the error. It is good practice to provide the CEET log, DDNAME CEEOUT output, and CICS SYSLOG.
System Action: The function returns unsuccessfully to the application and the
tibems_status (return code) is set to
1051.
|
| 1052
|
Master Thread has ended.
Explanation: The Master Thread has ended when processing a Master Command. All Connection Threads and Work Threads end. This is an internal error.
User Response: The user programs have to take the steps necessary to terminate the program, either normally or abnormally.
Contact TIBCO support and report the error. It is good practice to provide the CEET log, DDNAME CEEOUT output, and CICS SYSLOG.
System Action: The function returns unsuccessfully to the application and the
tibems_status (return code) is set to
1052.
|
| 1064
|
Work Thread stopped.
Explanation: The program issued a call to the EMS Library, but the Work Thread allocated to the CICS transaction is being or has been stopped. The Work Thread can stop for several reasons, including the following reasons:
- A stop connection or stop Work Thread command was issued for this connection and/or Work Thread. Since the Work Thread is terminating, all EMS API calls are rejected and a return code indicating error returned.
- The Work Thread to support the CICS transaction has terminated because of a problem. Review the CEET log to determine the reason for the Work Thread termination.
User Response: The user must verify the state of the Work Thread and issue a
S7MA command and/or review the CEET log to determine the reason for the Work Thread termination. DO NOT issue any more EMS API calls from that transaction since a Work Thread has not been allocated to the CICS transaction.
System Action: The function returns unsuccessfully to the application and the
tibems_status (return code) is set to
1064.
|
