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

Understanding the SNACRM

This chapter discusses the following topics:

- About the SNACRM

- Remote Host Domain Configuration

- Sample VTAM Configurations

About the SNACRM

The System Network Architecture Communications Resource Manager (SNACRM) runs as a separate native process that provides the emulation allowing Customer Information Control System (CICS), Distributed Program Link (DPL), and Information Management System (IMS) protocols to flow into and out of the Java environment.

The SNACRM System Platform

The SNACRM must run on the same platform as the SNA stack, but it may run on a different platform from the application and Java Communications Resource Manager Gateway (JCRMGW). The JCRMGW provides the configuration for the SNACRM. If the JCRMGW is running on a platform other than the one the SNACRM is on, then the SNACRM should already be started and monitoring the address specified in the JCRMGW configuration. Figure 1-1 is a diagram of a system configuration with the SNACRM located on the same platform as the application and gateway.

Figure 1-1 SNACRM System Diagram

Support for IMS Implicit Programs

The SNACRM supports non-transactional Information Management System (IMS) programs using implicit Application Program-to-Program (APPC) support for IMS. Implicit APPC is similar to the Customer Information Control System/Enterprise System Architecture (CICS/ESA) DPL. Any IMS program that sends and receives messages to and from the IMS message queue can be used as either a client or a server without change.

To use the implicit APPC capabilities of IMS, you must modify the APPCM file in the SYS1.PARMLIB Partitioned Data Set (PDS) under OS/390. The configuration parameters in this file associate the Logical Unit (LU) with the IMS scheduler. You must identify the LU representing the application name used by BEA eLink Java Adapter for Mainframe WLS Edition (JAM) to access the IMS region and the IMS system ID that provides scheduling for inbound requests. Consult with your mainframe support personnel before making changes to the APPCM file.

Remote Host Domain Configuration

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

Note: Always 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.

You must ensure the CICS/ESA remote domain is prepared to conduct operations with the BEA local domain. This includes:

- 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

- Setting Stack Traces

Establishing the VTAM Configuration

In the Java environment, SNACRM communicates with a Java application called the BEA eLink Java Adapter for Mainframe WLS Edition (JAM). This application is referred to as JAM throughout this document.

If your JAM system is used in a Virtual Telecommunications Access Method (VTAM) environment, you must ensure the host configuration supports it. Refer to "Sample VTAM Configurations," for some examples based on the requirements for JAM to be used in a VTAM environment with an Ethernet LAN and an APPN mainframe system.

Configuring the CICS/ESA LU

Before you can connect to the remote stack, the LU (Logical Unit) configuration must be established. This entails creating connection definitions, creating session definitions, and installing resource definitions.

Creating Connections at the Remote Host

If it is not already in place, you must work with the mainframe support personnel to create a remote connection definition file. When placed on the remote host, the definition provides a connection with the local domain. The following is an example of a 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)

To install the sample connection definition, put it on the host in a separate group that does not contain an existing connection. Use the CEDA INSTALL command.

For example:

>     CEDA INSTALL I GROUP(BEACONN)

Defining the Session at the Remote Host

If a session definition is not already in place, you must 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. The following is an example of a session definition:

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

AUTOCONNECT indicates how the activation of the session is to be negotiated. YES enables the CICS/ESA host to negotiate its own winner sessions when a conversation is allocated.

The MODENAME can be either a CICS/ESA-supplied mode name, such as SMSNA100, or your own defined mode name. If another set of session definitions exist 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.

The MAXIMUM option 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.

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

Summary of Cross-Platform Definitions

Before installing JAM software, please examine 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.

.

####

Table 1-1 Summary of Cross-Platform Definitions

