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

System Configuration for the APPC Access Method for SAS/SHARE

Network Administrator

Configure resources for the OS/390 system that allow it to behave as either a client or a SAS/SHARE server when using the APPC access method.

This section highlights the general tasks that you perform to set up the APPC access method and to configure the OS/390 host as a remote host for specific local host connections.

Configuring the SAS/SHARE Server

To configure the APPC access method for a SAS/SHARE server, perform the following tasks:

Define an LU for the server.
Define the server as a cross-domain resource, if necessary.

Defining an LU for the Server

You must define an LU for the server with an APPL statement in the APPC domain in which the server will run. All APPL statements must follow a VBUILD TYPE=APPL statement. Use a comma to separate each entry. The form of an APPL statement for a server is:

server-id  APPL      APPC=YES,
                     DDRAINL=NALLOW,
                     DLOGMOD=mode-table-entry,
                     DMINWNL=0,
                     DMINWNR=16384,
                     DSESLIM=32767,
                     MODETAB=mode-table,
                     SECACPT=CONV

An explanation of each entry follows:

server-id: specifies the name of the server, which is the value for the SERVER= option in the PROC SERVER, PROC OPERATE, and LIBNAME statements.
APPL: declares an APPL definition statement.
APPC=YES: tells APPC that the application program can issue APPCCMD macros.
DDRAINL=NALLOW: does not allow the application to drain its allocation requests during shutdown.
DLOGMOD=mode-table-entry: specifies the default name of the logon mode table entry. If you supply neither the MODETAB nor the DLOGMOD variables, the first entry in the logon mode table is used. A logon mode entry determines which entry in the logon mode table is used for providing a set of session parameters to the application program. See Defining the Logon Mode Table Entries for details about creating the logon mode table.
DMINWNL=0: specifies the minimum number of parallel sessions for a mode name group for a given remote LU of which the application program (local LU), not the remote LU, is guaranteed to be the contention winner. A mode name group is a group of sessions for a given mode name.
DMINWNR=16384: specifies the minimum number of parallel sessions for a mode name group for a given remote LU of which the remote LU, not the application program (local LU), is guaranteed to be the contention winner.
DSESLIM=32767: defines the maximum session limits allowed between the local application LU and a remote LU on a given mode name group.
MODETAB=mode-table: specifies the logon mode table to be used to associate each logon mode name with a set of session parameters for the application program. The name that you supply must correspond to the name of a logon mode table that you have already created. See Defining the Logon Mode Table Entries for details about creating the logon mode table.
SECACPT=CONV: specifies that this LU supports session requests that contain the access FMH5 security subfields.

Defining the Server as a Cross-Domain Resource

If the server will be communicating with clients in a different APPC domain, you must define the server as a cross-domain resource in the clients' domain. Use a CDRSC statement in the following form:

server-id     CDRSC CDRM=cdrm-name,ISTATUS=ACTIVE

where server-id specifies the name of the server. The server name must be identical to the name in the APPL statement for the server in the controlling domain. cdrm-name specifies the name of the CDRM in the domain in which the server is defined as an APPL.

Defining a Client LU Pool

You must define to APPC a pool of LUs for the connecting clients in the APPC domain in which the clients will run. Define this LU pool in a series of APPL statements. The APPC access method dynamically selects an available LU for a connecting client. The number of LUs in the pool should be greater than or equal to the maximum number of users that will be connected simultaneously to servers with the APPC access method.

All APPL statements must follow a VBUILD TYPE=APPL statement. Use a comma to separate each entry. The form of the APPL statement for a connecting client is

LU-name APPL      ACBNAME=LUPREFIX+length-of-LULAST,
                  APPC=YES,
                  DDRAINL=NALLOW,
                  DLOGMOD=mode-table-entry,
                  DMINWNL=conwin,
                  DMINWNR=0,
                  DSESLIM=seslimit,
                  MODETAB=mode-table,
                  SECACPT=CONV

An explanation of each entry follows:

LU-name

specifies the name of the LU pool. This name must be unique across the SNA network.

APPL

declares an APPL definition statement.

ACBNAME=LUPREFIX + length-of-LULAST

specifies the ACBNAME (minor node name assigned to this application program) that is associated with an LU pool. LUPREFIX is the name assigned to the LU pool whose size is determined by the value of the LULAST option. An ACBNAME results from combining the LUPREFIX with a value within the range defined by LULAST. See SAS/CONNECT and SAS/SHARE Options for an explanation and examples of how to name an LU pool and its members.

Although the ACBNAME parameter is not required, it is recommended that it be specified so that the ACBNAME can be shared by more than one OS/390 system on the APPC network. ACBNAMEs must be unique only within a single domain.

If you do not define ACBNAME explicitly, an LU-name is inferred from the LUPREFIX and LULAST options.

Note: This LU pool can also be used by the VTAM LU 6.2 access method for SAS/CONNECT remote sessions on OS/390 and the VTAM LU 0 access method for SAS/SHARE client sessions. [cautionend]

For definitions of all other pool entries, see Defining an LU for the Server.

You have completed the configuration of the APPC system for SAS/SHARE.

References

For complete details about configuring the APPC access method, see:

VTAM Installation and Resource Definition (SC23-0111)

For details about configuring OS/390 as a remote host, see:

MVS/ESA Planning: APPC Management (GC28-1110)

Contact IBM for information about obtaining this documentation.

Chapter Contents
Previous
Next
Top of Page