Corporate Info | News | Solutions | Products | Partners | Services | Events | Download | How To Buy
eLink Adapter for Mainframe Doc Home | CRM Administration Guide | Previous Topic | Next Topic | Contents | Index

Understanding the Communications Resource Manager

This section discusses the following topics:

- About the Communications Resource Manager

- System Configuration

- Remote Host Domain Configuration

  Note: All references to ATMI files, functions, and documentation apply to Tuxedo, eLink Platform, and WebLogic Enterprise files, functions, and documentation.

About the Communications Resource Manager

The Communications Resource Manager (CRM) is the component of the BEA eLink Adapter for Mainframe (eAM) that manages communications resources. The CRM coordinates the flow of data between applications running on an ATMI platform and applications running on a mainframe. The mainframe applications may use the following protocols:

- Customer Information Control System/Enterprise System Architecture (CICS/ESA)

  - Distributed Transaction Processing (DTP)

  - Distributed Program Link (DPL)

- Information Management System (IMS)

The CRM runs as a separate native process providing emulation that allows CICS/ESA and IMS protocols to flow into and out of the ATMI environment.

The CRM must run on the same platform as the SNA stack, but it may run on a different platform from the ATMI system and the eAM gateway (GWSNAX). The eAM gateway provides the configuration for the CRM. If the eAM gateway is to be brought up on a platform other than the one the CRM is on, then the CRM should already be started and monitoring the address specified in the eAM gateway configuration.

System Configuration

The CRM system may be configured as either a local configuration or a distributed configuration running on UNIX, Windows NT, or a mainframe operating system. For a complete list of operating systems, refer to the BEA eLink Adapter for Mainframe Release Notes. If the CRM is not run on a mainframe, it must run on the same platform as the SNA stack. If the eAM gateway is to be brought up on a platform other than the one the CRM is on, then the CRM should already be started and monitoring the address specified in the eAM gateway configuration.

Local Configuration

The local configuration, illustrated in Figure 1-1, combines the applications, eAM gateway, ATMI platform, and the CRM with the stack (PU2.1 server) on the same UNIX or Windows NT platform. It employs the IBM proprietary SNA protocol for communication with the mainframe via the stack.

Figure 1-1 eAM Local Configuration

Distributed Configurations

One type of distributed configuration separates the applications and the eAM gateway on a UNIX or Windows NT platform from the CRM by installing the CRM on the IBM OS/390 Mainframe. See Figure 1-2. This configuration eliminates the need for a third-party stack on the UNIX or NT machine. Note that this configuration requires a one-to-one relationship between the local eAM gateway and the remote CRM.

Figure 1-2 eAM Distributed Configuration

Another type of distributed configuration separates the applications and the eAM gateway from the CRM on different UNIX or Windows NT platforms. See Figure 1-3. This configuration employs Transmission Control Protocol/Internet Protocol (TCP/IP) connectivity between the applications platform and the CRM platforms, as well as the SNA connectivity to the mainframe environment(s). It provides the flexibility to deploy the ATMI platform separately from the CRM with installations that require the ATMI platform on a platform other than the one on which the SNA stack is running. Note that this configuration requires a one-to-one relationship between the local eAM gateway and the remote CRM.

Figure 1-3 Alternate eAM Distributed Configuration

Remote Host Domain Configuration

A basic understanding of the mainframe configuration requirements provides a context for understanding the CRM functions and configuration requirements.

Note: Consult with your local mainframe system administrator for specific information about your system. Any samples provided illustrate a starting point for configuring your system and do not represent all possibilities. The samples represent one way a mainframe can be configured to work in an Advanced Peer-to-Peer Networking (APPN) Local Area Network (LAN) environment.

Ensure that the CICS/ESA remote domain is prepared to conduct operations with the BEA local domain by:

- Establishing the VTAM Configuration

- Configuring the CICS/ESA LU

  - Creating Connections at the Remote Host

  - Defining the Session at the Remote Host

- Completing Cross-Platform Definitions

Establishing the VTAM Configuration

If your eAM system is used in a Virtual Telecommunications Access Method (VTAM) environment, make sure the host configuration supports it. Refer to "Sample Configurations" for examples based on the requirements for the eAM.

Configuring the CICS/ESA LU

Before you can connect the CRM to the remote stack, the CICS/ESA LU (Logical Unit) configuration must be established. To accomplish this task, you must create connection definitions, create session definitions, and install resource definitions.