Item | Name | Originates In | Needed In
--- | --- | --- | ---
>     1.
| 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 SNAplus2 or IBM CS/AIX Stack Configuration: Example: fqcp_name=SNANET1.SPARC1 adj_cp_name=SNANET1.VTAMHOST fqplu_name=SNANET1.CICSSYN
>     2.
| Mode Name (e.g. SNA62) | VTAM-MODEENT definition | CICS Sessions Definition: Example: MODENAME(SNA62) SunLink SNA Stack Configuration: Example: MODE NAME=SNA62 SNAplus2 Stack Configuration: Example: mode_name=SNA62 JCRMGW Configuration: Example: *JC_SNA_LINKS MODENAME="SNA62"
>     3.
| Control Point Name CPNAME (e.g. SPARC1) | VTAM-PU definition | SunLink SNA Stack Configuration: Example: CP NAME=SPARC1 CP NQ_CP_NAME=SNANET1.SPARC1 SNAplus2 Stack Configuration: Example: fqcp_name=SNANET1.SPARC cd_alias=SPARC1
>     4.
| 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 SNAplus2 Stack Configuration: Example: lu_name=L0F0024A lu_alias=L0F0024A JCRMGW Configuration: Example: *JC_SNA_STACKS LOCALLU="L0F0024A"
>     5.
| 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 SNAplus2 Stack Configuration: Example: fqplu_name=SNANET1.CICSSYN plu_alias=CICSSYN JCRMGW Configuration: Example: *JC_SNA_LINKS RLUNAME="CICSSYN"
>     6.
| Terminal Identifier (e.g. 05DF0024) | VTAM (IDNUM+IDBLK) | SunLink SNA Stack Configuration: Example: DLC TERM << ALIGN=CHAR SNAplus2 Stack Configuration: Example: node_id=<05000002>
>     7.
| Local Network Device (e.g. /dev/tr) | UNIX Configuration | SunLink SNA Stack Configuration: Example: TRLINE DEVICE='/dev/tr' or SDLCLINE DEVICE='/dev/dcp1'
>     8.
| Local MAC Address (token ring only) | Token ring address of Host | SunLink SNA Stack Configuration: Example: TRLINE Source_Address=X'080020117d7a'
>     9.
| Remote MAC Address (token ring only) | Token ring address of local machine | SunLink SNA Stack Configuration: Example: DLC RMTMACADDR=X'40000101000' SNAplus2 Stack Configuration: Example: mac_address=<400031720001>
>     10.
| LAN Speed (e.g. 4MBs) | Speed of token ring network | SunLink SNA Stack Configuration: Example: TRLINE LAN_rate=RING_4MBS
>     11.
| SDLC parameters (line protocol) | VTAM-line definition | SunLink SNA Stack Configuration: Example: SDLCLINE DUPLEX=half LINE=switched NRZI=no PAUSE=1 SPEED=4800
>     12.
| 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
>     13.
| Set LU definition so maximum sync-level allowed corresponds to JCRMGW.CFG entry: *DM_SNA_LINKS MAXSYNCLVL | Stacks | SunLink SNA Stack Configuration: Example: SYNC_LVL=SYNCPT SNAplus2 Stack Configuration: Example: [define local_lu] Syncpt.Support=YES
>     14.
| Map all incoming conversations to BEA Connect SNA 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' SNAplus2 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
>     15.
| CICS Transaction IDs (e.g. TOUP) | CICS/ESA | JCRMGW Configuration: Example: *JC_REMOTE_SERVICES

Microsoft SNA Cross-Platform Definitions

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

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

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

2. 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

3. 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

4. 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

5. 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

6. 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

7. 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

Setting Stack Traces

Consult the vendor publications for instructions on how to set up stack tracing.

Sample VTAM Configurations

The following sections provide sample environments showing how BEA eLink software can be configured for use with an Ethernet LAN and an APPN system 390. Considerations for token ring and subarea-style configurations are included. It is assumed that hardware and operating system installations have been completed.

An environment properly configured for the BEA eLink system involves two general components, a local environment and a remote environment.

Local Environment

A local environment is a UNIX-based or Windows NT-based machine running JAM software. JAM is a fully bidirectional program, supporting the local system as either a client or server. This environment consists of the following components:

- Hardware: any workstation and network interface supported by the required software

- Platform operating systems with protocol stacks (PU 2.1 servers)

Remote Environment

