Understanding TAS initialization parameters
The default TAS initialization parameters are contained in a list member called BBVTAS00 that resides in the hlq.sysid.UBBPARM data set.
You can create additional TAS parameter list members containing other initialization parameters that also reside in UBBPARM (see Defining-other-LAS-and-TAS-initialization-parameter-lists). These other TAS parameter list members require a naming convention of BBVTASxx, where xx is a unique identifier.
A BBVTASxx member can be configured to initialize a single AutoLogon session or one or more TASs that require parameters other than those parameters that are contained in the default BBVTAS00 member; see Defining-the-START-command-for-EXCP-AutoLogon-sessions and Defining-the-START-command-for-VTAM-AutoLogon-sessions, respectively, for more information.
The TAS initialization parameters that can be defined to any list member are shown in the following table:
Parameter | Description |
|---|---|
ACCOUNT | (Optional) Defines a default account value of up to 39 alphanumeric characters This account value is used for job accounting in any job card that is generated by ISPF when an account number is not available in the security profile for the specified user ID. MainView Alternate Access cannot access the account information for a user ID in UADS, so when a user submits a job, MainView Alternate Access attempts to obtain the account information from the security profile for the user ID in the external security manager, such as RACF, CA-ACF2, or CA-TOP SECRET. If an account number is not available in the security profile or a security profile for the user ID does not exist, a TAS obtains an accounting value from this parameter. If you do not need to define a default account number, delete this parameter or leave it commented out as *ACCOUNT=. |
APPLID( ) | (Optional) Used for VTAM terminal sessions only and is discussed in Using-the-LOGON-command and Defining-the-START-command-for-VTAM-AutoLogon-sessions. |
CAPS={YES | NO} | (Optional) Determines if the TAS 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. |
DATA( ) | (Optional subparameter) Used for both EXCP and VTAM sessions and is discussed in
|
DEVGROUP={device | SYSALLDA} | (Optional) Defines a one- to eight-character esoteric device name used for dynamic allocations of any session data sets, when a device name is not available in the security profile for the specified user ID MainView Alternate Access cannot access the device name information for a user ID in UADS, so when a TAS initializes, MainView Alternate Access attempts to obtain the esoteric device name information from the security profile for the user ID in the external security manager, such as RACF, CA-ACF2, or CA-TOP SECRET. If a device name is not available in the security profile or if a security profile for the user ID does not exist, the TAS obtains the device name from the DEVGROUP parameter. If a DEVGROUP parameter is not specifically defined, and the device name is not available in the security profile, the default value for the esoteric device name is SYSALLDA, which means that data sets can be allocated dynamically to any available device at TAS initialization. Note: Your site might have devices specifically grouped for dynamic allocations, such as ISPF allocations, and might require that a particular device value be defined. BMC recommends that you specify this parameter only if you experience problems with the default allocation unit at TAS initialization. For RACF or CA-TOP SECRET sites, the device name is obtained from the security product database; for CA-ACF2 sites, the device name is obtained from the LOGONID profile. |
LOGON | (Optional) Used for both EXCP and VTAM sessions and is discussed in:
|
OPT( ) | (Optional) Used for both EXCP and VTAM AutoLogon sessions and is discussed in:
|
PHRASE={YES | NO} | (Optional) Determines whether the login screen supports pass phrases (up to 100 characters long) or supports only passwords (up to 8 characters long). If you enable pass phrases, you can enter either pass phrases or passwords; MainView Alternate Access will handle 8 characters or fewer as a password (or pass ticket). Note: Some implementations of Multi-Factor Authentication might require that you enable pass phrase support in order to enter more than 8 characters. |
SYSPREF={userID | prefix} | (Optional) Defines a one- to eight-character TSO profile prefix value for the ISPF profile data sets that are allocated to a user ID at logon. MainView Alternate Access cannot access the prefix value for a user ID in UADS, so when a TAS initializes, MainView Alternate Access obtains the prefix value from the security profile for the user ID in the external security manager. If a prefix value is not available in the security profile or a security profile does not exist, the TAS obtains the prefix value from the SYSPREF parameter. The SYSPREF prefix value must be defined when:
If a SYSPREF parameter is not defined and the prefix value is not available in the security profile, the default for the prefix value for the ISPF profile data sets that are allocated at logon is the user ID. If your site uses the user ID as the high level for ISPF profile data sets, delete this parameter or leave it commented out as *SYSPREF=prefix; if your site requires a prefix value, manually add the SYSPREF parameter to the parameter list member with a prefix value. For RACF sites, the prefix value is obtainable when TSO segment data is defined. |
TERMID( ) | (Optional) Used for VTAM AutoLogon sessions only and is discussed in Defining-the-START-command-for-VTAM-AutoLogon-sessions. |
TIMEOUT= {YES | NO | HHMM} (PTF BQY2299 applied) | (Optional) Defines a timeout value of 4 numeric characters, in the format hhmm, or alternatively, YES or NO.
If the user has AUTO REFRESH enabled with a shorter time interval than the timeout, the user will never be logged off due to the continuous activity made by AUTO REFRESH. To learn more about AUTO REFRESH, see Refreshing-view-data-in-windows-mode. If you do not want to use the timeout feature, delete this parameter, comment it out as *TIMEOUT= or set it to NO. |
UCB( ) | (Optional) Used for EXCP AutoLogon sessions only and is discussed in Defining-the-START-command-for-EXCP-AutoLogon-sessions. |
Related topic