Chapter Contents
Previous
Next
Communications Access Methods for SAS/CONNECT and SAS/SHARE Software

System Configuration for the VTAM LU 0 Access Method

Applications Programmer, Network Administrator, or Systems Installation Staff
Configure resources for the VTAM LU 0 access method by defining the server and the connecting clients in their respective domains.

To configure the OS/390 system for VTAM LU 0, perform the following tasks:

  1. Define the server LU in the server's VTAM domain.

  2. Define the client LUs in the clients' VTAM domain.

  3. Optionally, define cross-domain resources.

  4. Optionally, define resources in the same domain.

File these definitions in members of your installation's VTAMLST data set. Add the member names to the configuration startup list (member ATCONNxx), where xx represents each member in the list.

Defining a Server

You must define each server with an APPL statement in the VTAM domain in which the server will run. Use the following syntax: 

VBUILD TYPE=APPL
server-id  APPL AUTH=(ACQ), EAS=n, PARSESS=YES

All APPL statements must follow a VBUILD TYPE=APPL statement.

An explanation of each entry follows:

VBUILD TYPE=APPL
specifies that this VBUILD statement defines an application major node.

server-id
specifies a unique name for the server in the network. The name may contain up to a maximum of eight characters and is used as the value for the SERVER= option in the PROC SERVER, the PROC OPERATE, and the LIBNAME statements.

AUTH=(ACQ)
specifies that this APPL can initiate a session.

EAS=n
specifies the estimated number of concurrent sessions that the server can have with clients in the network. To determine a value for this entry, estimate the number of users that you expect to be connected to the server simultaneously and multiply by three.

PARSESS=YES
indicates support for parallel session capability.

Example: 

Domain 1 VTAMLST member C01ASAS:

*************************************************
* Application major node for SAS/SHARE software *
* Server name is C01SHARE                       *
*                                               *
*************************************************
  VBUILD TYPE=APPL
*-----------------------------------------------*
* SAS Server application running in domain 1    *
*-----------------------------------------------*
C01SHARE APPL AUTH=(ACQ),EAS=30,PARSESS=YES

A server is defined in Domain 1. The server-id is C01SHARE. The value for server-id is used in the SERVER option in the PROC SERVER, the PROC OPERATE, and the LIBNAME statements.

Defining Each Client

You must define each client application with an APPL statement in the VTAM domain in which the client will run. Separate each entry with a comma. Use the following syntax: 

VBUILD TYPE=APPL
client-name  APPL ACBNAME=acbname AUTH=(ACQ), 
                EAS=n, PARSESS=YES

An explanation of each entry follows:

VBUILD TYPE=APPL
specifies that this VBUILD statement defines an application major node.

client-name
specifies a unique name for the client across all networks. The name may contain up to a maximum of eight characters.

ACBNAME=acbname
identifies an LU pool member, whose name is formed by combining the value of LUPREFIX with a value that is between the values of the LUFIRST and LULAST options. See Setting SAS Options for information about forming ACBNAMEs.

AUTH=(ACQ)
specifies that this APPL can initiate a session.

EAS=n
specifies the number of concurrent sessions that the user can have at one time. To determine a value for this entry, estimate the number of users that you expect to be connected to the server simultaneously and multiply by three.

PARSESS=YES
indicates support for parallel session capability.

Example: 

Domain 2 VTAMLST member C02ASAS:

****************************************************
*   Application major node for SAS/SHARE software  *
*   LUPREFIX = SASCON, LUFIRST = 1, LULAST = 5     *
****************************************************
    VBUILD TYPE=APPL
*--------------------------------------------------*
*   SAS User applications running in domain 2      *
*   and communicating with server C01SHARE in      *
*   domain 1                                       *
*--------------------------------------------------*
C02SI001 APPL ACBNAME=SASCON1,AUTH=(ACQ),EAS=3,PARSESS=YES
C02SI002 APPL ACBNAME=SASCON2,AUTH=(ACQ),EAS=3,PARSESS=YES
C02SI003 APPL ACBNAME=SASCON3,AUTH=(ACQ),EAS=3,PARSESS=YES
C02SI004 APPL ACBNAME=SASCON4,AUTH=(ACQ),EAS=3,PARSESS=YES
C02SI005 APPL ACBNAME=SASCON5,AUTH=(ACQ),EAS=3,PARSESS=YES

The APPL statements in Domain 2 define a pool of LUs for clients on Domain 2 that will communicate with the server in Domain 1. The first field shows a unique eight-character client name, and the ACBNAME field shows the name of each LU in the pool, which is formed by combining the value of LUPREFIX with a value that is in the range between the values of the LUFIRST and LULAST options.

