TUXMQ Messages 1100-1199
|
|
1100
TPMQ_ECONFIG No parameter name specified before '='
Description
An MQ Adapter server found a line with an = sign without any preceeding parameter name in its configuration file.
Due to the configuration file syntax error, the server was not booted.
Action
Fix the MQ Adapter server configuration file so that there is a parameter name before each = sign on every line of the file.
Once the configuration file syntax is fixed, reboot the failed server.
1101
TPMQ_ECONFIG Parameter parameter_name is not followed by '='
Description
An MQ Adapter server found a line which contained a parameter name without an = sign and was not a section name line starting with *.
Due to the configuration file syntax error, the server was not booted.
Action
Ensure that every parameter name in the configuration file is followed by an = sign and an associated value.
Once the configuration file syntax is fixed, reboot the failed server.
1102
TPMQ_ECONFIG No value after '=' for parameter parameter_name
Description
An MQ Adapter server found a line which contained a parameter name and an = sign but which did not contain a parameter value following the = sign.
Due to the configuration file syntax error, the server was not booted.
Action
Ensure that every parameter name in the configuration file is followed by an = sign and an associated value.
Once the configuration file syntax is fixed, reboot the failed server.
1103
TPMQ_ECONFIG Parameter parameter_name exceeds maximum length
Description
The parameter name parameter_name is not a valid parameter name and exceeds the maximum allowable length for a parameter name in the MQ Adapter server configuration file. Due to the configuration file syntax error, the server was not booted.
Action
Ensure that every parameter name in the configuration file is a valid parameter name followed by an = sign and a parameter value.
Once the configuration file syntax is fixed, reboot the failed server.
1104
TPMQ_ECONFIG Value for parameter parameter_name exceeds maximum length
Description
The value for parameter parameter_name in the MQ Adapter server configuration file exceeds the maximum allowable length. Due to the configuration file syntax error, the server was not booted.
Action
Specify a valid value for parameter parameter_name in the MQ Adapter server configuration file. Once the configuration file syntax is fixed, reboot the failed server.
1105
TPMQ_SYSTEM No composite header in buffer
Description
The TMQUEUE_MQM received a service request that did not contain the composite buffer type sent by tpenqueue() and tpdequeue().
Action
Examine your application to ensure that a program is not mistakenly using tpcall() or tpacall() to send service requests to the TMQUEUE_MQM server. The TMTRACE(5) facility may be helpful in determining which programs are making calls to the TMQUEUE_MQM server. All invocations of services offered by TMQUEUE_MQM should be done via tpenqueue() or tpdequeue().
1106
TPMQ_SYSTEM No composite FML data in buffer
Description
The TMQUEUE_MQM received a service request that contained a composited buffer type, but which did not contain FML data.
Action
All invocations of services offered by TMQUEUE_MQM should be done via tpenqueue() or tpdequeue().
Examine your application to ensure that a program is not mistakenly using tpcall() or tpacall() to send a service requests with a composite buffer type to the TMQUEUE_MQM server.
If this is not the case, contact your Tuxedo technical support organization.
1107
TPMQ_WARNING Failed to get field field_name from operation message
Description
The TMQUEUE_MQM server was unable to find expected field field_name
in the service input buffer.
operation tells whether the error occurred during a tpenqueue() operation or during a tpdequeue() operation.
Action
Contact your Tuxedo technical support organization.
1108
TPMQ_EATMI Failed to set field field_name in operation message
Description
The TMQUEUE_MQM server was unable to set field field_name
in the service output buffer.
operation tells whether the error occurred during a tpenqueue() operation or during a tpdequeue() operation.
Action
Contact your Tuxedo technical support organization.
1109
TPMQ_EINVAL Received message with unknown ReplyToQ queue_name
Description
The TMQUEUE_MQM server received a tpdequeue() request from Tuxedo for a queue which was not mapped to a WebSphere MQ queue in the TMQUEUE_MQM configuration file.
Action
Modify the TMQUEUE_MQM configuration file so that queue_name is specified as the TUXNAME parameter of a *QUEUE table entry and reboot the TMQUEUE_MQM server. Alternatively, fix the client which specified queue_name as a reply queue name to specify a proper name.
1110
TPMQ_EINVAL tpenqueue parameter TPQREPLYQOS not supported
Description
The TPQREPLYQOS parameter does not map to a corresponding WebSphere MQ parameter and is not allowed on tpenqueue() requests to the TMQUEUE_MQM server. As a result of the error, a QMEINVAL diagnostic is being returned to the caller.
Action
Modify the application so that TPQUREPLYQOS is not specified on requests to the TMQUEUE_MQM server.
1111
TPMQ_EAPP_API Inquire on queue queue_name failed, Reason=MQRC_Q_DELETED, marking queue down
Description
The specified queue_name has been deleted from WebSphere MQ. As a result, the TM_MQI server will no longer poll this queue for incoming messages.
Action
If queue_name was deliberately deleted, no action is required. If queue_name has been deleted by accident, have the WebSphere MQ administrator recreate this queue and reboot the TM_MQI server once queue_name has been recreated.
1112
TPMQ_EAPP_API Inquire on LQMID lqmid Queue queue_name failed, Reason=error_code (num_err error(s) for this queue since last message; message will not be repeated for num_sec seconds)
Description
An MQINQ operation on queue_name failed with MQ error
Action
Examine the MQ error_code for further information on the cause of the error. Verify that the current user has permission to perform MQINQ operations on queue_name.
1113
TPMQ_EAPP_API Get on LQMID lqmid Queue queue_name failed, Reason=error_code (number message(s) on queue; num_err error(s) for this queue since last message; message will not be repeated for num_sec seconds)
Description
An MQGET operation on queue_name failed with MQ error
Action
Examine the MQ error_code for further information on the cause of the error. Verify that the current user has permission to perform MQGET operations on queue_name.
1114
TPMQ_EAPP_API MQPUT1 on Queue Manager queue_manager_name Reply Queue reply_queue_name failed, Reason = error_code
Description
A WebSphere MQ MQPUT1 operation failed on queue queue_name. As a result, the TM_MQI server was unable to place the reply to a service request on this queue. As a result of the error, TM_MQI will attempt to send this reply to the WebSphere MQ Dead Letter Queue, if any.
Action
Examine the MQ error_code for further information as to the cause of the error.
1115
TPMQ_EAPP_API MQPUT1 on Queue queue_name failed, Reason = _error_code
Description
A WebSphere MQ MQPUT1 operation failed on queue queue_name. As a result, the TM_MQO server was unable to process the current service request.
Action
Examine the MQ error_code for further information as to the cause of the error. Resubmit the failed request once the error has been fixed.
1116
TPMQ_WARNING MQOPEN on Reply Queue queue_name failed, Reason = error_code
Description
A WebSphere MQ MQOPEN operation failed on reply queue queue_name. As a result, the TM_MQO server was unable to receive a reply for this service request. Any reply that may exist remains queued on queue_name.
Action
Examine the MQ error_code for further information as to the cause of the error. If necessary, have the MQ administrator manually dequeue this message from reply queue queue_name.
1117
TPMQ_EPROTO SERVICE service_name defined as nontransactional but called within a transaction
Description
The TM_MQO server received a service request for a service defined with TRAN=N inside a Tuxedo transaction. This is not allowed, and a TPFAIL reply is being returned to the caller.
Action
Call the service outside of a Tuxedo transaction or using the TPNOTRAN flag. (If the service should be called within a transaction, change the TM_MQO configuration file to specify TRAN=Y and reboot the TM_MQO server.)
1118
TPMQ_ELIMIT OUTFIELDVNAME viewname parameter for SERVICE exceeds maximum length maxlen
Description
The OUTFIELDVNAME parameter specified in the TM_MQO configuration file exceeds the maximum allowable length. As a result of this error, the TM_MQO server did not boot.
Action
Fix the OUTFIELDVNAME parameter name and reboot the TM_MQO server.
1119
TPMQ_EINVAL OUTFIELDVNAME not found for FLD_VIEW32 field field_name
Description
The TM_MQO server could not find field_name in the FML32 field tables. As a result, TM_MQO was unable to return VIEW32 data in this field and is returning an error buffer to the caller.
Action
Ensure that the FLDTBLDIR32 and FIELDTBLS32 environment variables are correctly set in the environment of the TM_MQO server or add a definition for field_Name to the existing FLDTBLDIR32 and FIELDTBLS32 location. If an environment variable change needs to be made, reboot the TM_MQO server so that the change takes effect.
1120
TPMQ_ESYSTEM FML32 error adding field field_name - error_string
Description
The TM_MQO server was unable to add the specified field_name to its output buffer due to the FML32 error reported by error_string. As a result, TM_MQO is returning an error message to its caller.
Action
Contact your Tuxedo technical support organization.
1121
TPMQ_ECONFIG OUTFIELDVNAME parameter specified for SERVICE service_name but OUTFIELD and INFIELD are not specified
Description
A *SERVICE section entry in the TM_MQO configuration file specified the OUTFIELDVNAME parameter without specifying the OUTFIELD or INFIELD parameter. As a result of the configuration error, the TM_MQO server failed to boot.
Action
The OUTFIELDVNAME parameter is meaningful only when the OUTFIELD parameter is specified, or when the INFIELD parameter is specified as a default value for the OUTFIELD parameter.
Fix the TM_MQO configuration file to specify consistent parameters and then reboot the failed TM_MQO server.
1122
TPMQ_EATMI Error error_code sending buffer to backout queue queue_name
Description
An MQPUT1 call in the TM_MQI server returned an error when attempting to send a previously failed message to backout queue queue_name.
Action
Examine the WebSphere MQ error_code for further information as to the cause of the error. Verify that queue_name exists and that put operations are allowed on this queue.
1123
TPMQ_WARNING Unable to invoke audit post-op on security failure
Description
A call to the the audit_postop() plugin security function on a
service operation failed. This call was being attempted due to a deny or
failure return from the authorize_preop() plugin security
function call. No audit of the failure was able to be performed/recorded.
Action
Check the registration of the auditing plugin. If the plugin used is the
default supplied plugin, check the userlog file and filesystem space. If the
plugin used is not the default supplied plugin, check with the supplier of
the plugin code.
In addition, because of the authorize_preop() deny or failure,
if the denial was not intended, check the registration, authorization
configuration, and return from the authorize_preop() function.
See Also
epifregedt, epifreg
1124
TPMQ_WARNING Unable to invoke audit pre-op on service invocation
Description
A call to the audit_preop() plugin security function on a
service operation failed. This call was being attempted prior to the operation
execution. No audit of the attempt was able to be performed/recorded.
Action
Check the registration of the auditing plugin. If the plugin used is the default supplied plugin, check the userlog file and filesystem space. If the plugin used is not the default supplied plugin, check with the supplier of the plugin code.
See Also
epifregedt, epifreg
1125
TPMQ_WARNING Unable to invoke audit post-op on security failure
Description
A call to the the audit_postop() plugin security function on a
service operation failed. This call was being attempted due to a deny or
failure return from the authorize_preop() plugin security
function call. No audit of the failure was able to be performed/recorded.
Action
Check the registration of the auditing plugin. If the plugin used is the
default supplied plugin, check the userlog file and filesystem space. If the
plugin used is not the default supplied plugin, check with the supplier of
the plugin code.
In addition, because of the authorize_preop() deny or failure,
if the denial was not intended, check the registration, authorization
configuration, and return from the authorize_preop() function.
See Also
epifregedt, epifreg
1126
TPMQ_ECONFIG Duplicate FORMAT parameter found for SERVICE definition
Description
A *SERVICE section entry in the TM_MQI or TM_MQO configuration file contained more than one FORMAT line. This is an error, and as a result the TM_MQI or TM_MQO server did not boot.
Action
Fix the TM_MQI or TM_MQO configuration file and reboot the failed server.
1127
TPMQ_WARNING Queue queue_name open failed, Reason=error_code; assuming backout threshold is 0
Description
The TM_MQI server was unable to perform an MQOPEN on queue_name in order to determine the queue backout threshold. As a result, TM_MQI assumes that the backout threshold for this request on this queue is 0 and TM_MQI will act as if the backout threshold for this message has been exceeded.
Action
Examine the error_code and WebSphere MQ error logs to determine why queue_name could not be opened. Verify that the queue_name has not been deleted and that the access permissions on queue_name have not changed.
1128
TPMQ_WARNING Queue queue_name inquire failed, Reason=error_code; assuming backout threshold is 0
Description
After successfully performing an MQOPEN on queue_name, TM_MQI was unable to successfuly perform an MQINQ on the queue to determine the queue backout threshold. As a result, TM_MQI assumes that the backout threshold for this request on this queue is 0 and TM_MQI will act as if the backout threshold for this message has been exceeded.
Action
Examine the error_code and WebSphere MQ error logs to determine why the inquire operation on queue_name failed. Verify that the queue_name has not been deleted and that the access permissions on queue_name have not changed.
1129
TPMQ_WARNING Queue queue_name close failed, Reason=error_code
Description
After sucessfully performing an MQOPEN and an MQINQ on queue_name, TM_MQI was unable to successfully close the queue.
Action
Examine the error_code and WebSphere MQ error logs to determine why queue_name could not be closed. Verify that the queue_name has not been deleted and that the access permissions on queue_name have not changed.
 |
 |
 |