Defining SMCS to VTAM

To define the SMCS application to VTAM®, you must update the ATCCONxx member of SYS1.VTAMLST to point to a member of SYS1.VTAMLST that defines the SMCS application id (APPLID). You could write the SMCS application definition as:

     SMCS    VBUILD TYPE=APPL
     SMCS&SYSCLONE. APPL

You can also choose to specify DLOGMOD and MODETAB, but you should take defaults for all other keywords. Each system within the sysplex that will run SMCS must have a unique application name. See z/OS Communications Server: SNA Resource Definition Reference for more details.

A LOGON mode table can be provided to define the session protocols for devices that will be used as SMCS consoles. Each LOGON mode table is assembled and link-edited into SYS1.VTAMLIB. In most cases, the same LOGON mode table that is used for TSO will be suitable for SMCS.

The DLOGMOD and/or MODETAB specifications indicate which LOGON mode table to use. The specifications can be made on:

The APPL statement pointed to by ATCCONxx.
The LOCAL statement when defining local non-SNA major nodes.
The LU statement when defining SNA major nodes.

See z/OS Communications Server: SNA Resource Definition Reference for details.

If certain devices are always used for SMCS, they can be defined to automatically log on to the SMCS application when the device becomes active using the LOGAPPL keyword on the LOCAL or LU statements:

     LOCALDEV LBUILD
     S&SYSCLONE.D3E0 LOCAL CUADDR=3E0
                    TERM=3277,
                    FEATUR2=(MODEL2),
                    ISTATUS=ACTIVE,
                    USSTAB=USSCNH,
                    DLOGMOD=S3270,
                    LOGAPPL=SMCS&SYSCLONE

Figure 1 shows a sample LOGON mode table entry. Table 1 defines the keywords in the LOGON mode table entry, and the values that SMCS expects. Table 2 provides details about the values to specify for the PSERVIC keyword.

Figure 1. Sample LOGON Mode Table Entry

**********************************************************************
*                                                                    *
*        DYNAMIC LOGMODE ENTRY FOR SNA                               *
*        3270 DISPLAYS (APPLIES TO QUERIABLE TERMINALS)              *
*                                                                    *
**********************************************************************
DYNSNA   MODEENT LOGMODE=DYNSNA,COS=INTERACT,APPNCOS=#INTER,
               FMPROF=X'03',
               TSPROF=X'03',
               PRIPROT=X'B1',
               SECPROT=X'90',
               COMPROT=X'3080',
               RUSIZES=X'87F8',  * OUTBOUND 3840     INBOUND 1024
               TYPE=1,
               PSERVIC=X'028000000000000000000300'

Table 1. Keyword Definitions
Keyword	Definition	Local Non-SNA Value	SNA Value
FMPROF	Function Management Profile	X'02'	X'03'
TSPROF	Transmission Services Profile	X'02'	X'03'
PRIPROT	Primary LU Protocol	X'71'	X'B1'
SECPROT	Secondary LU Protocol	X'40'	X'90'
COMPROT	Common LU Protocol	X'2000'	X'3080'
RUSIZES	Maximum length of data in a request unit	X'0000'	X'87F8' The X'87' indicates a 1024–byte maximum secondary logical unit RU send size and the X'F8' indicates a 3840–byte maximum primary logical unit RU send size.
TYPE	Bind type	1	1
PSERVIC	LU Presentation Services Profile	X'008000000000185000000300'	Value depends on the device type. See Table 2 for values.

Table 2. PSERVIC Values for SNA Devices
Byte	Value	Definition
1	X'00' or X'02'	LU type 0 or LU type 2. LU0 indicates that the session protocol is determined by the application. SMCS will use LU0 for non-SNA locally attached 3270 data stream devices. LU2 indicates that the session protocol is for an SNA 3270 data stream device. SMCS will use this for SNA locally or remotely attached devices.
2	X'80'	Indicates that query is supported. This is the recommended value for byte 2 whenever possible. If X'00' is specified, the alternate screen size may be required depending on the presentation space size indication.
3,4,5,6	0	These must be zero.
7,8	X'0000'	Screen size when in default presentation space size (24 rows x 80 columns).
9,10	Possible values: X'0000' X'1850' X'1B84' X'2050' X'2B50'	Screen size when in alternate presentation space size. This value depends on the specification in byte 11 and the device type to be used as an SMCS console. Byte 9 (number of rows) is limited to 8 (X'08') through 255 (X'FF'). Byte 10 (number of columns) is limited to 80 (X'50') through 255 (X'FF'). The product of bytes 9 and 10 (rows * columns) must be less than or equal to 16,383. If both bytes 9 and 10 are zero, the screen size is determined by querying the device. Possible values are: X'0000' Screen size determined by querying the device. Byte 11 contains an X'03'. This is the recommended value for bytes 9 and 10. X'1850' 24 rows by 80 columns. Byte 11 contains a X'02', X'7E' or X'7F'. X'1B84' 27 rows by 132 columns. Byte 11 contains a X'7F'. X'2050' 32 rows by 80 columns. Byte 11 contains a X'7F'. X'2B50' 43 rows by 80 columns. Byte 11 contains a X'7F'.
11		Indicates which screen size should be used. Supported values are: X'02' - Screen size is always 24 rows by 80 columns X'03' - Default presentation space is 24 x 80 and the alternate presentation space is specified in the Query Reply. This is the recommended value. If this value is specified, byte 2 must contain a X'80'. X'7E' - The default screen size is to be used. X'7F' - The alternate screen size is to be used.
12	0	Must be zero.

For more information, see z/OS Communications Server: SNA Resource Definition Reference.