Configuration for SNA (UNIX/Linux)

The setup and configuration of the inter system communication services over the SNA protocol, requires the following steps:

SNA server product setup

First of all, the SNA server product (DataConnection SNAP-IX, IBM Comm. Serv. or HP SNAPlus2), must be installed on the system and correctly configured.

Some of these products have the possibility to select the components to install: It is mandatory to install the core and APPC API components.

Please refer to your SNA server product documentation.

XFRAME setup

When the SNA server products is installed, XFRAME APPC components must be built with the product libraries.

To do that, simply (re)install XFRAME, and specify the SNA product type during configuration phase.

SNA node configuration

SNA node must be configured and an active link to the partner system must be created.

Of course, this link requires a correspondent definition in the VTAM of the partner system.

Please refer to your SNA server product documentation to configure the node and the link, and refer to the corresponding documentation to define the node in the partner system (VTAM documentation for mainframes and SNA server product for other UNIX systems).

Furthermore at least one LU to be used by the XCICS region must be defined.

This LU should normally have the same name as the XCICS application name. XCICS identifies the LU by its alias therefore remember to correctly defined the alias too. The easiest way to configure the LU is to provide the same 8 byte identifer to the LU, to its alias and to the XCICS application name.

Finally an alias identifying the remote partner must be added.

XCICS configuration

First of all, the LU alias for incoming and outgoing connections must be declared in xcics.conf. By default XCICS uses an LU alias equal to its name. Alternatively it is possible to override this behaviour specifing the default_inbound_lu and default_outbound_lu in xcics.conf.

Then one or more connection entries (CCT) must defined using the define connection directive. A connection identifies the partner system, specifying the SYSID used in the application and the remote LU alias.

Finally, sessions to serve incoming requestes must be defined, using the define sessions directive.

Example configuration

Following some example configuration describing a connection between an XCICS TS region and an IBM CICS TS on SNA over ethernet.

Unix side

in the UNIX/Linux SNA server product configuration file:

[define_node]
cp_alias = UNIX01
description = ""
fqcp_name = MYNET.UNIX01
node_type = LEN_NODE
mode_to_cos_map_supp = NO
mds_supported = YES
node_id = <05f00002>                             # (3) as defined in the VTAM VBUILD
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
dlur_support = NO
pu_conc_support = YES
nn_rar = 128
max_ls_exception_events = 0
ptf_flags = NONE
cplu_syncpt_support = NO
 
[define_local_lu]
lu_alias = XCICS001                        # (1) the same as local XCICS application name
list_name = ""
description = XCICS TS region on UNIX01
lu_name = XCICS001                         # (3) the same as in remote VTAM definition
lu_session_limit = 0
pu_name = <0000000000000000>
nau_address = 0
default_pool = NO
syncpt_support = YES
lu_attributes = NONE
sscp_id = 0
disable = NO
sys_name = ""
timeout = 60
back_level = NO
 
[define_partner_lu]
plu_alias = IMBCICS1                        # (2) partner lu alias
description = ""
fqplu_name = MYNET.IBMCICS1                 # remote CICS LU name
plu_un_name = DBDCCICS                      
parallel_sess_supp = YES
max_mc_ll_send_size = 0
conv_security_ver = NO

in xcics.conf:

set application_name=XCICS001;               # (1) the same as local LU alias
define connection sysid=P390,
          type=sna,
          netname=IBMCICS1,                 # (2) partner lu alias
          mode=LU62APPB,
          acquire, os=ebcdic;
define sessions size=4;                      # number parallel sessions available

Mainframe side

LU definition in the partner VTAM for UNIX system

XCASNET VBUILD TYPE=SWNET                                           
HPUX02   PU    PUTYPE=2,ADDR=C1,                                -
       IDBLK=05F,IDNUM=00002,                                  -
       MODETAB=ISTINCLM,                                       -
       DISCNT=NO,                                              -
       MAXDATA=265,MAXOUT=7,MAXPATH=1,SSCPFM=FSS,              -
       PACING=0,VPACING=0,ISTATUS=ACTIVE,                      -
       CONNTYPE=APPN,CPCP=YES                                  
HP02     PATH  GRPNM=XGE40E,                                    -
       DIALNO=010400306EF3C2FB,                                -
       GID=1,PID=1,USE=YES      
*/* (3) the following is the same XCICS LU name                            
XCICS001 LU    LOCADDR=0                                               

CICS CEDA definitions:

DEFINE CONNECTION(XCX1) GROUP(XCICS001)
      NETNAME(XCICS001)
      ACCESSMETHOD(VTAM)
      PROTOCOL(APPC)
      SINGLESESS(NO)
 
DEFINE SESSION(XCX1SESS) GROUP(XCICS001)
      CONNECTION(XCX1)
      ACCESSMETHOD(VTAM)
      MODENAME(LU62APPB)
      MAXIMUM(10,6)