|Communications Access Methods for SAS/CONNECT and SAS/SHARE Software|
Perform the following tasks to configure CMS userids to use with the APPC access method:
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
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.
For connections within the TSAF collection the first name can be USERID and the second name the remote host userid.
Note: You can
omit specifying the USERID.
userid and PASSWORD.
password parameters, if you do one of the following:
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
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.
|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.
An explanation of each entry follows:
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.
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
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.
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.
Top of Page
Copyright 1999 by SAS Institute Inc., Cary, NC, USA. All rights reserved.