System Messages: TUXMQ Catalog 1000-1099
|
![]() |
![]() |
1000 |
TPMQ_EATMI tpopen failed error = error_string | |
|
Description |
The WebSphere MQ Resource Manager failed to open correctly. The error_string indicates the |
Action |
Examine the userlog and WebSphere MQ error logs for information on the specific XA error that occurred. Check to determine if WebSphere MQ was running at the time of the failure. | |
1001 |
TPMQ_EAPP_API Connect to LQMID queue_manager failed, Reason = reason_code | |
|
Description |
An error occurred while attempting to connect to the queue_manager. The WebSphere MQ reason_code is shown. |
Action |
Check the WebSphere MQ configuration to determine if the specified queue_manager is defined correctly and is currently running. Refer to IBM WebSphere MQ documentation for the specific meaning of reason_code. | |
1002 |
TPMQ_EAPP_API Inquire on LQMID queue_manager failed, Reason = reason_code | |
|
Description |
An error occurred while attempting to inquire about the queue_manager. The WebSphere MQ reason_code is shown. |
Action |
Check the WebSphere MQ configuration to determine if the specified queue_manager is defined correctly and is currently running. Refer to IBM WebSphere MQ documentation for the specific meaning of reason_code. | |
1003 |
TPMQ_EAPP_API Inquire on LQMID queue_manager Queue queue_name failed, Reason = reason_code | |
|
Description |
An error occurred while attempting to inquire about queue queue_name located on queue manager queue_manager. The WebSphere MQ reason_code is shown. |
Action |
Check the WebSphere MQ configuration to determine if the specified queue_manager and queue_name are defined correctly and are currently running. Refer to IBM WebSphere MQ documentation for the specific meaning of reason_code. | |
1004 |
TPMQ_ECONFIG Get First Element failed for LQMID queue_manager | |
|
Description |
The TM_MQI configuration file did not contain a Queue Manager definition for queue_manager. |
Action |
Add a QUEUE_MANAGER section to the TM_MQI configuration file and restart the server. | |
1005 |
TPMQ_ECONFIG Get First Queue Element failed LQMID queue_manager | |
|
Description |
The TM_MQI configuration file did not contain a QUEUE definition for the QUEUE_MANAGER associated with the specfiied LQMID. |
Action |
Add a QUEUE section to the TM_MQI configuration file and restart the server. | |
1006 |
TPMQ_WARNING Received unexpected tmadmin message | |
|
Description |
The TM_MQI server received an unexpected message from the tmadmin administration service. |
Action |
No action is needed. | |
1007 |
TPMQ_ENOENT Unable to locate QUEUE_MANAGER for requested SERVICE service_name | |
|
Description |
The service_name specified in the call to the TM_MQO server is not asssociated with a QUEUE_MANAGER in the current configuration file. |
Action |
If this service call was not made in error, check the TM_MQO configuration file for the specified service and make sure the SERVICE LQMID maps to a valid QUEUE_MANAGER section. | |
1008 |
TPMQ_EAPP_API MQOPEN on queue queue_name failed Reason = reason_code, marking queue down | |
|
Description |
An error occured while the TM_MQI server was attempting to open the specified queue_name. The specific WebSphere MQ reason_code is shown. The queue_name will be marked inactive and processing of this queue will no longer be performed. |
Action |
Refer to IBM WebSphere MQ documentation for the meaning of the specific reason_code. Correct the problem if necessary and restart the TM_MQI server to restart polling of this queue. | |
1009 |
TPMQ_EAPP_API MQOPEN on LQMID queue_manager Queue queue_name failed Reason = reason_code - shutting down | |
|
Description |
A fatal WebSphere MQ error occurred when attempting to open the specified queue_name. The WebSphere MQ reason_code is shown. |
Action |
Refer to IBM WebSphere MQ documentation for the meaning of the specific reason_code. Correct the problem if necessary and restart the TM_MQI server to restart polling of this queue. | |
1010 |
TPMQ_WARNING MQOPEN on LQMID queue_manager Queue queue_name failed Reason = reason_code | |
|
Description |
A WebSphere MQ error occurred when attempting to open the specified queue_name. The WebSphere MQ reason_code is shown. |
Action |
Refer to IBM WebSphere MQ documentation for the meaning of the specific reason_code. Correct the problem if necessary and restart the server to restart polling of this queue. | |
1011 |
TPMQ_ETRAN Unable to start transaction error = error_text, queue queue_name | |
|
Description |
While processing the specified queue_name, the TM_MQI server's request to begin a Tuxedo transaction failed with the indicated error_text |
Action |
Refer to the | |
1012 |
TPMQ_EATMI Could not allocate buffer error = error_text | |
|
Description |
An attempt to dynamically allocate memory from the operating system failed. |
Action |
Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine. | |
1013 |
TPMQ_EATMI Receive buffer length len exceeds Queue max message length maxlen | |
|
Description |
The buffer received from an |
Action |
Either shorten the message being sent or increase the MAXMSGLEN defined for the queue. | |
1014 |
TPMQ_EAPP_API MQGET on queue queue_name failed Reason = reason_code, marking queue down | |
|
Description |
An attempt to get a message from the specified queue_name failed for the reason_code indicated. This queue will be marked in active and processing of this queue by the TM_MQI server will no longer be performed. |
Action |
Refer to IBM WebSphere MQ documentation for the meaning of the specific reason_code. Correct the problem if necessary and restart the TM_MQI server to restart polling of this queue. | |
1015 |
TPMQ_EAPP_API MQGET failed Reason = reason_code - shutting down | |
|
Description |
A fatal error occured in the TM_MQI server while attempting to get a message from the specified queue_name as indicated by the reason_code. |
Action |
Refer to IBM WebSphere MQ documentation for the meaning of the specific reason_code. Correct the problem and restart the TM_MQI server. | |
1016 |
TPMQ_ETRAN Transaction abort failed error = error_text, queue queue_name | |
|
Description |
The abort of a transaction failed while processing the specified queue_name. |
Action |
No action required. | |
1017 |
TPMQ_INFO Message type mtype received is not a request or datagram; sending to dead letter queue | |
|
Description |
The message type mtype received by the TM_MQI server from WebSphere MQ is not equal to MQMT_REQUEST or MQMT_DATAGRAM. |
Action |
Examine the WebSphere MQ application code to determine why messages of type mtype are being sent to the TM_MQI server. | |
1018 |
TPMQ_EPERM User Identifier userid not found, unable to Authorize | |
|
Description |
An invalid Tuxedo userid was specified in the UserIdentifier field of the MQMD structure received from WebSphere MQ. As a result, the user is not authorized to use the requested service. |
Action |
Ensure that the request is from a valid user, or
add userid to the | |
1019 |
TPMQ_ENOENT Unable to locate QUEUE_MANAGER for requested QUEUE queue_name | |
|
Description |
The requested queue_name is not associated with a QUEUE_MANAGER in the TMQUEUE_MQM configuration file. |
Action |
Fix the problem in the TMQUEUE_MQM configuration file and restart the server. | |
1020 |
TPMQ_ECONFIG Duplicate QUEUE_MANAGER qmgr found in configuration | |
|
Description |
A duplicate QUEUE_MANAGER section was found in the configuration file for this server. |
Action |
Correct the problem and restart the server. | |
1021 |
TPMQ_ENOENT Could not find SERVICE mapping to service_name | |
|
Description |
The service requested in the WebSphere MQ MQMD Format field does not map to a service defined in the TM_MQI configuration file. |
Action |
Modify the TM_MQI configuration file so that the service requested in the WebSphere MQ MQMD Format field maps to a Tuxedo service name and restart the TM_MQI server. Alternatively, modify the application on the MQ side to specify a proper service name for the existing MQ adapter configuration. | |
1022 |
TPMQ_EATMI Service service_name request failed, error = error_text | |
|
Description |
A Tuxedo service request made by the TM_MQI server failed with the indicated error_text. |
Action |
Refer to Tuxedo | |
1023 |
TPMQ_EAPP_API MQPUT1 on LQMID qmgr Queue queue_name failed, Reason = reason_code | |
|
Description |
An attempt to put a message on the specified queue_name failed with the specified reason_code. |
Action |
Refer to IBM WebSphere MQ documentation for the meaning of the specific reason_code and correct the problem if necessary. | |
1024 |
TPMQ_EPROTO FML32 buffer received but INFIELD not defined for SERVICE service_name | |
|
Description |
The TM_MQO server recieved an FML32 buffer for service_name but no |
Action |
Either add an | |
1025 |
TPMQ_ETRAN Commit failed, error = error_text, queue queue_name | |
|
Description |
An error occurred when the TM_MQI server attempted to commit a transaction while processing the specified queue_name. |
Action |
Refer to the Tuxedo tpcommit() documentation to determine what action to take for the specified error_text. | |
1026 |
TPMQ_EAPP_API MQCLOSE failed, Reason = reason_code LQMID queue_manager queue queue_name | |
|
Description |
An attempt to close the specified queue_name failed for the reason_code indicated. |
Action |
Refer to IBM WebSphere MQ documentation for the meaning of the specific reason_code and correct the problem if necessary. | |
1027 |
TPMQ_ELIMIT INFIELD field_name parameter for SERVICE exceeds maximum length maxlen | |
|
Description |
The FML32 field name field_name specified for the |
Action |
Fix the FML32 field name specifed in the | |
1028 |
TPMQ_EATMI Error reason_code sending buffer to Dead Letter queue queue_name | |
|
Description |
An attempt by the TM_MQI server to put a message on the specified dead letter queue queue_name failed for the reason_code indicated. The message has been dropped. |
Action |
Refer to IBM WebSphere MQ documentation for the meaning of the specific reason_code and correct the problem if necessary. | |
1029 |
TPMQ_ECONFIG Dead Letter Queue not defined for LQMID qmgr | |
|
Description |
A Dead Letter Queue was not defined for the WebSphere MQ Queue Manager indicated by qmgr. The message has been dropped by the TM_MQI server. |
Action |
In order to save messages which cannot be processed or sent to a specfied reply queue or backout queue, a dead letter queue must be defined for the queue manager. If a Dead Letter Queue is desired, define one and restart the TM_MQI server. | |
1030 |
TPMQ_ECONFIG Unable to open configuration file filename | |
|
Description |
The configuration file specified by the -C CLOPT option for this server could not be opened. As a result, the server is exiting. |
Action |
Check filename to make sure that it matches a valid configuration file that can be read by the current user. | |
1031 |
TPMQ_ECONFIG Invalid SERVER parameter tag_name | |
|
Description |
The specified parameter tag_name is not a valid SERVER parameter for this server. |
Action |
Fix the SERVER section to include only valid parameters and restart the failed MQ Adapter server. | |
1032 |
TPMQ_ECONFIG QUEUE_MANAGER not defined | |
|
Description |
A QUEUE_MANAGER section was not defined in the configuration file. A QUEUE_MANAGER section must be defined for all MQ Adapter servers. |
Action |
Add a QUEUE_MANAGER section to the configuration file and restart the server. | |
1033 |
TPMQ_ECONFIG Invalid QUEUE_MANAGER parameter tag_name | |
|
Description |
The specified parameter tag_name is not a valid parameter QUEUE_MANAGER parameter for this server. |
Action |
Fix the QUEUE_MANAGER section to include only valid parameters and restart the failed MQ Adapter server. | |
1034 |
TPMQ_ECONFIG QUEUE_MANAGER qmgr failed validation | |
|
Description |
The QUEUE_MANAGER section specified for the TM_MQI server failed validation. |
Action |
A required parameter in the TM_MQI configuration file was either invalid or missing from the QUEUE_MANAGER definition. Add the required parameters to the TM_MQI QUEUE_MANAGER section and restart the server. | |
1035 |
TPMQ_ECONFIG Unable to add QUEUE_MANAGER to collection | |
|
Description |
An internal processing error occurred during the load of conffiguration file data, possibly due to a shortage of system resources. |
Action |
Verify that system resources (memory) are available and restart the failed server. If the problem persists, contact your Tuxedo technical support organization. | |
1036 |
TPMQ_ECONFIG SERVICE not defined | |
|
Description |
A SERVICE section was not defined in the configuration file. |
Action |
At least one SERVICE section is required for this server. Add the necessary SERVICE section to the configuration file and restart the server. | |
1037 |
TPMQ_ECONFIG Invalid SERVICE parameter tag_name | |
|
Description |
The specified parameter tag_name is not a valid SERVICE parameter for this server. |
Action |
Change the SERVICE section to include only valid parameters and restart the server. | |
1038 |
TPMQ_ECONFIG Duplicate SERVICE service_name found in configuration | |
|
Description |
A duplicate SERVICE section was found in the configuration file. A duplicate SERVICE is one whose name matches that of another SERVICE. |
Action |
Correct the problem and restart the server. | |
1039 |
TPMQ_ECONFIG SERVICE service_name failed validation | |
|
Description |
The SERVICE section specified for service_name failed validation. |
Action |
A required parameter was either invalid or missing from the SERVICE definition. Add the required parameters to the SERVICE section and restart the TM_MQI server. | |
1040 |
TPMQ_ECONFIG Unable to add SERVICE to collection | |
|
Description |
An internal processing error occurred during the load of conffiguration file data, possibly due to a shortage of system resources. |
Action |
Verify that system resources (memory) are available and restart the failed server. If the problem persists, contact your Tuxedo technical support organization. | |
1041 |
TPMQ_ECONFIG QUEUE not defined | |
|
Description |
A QUEUE section was not defined in the configuration file. |
Action |
At least one QUEUE section is required for this server. Add the necessary QUEUE section to the configuration file and restart the server. | |
1042 |
TPMQ_ECONFIG Invalid QUEUE parameter tag_name | |
|
Description |
The specified parameter is not a valid QUEUE parameter for this server. |
Action |
Change the QUEUE section to include only valid parameters and restart the server. | |
1043 |
TPMQ_ECONFIG QUEUE queue_name failed validation | |
|
Description |
The QUEUE section specified for queue_name failed validation. |
Action |
A required parameter was either invalid or missing from the QUEUE definition. Add the required parameters to the QUEUE section and restart the TM_MQI server. | |
1044 |
TPMQ_ECONFIG Invalid LQMID qmgr assigned to QUEUE queue_name | |
|
Description |
The logical queue manager ID for the specified queue_name did not match to the configured queue manager. |
Action |
Correct the LQMID parameter in the configuration file and restart the server. | |
1045 |
TPMQ_ECONFIG Duplicate QUEUE queue_name found in QUEUE_MANAGER qmgr configuration | |
|
Description |
A duplicate QUEUE section was found in the configuration file. A duplicate QUEUE is one whose name parameter matches that of another QUEUE. |
Action |
Correct the problem and restart the server. | |
1046 |
TPMQ_ECONFIG Unable to add QUEUE to collection | |
|
Description |
An internal processing error occurred during the load of conffiguration file data, possibly due to a shortage of system resources. |
Action |
Verify that system resources (memory) are available and restart the failed server. If the problem persists, contact your Tuxedo technical support organization. | |
1047 |
TPMQ_ECONFIG Required parameter NAME missing from QUEUE_MANAGER definition | |
|
Description |
A required parameter is missing from the QUEUE_MANAGER definition in the configuration file. |
Action |
Add the required parameter to the configuration file and restart the server. | |
1049 |
TPMQ_ECONFIG Required parameter NAME missing from SERVICE definition | |
|
Description |
A required parameter is missing from a SERVICE definition in the configuration file. |
Action |
Add the required parameter to the configuration file and restart the server. | |
1050 |
TPMQ_ECONFIG Required parameter FORMAT missing from SERVICE service_name definition | |
|
Description |
A required parameter is missing from a the definition of SERVICE service_name in the configuration file. |
Action |
Add the required parameter to the configuration file and restart the server. | |
1051 |
TPMQ_ECONFIG Required parameter MQNAME missing from QUEUE definition | |
|
Description |
A required parameter is missing from a QUEUE definition in the configuration file. |
Action |
Add the required parameter to the configuration file and restart the server. | |
1052 |
TPMQ_ECONFIG Required parameter TUXNAME missing from QUEUE definition | |
|
Description |
A required parameter is missing from a QUEUE definition in the configuration file. |
Action |
Add the required parameter to the configuration file and restart the server. | |
1053 |
TPMQ_ELIMIT OUTFIELD field_name parameter for SERVICE exceeds maximum length maxlen | |
|
Description |
The FML32 field_name specified for the OUTFIELD parameter in the TM_MQO configuration file exceeds the maximum allowable length of maxlen characters. As a result of this configuration error, the TM_MQO server will not boot. |
Action |
Fix the OUTFIELD field name to be a valid field name and reboot the TM_MQO server. | |
1054 |
TPMQ_ECONFIG Required parameter -C missing | |
|
Description |
The CLOPT for this server requires a -C configuration_file after the -- which separates generic server options from server-specific option. However, no -- followed by -C configuration_file was found in the server CLOPT. |
Action |
If the application can be shutdown, edit the UBBCONFIG file to fix the CLOPT for the failed server, shut the application down, run tmloadcf(1), and reboot the application. If the application cannot be shutdown, use TM_MIB(5) to edit the TA_CLOPT in the TA_SERVER class for the failed server, and then boot the server. | |
1055 |
TPMQ_INFO process_name started | |
|
Description |
The indicated server has started. |
Action |
No action required. | |
1056 |
TPMQ_INFO process_name shutdown | |
|
Description |
The indicated server has shutdown. |
Action |
No action required. | |
1057 |
TPMQ_ELIMIT Configuration file name exceeds maximum length | |
|
Description |
The fully qualified configuration file name specified by the -- -C option in the server CLOPT exceeds the maximum allowable length of 256 characters. As a result, this MQ Adapter server cannot boot. |
Action |
If the application can be shutdown, edit the UBBCONFIG file to fix the CLOPT for the failed server, shut the application down, run tmloadcf(1), and reboot the application. If the application cannot be shutdown, use TM_MIB(5) to edit the TA_CLOPT in the TA_SERVER class for the failed server, and then boot the server. | |
1058 |
TPMQ_ECONFIG LQMID qmgr for SERVICE service_name not defined | |
|
Description |
The QUEUE_MANAGER associated with the indicated SERVICE definition does not exist. |
Action |
Change the SERVICE definition to reflect a valid QUEUE_MANAGER and reboot the TM_MQO server. | |
1059 |
TPMQ_ECONFIG SERVICE service_name is defined as transactional but LQMID qmgr is non-transactional | |
|
Description |
A SERVICE was defined as transactional, however the associated WebSphere MQ QUEUE_MANAGER does not support syncpoint processing. |
Action |
Change the SERVICE definition or enable syncpoint processing for the QUEUE_MANAGER. | |
1060 |
TPMQ_EATMI Error advertising SERVICE service_name, error = error_text | |
|
Description |
An error occurred in the TM_MQO server when attempting to advertise SERVICE service_name |
Action |
Refer to the | |
1061 |
TPMQ_EOS: Memory allocation error | |
|
Description |
An attempt to dynamically allocate memory from the operating system failed. |
Action |
Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine. | |
1062 |
TPMQ_EAPP_API Unable to disconnect from QUEUE_MANAGER, Reason = reason_code | |
|
Description |
An error occurred during shutdown processing while disconnecting from the QUEUE_MANAGER. The reason_code returned by MQDISC is included as part of the message. |
Action |
Refer to IBM WebSphere MQ documentation for the specific meaning of reason_code. | |
1063 |
TPMQ_ENOENT Unable to locate requested service service_name | |
|
Description |
The configuration information for the indicated service_name could not be located in the TM_MQO configuration file. As a result, this service request is returning failure. |
Action |
Verify that the service_name is valid and defined in the TM_MQO configuration file. | |
1064 |
TPMQ_EAPP_API MQGET on QUEUE queue_name failed, Reason = reason_code | |
|
Description |
An error occurred during the retrieval of a message from the indicated queue_name. The reason_code returned by MQGET is included as part of the message. |
Action |
Refer to IBM WebSphere MQ documentation for the specific meaning of reason_code. | |
1065 |
TPMQ_ELIMIT NAME name_value parameter for QUEUE_MANAGER exceeds maximum length maxlen | |
|
Description |
The NAME parameter in the QUEUE_MANAGER section of the configuration file exceeded the maximum allowable length of maxlen characters. As a result of this configuration file error, the boot of this server failed. |
Action |
Correct the NAME parameter in the configuration file and reboot the server. | |
1066 |
TPMQ_ELIMIT LQMID lqmid_value parameter for QUEUE_MANAGER exceeds maximum length maxlen | |
|
Description |
The LQMID parameter in the QUEUE_MANAGER section of the configuration file exceeded the maximum allowable length of maxlen characters. As a result of this configuration file error, the boot of this server failed. |
Action |
Correct the LQMID parameter in the configuration file and reboot the server. | |
1067 |
TPMQ_ELIMIT NAME name_value parameter for SERVICE exceeds maximum length maxlen | |
|
Description |
The NAME parameter in a SERVICE section of the configuration file exceeded the maximum allowable length of maxlen characters. As a result of this configuration file error, the boot of this server failed. |
Action |
Correct the NAME parameter in the configuration file and reboot the server. | |
1068 |
TPMQ_ELIMIT MQNAME mqname_value parameter for SERVICE exceeds maximum length maxlen | |
|
Description |
The MQNAME parameter in a SERVICE section of the configuration file exceeded the maximum allowable length of maxlen characters. As a result of this configuration file error, the boot of this server failed. |
Action |
Correct the MQNAME parameter in the configuration file and reboot the server. | |
1069 |
TPMQ_ELIMIT REPLYTOQ replytoq_value parameter for SERVICE exceeds maximum length maxlen | |
|
Description |
The REPLYTOQ parameter in a SERVICE section of the configuration file exceeded the maximum allowable length of maxlen characters. As a result of this configuration file error, the boot of this server failed. |
Action |
Correct the REPLYTOQ parameter in the configuration file and reboot the server. | |
1070 |
TPMQ_ELIMIT LQMID lqmid_value parameter for SERVICE exceeds maximum length maxlen | |
|
Description |
The LQMID parameter in a SERVICE section of the configuration file exceeded the maximum allowable length of maxlen characters. As a result of this configuration file error, the boot of this server failed. |
Action |
Correct the LQMID parameter in the configuration file and reboot the server. | |
1071 |
TPMQ_ELIMIT FORMAT format_value parameter for SERVICE exceeds maximum length maxlen | |
|
Description |
The FORMAT parameter in a SERVICE section of the configuration file exceeded the maximum allowable length of maxlen characters. As a result of this configuration file error, the boot of this server failed. |
Action |
Correct the FORMAT parameter in the configuration file and reboot the server. | |
1072 |
TPMQ_ECONFIG Required parameter MQNAME missing from SERVICE service_name definition | |
|
Description |
The required parameter MQNAME is missing from the SERVICE definition for service_name in the configuration file. |
Action |
Add the required parameter to the configuration file and reboot the server. | |
1074 |
TPMQ_ECONFIG Conflicting parameters specified (REPLYTOQ and TRAN=YES) for Service service_name | |
|
Description |
A SERVICE cannot be defined in the TM_MQO configuration as having a reply queue and transactional support. |
Action |
Correct the SERVICE configuation and restart the TM_MQO server. | |
1075 |
TPMQ_ECONFIG SERVICE parameter TIMEOUT not specified and no default available | |
|
Description |
A TIMEOUT parameter was not defined for the SERVICE and a DEFTIMEOUT parameter was not defined in the SERVER section of the TM_MQO configuration file. |
Action |
Define a DEFTIMEOUT value or add a TIMEOUT parameter to the SERVICE definition and reboot the TM_MQO server. | |
1076 |
TPMQ_ECONFIG SERVICE parameter MAXMSGLEN not specified and no default available | |
|
Description |
A MAXMSGLEN parameter was not defined for the SERVICE and a DEFMAXMSGLEN parameter was not defined in the SERVER section of the TM_MQO configuration file. |
Action |
Define a DEFMAXMSGLEN value or add a MAXMSGLEN parameter to the SERVICE definition and reboot the TM_MQO server. | |
1077 |
TPMQ_ECONFIG QUEUE queue_name parameter MAXMSGLEN not specified and no default available | |
|
Description |
A MAXMSGLEN parameter was not defined for QUEUE queue_name and a DEFMAXMSGLEN was not defined in the SERVER section of the TMQUEUE_MQM configuration file. |
Action |
Define a DEFMAXMSGLEN value or add a MAXMSGLEN parameter to the QUEUE definition and reboot the TMQUEUE_MQM server. | |
1078 |
TPMQ_ECONFIG Required parameter MQNAME missing from QUEUE queue_name definition | |
|
Description |
A required prameter is missing from the indicated QUEUE definition in the TMQUEUE_MQM configuration file. As a result of this configuration error, the TMQUEUE_MQM server did not boot. |
Action |
Add the required MQNAME parameter to the configuration file and reboot the TMQUEUE_MQM server. | |
1079 |
TPMQ_ELIMIT LQMID lqmid_value parameter for QUEUE exceeds maximum length maxlen | |
|
Description |
The LQMID parameter for the indicated QUEUE exceeds the maximum number of characters allowed. |
Action |
Correct the LQMID parameter in the server configuration file and reboot the server. | |
1080 |
TPMQ_ELIMIT MQNAME mqname_value parameter for QUEUE exceeds maximum length maxlen | |
|
Description |
The MQNAME parameter for the indicated QUEUE exceeds the maximum number of characters allowed. As a result of this configuration error, the server did not boot. |
Action |
Correct the MQNAME parameter in the configuration file and reboot the server. | |
1081 |
TPMQ_ELIMIT TUXNAME tuxname_value parameter for QUEUE exceeds maximum length maxlen | |
|
Description |
The TUXNAME parameter for the indicated QUEUE exceeds the maximum number of characters allowed. As a result of this configuration error, the server did not boot. |
Action |
Correct the TUXNAME parameter in the configuration file and reboot the server. | |
1084 |
TPMQ_EINVAL tpdequeue parameter TPQWAIT not supported | |
|
Description |
The TPQWAIT option is not supported when making a tpdequeue() call to a WebSphere MQ queue. |
Action |
Change the client code so that TPQWAIT is not specified when dequeuing from a WebSphere MQ queue. | |
1085 |
TPMQ_EINVAL tpenqueue parameter TPQTIME_ABS not supported | |
|
Description |
The TPQTIME_ABS option is not supported when making a tpenqueue() call to a WebSphere MQ queue. |
Action |
Change the client code so that TPQTIME_ABS is not specified when enqueuing to a WebSphere MQ queue. | |
1086 |
TPMQ_EINVAL tpenqueue parameter TPQTIME_REL not supported | |
|
Description |
The TPQTIME_REL option is not supported when making a tpenqueue() call to a WebSphere MQ queue. |
Action |
Change the client code so that TPQTIME_REL is not specified when enqueuing to a WebSphere MQ queue. | |
1087 |
TPMQ_EINVAL tpenqueue parameter TPQTOP not supported | |
|
Description |
The TPQTOP option is not supported when making a tpenqueue() call to a WebSphere MQ queue. |
Action |
Change the client code so that TPQTOP is not specified when enqueuing to a WebSphere MQ queue. | |
1088 |
TPMQ_EINVAL tpenqueue parameter TPQBEFOREMSGID not supported | |
|
Description |
The TPQBEFOREMSGID option is not supported when making a tpenqueue() call to a WebSphere MQ queue. |
Action |
Change the client code so that TPQBEFOREMSGID is not specified when enqueuing to a WebSphere MQ queue. | |
1089 |
TPMQ_EINVAL tpenqueue parameter TPQFAILUREQ not supported | |
|
Description |
The TPQFAILUREQ option is not supported when making a tpenqueue() call to a WebSphere MQ queue. |
Action |
Change the client code so that TPQFAILUREQ is not specified when enqueuing to a WebSphere MQ queue. | |
1090 |
TPMQ_ECONFIG LQMID qmgr for QUEUE queue_name not defined | |
|
Description |
The QUEUE_MANAGER associated with the indicated QUEUE definition does not exist. |
Action |
Change the QUEUE definition to reflect a valid QUEUE_MANAGER and reboot the server. | |
1091 |
TPMQ_ECONFIG OUTFIELD parameter specified for SERVICE service_name but INFIELD parameter missing | |
|
Description |
A TM_MQO SERVICE definition cannot contain an OUTFIELD parameter unless an INFIELD parameter is also specified. As a result of the configuration error, the TM_MQO server did not boot. |
Action |
Correct the error in the definition of SERVICE service_name and reboot the TM_MQO server. | |
1092 |
TPMQ_EPROTO SERVICE service_name defined as transactional but called outside of a transaction | |
|
Description |
Service service_name was defined with |
Action |
Alter the calling program to make a | |
1093 |
TPMQ_ESYSTEM Unable to locate FLDID32 for field name field_name | |
|
Description |
The TM_MQO server was unable to locate the FML32 field identifier corresponding to FML32 field name field_name. |
Action |
Verify that the FLDTBLDIR32 and FIELDTBLS32 environment variables are set correctly in the TM_MQO server environment so that field_name can be found. | |
1094 |
TPMQ_EINVAL Required FML32 field name field_name for SERVICE service_name not found | |
|
Description |
The TM_MQO server received an FML32 data type as input, but was unable to locate field name field_name specified as the |
Action |
Ensure that FML32 buffers sent to TM_MQO contain the FML32 field defined as | |
1095 |
TPMQ_ECONFIG Only 1 QUEUE_MANAGER allowed | |
|
Description |
Only one *QUEUE_MANAGER section is allowed in the server configuration file. As a result of this configuration error, the server did not boot. |
Action |
Remove all but one *QUEUE_MANAGER section from the configuration file and reboot the server. | |
1097 |
TPMQ_ECONFIG Only 1 SERVER section allowed | |
|
Description |
Only one *SERVER section is allowed in the server configuration file. As a result of this configuration error, the server did not boot. |
Action |
Remove all but one *SERVER section from the configuration file and reboot the server. | |
1098 |
TPMQ_ECONFIG parameter_name parameter value "parameter_value" is not numeric | |
|
Description |
The parameter parameter_name requires a numeric value but the value parameter_value is not numeric. As a result of this configuration error, the server did not boot. |
Action |
Fix the parameter error in the server configuration file and reboot the server. | |
1099 |
TPMQ_ECONFIG parameter_name parameter value "parameter_value" is not in allowable range of minval through maxval | |
|
Description |
The value of parameter_value specified for parameter_name in the configuration file was not in the valid range of minval through maxval. As a result of this configuration error, the server did not boot. |
Action |
Fix the parameter error in the server configuration file and reboot the server. |
![]() |
![]() |
![]() |