BEA Home | Events | Solutions | Partners | Products | Services | Download | Developer Center | WebSUPPORT
JAM Documentation | JAM Configuration and Administration Guide | Previous Topic | Next Topic | Contents | Index

Preparing Mainframe Configurations for CRM Requirements

The Communications Resource Manager (CRM) runs as a separate native process that provides an emulation allowing Customer Information Control System/Enterprise System Architecture (CICS/ESA) and Information Management System (IMS) protocols to flow into and out of the Java environment. After you install the WebLogic Java Adapter for Mainframe (JAM) product, you must set up your mainframe configurations to allow the CRM to access your CICS or IMS systems.

If the CRM runs on the mainframe, it uses the native SNA networking product, Virtual Telecommunications Access Method (VTAM), to establish its SNA connectivity to the CICS or IMS application environments. If the CRM runs on a Windows NT or UNIX platform, a third-party SNA stack must also be installed on this platform and configured to establish SNA connections with the CRM and target mainframe.

The topics in this section cover mainframe configuration requirements for the CRM.

Action List

Before you prepare mainframe configurations for CRM requirements, see the following action list and refer to the appropriate information sources.

| Your action... | Refer to...
--- | --- | ---
1 | Complete all prerequisite tasks. | Prerequisites
2 | Learn about the CRM. | How the CRM Works
3 | Learn about configurations for Windows NT or UNIX platforms. | Configuring the CRM for Windows NT or UNIX Platforms
4 | Learn about configurations for OS/390 platforms. | Configuring the CRM for OS/390 Platforms
5 | Learn about configurations for the CICS/ESA LU. | Configuring the CICS/ESA LU
6 | Prepare for the next step. | What Do I Do Next? and the next section, Defining the JAM Gateway Configuration

Prerequisites

Before you prepare mainframe configurations for CRM requirements, you should complete the following tasks.

| Your action... | Refer to...
--- | --- | ---
1 | Verify that system requirements have been met. | BEA WebLogic Java Adapter for Mainframe Introduction and Release Notes
2 | Determine which configuration your system requires and install the JAM product as appropriate for your configuration. | BEA WebLogic Java Adapter for Mainframe Installation Guide

How the CRM Works

The CRM is the component of the BEA WebLogic Java Adapter for Mainframe (JAM) that manages communications resources. The CRM coordinates the flow of data between Java applications running on a WebLogic Server platform and applications running on a mainframe. The mainframe applications may use CICS/ESA with Distributed Program Link (DPL) or IMS with implicit Advanced Program-to-Program Communications (APPC).

The CRM uses both SNA and TCP communication protocols. TCP protocols always flow between the JAM gateway and CRM. SNA protocols always flow from the CRM to the mainframe and from either an SNA stack or VTAM on the mainframe to the CRM depending upon the configuration option.

The CRM may be located on the same machine as the JAM gateway or distributed on another UNIX, Windows NT, or mainframe operating system. For a complete list of operating systems, refer to the BEA WebLogic Java Adapter for Mainframe Release Notes. If the CRM is not running on a mainframe, it must run on the same platform as the SNA stack.

The following requirements should be considered for establishing a VTAM Configuration:

- If you are running your CRM on a mainframe, your mainframe must have a local VTAM configuration that communicates with the CRM.

- If your JAM system is used in a VTAM environment, make sure the host configuration supports VTAM.

- If you are using a third-party SNA stack, you must configure VTAM to communicate with the SNA stack.

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 JAM local domain.

Configuring the CRM for Windows NT or UNIX Platforms

A basic understanding of the mainframe configuration requirements provides a context for understanding the CRM functions and configuration requirements. The following sections discuss the various configuration considerations and give examples of those configurations.

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

Third-Party Stack Configuration

Third-party stack configurations may be set up using stack-specific configuration utilities or by manually creating a configuration file with any text editor. Listing 1-1 shows an example of an SNA node configuration file. The configuration file is divided into sections for various components of the configuration. Each section defines a component using parameters (or keywords) and values. Some of these keywords and values will affect how your JAM configuration is defined.

Listing 1-1 SNA Node Configuration File

>     [define_node_config_file]
>     major_version = 5
>     minor_version = 1
>     update_release = 1
>     revision_level = 57

