Space banner

   

This space provides the same content as before, but the organization of the home page has changed. The content is now organized based on logical branches instead of legacy book titles. We hope that the new structure will help you quickly find the content that you need.

Understanding LAS initialization parameters

The default LAS initialization parameters are contained in a list member called BBVLAS00 that resides in the hilevel.sysid.UBBPARM data set.

You can create additional LAS parameter list members containing other initialization parameters that also reside in UBBPARM (see Defining other LAS and TAS initialization parameter lists). These other LAS parameter list members require a naming convention of BBVLASxx, where xx is a unique identifier. A BBVLASxx member can be used to initialize the LAS instead of the default BBVLAS00 member (see Controlling LAS initialization parameters for more information).

The LAS initialization parameters that can be defined to any list member are shown in the following table.

Parameter

Description

APPLID=

{applid | BBVTAS}

(required) defines the VTAM minor node root name that is assigned to MainView Alternate Access during customization.

When a VTAM terminal is signed on, this parameter determines the name of the application where the LAS is to pass the user session. The default value of the VTAM minor node root name is BBVTAS, but this value can be changed during customization.

CAPS={YES | NO}

(optional) determines whether the LAS should function with or without Katakana terminal support.

The default is NO. If you need Katakana terminal support, define YES. All MainView Alternate Access panels and messages are converted to uppercase.

If you do not need Katakana terminal support, delete the CAPS=?CAPS parameter or define CAPS=NO.

GNAME= genericName

(optional) indicates the one- to eight-character generic name that is used to define one or more VTAM version 4, release 4 or later applications.

Using a generic name increases VTAM availability; if one VTAM is unavailable, the MainView Alternate Access logon request can be handled by another VTAM.

To use a generic name on the LOGON command, specify this parameter and substitute the generic name for applid on the LOGON command (see Using the LOGON command).

To use a generic name with the abbreviated logon command, specify this parameter and substitute the generic name for ?VAPPL in the USS table entry (see Step 4: (optional) Defining logon interpret table entries).

If this parameter is specified, users can still log on to a particular VTAM application by using the applid that is specified for the APPLID LAS initialization parameter.

If you do not need generic name support, delete the GNAME=?GNAME parameter.

PROCNAME=

{procName | BBVTAS}

(required) defines the TAS proc for the VTAM session that is initiated by the LAS and then passed off to a TAS.

The default value of the TAS proc is BBVTAS, but this value can be changed during customization.

USS={YES | NO}

(optional) specifies whether MainView Alternate Access is configured with a USS table entry instead of a logon interpret table entry.

Sample entries for either table can be created during customization, but an entry must be added to the appropriate table and the table must be recompiled before customization is complete.

The default is YES. If a USS table entry is customized to your VTAM configuration, either delete the USS=?USS parameter or define USS=YES. This definition enables the abbreviated logon command (see Using the abbreviated logon command) that is defined in your USS table entry.

If a logon interpret table entry is customized to your VTAM configuration, you must specify USS=NO. This enables the abbreviated logon command (see Using the abbreviated logon command) that is defined in your logon interpret table entry; however, specifying NO also creates a requirement for defining extra characters in the DATA( ) parameter of the LOGON command when this command is issued from a VTAM terminal (see Using the LOGON command).

If no table entry exists, you can define YES or NO. If your site requires support of user logons from VTAM terminals, however, you might want to define YES so that extra characters are not required in the DATA( ) parameter of the LOGON command.

Was this page helpful? Yes No Submitting... Thank you

Comments