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 resources that enable the OS/390 system to behave as either a local host or a remote host in a SAS/CONNECT session when using the APPC access method.

To configure the APPC system perform the following tasks:

  1. Define an LU pool.

  2. Add entries to the logon mode table.

  3. Define the OS/390 host as a remote host, if necessary.

This section highlights the tasks that you perform to configure a system for the APPC access method. For full details about configuring the APPC subsystem, see References for a list of related documents. For full details about configuring an OS/390 remote host, see MVS/ESA Planning: APPC Management (GC28-1110).

Defining an LU Pool

Specify APPL statements to define a pool of LUs from which an LU is dynamically selected for a connecting local host. Use a comma to separate each entry.

A sample APPL definition follows: 

N02SVnnn  APPL   APPC=YES,
              AUTOSES=1,
              DDRAINL=NALLOW,
              DLOGMOD=mode-table-entry,
              DMINWNL=16384,
              DMINWNR=0,
              DRESPL=NALLOW,
              DSESLIM=32767,
              EAS=3,
              MODETAB=mode-table,
              SECACPT=CONV,
              VPACING=n

An explanation of each entry follows:

NO2SVnnn
specifies the LU name, which is formed by the values of the LUPREFIX, LUFIRST, and LULAST options. These options are used to form the name of the pool of LUs from which an LU is dynamically selected. See SAS/CONNECT and SAS/SHARE Options for more information about these options and how they are used to name an LU pool.

APPL
declares an APPL definition statement.

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

AUTOSES=1
tells the APPC subsystem how many sessions to start automatically after CNOS (Change Number of Sessions) negotiation.

DDRAINL=NALLOW
does not allow the application to drain its allocation requests during shutdown.

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

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

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

DRESPL=NALLOW
requires the remote partner to deactivate sessions.

DSESLIM=32767
defines the maximum session limits.

EAS=3
specifies the estimated number of sessions that are active with this logical unit at any given time.

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

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

VPACING=n
sets network requirements per site.

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

Defining the Logon Mode Table Entries

A logon mode table contains one or more sets of session properties that contain session protocols, which characterize how the session is conducted. These entries 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 Technical Reference 5, VTAM Customization for complete information.

A typical logon mode table, which contains three sets of session properties, is shown here. 

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

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

MAPPCDEP MODEENT LOGMODE=MAPPCDEP,
                 FMPROF=X'13',
                 TSPROF=X'07',
                 PRIPROT=X'B0',
                 SECPROT=X'B0',
                 COMPROT=X'50B1',
                 RUSIZES=X'xxxx',
                 PSERVIC=X'060200000000000000102C00',
                 COS=name,
                 TYPE=0

Note:   The SNASVCMG entry is required to support SNA services that are initiated through a boundary NCP. Although the MAPPCIND entry specifies a parallel session and CNOS support for independent LUs, the MAPPCDEP entry for dependent LUs does not. Both examples specify access security field acceptance. The RUSIZES and COS settings are site-specific.  [cautionend]

If you do not intend to use an OS/390 host as a remote host, then you have completed the APPC system configuration.

Configuring an OS/390 Remote Host

You must perform additional tasks if you plan to use the OS/390 host as a remote host in a SAS/CONNECT session with a local host that is one of the following types:
CMS
OS/390
OS/2 (without TSO logon)
UNIX (AIX, HP-UX, Solaris)
VSE
Windows NT, Windows 95, Windows 98, Windows 32s

These types of connections depend on SAS/CONNECT MVS/ESA APPC/MVS subsystem capabilities.

To configure an OS/390 remote host, perform the following tasks:

  1. Define the VSAM transaction program profile data set to be run when a local host attempts to connect to an OS/390 remote host.

  2. Define the transaction program profile.

  3. Define a class name for the SASRMT transaction program.

  4. Define and activate a target LU.


Defining the VSAM Transaction Program Profile Data Set

Run the IDCAMS utility to define the VSAM transaction program (TP) profile data set. This program creates a KSDS VSAM cluster, which defines the TP profile. An example follows: 

DEFINE CLUSTER  ( NAME ( vsam.profile.dataset ) -
                 VOLUME ( volser ) -
                 KEYS ( 112 0 ) -
                 RECORDSIZE ( 248 4000 ) -
                 RECORDS ( 100 100 ) -
                 SHAREOPTIONS ( 3 3 ) -
                 INDEXED REUSE ) -
         DATA    ( NAME ( vsam.profile.data ) ) -
         INDEX   ( NAME ( vsam.profile.index ) )

