Valid on z/OS.
Use the SUBACID control option to indicate how CA Top Secret derives an ACID for batch jobs that are submitted by the following methods:
All entry methods are accepted.
This control option has the following format:
SUBACID(J|U,n)
Indicates that the first n characters of the jobname parameter on the job card is used as the ACID, unless USER=acid is present.
Specifying SUBACID(J,7) restricts jobnames to the user's userid plus one character. This will occur unless the user is explicitly PERMITted to submit other ACIDS.
Indicates that the first n characters of the logged on user's ACID, or of the ACID associated with the started task, is used as the ACID for the batch job.
Default: SUBACID(U,7).
SUBACID only applies to jobs issued through an internal reader. It does NOT apply to jobs submitted via remotes, nodes, or local readers.
CA Top Secret uses settings for the JOBACID and DEFACID control options to derive ACIDS for jobs issued from physical card readers or NJE and RJE remote readers. For information, see JOBACID or the DEFACID suboption of the FACILITY control option.
The following algorithm assumes that the JES control option is set to JES(NOVERIFY).
This indicates that the JES Early Verify feature is not in effect. In FAIL mode, all jobs must have an ACID in order to be processed by CA Top Secret.
If IBM's JES Early Verify feature is active (JES(VERIFY) control option is set), then jobs submitted through TSO is checked for valid USER and PASSWORD specification as part of job submission. CA Top Secret will not insert USER= or PASSWORD= as described in the algorithm. The job will run under the signed‑on User's ACID if USER= is the same as the TSO userid.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|