Chapter Contents

Previous

Next
Communications Access Methods for SAS/CONNECT and SAS/SHARE Software

System Configuration for the APPC Access Method for SAS/CONNECT

VTAM Systems Personnel
Configure CMS userids for the CMS system that enable it to behave as either a local or a remote host in a SAS/CONNECT session when using the APPC access method.

Perform the following tasks to configure CMS userids to use with the APPC access method:

  1. At a CMS local host, create a communications directory.

  2. At a CMS remote host, set up a $SERVER$ NAMES directory.

  3. At a CMS remote host, edit the PROFILE EXEC file, as necessary.

  4. At both a CMS local host and a remote host, define a VTAM gateway.

  5. At both a CMS local host and a remote host, define the logon mode table entries.

  6. At a CMS local host, set session limits and contention values.

This section highlights the general tasks that you must perform to configure the system to use with the APPC access method. For full details about configuring the APPC access method, see References.


Creating a Communications Directory File

To connect a CMS local host to a remote host, create a communications directory file for the connecting user. The file contains an entry that is used for the value of the SAS option REMOTE=, at the local host.

The communications directory file can reside at the system level, the user level, or both. The default system-wide communications directory file is named SCOMDIR NAMES, and the default user communications directory file is named UCOMDIR NAMES. The format of a CMS communications directory entry follows:

:NICK.LU-name  :LUNAME.gateway target-LU
               :TPN.SASRMT
               :MODENAME.modename
               :SECURITY.level
               :USERID.userid
               :PASSWORD.password

where

NICK.LU-name
is short for nickname. It specifies the eight-character symbolic destination name of the resource.

You will use LU-name as the value for the REMOTE= option at the local host.

A CMS user cannot take advantage of the aliasing support that is implicit in the CMS communications directory structure when accessing a host that is not a CMS host. Instead, the NICK value in the communications directory must be identical to the target LU value in the :LUNAME definition.

LUNAME.gateway target-LU
is composed of two eight-character names. The first name defines the name of the gateway for connections outside the TSAF collection; the second is the name of the partner LU.

For connections within the TSAF collection the first name can be USERID and the second name the remote host userid.

TPN.SASRMT
indicates the transaction program name as it is known to the target LU. For SAS/CONNECT, the transaction program name is always SASRMT.

MODENAME.modename
specifies the mode name of the SNA session that connects the gateway to the target LU.

SECURITY.level
specifies whether to use security in a SAS/CONNECT session. The two values for level are PGM, which indicates program security, or NONE. Specify PGM if the server is running secured (requiring a userid and password from each connecting user). Specify NONE if the server is running unsecured (not requiring a userid and password from each connecting user). See Setting Security for SAS/CONNECT and SAS/SHARE for more information about userid and password security.

USERID.userid
indicates the access security userid that is presented to the target LU for verification.

PASSWORD.password
indicates the access security password that is presented to the target LU.

Note:   You can omit specifying the USERID. userid and PASSWORD. password parameters, if you do one of the following:

Both the APPCPASS statement and the APPCSEC option are more secure methods for presenting userid and password information to a target LU than the USERID and PASSWORD parameters. Refer to VM/ESA Connectivity Planning, Administration and Operation (SC24-5448) for more details about the APPCPASS statement.  [cautionend]

Examples:

The first example allows a CMS-to-CMS connection. In this example, the NICK value (CONNVM) is different from the target-LU value (N01SASPG).

:NICK.CONNVM   :LUNAME.N01SASOG N01SASPG
               :TPN.SASRMT
               :MODENAME.SASAPPC
               :SECURITY.PGM
               :USERID.bass
               :PASSWORD.time2go

The next example allows a CMS-to-OS/390 connection. In this example, the NICK value (N01TGT62) is identical to the target-LU value (N01TGT62).

:NICK.N01TGT62 :LUNAME.N01SASOG N01TGT62
               :TPN.SASRMT
               :MODENAME.SASAPPC
               :SECURITY.PGM
               :USERID.bass
               :PASSWORD.time2go


Creating a $SERVER$ NAMES Directory

