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 the START command for VTAM AutoLogon sessions

The TAS PROC must execute from a procedure library, such as SYS1.PROCLIB.

You can start a TAS for a VTAM AutoLogon session by issuing the START command. When the START command is issued, the following messages appear on the VTAM terminal screen:

MainView ALTERNATE ACCESS LOGON IN PROGRESS
MainView Alternate Access AUTOLOGON in progress

The syntax for the START command is shown here:

S BBVTAS.<userID>[,SUF=<xx>][,P='LOGON APPLID(<applid>) TERMID(<LUName>) DATA(<userID>/<password>) OPT<x>;<x>;<x>):ACCOUNT=<value>:CAPS=<x>:DEVGROUP=<device>:SYSPREF=<prefix>']

START command parameters

Each parameter and subparameter in the VTAM START command is explained in the following table:


START command parameters for VTAM AutoLogon

Parameter or subparameter

Description

userID

(Required) Indicates the unique started task identifier for the TAS.

Use this value to differentiate one TAS task from another task that runs concurrently on your system.

When displaying active address spaces in MVS, theuser ID appears in the procedure name field.

The user ID value should be the user ID to be associated with your session, which is the same value that is defined to the DATA( user ID) subparameter.

SUF

(Required) Defines a UBBPARM(BBVTASxx) member to a START command.

The BBVTASxx member must contain the LOGON command and subparameters; otherwise, the VTAM session is not logged on.

Use the SUF keyword to point to a BBVTASxx member when the LOGON command does not fit into the amount of space that you have for defining the START command, or when you want to customize and save the LOGON command and subparameters for an AutoLogon session. BBVTASxx members provide a means of expanding the amount of space that is necessary to specify the required LOGON command subparameters with the START command.

Each BBVTASxx member for AutoLogon sessions must contain a user ID; therefore, each AutoLogon session that is started by using the SUF keyword must have a separate BBVTASxx member, or possible ISPF profile data set conflicts can result. See Step 5: Defining a default TAS initialization parameter list and Defining the START command for VTAM AutoLogon sessions for information about creating BBVTASxx members.

The following command is an example of how SUF is used in the START command:

S BBVTAS. userID, SUF=xx

See Defining BBVTASxx members for VTAM AutoLogon sessions for more information about BBVTASxx members; see Controlling TAS initialization parameters for more information about using the SUF keyword.

P

(Optional) Changes keywords and LOGON command subparameters that are specified in the BBVTASxx member that is used to initialize the session, or defines keywords and subparameters that are not specified in BBVTASxx

To define more than one value to P, separate each value with a : (colon). For example, if you define two keywords or the LOGON command and a keyword, you must use a : (colon) to separate the values.

Single quotation marks must surround the entire value that is defined to the P parameter.

See Controlling TAS initialization parameters for more information about using the P parameter. The P parameter allows AutoLogon sessions to be started by an operator, without requiring additional customization. It also provides a method of specifying different session values, such as user ID, application menu, or caps support for Katakana terminals, when starting an AutoLogon session.

When using the P parameter, the length of the START command and the entire LOGON command string might be too long to use with some methods of issuing the START command (see Understanding the methods of VTAM AutoLogon session initialization).

The following command is an example of how P is used in the START command:

S BBVTAS.userID,P='parm:parm:parm:...'

SUF and P

Are used together in a single START command to:

  • Temporarily modify one or more parameter values that are defined to a BBVTASxx member without having to edit the member
  • Define parameters or keywords that are not specified in the BBVTASxx member without having to edit the member

By defining both the SUF keyword and the P keyword in the START command, any duplicate parameter values that are defined in the operator START command override the similar parameters that are defined in the BBVTAS xx member (see xref Appendix B for more information).

The following command is an example of how SUF and P are used together in the START command:

S BBVTAS.userID,SUF=xx,P='parm:parm:parm:...'

LOGON

Required when defining the TERMID, APPLID, DATA, and OPT subparameters.

When specified in the START command, the LOGON command and its subparameters must be defined to the P keyword.

When defined to a BBVTASxx member, the LOGON command and its subparameters must be pointed to in the START command by the SUF keyword.

APPLID(applid)

Required subparameter of the LOGON command and must be defined for VTAM AutoLogon sessions, either in a START command or in the BBVTAS xx member.

The applid value is the minor node root name that is defined in the VTAM application major node definition.

TERMID(LUName)

Required subparameter of the LOGON command and must be defined for VTAM AutoLogon sessions, either in a START command or in a BBVTASxx member.

The TERMID( ) subparameter indicates to the TAS which terminal session (known as an LU to VTAM) should be initialized and logged on.

The LUName value is the VTAM address of the terminal device.

DATA(userID/password)

Required subparameter of the LOGON command and must be defined for AutoLogon sessions, either in a START command or in a BBVTASxx member.

The DATA subparameter has the following operands:

  • userID

    This required operand is the user ID to be associated with your session. The userID must be defined or the session will not initialize. Any standard ID that TSO supports is supported by MainView Alternate Access; however, the ID must be defined to your external security manager to be accepted by MainView Alternate Access.

  • /password

    This operand is the optional password that is associated with the userID operand. When defined, password must be separated from userID by a / (slash) character.

    Your userID might not require a /password, depending on how security is defined for MainView Alternate Access and userID. If a password is not required for userID, password is not a required operand of the DATA subparameter.

    • If you use password, you should be aware of the security issues concerning this operand; for more information about defining security for MainView Alternate Access, see Security implementation for MainView Alternate Access.

    • If you do not use password and the specified userID requires that a password be entered, the password panel is displayed as explained in in Using the password panel.

    • If you do use password, the password panel is skipped and you are logged on directly to your session.

    • If you are using passphrases or IBM Multi-Factor Authentication for z/OS (IBM MFA), do not use password. You must enter the information manually on the password panel as explained in Using the password panel.