Creating Connections at the Remote Host

If a remote connection definition file is not already in place, you must work with the mainframe support personnel to create one. When placed on the remote host, the definition provides a connection with the local domain. Note the following example of an eAM connection definition file:

>     DEFINE CONNECTION(BEA)      GROUP(BEACONN)
>            DE(eAM EXAMPLE RDO CONNECTION)
>            ACCESSMETHOD(VTAM)   PROTOCOL(APPC)
>            NETNAME(**VTAM NETWORK NAME OF REMOTE SYSTEM**)
>            ATTACHSEC(LOCAL)     AUTOCONNECT(NO)

To install the sample connection definition, put it on the host in a separate group. Use the CEDA INSTALL command.

For example:

>     CEDA INSTALL GROUP(BEACONN)

Defining the Session at the Remote Host

If a session definition is not already in place, work with the mainframe support personnel to create one. When placed on the remote host, the session definition defines the logical links by which the local domain communicates with the remote host. Note the following example of an eAM session definition:

>     DEFINE SESSION(BEATEST)       GROUP(BEACONN)
>            CONNECTION(BEA)
>            DE(eAM EXAMPLE RDO SESSION)
>            PROTOCOL(APPC)         AUTOCONNECT(YES)
>            MODENAME(**MODE**)     MAXIMUM(**SESSNBR**,**WINNER**)

The arguments and options in this example are defined in the following way:

AUTOCONNECT

  Indicates how the activation of the session is negotiated.

  YES

  Enables the CICS/ESA host to negotiate its own winner sessions when a conversation is allocated.

  MODENAME

  Indicates either a CICS/ESA-supplied mode name, such as SMSNA100, or your own defined mode name. If another set of session definitions exists for the BEA connection, this mode name must be unique among all sets defined to the connection. The mode name corresponds to the VTAM LOGMODE name.

  MAXIMUM

  Defines the total number of sessions in the set and the total number of winner sessions. The total number of winner sessions must include those for the host and the remote stack. The WINNER number plus the remote WINNER number should equal the SESSNBR.

  Viewing Connection and Session Status

  After you have installed group definitions, you can view the status of connections and sessions using the following CICS/ESA system commands:

  >     CEMT I CONN(BEA)            **view the status of the connection
  >     CEMT I NET(**Netname**)     **View the status of the sessions
  >     CEMT I MODENAME(**MODE**)   **View the status of the mode

  Completing Cross-Platform Definitions

  Consult with your CICS/ESA remote domain administrator to obtain key parameters in the VTAM definition that must be included in the SNA stack configuration, as well as in other configuration files in the eAM local domain.

  VTAM Cross-Platform Definitions

  Before installing eAM software, please review Table 1-1 for a summary of cross-platform definitions. Consult with the VTAM system administrator to obtain the value indicated in the Name column and make the corresponding entries shown in the Needed In column.

  DCL-based stacks referred to in Table 1-1 include the following stacks:

  - HP SNAplus2

  - Solaris SNAP-1X

  - IBM Comm Server

    .

    ####

    Table 1-1 Summary of Cross-Platform Definitions

    Name | Originates In | Needed In
    --- | --- | ---
    SNA Network ID (e.g. SNANET1) and VTAM Host ID (e.g. VTAMHOST) | VTAM configuration | SunLink SNA Stack Configuration: Example: CP NQ_CP_NAME=SNANET1.SPARC1 DLC RMTNQ_CP_NAME=SNANET1.VTAMHOST LU NQ_LU_NAME=SNANET1.L0P0024A PTNR_LU NQ_LU_NAME=SNANET1.CICSSYN DCL-based Stack Configuration: Example: fqcp_name=SNANET1.SPARC1 adj_cp_name=SNANET1.VTAMHOST fqplu_name=SNANET1.CICSSYN
    Mode Name (e.g. SNA62) | VTAM-MODEENT definition | CICS Sessions Definition: Example: MODENAME(SNA62) SunLink SNA Stack Configuration: Example: MODE NAME=SNA62 DCL-based Stack Configuration: Example: mode_name=SNA62 GWSNAX Configuration: Example: *DM_SNA_LINKS MODENAME="SNA62"
    Control Point Name CPNAME (e.g. SPARC1) | VTAM-PU definition | SunLink SNA Stack Configuration: Example: CP NAME=SPARC1 CP NQ_CP_NAME=SNANET1.SPARC1 DCL-based Stack Configuration: Example: fqcp_name=SNANET1.SPARC cd_alias=SPARC1
    Local LU Name (e.g. L0F0024A) | VTAM-LU definition | CICS CONNECTION definition: Example: NETNAME(L0F0024A) SunLink SNA Stack Configuration: Example: LU NAME=L0F0024A LU NQ_LU_NAME=SNANET1.L0F0024A PTNR_LU LOC_LU_NAME=L0F0024A TP LOC_LU_NAME=L0F0024A DCL-based Stack Configuration: Example: lu_name=L0F0024A lu_alias=L0F0024A GWSNAX Configuration: Example: *DM_SNA_STACKS LOCALLU="L0F0024A"
    CICS LU Name (e.g. CICSSYN) | VTAM-LU definition | SunLink SNA Stack Configuration: Example: PTNR_LU NAME=CICSSYN PTNR_LU NQ_LU_NAME=SNANET1.CICSSYN MODE PTNR_LU_NAME=CICSSYN DCL-based Stack Configuration: Example: fqplu_name=SNANET1.CICSSYN plu_alias=CICSSYN GWSNAX Configuration: Example: *DM_SNA_LINKS RLUNAME="CICSSYN"
    Terminal Identifier (e.g. 05DF0024) | VTAM (IDNUM+IDBLK) | SunLink SNA Stack Configuration: Example: DLC TERM << ALIGN=CHAR DCL-based Stack Configuration: Example: node_id=<05000002>
    Local Network Device (e.g. /dev/tr) | UNIX Configuration | SunLink SNA Stack Configuration: Example: TRLINE DEVICE='/dev/tr' or SDLCLINE DEVICE='/dev/dcp1'
    Local MAC Address (token ring only) | Token ring address of Host | SunLink SNA Stack Configuration: Example: TRLINE Source_Address=X'080020117d7a'
    Remote MAC Address (token ring only) | Token ring address of local machine | SunLink SNA Stack Configuration: Example: DLC RMTMACADDR=X'40000101000' DCL-based Stack Configuration: Example: mac_address=<400031720001>
    LAN Speed (e.g. 4MBs) | Speed of token ring network | SunLink SNA Stack Configuration: Example: TRLINE LAN_rate=RING_4MBS
    SDLC parameters (line protocol) | VTAM-line definition | SunLink SNA Stack Configuration: Example: SDLCLINE DUPLEX=half LINE=switched NRZI=no PAUSE=1 SPEED=4800
    Partner Definition (e.g. TUXPART1) | CICS/ESA | Mainframe Client Application: (for example, COBOL with embedded CPI-C to route CICS to appropriate LU for BEA Connect SNA) COBOL Example: MOVE `TUXPART1' TO SYM-DEST-NAME CALL `CMINIT' USING CONVERSATION-ID SYM-DEST-NAME, CM_RETCODE END-CALL
    Set LU definition so maximum sync-level allowed corresponds to DMCONFIG file entry: *DM_SNA_LINKS MAXSYNCLVL | Stacks | SunLink SNA Stack Configuration: Example: SYNC_LVL=SYNCPT DCL-based Stack Configuration: Example: [define local_lu] Syncpt._Support=NO
    Map all incoming conversations to eAM gateway (make sure TPs have all privileges available, e.g. CNOS, syncpoint if licensed, service conversations, etc.). | Stacks | SunLink SNA Stack Configuration: Example: TP_HEXNAME=x`2a' DCL-based Stack Configuration: Example: Sna_tps <404040...hex representation of 64 EBCDIC spaces...404040> TYPE=QUEUED TIMEOUT=-1 USERID=authorized_user_here GROUP=authroized_group_here LUALIAS=lu_name_here
    CICS Transaction IDs (e.g. TOUP) | CICS/ESA | GWSNAX Configuration: Example: *DM_REMOTE_SERVICES

  OS/390 UNIX Platform Definitions

  Before installing eAM software, please review Table 1-2 for a summary of SNA definitions when CRM runs on an OS/390 UNIX platform. Consult with the system administrator to obtain the value indicated in the Name column and make the corresponding entries shown in the Needed In column.

  .

  ####

  Table 1-2 Summary of OS/390 SNA Definitions

  Name | Originates In | Needed In
  --- | --- | ---
  Local LU Name (e.g. BEAAPPL1) | VTAM-LU definition | CICS CONNECTION definition: Example: NETNAME(BEAAPPL1) VTAM Configuration: Example: BEASNA VBUILD TYPE=APPL BEAAPPL1 APPL ACB=BEAAPPL1, APPC=YES, PARSESS=YES GWSNAX Configuration: Example: *DM_SNA_STACKS LOCALLU="BEAAPPL1"
  Mode Name (e.g. SNA62) | VTAM-MODEENT definition | CICS Sessions Definition: Example: MODENAME(SNA62) GWSNAX Configuration: Example: *DM_SNA_LINKS MODENAME="SNA62" VTAM Configuration (not required): Example: MODEENT=SNA62
  CICS LU Name (e.g. CICSSYN) | VTAM-LU definition | GWSNAX Configuration: Example: *DM_SNA_LINKS RLUNAME="CICSSYN"
  Maximum sync-level allowed | Stacks | VTAM Configuration: Example: SYNCLVL=SYNCPT GWSNAX Configuration: Example: *DM_SNA_LINKS MAXSYSCLVL=2
  CICS Transaction IDs (e.g. TOUP) | CICS/ESA | GWSNAX Configuration: Example: *DM_REMOTE_SERVICES

  Microsoft SNA Cross-Platform Definitions

  Be sure to communicate with the administrator of the CICS/ESA remote domain to obtain key parameters in the VTAM definition that must be included in the Microsoft SNA Server configuration, as well as in other configuration files in the eAM local domain.

  Before installing eAM software, please examine the following general procedure for configuring the Microsoft SNA Server. Use the Microsoft SNA Server Manager. Sample values are shown in parenthesis. Consult with the VTAM system administrator to obtain the proper values.

  1. Start Microsoft SNA Server Manager from Start on the Task Bar.

  2. When a server is automatically created (MVSNT1), note the configuration values displayed in the Server Properties window:

  Server: MVSNT1

  Subdomain: MVSNT1

  Server Role: Primary

  Network Transports: TCP/IP

  - Under Link Services, define a link service (SNADLC1):

    In the Link Service Properties, define DLC 802.2 Link Service Configuration:

  Title: DLC 802.2 Link Service #1

  Adapter: <your ethernet adapter>

  Local Service Access Point (SAP): 0x4

  Use Fixed SAP

  - Under SNA Service Connections, define an 802.2 connection (MVSNT1):

    In the MVSNT1 Properties, define:

    General

  Name: MVSNT1

  Link Service: SnaDlc1

  Remote End: Peer System

  Allowed Directions: Both Directions

  Activation: On Server Startup

  Supports Dynamic Remote APPC LU Definition

  Address

  Remote Network Address: <host MAC address>

  Remote SAP Address: <host SAP address>

  System Identification

  Local Node Name

  Network Name: <mynetwork>

  Control Point Name: MVSNT1

  Local Node ID: <xxx nnnn>XID Type: Format 3

  Remote Node Name

  Network Name: <hostnetwork>

  Control Point Name: <vtamcpname>

  Remote Node ID: Peer DLC Role: Negotiable

  Compression Type: None

  802.2 DLC

  Take Defaults

  - Under Local APPC LUs (SNA Service: Connections: Insert: APPC: Local LU), define a local LU (LUNT1A) in the LUNT1A Properties:

    General

  LU Alias: LUNT1A

  Network Name: <mynetwork>

  LU Name: LUNT1A

  Advanced

  Take Defaults

  - Under Remote APPC LUs, define a remote LU (CICS1) in the CICS1 Properties:

    General

  Connection: MVSNT1

  LU Alias: CICS1

  Network Name: <hostnetwork>

  LU Name: CICS1

  Uninterpreted Name: CICS1

  Options

  Take Defaults

  - Under APPC Modes, define a mode (SMSNA100) in the SMSNA100 Properties:

    General

  Mode Name: SMSNA100

  Limits

  Parallel Session Limit: <max sessions>

  Minimum Winner Contention Limit: <min winners>

  Partner Min Winner Contention Limit: <max sessions - min winners>

  Automatic Activation Limit: 0

  Characteristics

  Take Defaults

  Partners

  Add partnership for Server Name: MVSNT1 between Local LU: LUNT1A and Partner LU: CICS1

  Compression

  Take Defaults

  Copyright © 2001 BEA Systems, Inc. All rights reserved. Required browser: Netscape 4.0 or higher, or Microsoft Internet Explorer 4.0 or higher.