A remote environment is an IBM mainframe that may or may not be on the same local network. As in the local environment, JAM is a fully bidirectional program, supporting the remote system as either a client or server. This environment consists of the following components:

- Hardware: any workstation and network interface supported by the required software

- Software: any supported host software

Sample Environments

Samples of each environment are provided to illustrate a starting point when first configuring your system. These samples are not intended to be used without modifications. Any similarity between them and any actual system is coincidental.

Machine Attributes (LAN Descriptions)

The attributes of the sample environment machines are listed in the following tables for reference. The subsequent sample configurations refer to these attributes as required. Sample configurations are presented for example only and may contain components that are not supported for your system

####

Table 1-2 SPARCstation 5

Name | Attribute
--- | ---
OS | Solaris 2.5.1 or 2.6)
SNA | Brixton/CNT 4.1
APP | Tuxedo 6.5
MAC | 08:00:20:7C:47:50
IP | 206.189.43.14
NAME | beasun2

####

Table 1-3 SPARCstation 5

Name | Attribute
--- | ---
OS | Solaris 2.5.1 or 2.6 (SunOS 5.5.1)
SNA | SunLink 9.1
APP | Tuxedo 6.5
MAC | 08:00:20:87:47:2d
IP | 206.189.43.54
NAME | dalsun4

####

Table 1-4 HP 9000/847

Name | Attribute
--- | ---
OS | HP-UX B.10.20 or 11.00 (patches:PHNE_9663,9761,9889)
SNA | HPSNAPlus2 5.1 or 6.0
APP | Tuxedo 6.5
MAC | 08:00:09:30:24:77
IP | 206.189.43.13
NAME | dalhp10

####

Table 1-5 P390 Server 500

Name | Attribute
--- | ---
OS | MVS 5.22 9510
SNA | VTAM 4.3
APP | CICS 4.1 / IMS DC 5.1
MAC | 10:00:5a:d4:3e:8e
IP | 206.189.43.98
NAME | beavs

####

Table 1-6 P390 Server 500

Name | Attribute
--- | ---
OS | OS/390 1.2
SNA | VTAM 4.3
APP | CICS 4.1
MAC | 10:00:5a:d4:c1:e0
IP | 206.189.43.96
NAME | dalvs2

####

Table 1-7 Windows NT Server

Name | Attribute
--- | ---
OS | Windows NT Server 4.0, SP2
SNA | MS SNA Server 4.0, SP3
APP | CICS 4.1
MAC | 10:00:5a:d4:c1:e0
IP | 206.189.43.99
NAME | dalnt

Local Environment Configuration

HPSNAPlus2 configurations are usually setup using the HP xSnapAdmin utility, resulting in the configuration text file /etc/opt/sna/sna_node.cfg. This file can be manually created and/or maintained using a text editor; however, using the HP xSnapAdmin utility is recommended. The following example is the sna_node.cfg file for the sample environment.

Listing 1-1 HPSNAPlus2 Configuration

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

>     [define_node]
>     node_name = dalhp10
>     description = snacrm development
>     node_type = END_NODE
>     fqcp_name = BEALAN.DALHP10
>     cp_alias = dalhp10
>     mode_to_cos_map_supp = NO
>     mds_supported = YES
>     node_id = <05ffffff>
>     max_locates = 100
>      dir_cache_size = 255
>     max_dir_entries = 0
>     locate_timeout = 60
>     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
>     dlur_support = YES
>     pu_conc_support = NO
>     nn_rar = 128
>     ptf_flags = NONE

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

