Implementing Security for STC › Automatic Logon

Automatic Logon

Automatic logon is supported for STCs (and subsystems) that are started prior to the first initialization of CA Top Secret after an IPL (these STCs later invoke security checking after it has initialized). This feature builds a security environment when the first security event takes place in that address space after TSS has fully initialized.

• CA Top Secret uses the STC Record for automatic logon, as if the started task was initialized after CA Top Secret initialization.
• Automatic logon begins when SVC security events occur. For example: RACROUTE REQUEST=AUTH, and RACROUTE REQUEST=VERIFY, ENVIR=CREATE but not RACROUTE REQUEST=FASTAUTH.
• Automatic logon is intended for primary job entry subsystems (JES2 or JES3), or console automation products such as CA‑Opera and NETVIEW.
• Automatic logon should not be used for CICS, IMS, CA‑Roscoe®, Batch initiators, or other online STCs.