Creating a Logical Unit for the CRM Gateway

In this section:

The CRM gateway uses an LUTYPE 6.2 logical unit to communicate with backend systems running on the mainframe. Each back-end system must have its own logical unit, and sessions must be defined to allow the CRM to allocate sessions between its logical unit and the logical unit of the mainframe system. Each peer must be configured ahead of time to connect to the logical unit of its peer.

In this step, your VTAM administrator creates a logical unit within VTAM for the CRM. The logical unit defines the CRM to the SNA network. This logical unit is a new CRM parameter (SNA_LOCALLU) in the CRM ENV file.


Top of page

x
Parameters for Establishing the CRM Logical Unit

The VTAM application program major node (VTAM APPLID) is also the CRM logical unit. You define the APPLID to VTAM and activate it in the VTAM network.

This section provides the parameters that the VTAM administrator needs to create a logical unit for the CRM gateway.

The following syntax shows a sample VTAM APPLID definition node.

IWY  VBUILD TYPE=APPL           APPLICATION MAJOR NODE
IWYAPPL1 APPL    ACBNAME=IWYAPPL1,  ACBNAME FOR APPC
                 APPC=YES,
                 SYNCLVL=SYNCPT,
                 PARSESS=YES

The following parameters represent the minimum requirements for defining the logical unit.

Application Program Major Node Name

This tag identifies the node to the network.

TYPE=APPL

Major node should be an Application Major Node type.

ACBNAME=LU Name

Logical unit name. This can be identical to the Application Major Node name. This is the logical unit name used in the CRM configuration.

APPC=YES

Defines this as an APPC logical unit.

SYNCLVL=[CONFIRM | SYNCPT]

Determines level of transactional support. CONFIRM supports non-transactional DPL and APPC service requests only, while SYNCPT will in addition, support transactional service requests.

PARSESS=YES

Allows multiple sessions between session partners.

SRBEXIT=NO

The CRM logical unit does not support the service request block (SRB) exit routines. This parameter must be set to NO, which is the default value if the parameter is not specified.


Top of page

x
Connecting the CRM Gateway to Back-End Systems on the Mainframe

To connect the CRM gateway to your mainframe applications, you may need to connect to different types of regions that run on the mainframe. Instances of IMS and CICS systems are usually referred to as an IMS region or a CICS region respectively.

This section provides information on the following subjects:


iWay Software