>     [define_ethernet_port]
>     port_name = ethl0
>     description = 1st ethernet adapter
>     dlc_name = ETHER0
>     port_type = PORT_SATF
>     port_number = 1
>     max_rcv_btu_size = 1033
>     tot_link_act_lim = 64
>     inb_link_act_lim = 0
>     out_link_act_lim = 0
>     ls_role = LS_NEG
>     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 = <000000000000>
>      lsap_address = 0x08
>     implicit_cp_cp_sess_support = NO
>     implicit_limited_resource = NO
>     implicit_deact_timer = 0
>     effect_cap = 3993600
>     connect_cost = 0
>     byte_cost = 0
>     security = SEC_NONSECURE
>     prop_delay = PROP_DELAY_LAN
>     user_def_parm_1 = 0
>     user_def_parm_2 = 0
>     user_def_parm_3 = 0
>     initially_active = YES
>     test_timeout = 5
>     test_retry_limit = 2
>     xid_timeout = 5
>     xid_retry_limit = 2
>     t1_timeout = 5
>     t1_retry_limit = 5

>     [define_ethernet_ls]
>     ls_name = P390HP10
>     description = P390 - beavs
>     port_name = ethl0
>     adj_cp_name = P390.USS3270
>     adj_cp_type = LEARN_NODE
>     mac_address = <0020af543176>
>     lsap_address = 0x08
>     auto_act_supp = NO
>     tg_number = 0
>     limited_resource = NO
>     solicit_sscp_sessions = NO
>     pu_name = <0000000000000000>
>     disable_remote_act = NO
>     default_nn_server = NO
>     dspu_services = NONE
>     dspu_name = <0000000000000000>
>     dlus_name = <0000000000000000000000000000000000>
>     bkup_dlus_name = <0000000000000000000000000000000000>
>     link_deact_timer = 0
>     use_default_tg_chars = YES
>     ls_attributes = SNA
>     adj_node_id = <00000000>
>     local_node_id = <00000000>
>     cp_cp_sess_support = YES
>     effect_cap = 3993600
>     connect_cost = 0
>     byte_cost = 0
>     security = SEC_NONSECURE
>      prop_delay = PROP_DELAY_LAN
>     user_def_parm_1 = 0
>     user_def_parm_2 = 0
>     user_def_parm_3 = 0
>     target_pacing_count = 7
>     max_send_btu_size = 1033
>     ls_role = USE_PORT_DEFAULTS
>     initially_active = NO
>     react_timer = 30
>     react_timer_retry = 65535
>     test_timeout = 5
>     test_retry_limit = 2
>     xid_timeout = 5
>     xid_retry_limit = 2
>     t1_timeout = 5
>     t1_retry_limit = 5

>     [define_local_lu]
>     lu_name = LUHP10A
>     description = Test LU #1
>     lu_alias = LUHP10A
>     nau_address = 0
>     syncpt_support = YES
>     lu_session_limit = 0
>     default_pool = NO
>     pu_name = <0000000000000000>
>     sys_name = ""
>     timeout = -1
>     back_level = NO

>     [define_local_lu]
>     lu_name = LUHP10B
>     description = Test LU #2
>     lu_alias = LUHP10B
>     nau_address = 0
>     syncpt_support = YES
>     lu_session_limit = 0
>     default_pool = NO
>     pu_name = <0000000000000000>
>     sys_name = ""
>     timeout = -1
>     back_level = NO

>     [define_local_lu]
>     lu_name = LUHP10C
>     description = Test LU #3
>     lu_alias = LUHP10C
>     nau_address = 0
>     syncpt_support = YES
>     lu_session_limit = 0
>     default_pool = NO
>     pu_name = <0000000000000000>
>     sys_name = ""
>     timeout = -1
>     back_level = NO

>     [define_partner_lu]
>     description = APPC MVS LU for IMS
>     fqplu_name = P390.MVSLU01
>     plu_alias = MVSLU01
>     plu_un_name = MVSLU01
>     max_mc_ll_send_size = 32767
>     conv_security_ver = NO
>     parallel_sess_supp = YES

>     [define_partner_lu]
>     description = backend cics #1
>     fqplu_name = P390.C410XB01
>     plu_alias = C410XB01
>     plu_un_name = C410XB01
>     max_mc_ll_send_size = 32767
>     conv_security_ver = NO
>     parallel_sess_supp = YES

>     [define_partner_lu]
>     description = Second backend cics
>     fqplu_name = P390.C410XB02
>     plu_alias = CICS2
>     plu_un_name = C410XB02
>     max_mc_ll_send_size = 32767
>     conv_security_ver = NO
>     parallel_sess_supp = YES

