Testing the CICS Bridge Using RFHUTIL

Created by Lyn Elkins and Leigh Compton, IBM ATS Introduction

We have received a number of questions on the parameters used to execute a program using the WMQ/CICS bridge from the RFHUTIL utility provided in SupportPac IH03, WBI Message Broker V6 - Message display, test and performance utilities. All WMQ SupportPacs may be found at: http://www-1.ibm.com/support/docview.wss?rs=977&uid=swg27007205

Please note that even though the SupportPac was designed for use with the message broker, it is also very useful when testing WMQ.

This document assumes that both the CICS and WMQ environments have been set up and the CICS Sample program EC01 program is available.

Three scenarios are covered, in all cases the RFHUTIL program is running on a WINDOWS platform:

1) Passing an EBCDIC message body, no CIH header attached to the message 2) Passing an ASCII message body, no CIH header attached to the message 3) Passing an EBCDIC message body, attaching a CIH header to the message I. Using RFHUTIL to input a CICS Bridge message, when the body of the message is in EBCDIC:

a. Bring up RFHUTIL. b. Enter the queue manager and target queue. Please note these examples illustrate a queue manager to queue manager connection from a local queue manager on the Windows platform. c. Read the sample message as illustrated:

The message is in a file called EBCDIC_Data.txt, which is included in this posting. d. Navigate to the data tab to review the message:

Note the Char format setting on the right hand side of the panel. i. Navigate to the MQMD tab and fill in the fields as shown:

The important fields are:

1. MQ Message Format = MQSTR 2. MQ Message Type = 1-Request 3. Correlid – this value tells the WMQ Bridge that this is a new request, not a continuation. In hex it is: 414D51214E45575F53455353494F4E5F434F5252454C4944 The Correlation ID is included in a file called NEW_CORRELID.txt included in this posting. 4. Reply to Queue Manager 5. Reply to Queue ii. Navigate back to the main tab and hit the WriteQ button iii. The count of message on the reply queue should be increased as shown: II. Using RFHUTIL to input a CICS Bridge message, when the body of the message is in ASCII. a. Repeat the same initial steps, bring up RFHUTIL, connect to the queue manager and queue, and read the sample message (this time in ASCII). The sample data is in a file called ASCII_Data.txt attached to this posting. When you display the data is should look as follows: b. Navigate to the MQMD tab and fill in the fields as shown:

The important fields are: i. MQ Message Format = MQSTR ii. MQ Message Type = 1-Request iii. Correlid – this value tells the WMQ Bridge that this is a new request, not a continuation. It is 414D51214E45575F53455353494F4E5F434F5252454C4944 The Correlation ID is included in a file called NEW_CORRELID.txt included in this posting. iv. Reply to Queue Manager v. Reply to Queue c. Navigate to the Main tab, and hit the WriteQ button. You should see the reply to queue depth increase as shown below: III. Using RFHUTIL to submit a message with a CIH header.

a. Read the sample message as illustrated below. It is the same data, but without the program ID that will be LINKed to (‘EC01 ‘).

b. Navigate to the MQMD tab, filling the same fields as you did for the sample EDBDIC data with one exception, note the Message format is now MQCICS c. Navigate to the CIH tab an enter the information as shown:

d. Navigate to the Main tab and hit the WriteQ button. Again the message depth in the reply to queue should be increased.