3.2.3.2 Optional Parameter
-
EXPIRE = integer
- Specifies the amount of time, in tenths of a second, the expiry time for the MQ service request message sent with MQPUT1. The value must be greater than or equal to 0. A value of 0 indicates that the message will not be expired. The default value is 0.
-
PRIORITY = integer
- Specifies the WebSphere MQ priority at which requests to this service will be sent. WebSphere MQ has traditionally allowed values of 0 through 9 for priorities. If not specified, the default queue priority represented in MQ by the value MQPRI_PRIORITY_AS_Q_DEF will be used.
-
FORMAT = string
- Maps to the WebSphere MQ Message Descriptor Format. Can contain up to 8 characters. Refer to WebSphere MQ documentation for specific format of the Message Descriptor Format field.
-
TRAN = {Y|N}
- Specifies whether the Service is transactional. Y indicates transactional; N indicates non-transactional. The default value is N. (A service defined as transactional must be called within an Oracle Tuxedo transaction. A service defined as non-transactional must be called outside of an Oracle Tuxedo transaction. Messages sent to transactional services are sent with persistence MQPER_PERSISTENT and messages sent to non-transactional services are sent with the default queue persistence MQPER_PERSISTENCE_AS_Q_DEF.)
-
REPLYTOQ = string
- Specifies the name of the WebSphere MQ Reply To Queue. Can contain up to 48 characters, all uppercase. Refer to WebSphere MQ documentation for the specific format of Queue names.
-
INFIELD = string
- Specifies the FML32 field name of the input data in an FML32 buffer. If you specify this parameter, requests for this service may pass FML32 buffers for input, and the data in INFIELD will be passed as the actual service data. (A request to a service which specifies INFIELD may still pass a non-FML32 data type as input, which will be treated exactly as if INFIELD had not been specified, but a request to a service which specifies INFIELD may not pass NULL data.)
If INFIELD is a FLD_VIEW32 field, TM_MQO will pass only the actual VIEW32 data to MQ and will not pass the FVIEWFLD structure that was returned by FML32. The MQ program must know which view it is expecting to receive. The application should not use fields of type FLD_PTR, FLD_FML32, FLD_MBSTRING, or FLD_FML for the TM_MQO INFIELD or OUTFIELD. These field types will not result in meaningful data being passed to or from the MQ application.
If INFIELD is not specified, then TM_MQO will accept only buffers not of type FML32 as input, and will pass this data directly to WebSphere MQ.
-
OUTFIELD = string
- Specifies the FML32 field name of the output data to be used when building an FML32 response buffer. If you specify this parameter, you must also specify the INFIELD parameter. The omission of this parameter causes the response data field name to match the name specified by the INFIELD parameter.
When OUTFIELD is a FLD_VIEW32 field, the data returned by MQ should be VIEW32 data, and not a FVIEWFLD structure. In order to pass VIEW32 data back to an Oracle Tuxedo application, TM_MQO must internally fill in a FVIEWFLD structure to add the VIEW32 data to the FML32 reply buffer, and therefore TM_MQO must know the name of the view to be returned. The TM_MQO server will obtain this information in the following manner:
- If the OUTFIELDVNAME parameter is set, the value of this parameter will be used as the view32 name.
- Otherwise, if the INFIELD was a FLD_VIEW32 field, the same viewname used in the INFIELD will be used for the OUTFIELD.
- Otherwise, TM_MQO will log an error message and call
tpreturn()
with TPFAIL.
The application should not use fields of type FLD_PTR, FLD_FML32, FLD_MBSTRING, or FLD_FML for the TM_MQO INFIELD or OUTFIELD. These field types will not result in meaningful data being passed to or from the MQ application.
-
OUTFIELDVNAME = view32name
- Specifies the name of the VIEW32 subtype used for output to the FML32 OUTFIELD (or the FML32 INFIELD if OUTFIELD is not configured.) OUTFIELDVNAME is allowed only if OUTFIELD and/or INFIELD are also specified.
Parent topic: Defining the TM_MQO SERVICE Section (Required)