>     [define_mode]
>     mode_name = SMSNA100
>     description = Sessions: 10 -- 5,5
>     max_ru_size_upp = 1024
>     receive_pacing_win = 4
>     default_ru_size = YES
>     max_neg_sess_lim = 256
>     plu_mode_session_limit = 10
>     min_conwin_src = 5
>     cos_name = #eLink
>     cryptography = NONE
>     auto_act = 0

Remote Environment Configurations

You must involve your mainframe system support personnel early in the process of setting up your configuration. In a large shop there will most likely be different individuals responsible for Multiple Virtual Storage (MVS), VTAM, CICS, and IMS. Make sure everyone is involved. Most of the configuration for your mainframe may have already been done.

These samples are provided for illustration. Mainframe technical support is not trivial, and this information is not intended to explain all of the possible configurations. These samples represent one way a P390 can be configured to work in an APPN LAN environment.

ATCSTRxx VTAM Start List

The following example is the VTAM start list for the BEAVS P390 machine. It supports both the subarea and APPN environments.

Listing 1-2 VTAM Start List for BEAVS P390

>     * --------------------------*
>     * VTAM START LIST FOR SYS1  *
>     * --------------------------*
>     BN=YES,
>     BNDYN=FULL,
>     XNETALS=YES,
>     SSCPID=06,NOPROMPT,
>     CONFIG=00,MAXSUBA=31,SUPP=NOSUP,
>     SSCPNAME=USS3270,
>     NETID=P390,
>     NODETYPE=NN,
>     HOSTSA=6,
>     CRPLBUF=(208,,15,,1,16),
>     IOBUF=(100,512,19,,1,20),
>     LFBUF=(104,,0,,1,1),
>     LPBUF=(64,,0,,1,1),
>     SFBUF=(163,,0,,1,1)

XCA Major Node Defines the LAN Adapter for SYS1

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

Listing 1-3 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

The three switched network definition examples in this section specify the VTAM PU (Physical Unit), 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-4 SWNET Major Node (DALHP10)

>     SWNETHHP   VBUILD  TYPE=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-5 SWNET Major Node (SUN2)

>     SWNETH2    VBUILD  TYPE=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

Listing 1-6 SWNET Major Node (SUN4)

>     SWNESUN4   VBUILD  TYPE=SWNET,MAXNO=3,MAXGRP=3
>     P390ETH4   PU  ADDR=03,
>                    IDBLK=018,
>                    IDNUM=10092,
>                    PUTYPE=2,
>                    NETID=BEALAN,
>                    CPNAME=SUN4,
>                    MAXPATH=3,
>                    DWACT=YES,
>                    CONNTYPE=APPN,
>                    CPCP=YES,
>                    DYNLU=YES
>     * -------------------------------------------------
>     * SNA SAP & SUN4 MAC ADDRESS BIT REVERSED FOR TRFMT
>     * -------------------------------------------------
>     PATHSL4    PATH DIALNO=0008100002E1E2B4,
>                    GRPNM=G1ETH2
>     LUSUN4A  LU  LOCADDR=0
>     LUSUN4B  LU  LOCADDR=0
>     LUSUN4C   LU  LOCADDR=0

VTAM Application Major Nodes for CICS Regions

These examples represent the partner LU definitions to be accessed from the local environment. The APPL names must match those specified in the partner LU definitions on the local machine.

Listing 1-7 Partner LU Definitions

>     BEACICS VBUILD TYPE=APPL               APPLICATION MAJOR NODE
>     * APPL DEFINITION STATEMENTS FOR CICS
>     * CICS 4.10 BACKEND REGION #1 SYSID=B41A
>     C410XB01 APPL EAS=64,               ESTIMATED CONCURRENT SESSIONS
>                   MODETAB=ISTINCLM,     MAKE SURE DEFAULT MODETAB
>                   PARSESS=YES,
>                   AUTH=(ACQ,BLOCK,PASS) CICS CAN ACQUIRE & PASS TMLS
>                                            CICS CAN REQUEST BLOCKED INPUT