>     [define_node]
>     cp_alias = dqasun1
>     description = ""
>     fqcp_name = BEALAN.DQASUN1
>     node_type = LEN_NODE
>     mode_to_cos_map_supp = YES
>     mds_supported = YES
>     node_id = <bea12899>
>     max_locates = 1500
>     dir_cache_size = 255
>     max_dir_entries = 0
>     locate_timeout = 0
>     reg_with_nn = YES
>     reg_with_cds = YES
>     mds_send_alert_q_size = 100
>     cos_cache_size = 24
>     tree_cache_size = 40
>     tree_cache_use_limit = 40
>     max_tdm_nodes = 0
>     max_tdm_tgs = 0
>     max_isr_sessions = 1000
>     isr_sessions_upper_threshold = 900
>     isr_sessions_lower_threshold = 800
>     isr_max_ru_size = 16384
>     isr_rcv_pac_window = 8
>     store_endpt_rscvs = NO
>     store_isr_rscvs = NO
>     store_dlur_rscvs = NO
>     cos_table_version = VERSION_0_COS_TABLES
>     send_term_self = NO
>     disable_branch_awareness = NO
>     cplu_syncpt_support = NO
>     cplu_attributes = NONE
>     dlur_support = NO
>     pu_conc_support = YES
>     nn_rar = 128
>     max_ls_exception_events = 0
>     ptf_flags = NONE

>     [define_ethernet_dlc]
>     dlc_name = ETHER0
>     description = ""
>     neg_ls_supp = YES
>     initially_active = NO
>     adapter_number = 0
>     lan_type = 802_3_DIX

>     [define_ethernet_port]
>     port_name = ETSAP0
>     description = ""
>     dlc_name = ETHER0
>     port_type = PORT_SATF
>     port_number = 0
>     max_rcv_btu_size = 1033
>     tot_link_act_lim = 64
>     inb_link_act_lim = 0
>     out_link_act_lim = 0
>     ls_role = LS_NEG
>     implicit_dspu_services = NONE
>     implicit_dspu_template = ""
>     implicit_ls_limit = 0
>     act_xid_exchange_limit = 9
>     nonact_xid_exchange_limit = 5
>     ls_xmit_rcv_cap = LS_TWS
>     max_ifrm_rcvd = 7
>     target_pacing_count = 7
>     max_send_btu_size = 1033
>     mac_address = <080020a6808a>
>     lsap_address = 0x04
>     implicit_cp_cp_sess_support = NO
>     implicit_limited_resource = NO
>     implicit_deact_timer = 30
>     implicit_hpr_support = NO
>     implicit_link_lvl_error = NO
>     implicit_uplink_to_en = NO
>     effect_cap = 3993600
>     connect_cost = 0
>     byte_cost = 0
>     security = SEC_NONSECURE
>     prop_delay = PROP_DELAY_LAN
>     user_def_parm_1 = 128
>     user_def_parm_2 = 128
>     user_def_parm_3 = 128
>     initially_active = YES
>     window_inc_threshold = 1
>     test_timeout = 10
>     test_timer_retry = 5
>     xid_timer = 10
>     xid_timer_retry = 5
>     ack_timeout = 5000
>     p_bit_timeout = 5000
>     t2_timeout = 100
>     rej_timeout = 10
>     busy_state_timeout = 30
>     idle_timeout = 30
>     max_retry = 3

>     [define_ethernet_ls]
>     ls_name = DV10QSN1
>     description = ""
>     port_name = ETSAP0
>     adj_cp_name = P390.DALVS10
>     adj_cp_type = END_NODE
>     mac_address = <0200bea07002>
>     lsap_address = 0x08
>     auto_act_supp = NO
>     tg_number = 0
>     limited_resource = NO
>     solicit_sscp_sessions = YES
>     pu_name = DV10QSN1
>     disable_remote_act = NO
>     default_nn_server = NO
>     dspu_services = NONE
>     dspu_name = <0000000000000000>
>     dlus_name = <0000000000000000000000000000000000>
>     bkup_dlus_name = <0000000000000000000000000000000000>
>     hpr_supported = NO
>     hpr_link_lvl_error = NO
>     link_deact_timer = 30
>     use_default_tg_chars = YES
>     ls_attributes = SNA
>     adj_node_id = <00000000>
>     local_node_id = <00000000>
>     cp_cp_sess_support = NO
>     effect_cap = 3993600
>     connect_cost = 0
>     byte_cost = 0
>     security = SEC_NONSECURE
>     prop_delay = PROP_DELAY_LAN
>     user_def_parm_1 = 128
>     user_def_parm

>     VTAM Cross Platform Definitions

>     The examples of cross platform definitions discussed in the following sections allow the VTAM network to communicate with your stack using the SNA protocol.

>     XCA Major Node Defines the LAN Adapter for SYS1

>     This definition is set up for use with an emulated IBM 3172 Interconnect Controller  for connecting an APPN network node to another APPN node. Note that the definition is for an Ethernet LAN, and the SAPADDR specified must be the same as the LSap specified for the local link station.

>     Listing 1-2	    XCA Major Node

