Micro Focus Enterprise Developer 3.0 for Visual Studio 2013 > Deployment > Mainframe Support for Deployed Applications > MSS Configuration and Administration > CICS Support > Setting Up Communications with Mainframe CICS Regions > Setting Up Communications from Host to Local CICS System > Defining Transaction Programs > Defining Transaction Programs using a HIS connection

Defining Transaction Programs using a HIS connection

Note: The information in this section relates specifically to Windows systems using Microsoft BizTalk Host Integration Server (HIS). For other Advanced Program-to-Program Communications (APPC) software, the command names used will vary, but the overall details added will be the same.

For inbound communications, the HIS SNA Server requires registry entries to be created for each CICS transaction on the local server or a client. These entries are used by the HIS SNA Server to start the CICS program dfhgatch.exe, which routes the request to the correct CICS region and transaction.

The Micro Focus CICS registry entries for the transaction programs can be found in the following location:

/HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/SnaBase
   /Parameters/TP's/tpname/Parameters

To add a new or overwrite an existing registry entry for an inbound transaction program for HIS:

Start an Enterprise Server command prompt.
From the prompt, run tpsetup.exe. The TP Setup dialog box is displayed.
tpsetup.exe is supplied with the HIS software.
Click Add to display the Add New TP dialog box.
In the TP Name field, enter the transaction name. This is used to identify the transaction program to the HIS SNA Server. This TP name should correspond to the transaction that the host system attempts to run on the local CICS region (for example, CRTE).
In the Command line field, specify an entry to run casatch.exe. This starts the transaction on the local CICS region. The entry will depend on the bit-version of your Enterprise Server region.
CAUTION:

Be sure that you specify the path to the correct casatch.exe bit-version corresponding to the region (not the installed Enterprise Server software) that you are using.

For example, the default locations for Enterprise Developer are:
- For 32-bit systems: %ProgramFiles(x86)%\Micro Focus\Enterprise Developer\bin\base\bin\casatch.exe
- For 64-bit systems: %ProgramFiles(x86)%\Micro Focus\Enterprise Developer\bin64\base\bin\WIN64\casatch.exet
In the Parameters field, specify the region, transaction and parameter details.
This will generally be in the format: /RREGIONNAME /TTPNAME where:
- REGIONNAME is the name of your region, for example MSSDEMO
- TPNAME is the name of your transaction program, for example CRTE
Specify the name of the Local LU Alias as defined to the HIS SNA server for the inbound request. This is the independent LU that you are going to use for your PU as defined to VTAM. The example value is: MCOLU021
Click OK

For information on adding and editing transaction programs, see the Host Integration Server 2006 Help.

Note:

tpstart.exe reads the registry only when it is started. So, if you have updated the registry by adding or changing a TP, you need to stop and restart tpstart.exe to pick up any updates.
casatch.exe fails unless it is run under the same userid, or a userid with identical privileges, as the local Enterprise Server region. Therefore, either the Enterprise Server region must be started from a normal Enterprise Developer command prompt (using the casstart command), or MFDS must be started from a normal Enterprise Developer command prompt, using the mfds command. That is, as opposed to running MFDS as a service.
If MFDS is running as a user process, started from the command prompt, then you can use either casstart or the user interface.

Send feedback about this topic