Rational Developer for System z, Version 7.6

WebSphere MQ invoke type -- CICS Service Flow Runtime: Level 1.0

This topic describes the generation properties of the WebSphere® MQ invoke type for CICS Service Flow Runtime: Level 1.0 (see CICS® Service Flow Runtime Levels 1.0 and 2.0).

This topic contains the following subtopics:

General information

Important: A WebSphere MQ invoke node can validly occur only within a Nonterminal flow node (see About flow types).

The WebSphere MQ invoke type causes the specified nonterminal application to be invoked through the WebSphere MQ application programming interface.

A WebSphere MQ invoke node is handled somewhat differently by the generation properties editor and the Generate Runtime Code wizard, depending on the target runtime environment for the generation properties file. These differences are reflected in this help topic. (For a comparison of the differences see WebSphere MQ invoke type -- differences in treatment for different target runtime environments.)

Generation properties

For more information about these generation properties see the CICS Service Flow Runtime User's Guide (see Supported runtime environments for each project type).

Table 1. WebSphere MQ node generation properties
NAME DESCRIPTION VALUE RANGE DEFAULT VALUE
Invoke Type Type of node used in a COBOL-based flow
  • LINK with COMMAREA
  • LINK with Channel
  • WebSphere MQ
LINK with COMMAREA
Activity Name Name of the activity performed by the node.
Note: When the runtime code is generated for the CICS Service Flow Runtime environment, the runtime code generator uses the information in this node to create a CICS Business Transaction Services (BTS) activity. The name that you specify here is used as the name of the new BTS activity.
String value: 1-32 characters Node ID
Comment Optional text associated with the node N/A N/A
MQPUT Adapter Name The name of the generated COBOL program that implements the PUT function of the MQ command. String value: 1-7 characters First 7 characters of the Invoke name + "P"
MQPUT Transaction ID CICS TransID for the COBOL program that implements the PUT function of an MQ command String value: 1-3 characters First 3 characters of the Program Name + "P"
Queue Name Name of the MQ queue on which the command will put the message String value: 1-48 characters. Cannot be blank. N/A
Message Type Specifies the MQ message type for the Request Message
  • Request: Requires a reply.
  • Datagram: Does not require a reply.
Request
MQGET Adapter Name The name of the generated COBOL program that implements the GET function of the MQ command.
  • String value: 1-7 characters.
  • Not required when the Message Type is Datagram.
First 7 characters of the Invoke name + "G"
MQGET Transaction ID CICS TransID for the COBOL program that implements the GET function of an MQ command
  • String value: 1-3 characters.
  • Not required when the Message Type is Datagram.
First 3 characters of the Program Name + "G"
MQPUT Reply to Queue Name Name of the MQ queue from which the command will get a reply
  • String value: 1-48 characters.
  • Not required when the Message Type is Datagram.
.
N/A
MQPUT Reply to QManager Name of the MQ Queue Manager that owns the Reply Queue from which the command will get a reply
  • String value: 1-48 characters.
  • Not required when the Message Type is Datagram.
N/A
Maximum Output Message Length The maximum message length expected to be returned from the back-end application
  • Value > 0.
  • Not required when the Message Type is Datagram.
N/A
Wait Interval Time, in seconds, that the Queue Manager waits for a message to arrive on the Reply Queue
  • Use the value 999 to indicate an unlimited wait interval.
  • Not required when the Message Type is Datagram.
N/A


Terms of use | Feedback

This information center is powered by Eclipse technology. (http://www.eclipse.org)