Rational Developer for System z, Version 7.6

WebSphere MQ invoke type -- differences in treatment for different target runtime environments

The treatment of an invoke node with an invoke type of WebSphere® MQ is somewhat different both in the generation properties editor and in the creation of output files by the Generate Runtime Code wizard, depending on whether the target runtime environment is CICS Service Flow Runtime: Level 2.0 or CICS Service Flow Runtime: Level 1.0 (see CICS® Service Flow Runtime Levels 1.0 and 2.0)

The target runtime environment for a generation properties file is selected in the New Generation Properties wizard (see Step A1. Create a generation properties file for the main flow.)

The following table shows the differences in treatment in the generation properties editor:
Item: CICS Service Flow Runtime: Level 2.0: CICS Service Flow Runtime: Level 1.0:
MQGET and MQPUT adapter names (CICS Service Flow Runtime: Level 2.0) or program names (CICS Service Flow Runtime: Level 1.0)

By default the adapter names are the first 8 characters of the invoke name.

No source program is generated. The MQ invocation results in a call to a single generic MQ adapter server in the CICS Service Flow Runtime.

The CICS Service Flow Runtime uses the adapter name to uniquely identify the invocation of the PUT or GET function of the MQ command.

The program names are:
  • MQGET Program Name
  • MQPUT Program Name
Default name for MQGET and MQPUT transaction IDs:

CMAU Each field by default is empty.
Maximum lengths for adapter names and transaction names (number of characters): The maximum lengths are:
  • MQGET Adapter Name: (8)
  • MQGET Transaction Name: (4)
  • MQPUT Adapter Name: (8)
  • MQGET Transaction Name: (4)
The maximum lengths are:
  • MQGET Program Name: (7)
  • MQGET Transaction Name: (3)
  • MQPUT Program Name: (7)
  • MQGET Transaction Name: (3)
A character that is appended to the program names and the transaction names: No character is appended to the names. The appended character is:
  • For MQGET Program Name and MQGET Transaction Name: G
  • For MQPUT Program Name and MQPUT Transaction Name: P
Displaying an error message when the MQGET adapter name and the MQPUT adapter name are the same: An error message is displayed. No error message is displayed.

The following table shows the differences in the generation of output files by the Generate Runtime Code wizard:
Item: CICS Service Flow Runtime: Level 2.0: CICS Service Flow Runtime: Level 1.0:
Generic MQ Server adapter
  • The runtime environment contains a single generic MQ server adapter that handles all the MQ invocations.
  • Consequently, the Generate Runtime Code wizard does not have to generate a separate MQ server adapter for each MQ invocation.
  • The runtime does not have a generic MQ server adapter.
  • The Generate Runtime Code wizard must generate a separate MQ server adapter for each MQ invocation.
The following generated files:
  • COBOL source code files
  • JCL files for compiling the COBOL source code
The Generate Runtime Code wizard no longer creates the files described in the table cell to the right. The Generate Runtime Code wizard creates, for each MQ invocation:
  • COBOL source code for an MQ adapter
  • A JCL file to compile the COBOL source code
The generated JCL file that creates resource definitions (Part 1):
  • The JCL file no longer contains the resource definitions described in the cell to the right.
  • The JCL file contains a resource definition for each generated MQ adapter.
The generated JCL file that creates resource definitions (Part 2):
If you specified any value other than CMAU or blanks for the following transaction IDs in the generation properties editor:
  • MQGet Transaction ID
  • MQPut Transaction ID
The JCL file contains the following additional command:

Transaction
<transaction_name>
   Program DFHMASCQ

The JCL does not contain an additional command.

Terms of use | Feedback

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