To connect to a CMS remote host, you must create the $SERVER$ NAMES directory at the remote CMS host. This directory defines the EXEC to be run when the connection is made to the remote CMS system. The format of a CMS $SERVER$ NAMES directory entry follows:

:NICK.SASRMT   :LIST.userid1 ... useridn|.*
               :MODULE.exec-name

where

NICK.SASRMT
specifies the eight-character symbolic destination name of the resource. SASRMT is the transaction program name as it is known to the target LU. For SAS/CONNECT, the transaction program name is always SASRMT.

LIST.userid1 ... useridn
enables you to limit the number of users that are allowed to connect to this system.

LIST.*
specifies that all users are allowed to connect to this system.

MODULE.exec-name
specifies the EXEC to be run when a connection is made to the remote CMS system. Specifying this module eliminates the need for a sign-on script. The primary purpose of this EXEC is to invoke the remote SAS session with the SAS options that you want.

A sample $SERVER$ NAMES file follows:

 $SERVER$ NAMES
:NICK.SASRMT   :LIST.*
               :MODULE.RMTBOOT

The RMTBOOT EXEC that was specified in the previous example might be structured as follows:

 /*   This is the BOOTSTRAP EXEC */
 /*   for the remote CMS host */
 say 'Remote Bootstrap in Progress'
 say 'Invoking the SAS System     '
 'EXEC SAS (COMAMID=APPC DMR REMOTE=N01SASPG 

NOTERMINAL NO$SYNTAXCHECK)' queue 'CP logoff' exit

Note:   The SAS options COMAMID, DMR, and REMOTE that are included in this example are required to invoke SAS/CONNECT on the remote host.  [cautionend]


Customizing the PROFILE EXEC File

You must ensure that the appropriate CMS SET commands are specified in the remote CMS virtual machine to allow the virtual machine to function as a remote host. Edit the PROFILE EXEC file on the remote CMS userid and add the following commands:

 /*   Make sure that we are set up to accept */
 /*   connections if we get autologged       */
 if substr(diagrc(24,-1),11,1) = '2' then do
    'SET SERVER ON'
    'SET FULLSCREEN OFF'
    'SET AUTOREAD OFF'
 end

Because these commands are part of the PROFILE EXEC file, these CMS commands are automatically issued during login if the CMS userid is being autologged through a SAS/CONNECT sign on.


Defining a VTAM Gateway

A VTAM gateway provides a path for local host users to reach desired remote hosts. Use APPL statements to define separate VTAM gateways for

To connect a CMS local host to a remote host, you must define local-domain VTAM application minor node identifiers (outbound gateway) using APPL statements.

Use a comma to separate each entry.

APPL statements for a CMS local host follow:

N01SASOG  APPL   ACBNAME=N01SASOG,

                APPC=YES,
                AUTHL=(ACQ),
                AUTHEXIT=YES,
                AUTOSES=0,
                DLOGMOD=mode-table-entry,
                DMINWNL=16384,
                DMINWNR=0,
                DSESLIM=32767,
                EAS=30,
                MODETAB=mode-table,
                PARSESS=YES,
                SECACPT=CONV,
                SONSCIP=YES,
                VPACING=n

To connect to a VM/CMS system, you must define a non-dedicated private gateway to provide SAS/CONNECT users with a pathway for reaching the VM/CMS system. APPL statements for a CMS remote host follow:

N01SASPG  APPL   ACBNAME=N01SASPG,

                APPC=YES,
                AUTHL=(ACQ),
                AUTHEXIT=YES,
                AUTOSES=0,
                DLOGMOD=mode-table-entry,
                DMINWNL=0,
                DMINWNR=16384,
                DSESLIM=32767,
                EAS=30,
                MODETAB=mode-table,
                PARSESS=YES,
                SECACPT=CONV,
                SONSCIP=YES,
                VPACING=n

Note:   The only differences between the two sets of APPL statements are the values assigned to the DMINWNL and DMINWNR parameters.  [cautionend]

An explanation of each entry follows:

ACBNAME
defines the minor node name assigned to this application program.

APPC=YES
tells APPC that the application program can issue APPCCMD macros.

APPL
declares an APPL definition statement.

AUTH=(ACQ)
enables the application to acquire a session with a particular logical unit.

