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.

Defining BBVTASxx members for VTAM AutoLogon sessions

A BBVTASxx member can contain a LOGON command and subparameters for a VTAM AutoLogon session.

Any member is pointed to at TAS initialization by specifying the SUF keyword with the START command.

The LOGON command that is contained within a BBVTASxx member is used to specify the following subparameters for an AutoLogon session:

  • APPLID(BBVTAS)

  • TERMID(LUName), where LUName is a valid VTAM terminal LU name

  • DATA(userID/password), where:

    • userID  is a valid user ID that is defined to the external security manager (ESM) and can have at least read access to the FACILITY(BOOLEBBV) so that userID does not require a clear text password (for more information about defining security for MainView Alternate Access, see Security implementation for MainView Alternate Access).

    • password is a valid password for userID, if userID requires a password.  Passphrases and IBM Multi-Factor Authentication for z/OS (IBM MFA) are not supported.
  • OPT(x;x;x), where x;x;x is a valid option string

To define BBVTASxx members for VTAM AutoLogon sessions

  1. Read the information in Defining other LAS and TAS initialization parameter lists and follow the instructions in Step 5: Defining a default TAS initialization parameter list to create a new BBVTASxx member in UBBPARM.
  2. Use the following syntax rules to define the LOGON command and subparameters in a BBVTASxx member:
    • Each line must contain the LOGON command.

    • A single line cannot exceed 72 bytes.

    • Always begin the LOGON command in column 1.

    • Do not code comments on the same line as a LOGON command.

    • If the LOGON command and subparameter string exceeds 72 bytes, continue on additional lines by defining the LOGON command on each line that contains valid subparameters.

    • A single subparameter must be coded on one line; it cannot be started on one line and continued on another line.

    Note

    See Defining the START command for VTAM AutoLogon sessions for a description of each keyword and LOGON command subparameter.

  3. Use the SUF keyword in the START command to initialize your AutoLogon session; see Controlling TAS initialization parameters for a description of this keyword.

Examples of defining the LOGON command in a BBVTASxx member

The following examples show how the LOGON command can be defined to a BBVTASxx member for a VTAM AutoLogon session.

The default values are used in these examples, but your site might have defined other values; see Defining the START command for VTAM AutoLogon sessions for more information.

You can specify the following commands:

LOGON APPLID(BBVTAS) TERMID(S00A1432)

LOGON DATA(VEA1/VIRGINIA)

LOGON OPT(Z;1;;;;;SCR OVERVIEW;ASU 5)

As a result, the OVERVIEW screen is displayed in automatic screen update (ASU) mode set at 5 seconds, assuming user VEA1 has previously created a MainView for OS/390 screen named OVERVIEW.

Multiple ; (semicolons) are defined consecutively in the OPT subparameter value to adjust for the amount of time that a particular system might typically require to process the Connecting... message that is displayed when accessing the MainView window interface.

To invoke this AutoLogon session, you would issue the following START command:

S BBVTAS.VEA1,SUF=xx

where xx is the two-character suffix that is assigned to the BBVTASxx member containing the LOGON command

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

Comments