Defining Cross-Domain Resources

A multiple-domain network is a set of connected domains, each controlled by an ACF/VTAM with a cross-domain resource manager (CDRM). In a multiple-domain network, information about other domains must be provided to each ACF/VTAM.

In each domain from which a client will attempt to access a SAS/SHARE server, you must define that server as a cross-domain resource by using a VBUILD statement and a CDRSC statement.

If your site does not support the use of dynamic CDRSC definitions, then you must define each connecting client from other domains as a cross-domain resource in the server's domain.

The VBUILD and CDRSC statement formats follow. Separate each entry with a comma. 

VBUILD TYPE=CDRSC
name CDRSC CDRM=cdrm-name,ISTATUS=ACTIVE

An explanation of each entry follows:

VBUILD TYPE=CDRSC
specifies that this VBUILD statement defines a cross-domain resource major node.

name
specifies the name of a server or a client from another domain. This name may contain up to a maximum of eight characters, and it must be identical to that in the name field of the APPL statement for the server or the client in the controlling domain.

CDRM=cdrm-name
specifies the name of the CDRM in the domain in which the server or the client is defined as an APPL.

ISTATUS=ACTIVE
specifies that the CDRSC should be initialized as active.

Example: 

Domain 1 VTAMLST member C01CSAS:

******************************************************
* CDRSC major node for SAS/SHARE software            *
******************************************************
*----------------------------------------------------*
* CDRSCs for the SAS users in domain 2               *
*                                                    *
* The following statements are needed only if your   *
* installation is not using dynamic CDRSC definition *
*----------------------------------------------------*
    VBUILD TYPE=CDRSC
C02SI001 CDRSC CDRM=C02CDRM,ISTATUS=ACTIVE
C02SI002 CDRSC CDRM=C02CDRM,ISTATUS=ACTIVE
C02SI003 CDRSC CDRM=C02CDRM,ISTATUS=ACTIVE
C02SI004 CDRSC CDRM=C02CDRM,ISTATUS=ACTIVE
C02SI005 CDRSC CDRM=C02CDRM,ISTATUS=ACTIVE

Domain 1 contains CDRSC statements that define a corresponding pool of cross-domain resources for its clients.

The first field shows a unique eight-character client name, and the ACBNAME field shows the name of each LU in the pool, which is formed by combining the value of LUPREFIX with a value in the range between the values of the LUFIRST and LULAST options.

Domain 2 also requires a CDRSC statement to define the Domain 1 server as a cross-domain resource. 

Domain 2 VTAMLST member C02CSAS:

***********************************************
*   CDRSC major node for SAS/SHARE software   *
***********************************************
*---------------------------------------------*
*   CDRSC for the SAS server in domain 1      *
*---------------------------------------------*
   VBUILD TYPE=CDRSC
C01SHARE CDRSC CDRM=C01CDRM,ISTATUS=ACTIVE

Defining Resources within the Same Domain

Cross-memory resources are not needed for clients to access a server in the same domain. Instead, a client will access a server with the VTAM LU 0 access method.

To define resources for a server and clients within the same domain, you have two options:

An example of the second option follows: 

Domain 1 VTAMLST member C01ASAS:

*****************************************************
*   Application major node for SAS/SHARE software   *
*   Server name is C01SHARE                         *
*****************************************************
    VBUILD TYPE=APPL
*---------------------------------------------------*
*   SAS Server application running in domain 1      *
*---------------------------------------------------*
C01SHARE APPL AUTH=(ACQ),EAS=30,PARSESS=YES
*---------------------------------------------------*
*   SAS User applications running in domain 1       *
*---------------------------------------------------*
C01SI001 APPL ACBNAME=SASCON1,AUTH=(ACQ),EAS=3,PARSESS=YES
C01SI002 APPL ACBNAME=SASCON2,AUTH=(ACQ),EAS=3,PARSESS=YES
C01SI003 APPL ACBNAME=SASCON3,AUTH=(ACQ),EAS=3,PARSESS=YES
C01SI004 APPL ACBNAME=SASCON4,AUTH=(ACQ),EAS=3,PARSESS=YES
C01SI005 APPL ACBNAME=SASCON5,AUTH=(ACQ),EAS=3,PARSESS=YES

You have completed the configuration of the VTAM LU 0 access method.

References

For complete details about configuring the VTAM LU 0 subsystem, see VTAM Installation and Resource Definition (SC27-0610 for ACF/VTAM Version 2) and VTAM Installation and Resource Definition (SC23-0111 for ACF/VTAM Version 3).

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.