>     C410XB02 APPL EAS=64,               ESTIMATED CONCURRENT SESSIONS
>                   MODETAB=ISTINCLM,     MAKE SURE DEFAULT MODETAB
>                   PARSESS=YES,
>                   AUTH=(ACQ,BLOCK,PASS) CICS CAN ACQUIRE & PASS TMLS
>                                            CICS CAN REQUEST BLOCKED INPUT
>     C410XB03 APPL EAS=64,               ESTIMATED CONCURRENT SESSIONS
>                   MODETAB=ISTINCLM,     MAKE SURE DEFAULT MODETAB
>                   PARSESS=YES,
>                   AUTH=(ACQ,BLOCK,PASS) CICS CAN ACQUIRE & PASS TMLS
>                                            CICS CAN REQUEST BLOCKED INPUT
>     * #######################
>     * END OF BEACICS APPL DEF
>     * #######################

CICS Resource Definition Entries (RDO)

CICS connection and session definitions map the VTAM path definitions for the CICS application. Each connection represents one local LU definition in the local SNA configuration. Therefore, the names must match.

CICS session definitions associate a VTAM mode with the LU specified in the connection. The mode names and session count characteristics must match those specified in the mode definitions for the local SNA configuration. Note that these definitions set AUTOCONNECT to YES, allowing automatic session acquisition for a CICS client application.

Listing 1-8 CICS Resource Definition Entries

>     LIST GROUP(BEAHP10) OBJECTS
>     GROUP NAME: BEAHP10
>      ----------
>      CONNECTIONS:          FHPA     FHPB      FHPC
>      SESSION                        FHPA      FHPB   FHPC

>     CONNECTION(FHPA)       GROUP(BEAHP10)
>                            DESCRIPTION(1ST HP SNAP2+ CONNECTION)
>       CONNECTION-IDENTIFIERS
>          NETNAME(LUHP10A)           INDSYS()
>       REMOTE-ATTRIBUTES
>          REMOTESYSTEM()  REMOTENAME() REMOTESYSNET()
>       CONNECTION-PROPERTIES
>          ACCESSMETHOD(VTAM)         PROTOCOL(APPC)    CONNTYPE()
>          SINGLESESS(NO)             DATASTREAM(USER)  RECORDFORMAT(U)
>          QUEUELIMIT(NO)             MAXQTIME(NO)
>       OPERATIONAL-PROPERTIES
>          AUTOCONNECT(NO)            INSERVICE(YES)
>       SECURITY
>          SECURITYNAME()             ATTACHSEC(LOCAL)  BINDSECURITY(NO)
>          USEDFLTUSER(NO)
>       RECOVERY
>          PSRECOVERY(SYSDEFAULT)

>     CONNECTION(FHPB)       GROUP(BEAHP10)
>                            DESCRIPTION(2ND HP SNA+ 2 CONNECTION)
>       CONNECTION-IDENTIFIERS
>          NETNAME(LUHP10B)           INDSYS()
>       REMOTE-ATTRIBUTES
>          REMOTESYSTEM()             REMOTENAME()      REMOTESYSNET()
>       CONNECTION-PROPERTIES
>          ACCESSMETHOD(VTAM)         PROTOCOL(APPC)    CONNTYPE()
>          SINGLESESS(NO)             DATASTREAM(USER)  RECORDFORMAT(U)
>          QUEUELIMIT(NO)             MAXQTIME(NO)
>       OPERATIONAL-PROPERTIES
>          AUTOCONNECT(NO)            INSERVICE(YES)
>       SECURITY
>          SECURITYNAME()             ATTACHSEC(LOCAL)  BINDSECURITY(NO)
>          USEDFLTUSER(NO)
>       RECOVERY
>          PSRECOVERY(SYSDEFAULT)