The data set member ATBTPVSM, which is located in the SYS1.SAMPLIB data set, contains other examples for creating this type of data set.

Defining the Transaction Program Profile

Run the APPC/MVS administrative utility ATBSDFMU to define the TP profile. An example of a TP profile follows: 

//UPDTTPSI EXEC PGM=ATBSDFMU
//SYSPRINT DD SYSOUT=*
//SYSSDLIB DD DSN=vsam.profile.dataset,DISP=SHR
//SYSSDOUT DD SYSOUT=*
//SYSIN    DD DATA,DLM=$$
TPADD
     TPNAME(SASRMT)
     SYSTEM
     ACTIVE(YES)
     TPSCHED_DELIMITER(SCHEND)
     TAILOR_SYSOUT(YES)
     TAILOR_ACCOUNT(YES)
     CLASS(xxx)
     JCL_DELIMITER(JCLEND)
//SASRMT  JOB 'REMOTE SAS',MSGLEVEL=(1,1)
//   JCLLIB ORDER=(your.proc.library)
//   EXEC  copySAS
JCLEND
     KEEP_MESSAGE_LOG(ALWAYS)
SCHEND
$$

Note that the utility SYSIN input includes embedded JCL. The APPC/MVS transaction scheduler uses this JCL to invoke the SASRMT TP profile, which starts a remote SAS application on an OS/390 host by executing a SAS cataloged procedure. You must specify the DSN of the cataloged procedure library where your SAS procedure resides in the JCLLIB statement of this JCL.

If users on local hosts do not need to specify SAS options when invoking a remote SAS session, you can specify your standard SAS cataloged procedure in the preceding EXEC statement in the SASRMT JCL.

However, if users on local hosts do need to specify options when invoking a remote SAS session, you must set up a separate cataloged procedure, such as the following sample APPCSAS procedure. The cataloged procedure refers to a user-specific configuration file that has the system symbolic parameter &SYSUID. 

//APPCSAS  PROC USER=&SYSUID
//SAS  EXEC PGM=SASHOST,REGION=4096K
//STEPLIB  DD  DISP=SHR,DSN=prefix.LIBRARY
//CONFIG   DD  DISP=SHR,dsn=&USER..SASRMT.CONFIG
//         DD  DISP=SHR,DSN=prefix.CNTL(BATCH)
//SASHELP  DD  DISP=SHR,DSN=prefix.SASHELP
//SASMSG   DD  DISP=SHR,DSN=prefix.SASMSG
//WORK     DD  UNIT=3380,SPACE=(CYL,(1,1)),
//
DCB=(RECFM=FS,LRECL=6144,BLKSIZE=6144,DSORG=PS) 
//SASLOG   DD SYSOUT=A,DCB=(BLKSIZE=141,LRECL=137,
                            RECFM=VBA) 
//SASLIST  DD SYSOUT=A,DCB=(BLKSIZE=141,LRECL=137,
RECFM=VBA) 
//SYSIN    DD  DUMMY

Defining a Class Name for the SASRMT Transaction Program

Create an ASCHPMxx member in the SYS1.PARMLIB data set, where xx is a two-character identifier for the member that defines the CLASS name for the SASRMT transaction program (TP). The MAX() parameter determines how many SAS SASRMT TPs can be initiated at a given time. Set MAX() to the maximum number of sessions that may be simultaneously initiated.

An example follows: 

CLASSADD CLASSNAME(xxx) MIN(1) MAX(10) RESPGOAL(1)

where xxx specifies the class name that is in the site-specific transaction program profile.

Defining and Activating an LU

To define and activate an LU, perform the following tasks:

  1. Create an APPCPMxx member in the SYS1.PARMLIB data set, where xx is a two-character identifier for the member that defines the LU for connecting local hosts.

    This LU name is the value supplied to the REMOTE= option in both the local and remote SAS/CONNECT sessions.

  2. Create a statement to specify the target LU name. An example follows: 
    LUADD ACBNAME(N01APL00)
TPDATA(vsam.profile.dataset)
TPLEVEL(SYSTEM)

  3. In addition to defining an LU pool using the example in Defining an LU Pool, you must also create another APPL statement to define a VTAM application node for an LU that is dedicated to APPC/MVS .

    An APPL statement is used for each member within the pool and for the APPC/MVS dedicated LU. The dedicated LU is also referred to as a scheduler LU and as the APPC/MVS LU.

  4. To activate the LU to APPC/MVS, use a START or SET APPC command to specify the xx identifier.

You have completed the OS/390 remote host configuration.

References

For complete details about how to install and configure the APPC system, refer to the following documents:
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.