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

SAS/SHARE

System Administrator or User

To use the VTAM LU 0 access method with an OS/390 host for SAS/SHARE, perform these tasks:

Verify that you have met all your site and software requirements.
Verify that the resources for the VTAM LU 0 access method have been defined.
Verify that you know how to set SAS options.
Set the SAS/SHARE options that you want to use.

System and Software Requirements for SAS/SHARE

Ensure that the following conditions have been met:

ACF/VTAM Version 2.1 or a subsequent version has been installed at your site.
SAS software is installed on both the local and the remote hosts.
If a link connection is used in your network, ACF/NCP/VS Version 1.3 or a subsequent version has been installed at your site.

Defining Resources for the VTAM LU 0 Access Method

Applications Programmer, Network Administrator, and System Installation Staff: Before you can use SAS/SHARE with the VTAM LU 0 access method, you must first configure VTAM resources. See System Configuration for the VTAM LU 0 Access Method for SAS/SHARE resource configuration.

Understanding VTAM Access Method Terminology

Familiarity with these terms will help you when you talk with your systems installation staff about the appropriate SAS option settings.

LU (logical unit): a device or program by which an end user (LU 0 applications program) gains access to the system on which the VTAM LU 0 access method is configured.
LU pool: a group of LUs provided through the VTAM subsystem that provide the dynamic assignment of an LU from the pre-defined pool to a client in a SAS/SHARE session. Pool size is determined by the setting of the LUFIRST and LULAST variables (see the next section for information about these variables). See System Configuration for the VTAM LU 0 Access Method for details about defining the properties of the LU pool.

Setting SAS Options

You must set specific SAS options to enable the connections that you want with SAS/SHARE when using the VTAM access method. The values that you assign to these variables depend on how your VTAM subsystem has been configured. Ask your systems installation staff for advice about these settings.

You may set options in the following forms:

in an OPTIONS statement in a SAS session or in an AUTOEXEC file:
OPTIONS option-name=value;
Example:
```
options lu0sec=_trust_;
```
in a SAS configuration file or at a SAS invocation:
option-name=value
Example:
```
lu0sec=_trust_
```
CLIST variable:
Add variable-name(default value) to the SAS CLIST. Then add variable-name(current value) at the SAS invocation.
Example CLIST:
```
lu0sec(_trust_)    /* VTAM options */ 
```
You would specify the CLIST at a SAS invocation, as follows:
```
sdssas lu0sec(_trust_) ('comamid=vtam')
```

