This chapter describes any installation or configuration needed at the mainframe to support the deployment of eBiz or Data Access Transaction mainframe components in a CICS region.
Note: For information on IMS, see the chapter IMS Support in your User's Guide and the appendiz Deploying IMS eBiz Transactions in your Deployment Guide.
The environment required to support the deployment of eBiz or Data Access Transaction mainframe components consists of:
Mainframe Access is a client-server connectivity tool that enables you to either offload mainframe source files or access them in place. Installing Mainframe Access also eases the installation of the SOA Express Server.
The SOA Express Server consists of run-time modules that are deployed to support CICS eBiz or Data Access Transactions. See the section SOA Express Server below for details.
The SOA Express Server consists of:
The Micro Focus CICS 3270 Bridge Exit intercepts certain CICS API calls from the legacy application (notably SEND MAP, SEND CONTROL, SEND TEXT and RECEIVE MAP). For each call, it passes appropriate message data between the legacy application and the mainframe component of the eBiz or Data Access Transaction, using the CICS Bridge facility. For more information about the CICS 3270 Bridge, refer to the IBM CICS External Interfaces Guide.
These are a set of related programs that can assist recovery in the event of a CICS region failure.
When you define an eBiz Transaction, you specify whether it is recoverable and, optionally, its associated recovery exit program. You can also specify a recovery program for the project as a whole, to be used if there is no recovery program for a particular eBiz Transaction.
This program is activated at the standard global exit points XRCINIT and XRCINPT. During a CICS warm or emergency restart, it copies records relating to recoverable eBiz Transactions from the CICS system log to an extrapartition transient data queue (TDQ) named MERJ, from the last keypoint up to the time of the failure.
If required, this program can be activated at CICS post-initialization time. It reads the MERJ queue and for each failed eBiz Transaction it activates the associated recovery exit program or, if none is specified, the project recovery program. MER0MERJ also collates data about each eBiz Transaction's in-doubt tasks (steps) in a set of temporary storage queues (TSQs). An eBiz Transaction is deemed to have failed if it does not have a termination record; an in-doubt task is one that is not known to have completed correctly.
This program, when activated through the MERV transaction ID, reads the TSQs set up by MER0MERJ and displays a list of all in-doubt tasks. From this list you can view the underlying 3270 terminal workflow and screen images. You can use this information to determine the best course of action to complete the eBiz Transaction.
MER0MERV can also be activated through the MERP transaction ID, in which case it presents a similar display for all tasks that had trace enabled.
For more information about turning on logging, and associating recovery programs with SOA Express projects and individual eBiz Transactions, refer to the Defining eBiz Transactions chapter in your User's Guide.
Also known simply as the mainframe MWI, the MQMW transaction provides the interface between WebSphere MQ and the eBiz or Data Access Transactions.
When using the CICS START bridge, MER0MQMW links via a CICS LINK to the eBiz or Data Access Transaction.
When using the Link3270 Bridge, MER0MQMW links via a CICS START of transaction MQST under the authority of the user ID passed up from the client. See also MER0MQST program below.
When using the Link3270 Bridge, program MER0MQMW executes a CICS START using transaction MQST, specifying the user ID entered in the client. This forces program MER0MQST to run under the specified user ID. Program MER0MQST then links via a CICS LINK to the eBiz or Data Access Transaction that runs under the specified user ID.
The MMTM transaction starts a separate instance of the mainframe MWI for each WebSphere MQ message received from the middle tier.
The MECI transaction provides the interface to handle the ECI calls between CICS Transaction Gateway and the eBiz or Data Access Transactions.
The SOA Express Server also includes the support modules listed in Table 5-1.
Module | Description |
---|---|
MER0ADSX | Works in conjunction with the Micro Focus 3270 Bridge Exit to run transactions under the IBM 3270 Bridge. |
MER0CONV | A dynamically called subroutine to convert from/to client platform data representation. |
MER0MERA | This module works in conjunction with the Micro Focus 3270 Bridge Exit to run transactions under the IBM 3270 bridge. |
MER0LINK | This module works in conjunction with the Micro Focus 3270 Bridge Exit to run transactions under the IBM Link3270 bridge. |
MER0MERB | This module provides the bridge component with a means of conversing with transactions on remote systems. |
MER0MERD | Responsible for export of Trace queue and Restart/Recovery queue. |
MER0MERE | Responsible for import of Trace queue and Restart/Recovery queue. |
MER0MERF | Responsible for Trace queue housekeeping. |
MER0MERH | Menu module. |
MER0MERL | Responsible for loading mapsets from remote systems. |
MER0MERQ | Provides formatted display of the trace information produced by the Middleware Interface, eBiz Transaction and Bridge Exit. |
MER0MERT | This transaction simulates CICS Terminal Control for the terminal that is its primary facility and drives transactions via the Bridge Facility. It serves as a development test harness and will also potentially provide trace data to the eBiz Transaction build process. It is a specialized eBiz Transaction that has a real 3270 user interface. |
To set up the mainframe environment you must:
Ensure the following are in place before continuing. For supported versions, see the chapter Third Party Software in your Readme:
Applications must run with Language Environment (LE) extensions.
Install one of the following to acquire the necessary CICS 3270 Bridge support, depending on the 3270 bridge software you are using:
Mainframe Access has a client component and three individually-installable server (mainframe) components, namely the Mainframe Access Standard, CICS and Endevor Servers. A Mainframe Access client is installed automatically with SOA Express. The Mainframe Access servers are included on the Host Connectivity CD supplied with Mainframe Express Enterprise Edition (for detailed installation instructions, refer to your Mainframe Access Installation and Usage Guide).
The Setup program prompts you to specify details about your mainframe. For an initial installation of Mainframe Access, the program generates a set of tailored JCL files and installation notes (text files). However, once the Mainframe Access Standard Server has been set up, the program can call upon Mainframe Access itself to upload and install additional or updated servers to the mainframe.
When you install Mainframe Express Enterprise Server, the SOA Express Server installation files are installed in the mfe-install-dir\SOA Express\mainframe folder. This folder contains two sets of installation files - one set for IBM’s original IBM 3270 bridge and one set for the Link3270 bridge. JCL and PROC files are also provided; these files are common to both the original 3270 bridge and Link3270 bridge. Table 5-2 shows a list of the files provided.
File | Description |
---|---|
emrglseq.bin | A binary image containing executable files for the 3270 bridge |
emrgdseq.bin | A binary image containing data files for the 3270 bridge |
cg_link3270_loadlib.bin | A binary image containing executable files for the Link3270 bridge |
cg_link3270_data.bin | A binary image containing data files for the Link3270 bridge |
proc.txt | A proc file that installs the SOA Express Server modules |
jcl.txt | A text file containing JCL used to invoke the proc file |
The proc.txt and jcl.txt files referenced above are used to install both the 3270 and Link3270 bridge runtime modules.
Note: If you are upgrading to SOA Express from Component Generator, you must replace your current Component Generator Server modules on the mainframe with the modules supplied with SOA Express.
To install or update the Server modules:
your.name.LOADLIB.X
A sequential fixed block file
organization PS
record format FB
record length 80
block size 3120
your.name.DATA.X
A sequential fixed block file
organization PS
record format FB
record length 80
block size 6160
put emrglseq.bin your.name.LOADLIB.X
put emrgdseq.bin your.name.DATA.X
put cg_link3270_loadlib.bin your.name.LOADLIB.X
put cg_link3270_data.bin your.name.DATA.X
Notes:
put jcl.txt your.pds(MERJCL) put proc.txt your.pds(CUSINST)
//MFICPI JOB (9999,9999),'DEFINE ', // MSGCLASS=X,CLASS=A,NOTIFY=&SYSUID;, // MSGLEVEL=(1,1) //MLIB JCLLIB ORDER=your.pds //******************************************************* //STEP01 EXEC CUSINST, // PREFIX='your.name', // CICS='your.cics.LOADLIB', // CSD='CICSTS13.DFHCSD5', // CSDUPLIB='CICSTS13.CICS.SDFHLOAD' //STEP30.SYSTSIN DD * RECEIVE INDDNAME(INFILE) DSN('your.name.LOADLIB') /* //STEP50.SYSIN DD * COPYOPER COPY OUTDD=OUT1,INDD=((IN1,R)) //
Contains all the CICS DEFINE commands.
Contains the command to delete the group MFCMPGEN.
Supplied source for the Micro Focus WebSphere MQ Message Trigger Monitor (MER0MMTM).
If you are using WebSphere MQ, you must install the following items of WebSphere MQ middleware at the mainframe:
For installation and customization instructions, refer to your IBM WebSphere MQ for z/OS Program Directory and IBM WebSphere MQ for z/OS System Management Guide.
After installing WebSphere MQ, define WebSphere MQ objects as described in the chapter WebSphere MQ Middleware.
To set up the Restart and Recovery feature for your eBiz Transaction(s):
Allocate a file for the MERJ extrapartition transient data queue with the following properties:
Add a MER0MERJ DD statement for the file that you allocated in step 1 to your CICS startup job. For example:
//MER0MERJ DD DISP=SHR,DSN=MFHOST.CMPGEN.MERJ
(In this example the file is called MFHOST.CMPGEN.MERJ but you can use any name that you like.)
Add a pre-initialization PLT statement for MER0XPLT (prior to the PLT statement for DFHDELIM):
DFHPLT TYPE=ENTRY,PROGRAM=MER0XPLT
Copyright © 2007 Micro Focus (IP) Ltd. All rights reserved.