>     XETH2LP1 VBUILD TYPE=XCA ** EXTERNAL COMMUNICATION ADAPT**
>     PORTE2   PORT  ADAPNO=1,      ** 3172 RELATIVE ADAPTER NUMBER**
>                    CUADDR=E22,    ** CHANNEL UNIT ADDRESS        **
>                    MEDIUM=CSMACD, ** LAN TYPE=ETHERNET           **
>                    SAPADDR=8,     ** SERVICE ACCESS POINT ADDRESS**
>                    TIMER=120      ** CHANNEL ACTIVATE RESP TIME  **
>     *
>     G1ETH2   GROUP DIAL=YES,      ** YES required for putype 2   **
>                    DYNPU=YES,
>                    CALL=INOUT,
>                    ANSWER=ON,
>                    ISTATUS=ACTIVE
>     LETH20   LINE
>     PETH20   PU
>     LETHE3   LINE
>     PETHE3   PU
>     LETHF3   LINE
>     PETHF3   PU

>     Switched Network (SWNET) Definitions

>     VTAM Switched Major Node (SWNET) definitions define and link together physical units (PU) and logical units (LU). Each workstation connected to a network must be represented on the network as a PU and each PU can have one or more LUs. The VTAM SWNET definition defines how the PUs and LUs communicate with a server.

>     The two switched network definition examples in this section (Listing 1-3 and Listing 1-4) specify the VTAM PU, representing the local link stations that expect to connect with the host machine. The IDBLK and IDNUM definitions are provided to support 3270 traffic and must be unique, as well as match the values specified in the local link definition.

>     Listing 1-3	    SWNET Major Node

>     SWNETHHPVBUILDTYPE=SWNET,MAXNO=3,MAXGRP=3
>     P390HP10   PU  ADDR=02,
>                    IDBLK=05F,
>                    IDNUM=FFFFF,
>                    PUTYPE=2,
>                    NETID=BEALAN,
>                    CPNAME=DALHP10,
>                    MAXPATH=3,
>                    DWACT=YES,
>                    CONNTYPE=APPN,
>                    CPCP=YES,
>                    DYNLU=YES
>     * -------------------------------------------------
>     * SNA SAP & HP10 MAC ADDRESS BIT REVERSED FOR TRFMT
>     * -------------------------------------------------
>     PATHHP     PATH DIALNO=00041000900C24EE,
>                    GRPNM=G1ETH2
>     LUHP10A LU  LOCADDR=0
>     LUHP10B LU  LOCADDR=0
>     LUHP10C LU  LOCADDR=0

>     Listing 1-4	    SWNET Major Node

>     SWNETH2VBUILDTYPE=SWNET,MAXNO=3,MAXGRP=3
>     P390ETH2   PU  ADDR=04,
>                    IDBLK=019,
>                    IDNUM=10092,
>                    PUTYPE=2,
>                    NETID=BEALAN,
>                    CPNAME=SUN2,
>                    MAXPATH=3,
>                    DWACT=YES,
>                    CONNTYPE=APPN,
>                    CPCP=YES,
>                    DYNLU=YES
>     * -------------------------------------------------
>     * SNA SAP & SUN2 MAC ADDRESS BIT REVERSED FOR TRFMT
>     * -------------------------------------------------
>     PATH01     PATH DIALNO=00081000043EE20A,
>                    GRPNM=G1ETH2
>     LUSUN2A LU  LOCADDR=0
>     LUSUN2B LU  LOCADDR=0
>     LUSUN2C LU  LOCADDR=0

>     Configuring the CRM for OS/390 Platforms

>     VTAM must be configured to allow the CRM to communicate with CICS or IMS using the SNA protocol.

>     The APPLID definition shown in Listing 1-5 defines the local stack configuration to run under OS/390 using VTAM.

>     Listing 1-5	    APPLID Definition (OS/390)

>     BEASNA VBUILD TYPE=APPL
>     BEAAPPL1 APPL ACBNAME=BEAAPPL1,
>                   AUTH=(ACQ,PASS),
>                   APPC=YES,
>                   SYNCLVL=CONFIRM,
>                   PARSESS=YES

>     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 establish the configuration, 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, 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 a JAM connection definition file:

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

>     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 a JAM session definition:

>     DEFINE SESSION(BEATEST)       GROUP(BEACONN)
>            CONNECTION(BEA)
>            DE(JAM 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 number of remote sessions should equal the SESSNBR.

Installing Resource Definitions

To install the resource definitions, put them on the host in a separate group. Use the CEDA INSTALL command.

For example:

>     CEDA INSTALL GROUP(BEACONN)

Viewing Connection and Session Status

After you have installed the resource 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

What Do I Do Next?

After you prepare your mainframe configurations for the CRM, you are ready to create your JAM configuration file. Refer to Defining the JAM Gateway Configuration for more information about creating the configuration file.

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