Values for these variables may contain up to eight characters, consisting of alphanumeric characters, the percent sign (%), the dollar sign ($), the pound sign (#), the at sign (@), and the underscore (_).

If you set multiple forms of the same option, here is the order of precedence that is followed:

OPTIONS statement

AUTOEXEC file

SAS invocation

SAS configuration file

CLIST variable.

SAS/SHARE Options

LU0SEC=_TRUST_

Set this option at the server.

_TRUST_ specifies that the VTAM LU 0 access method present the userid of a connecting client to the server as if the userid had been validated with a password. The server then uses that userid to validate the user's authority to access SAS libraries.

Note: The VTAM LU 0 access method does not validate the userid. [cautionend]

If the userid of a connecting client is defined to the security software on the server's system, and the userid belongs to that user, the server's authorization verification for SAS libraries will be valid. However, if the connecting client's userid is defined but it belongs to another user, the authorization verification will be inappropriate, but it may allow the unrightful connecting client to access SAS libraries that it would not ordinarily be able to access directly.

APPCSEC = _SECURE_

Set this option at the server before issuing the PROC SERVER statement.

_SECURE_ allows the VTAM LU 0 access method to initialize so that the server can use it.

LUPREFIX=name

Set this option at the client and the server.

LUPREFIX specifies an identifying prefix to attach to a value that is in the range defined by the LUFIRST and LULAST options. Combining LUPREFIX and a value in the range defined by the LUFIRST and LULAST options forms an ACBNAME that is assigned to each LU pool member.

You can set this option only in a SAS configuration file or at a SAS invocation.

LUFIRST=n

Set this option at the client and the server.

LUFIRST specifies the beginning (numeric) boundary of the range to form the pool of LU names.

You can set this option only in a SAS configuration file or at a SAS invocation.

LULAST=n

Set this option at the client and the server.

LULAST specifies the final (numeric) boundary of the range to form the pool of LU names.

You can set this option only in a SAS configuration file or at a SAS invocation.

Example 1:

If you have a maximum pool size (or depth) of 99 LUs and you want an 8-byte ACBNAME LU name, you must select an LUPREFIX value that is 6 bytes long.

luprefix=sascon
lufirst=1
lulast=99

ACBNAME LU names (or LU pool names) would range from SASCON01 (zero-filling is required) to SASCON99 (no zero-filling is required).

Example 2:

If you have a maximum pool size (or depth) of 9 LUs and you want an 8-byte ACBNAME LU name, you must select an LUPREFIX value that is 7 bytes long.

luprefix=sascont
lufirst=1
lulast=9

ACBNAME LU names (or LU pool names) would range from SASCONT1 to SASCONT9 (no zero-filling is required).

Example 3:

If you have a maximum pool size (or depth) of 10 LUs and you want a 6-byte ACBNAME LU name, you must select an LUPREFIX value that is 4 bytes long.

luprefix=sasc
lufirst=1
lulast=10

LU pool names would range from SASC01 (zero-filling is required) to SASC10 (no zero-filling is required).

You may also infer the pool size from the setting of the LULAST and LUFIRST options by using the following formula:

pool-size= (LULAST - LUFIRST) + 1

Example:

pool-size=(99-1)+1=99

These option settings describe the pool of LUs from which an LU is dynamically selected when a client accesses a SAS/SHARE server.

Client Tasks

User or Applications Programmer

To prepare for accessing a server, make sure that you know how to:

Specify the VTAM LU 0 access method.
Specify a server name.

Specifying the VTAM LU 0 Communications Access Method

You must specify the VTAM LU 0 communications access method at the client before you access a server.

Use the following syntax to specify the VTAM LU 0 access method at each connecting client:

OPTIONS COMAMID=access-met hod-id;

where COMAMID is an acronym for Communications Access Method Identification. access-method-id identifies the method that is used by the client to communicate with the server. VTAM (an acronym for Virtual Telecommunications Access Method ) is an example of an access-method-id.

Example:

options comamid=vtam;

The server is accessed using the VTAM access method.

You may specify the COMAMID option in an OPTIONS statement, at a SAS invocation, or in a SAS configuration file.

Additionally, you may use the COMAUX1 and COMAUX2 options to designate auxiliary communications access methods. See SAS/CONNECT and SAS/SHARE: Supported Access Methods According to Host Release for the supported access methods by host. If the first method fails to access a server, the second method is attempted, and so on. You can specify up to two auxiliary access methods, depending on the number of methods that are supported between client and server hosts.

COMAUX options can be specified only at a SAS invocation or in a SAS configuration file. The syntax for the COMAUX options follows:

COMAUX1=alternate-method
COMAUX2=alternate-method

An example of configuration file entries for an OS/390 client connecting to an OS/390 server follows:

comamid=vtam
comaux1=tcp
comaux2=xms

If the server cannot be reached with the VTAM method, a second attempt is made with the TCP/IP access method, and a third with XMS.

Specifying a Server Name

To use the VTAM LU 0 access method, a server and a client must be part of the IBM SNA network.

You must specify the server name in the LIBNAME and PROC OPERATE statements as follows:

SERVER=server-name

where server-name is the LU name that is defined in the VTAM configuration. Consult with the person who configured resources for the VTAM LU 0 access method for the configured server name. The VTAM APPL syntax requires a server name that may contain up to eight characters. Because VTAM-naming and SAS-naming requirements are compatible, there should be no naming conflict.

See SAS Language Reference: Dictionary for details about SAS naming rules. See SAS/SHARE User's Guide for details about the LIBNAME and PROC OPERATE statements.

Client Example

The following example illustrates the statements that you specify in a configuration file on the OS/390 client:

luprefix=sascon
lufirst=1
lulast=10

LUPREFIX SASCON is specified with the LUFIRST and LULAST values to form ACBNAME LU names ranging from SASCON01 to SASCON10.

See Setting SAS Options for details about these options.

The following example illustrates the statements that you specify in an OS/390 client configuration file to access a server with the VTAM access method:

options comamid=vtam;
libname sasdata 'edc.prog2.sasdata' server=share1;

The VTAM access method is declared. The LIBNAME statement specifies the data library that is accessed through the server SHARE1.

Server Tasks

Server Administrator

To set up a server and make it accessible to a connecting client, perform the following tasks:

Specify the VTAM LU 0 access method.
Specify the server name.

Specifying the VTAM LU 0 Access Method

You must specify the VTAM LU 0 communications access method at the server before you create a SAS/SHARE server.

Use the following syntax to specify the VTAM access method at the server:

OPTIONS COMAMID=access-method-id;

where COMAMID is an acronym for Communications Access Method Identification. access-method-id identifies the method used by the server to communicate with the client. VTAM (an acronym for Virtual Telecommunications Access Method) is an example of an access-method-id.

For a server that is running on a host on which only one communications access method is available, use only the COMAMID option.

Example:

options comamid=vtam;

The server will be available only to SAS/SHARE sessions that use the VTAM access method.

You may specify the COMAMID option in an OPTIONS statement, at a SAS invocation, or in a SAS configuration file.

However, if the host on which a server is running supports multiple access methods, you may specify up to two auxiliary access methods by which clients may access the server by using the COMAUX1 and COMAUX2 options. See SAS/CONNECT and SAS/SHARE: Supported Access Methods According to Host Release for the supported access methods by host.

All of the access methods initialize when the server initializes. The activation of multiple access methods makes a server available to several groups of clients, each using a different communications access method simultaneously.

COMAUX options can be specified only at a SAS invocation or in a SAS configuration file. The syntax for the COMAUX options follows:

COMAUX1=alternate-method
COMAUX2=alternate-method

An example of configuration file entries for a server that is running on an OS/390 host follows:

comamid=vtam
comaux1=tcp
comaux2=xms

When the server starts, all of the communications access methods are initialized. The server is simultaneously available to client sessions that use the VTAM access method as well as to clients that use the TCP/IP and XMS access methods.

Specifying a Server Name

To use the VTAM LU 0 access method, a server and a client must be part of the IBM SNA network.

You must specify the server name in the PROC SERVER statement as follows:

SERVER=server-name

where server-name is the LU name that is defined in the VTAM configuration. Consult with the person who configured resources for the VTAM LU 0 access method for the configured server name. The VTAM APPL syntax requires a server name that may contain up to eight characters. Because VTAM naming and SAS naming requirements are compatible, there should be no naming conflict.

See SAS Language Reference: Dictionary for details about SAS naming rules. See SAS/SHARE User's Guide for details about the PROC SERVER statement.

Server Example

The following example illustrates the statements that you specify in a configuration file on the OS/390 host at which you start a server: comamid=vtam lu0sec=_trust_ luprefix=sascon lufirst=1 lulast=10

The VTAM LU 0 access method is declared, and the LU0SEC option sets server security that requires clients to supply a userid and a password that are valid on the server. LUPREFIX SASCON is specified with the LUFIRST and LULAST options to form ACBNAME LU names ranging from SASCON01 to SASCON10.

The following statements in a SAS session on the OS/390 remote host start a server:

proc server id=share1;
run;

The server SHARE1 is started on the OS/390 remote host.

Chapter Contents
Previous
Next
Top of Page

	OPTIONS statement
	AUTOEXEC file
	SAS invocation
	SAS configuration file
	CLIST variable.