OPT (x;x;x)

Optional subparameter of the LOGON command that can be defined for AutoLogon sessions, whether on a START command or in a BBVTASxx member.

The OPT subparameter contains a character string that is passed by MainView Alternate Access to the application and gets executed after the session is initialized.

The OPT subparameter value, (x;x;x), can be any alphanumeric character string that could be entered in the command field of the MainView Selection Menu, where each x is a command or menu option. Each x value in the character string must be separated by one or more ; (semicolons). Other delimiter characters might not be valid.

The maximum length of OPT(x;x;x) and its variable string is 80 bytes, but you might have fewer bytes available, depending on where this subparameter is defined. See Understanding the methods of VTAM AutoLogon session initialization for information about limitations when defined to a START command; see Defining BBVTASxx members for VTAM AutoLogon sessions for information about defining subparameters in a BBVTASxx member.

Each x value must be a MainView product menu option, view, screen, or command. Additionally, access to a MainView product results in a CONNECTING... message that requires you to define multiple consecutive semicolons (;;) in your OPT string at the point where this message occurs.

BMC Software recommends that you test your (x;x;x) value before defining it to the OPT subparameter. You can test (x;x;x) by displaying the respective menu and entering the character string to verify that it displays the view, screen, product, or service that you expect. See START command examples for examples of how the OPT subparameter can be configured.

ACCOUNT=value

(Optional) Defines a default account value that is used for job accounting; see Understanding TAS initialization parameters for more information.

When specified in the START command, ACCOUNT must be defined to the P keyword.

CAPS={YES | NO}

(Optional) Specifies Katakana terminal support; see Understanding TAS initialization parameters for more information.

When specified in the START command, CAPS must be defined to the P keyword.

DEVGROUP=device

(Optional) Specifies an esoteric device name for ISPF log, list, and profile data sets; see Understanding TAS initialization parameters for more information.

When specified in the START command, DEVGROUP must be defined to the P keyword.

SYSPREF=prefix

(Optional) Specifies a prefix for the ISPF profile data sets that is different from the user ID or the prefix that is defined in the profile for the user ID in the external security manager; see Understanding TAS initialization parameters for more information.

When specified in the START command, SYSPREF must be defined to the P keyword.

START command examples

The following examples show how the START command can be defined 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. These examples also assume that VTAM and the MainView Alternate Access major node are active, and that all VTAM terminals are varied active on the network.

Example 1

You can specify the following commands:

S BBVTAS.MAK1,P='LOGON APPLID(BBVTAS) TERMID(F099J206) DATA(MAK1 OPT(Z;1)'

As a result, the initial view or screen that is defined to the MAK1 profile is displayed or, if there is no initial display value assigned to the MAK1 profile, the default EZM390 screen for MainView for OS/390 is displayed on the VTAM terminal with an LU name of F099J206.

The following conditions must be valid for this AutoLogon session to initialize: 

  • The MAK1 user ID must have at least read access to the FACILITY(BOOLEBBV), so that MAK1 does not require a clear text password. For more information about defining security for MainView Alternate Access, see Security implementation for MainView Alternate Access.

  • This session must initialize by using the parameter list member BBVTAS00 (unless some other two-character suffix value is defined to the SUF parameter on the PROC statement in the BBVTAS proc; see Step 6: Defining a TAS startup procedure for more information).

Example 2

You can specify the following commands:

S BBVTAS.SXC2,SUF=SC,P='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 that user SXC2 has previously created a MainView for OS/390 screen named OVERVIEW.

The following conditions must be valid for this AutoLogon session to initialize:

  • This session must initialize by using the parameter list member BBVTASSC, even if some other two-character suffix value is defined to the SUF parameter on the PROC statement in the BBVTAS proc (see Step 6: Defining a TAS startup procedure for more information).

  • The BBVTASSC member must contain the LOGON command with the following subparameters defined:

    • APPLID(BBVTAS)

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

    • DATA(SXC2/SHARI), where SXC2 is a valid user ID that is defined to the external security manager (ESM) and SHARI is the valid password value for SXC2

  • The OPT(Z;1;;;;;SCR OVERVIEW;ASU 5) subparameter must be passed to ISPF even if an OPT subparameter is defined to the LOGON command in the BBVTASSC parameter list member. Any parameter that is defined in the START command overrides duplicate parameters that were defined in either the TAS proc or the parameter list member (see Cross-reference of parameters for more information).

  • Multiple ; (semicolons) must be 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.

Example 3

You can specify the following commands:

S BBVTAS.LRP1,SUF=LP

As a result, the product service or screen that is defined to the OPT subparameter is displayed.

The following conditions must be valid for this AutoLogon session to initialize:

  • This session must initialize by using the parameter list member BBVTASLP, even if some other two-character suffix value is defined to the SUF parameter on the PROC statement in the BBVTAS proc (see Step 6: Defining a TAS startup procedure for more information).

  • The BBVTASLP member must contain the LOGON command with the following subparameters defined:

    • APPLID(BBVTAS)

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

    • DATA(LRP1), where LRP1 is a valid user ID defined to the external security manager (ESM) and has at least read access to the FACILITY(BOOLEBBV) so that LRP1 does not require a clear text password

      For more information about defining security for MainView Alternate Access, see Security implementation for MainView Alternate Access.

    • OPT(x;x;x), where x;x;x is a valid option string

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

Comments