>     CONNECTION(FHPC)      GROUP(BEAHP10)
>                           DESCRIPTION(3RD HP SNA+ 2 CONNECTION)
>        CONNECTION-IDENTIFIERS
>           NETNAME(LUHP10C)          INDSYS()
>        REMOTE-ATTRIBUTES
>           REMOTESYSTEM()            REMOTENAME()      REMOTESYSNET()
>        CONNECTION-PROPERTIES
>           ACCESSMETHOD(VTAM)        PROTOCOL(APPC)    CONNTYPE()
>           SINGLESESS(NO)            DATASTREAM(USER)  RECORDFORMAT(U)
>           QUEUELIMIT(NO)            MAXQTIME(NO)
>        OPERATIONAL-PROPERTIES
>           AUTOCONNECT(NO)           INSERVICE(YES)
>        SECURITY
>          SECURITYNAME()             ATTACHSEC(LOCAL)  BINDSECURITY(NO)
>          USEDFLTUSER(NO)
>        RECOVERY
>          PSRECOVERY(SYSDEFAULT)

>      SESSIONS(FHPA)       GROUP(BEAHP10)
>                           DESCRIPTION(1ST HP SNAP2+ SESSION)
>         SESSION-IDENTIFIERS
>            CONNECTION(FHPA)         SESSNAME()        NETNAMEQ()
>            MODENAME(SMSNA100)
>         SESSION-PROPERTIES
>            PROTOCOL(APPC)           MAXIMUM(32,16)    RECEIVEPFX()
>            RECEIVECOUNT()           SENDPFX()         SENDCOUNT()
>             SENDSIZE(4096)          RECEIVESIZE(4096) SESSPRIORITY(0)
>         PRESET-SECURITY
>            USERID()
>         OPERATIONAL-PROPERTIES
>            AUTOCONNECT(YES)         BUILDCHAIN(YES)   USERAREALEN(0)
>            IOAREALEN(0,0)           RELREQ(NO)        DISCREQ(NO)
>            NEPCLASS(0)
>         RECOVERY
>           RECOVOPTION(SYSDEFAULT)

>      SESSIONS(FHPB)       GROUP(BEAHP10)
>                           DESCRIPTION(2ND HP SNAP2+ SESSION)
>         SESSION-IDENTIFIERS
>           CONNECTION(FHPB)          SESSNAME()        NETNAMEQ()
>           MODENAME(SMSNA100)
>         SESSION-PROPERTIES
>           PROTOCOL(APPC)            MAXIMUM(32,16)    RECEIVEPFX()
>           RECEIVECOUNT()            SENDPFX()         SENDCOUNT()
>           SENDSIZE(4096)            RECEIVESIZE(4096) SESSPRIORITY(0)
>         PRESET-SECURITY
>           USERID()
>         OPERATIONAL-PROPERTIES
>           AUTOCONNECT(YES)          BUILDCHAIN(YES)   USERAREALEN(0)
>           IOAREALEN(0,0)            RELREQ(NO)        DISCREQ(NO)
>           NEPCLASS(0)
>         RECOVERY
>           RECOVOPTION(SYSDEFAULT)

>      SESSIONS(FHPC)       GROUP(BEAHP10)
>                           DESCRIPTION(3RD HPSNAP2+ SESSION)
>        SESSION-IDENTIFIERS
>          CONNECTION(FHPC)          SESSNAME()         NETNAMEQ()
>          MODENAME(SMSNA100)
>        SESSION-PROPERTIES
>          PROTOCOL(APPC)            MAXIMUM(10,5)      RECEIVEPFX()
>          RECEIVECOUNT()            SENDPFX()          SENDCOUNT()
>          SENDSIZE(4096)            RECEIVESIZE(4096)  SESSPRIORITY(0)
>        PRESET-SECURITY
>          USERID()
>        OPERATIONAL-PROPERTIES
>          AUTOCONNECT(YES)          BUILDCHAIN(YES)    USERAREALEN(0)
>          IOAREALEN(0,0)            RELREQ(NO)         DISCREQ(NO)
>          NEPCLASS(0)
>        RECOVERY
>          RECOVOPTION(SYSDEFAULT)

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