AUTHEXIT=YES
allows the application's exit routines to run in supervisor state.

AUTOSES=0
defines the number of contention winner sessions to activate automatically.

DLOGMOD=mode-entry
defines the default session parameter mode table entry.

DMINWNL=x
specifies the initial negotiation value for local contention winner sessions.

DMINWNR=y
specifies that the remote partner's contention winner sessions request be used.

DSESLIM=32767
defines the maximum session limits.

EAS=30
specifies the estimated number of sessions that will be active with this logical unit at any given time.

MODETAB=mode-table
defines the session logon mode table.

PARSESS=YES
allows multiple concurrent sessions with another application program.

SECACPT=CONV
indicates that the FMH5 security subfield information is accepted.

SONSCIP=YES
allows the application to receive UNBIND RUs in its SCIP exit routine.

VPACING=n
sets network requirements per site.

See VTAM Installation and Resource Definition (SC23-0111) for more information about the VTAM gateway parameters.


Defining Logon Mode Table Entries

A logon mode table contains one or more sets of session properties that support session binding to a secondary LU that resides within the local VTAM domain.

Refer to the BIND RU description in Technical Reference 3, SNA Formats and the MODEENT discussion in VTAM Resource Definition Reference (SC32-6412) for complete information.

The following sample logon mode table entry contains a single set of session properties.

SASAPPC MODEENT  LOGMODE=SASAPPC,
                 FMPROF=X'13',
                 TSPROF=X'07',
                 PRIPROT=X'B0',
                 SECPROT=X'B0',
                 COMPROT=X'50B1',
                 RUSIZES=X'xxxx',
                 PSERVIC=X'060200000000000000102F00',
                 TYPE=0


Setting Session Limits and Contention Values

To use the SNA network for your APPC communications, you must use the CNOS (Change Number of Sessions) command to increase the session limits to greater than 0 between the AVS outbound gateway and the appropriate partner LU.

Note:   CNOS is a privileged command.  [cautionend]

Because the IBM APPC/VM implementation does not support a programming interface to this command, SAS cannot issue it automatically. Instead, you must enter control information at an AVS console. Alternatively, you may supply this information through the Programmable Operator Facility (PROP) that is included with the CMS system.

The CNOS command remains in effect while the remote host remains in operation until the system has been rebooted. If you do not re-issue the command following a system reboot, communication between the two partner LUs cannot proceed.

It is recommended that you routinely re-issue the CNOS command each time the remote system is restarted. Re-issuing the CNOS command enables CMS users to gain access to the remote system at any time without operator intervention.

The command format for the implementation of the CMS CNOS command follows:

PROP AGW CNOS gateway
remote-LU  modenameses-limit con-win con-lose

The parameters for the CNOS command are

gateway
specifies the name of the local LU that is the gateway.

remote-LU
specifies the name of the remote LU for which the session limits are set.

modename
specifies the logon mode name for which the session limit and contention values are changed.

ses-limit
specifies the maximum number of LU-to-LU sessions that are allowed between the gateway LU and the remote LU for the logon mode name.

con-win
specifies the number of parallel sessions for which the gateway LU is guaranteed to be the contention winner.

con-lose
specifies the number of parallel sessions to which the remote LU is guaranteed to be the contention winner.

Example:

PROP AWG CNOS N01SASOG N01TGT62 NO1MOD1 100 50 50

Appropriate values for your site are based on the number of simultaneous users of the gateway. A general recommendation for the CNOS ses-limit value is to allocate three sessions per userid that will simultaneously use the gateway.

You have completed the remote and local CMS host configuration procedure for SAS/CONNECT.


References

For complete details about how to install and configure the system for use with the APPC access method, see the following IBM publications:
VM/ESA Connectivity Planning, Administration, and Operation (SC24-5448)
SNA Technical Overview (GC30-3073)
SNA Formats (GA27-3136)
VTAM Programming for LU6.2 (SC30-3400)

Contact IBM for information about obtaining this documentation.


Chapter Contents

Previous

Next

Top of Page

Copyright 1999 by SAS Institute Inc., Cary, NC, USA. All rights reserved.