Enhanced Multi-Region Operation (MRO) uses facilities and services provided by CICS to execute a terminal-oriented transaction within an multi-region environment. To validate the configuration of HostBridge within your MRO envoironment, we developed a test application that simply adds two integer values together. However, it accomplishes this task using a complex division of labor that involves three transactions: HBAA, HBAB and HBAC. Each of these transactions reference the same program module (HBRMRTA).
HBRMRTA uses a COMMAREA to save state information and data values between invocations. The COMMAREA is also used to keep track of the execution path (i.e., SYSID, TERMID and TRANID). The complete execution path displays when the transaction ends.
By default, if the program detects that a TCTUA has been allocatedfor the session, it will prompt the user for the offset of a four-byte area that it can use within the TCTUA (it will default to using the last four bytes). The program will use this area to keep track of a counter which will be incremented once for each transaction executed (when the transaction ends the counter should have a value of 4).
The program supports two options on the command line that invokes HBAA. The options are:
- TRACE — This option instructs the program to generate trace messages to the HBROUT file.
- NOTCTUA — This option instructs the program to not use the TCTUA even if it is present.
Installing the Application
The HostBridge MRO Test Application includes one program and one BMS map. Both are provided in source form here for you to download: HBRMRTA.asm and HBRMRTM.asm
In order to create the test environment on your system, you will need to:
- Upload the files to TSO using IND$FILE or FTP. The files must be transferred to TSO as text files with 80 byte records.
- Use a standard map assembly and HLASM JCL to create load modules for HBRMRTA and HBRMRTM.
- Make the load modules (HBRMRTA and HBRMRTM) accessible to CICS via the DFHRPL concatenation list.
If you have any questions about this procedure, please contact HostBridge Support.
Running the Test Application from a Terminal
To run the application:
- Execute the transaction HBAA after logging on to CICS.
- If the program detects that a TCTUA has been allocated for the session (and if NOTCTUA has not been specified), thefollowing screen displays.
- Enter the offset of a 4 byte area within the TCTUA that this program can use. By default, the program will use the offset corresponding to the last 4 bytes. After you press the ENTER key, the following screen displays.
- Specify the first integer value to be added or accept the default value of 1. After you press the ENTER key the following screen displays.
Specify the second integer value to be added or accept the default value of 2. After you press the ENTER key the final screen displays.
This final screen should indicate the following:
- If the program detected that a TCTUA was allocated for the session, the COUNTER field should have a value of 4.
- "VALUE 1" should be the first value specified, "VALUE 2" should be the second value specified, and "TOTAL" should be the sum of the two values.
- The execution path should indicate that four transactions were executed. The SYSID's indicated in the execution path should reflect the regions in which the three transactions were defined.
Running the Application via HostBridge
After you confirm that the application runs correctly from a terminal, you can execute it through HostBridge. The following request sequence will exercise the transactions, adding 123 to 456.
CICS Resource Definitions
The HostBridge MRO Test Application requires you to define five resources to CICS. These resources must be defined in each region in which the application will execute (the definitions below assume that there are three regions involved: CICS, CICB and CICC).
Details for each of the resource definitions are below (parameters not specified are assumed to have the default value for the resource type).
The MAPSET resource should be defined as follows:
The PROGRAM resource should be defined as follows:
The three TRANSACTION resources should be defined as follows. The REMOTESYSTEM name should be whatever is appropriate for your environment.