- The CANCEL= and LONGWAIT= values work together.
We recommend that you set CANCEL=YES and set LONGWAIT to a value appropriate for your site.
- LGNFMT= should either not be specified, or should be specified as the default (LGNFMT=1), unless your session manager cannot provide logon data in the normal format.
If SARVTDB= is specified, LGNFMT=1 must be specified; any VTAM logon data will be ignored.
- The LGNSEC= and LGNPROP= work together, and require the default SARUSxUX exit.
If LGNSEC=YES or LGNSEC=YESP is used (to indicate external security signon), the LGNPROP=YES/NO will be used to control whether security violations, database opens, and jobs submitted will use the user ID (LGNPROP=YES which is the default) or will use the XMS region's user ID.
It works this way:
- In the online region, the CA View database is opened before logon, and uses the XMS region's user ID.
- The CA Deliver database will be opened (read only) when the selection list processes entries that were archived through the CA Deliver system.
- Any SARBCH jobs submitted by the online will open both the CA View database (read/write) and the CA Deliver database under the authorization of the user who submitted the job.
- This authorization can be changed by doing one of the following:
Use the SARSUBUX exit to set a USERID=
Add a /*JOBFROM statement in the submitted JCL.
We recommend that you use the LGNPROP=YES to do normal user ID propagation.
- The SARVTDB= only affects VTAM access, and is only to be used when the session manger cannot produce valid LOGON DATA.
For the valid formats supported by CA View, see the LGNFMT= parameter.
- The SMFSESS= is to be specified when the user needs to collect user session statistics (CPU, logon/LOGOFF times, storage used, and so on).
- The SUBSYS= is only to be specified when you are using a non-default subsystem ID under MVS.
The default is release specific; it does not require JCL/PARM changes when you are converting to a new software release.
- Specify VGRAPPL= only to activate VTAM generic resource support.
Using generic resources allows an application to be known by a generic resource name. Users can then log on to a VTAM cross‑memory region using the generic resource name.
The VGRAPPL= parameter must be specified with the SARAPPL= parameter. For more information, see the Reference Guide.
- VTAMPASS= is only to be specified if you are going to be running a multi-region VTAM interface.
The other VTAM regions must specify the same parameters (LGNFMT= SARVDTB=, VTMQUERY=, VTMSAA=), or the interface might react in unpredictable ways.
- VTMQUERY= is to be specified either as NORM (normal) or allowed to default to that value.
VTMQUERY=NONE works, but CA View cannot detect color/high-light terminal attributes so color/high-light support will be shut off.
VTAMSAA=NO is to be used if terminals cannot support the SNA QUERY LIST command, such as the older 3270/3290 devices and some older PC/3270 emulators.
- XMS=NO is to be used when you are going to be using only the VTAM interface.
- XMS=YES (the default) must be used to provide support for these interfaces.
- XMSSUB=YES must be specified to provide support for these interfaces.
The XMSSUB=YES must reside in an XMS region with a default SUBSYS= value. If multiple XMS regions are started, only one region can have XMSSUB=YES. The other regions will still be available for user sessions, but their traffic will be routed through the region specifying XMSSUB=YES.
If you terminate the region with XMSSUB=YES, all sessions using the subtask are going to fail (that is, all TSO/XMS, ISPF/XMS, CA Roscoe/XMS, IMS/DC regions). CICS has router SUBTASK in its region, and does not use the XMSSUB=YES function.
- The OVERRIDE parameter is valid for all interfaces and is optional. It might be specified only in the execute statement PARM field and it cannot be coded in the SYSIN data set.
- If the parameter is not coded, the default duplicate parameter substitution hierarchy is SYSIN then the EXEC PARM.
- The OVERRIDE parameter determines whether parameters in the execute statement PARM field have precedence over parameters in the SYSIN data set.
- If OVERRIDE is coded in the execute statement PARM field, parameters specified in the execute statement PARM field will override duplicate specifications in the SYSIN data set.
- If OVERRIDE is not coded, parameters specified in the SYSIN data set are used and corresponding parameter specifications in the execute statement PARM field are ignored.
- The OVERRIDE parameter does not have any sub-parameters and it is coded as is in the execute statement PARM field.
- If this parameter is coded in the SYSIN data set, error message "EBCDRV99 OVERRIDE KEYWORD NOT ALLOWED IN SYSIN STATEMENTS - RUN ENDED U0016" is going to be displayed in the XMS job log and XMS will terminate with a return code of 16.
