Previous Topic: Record the ACID and PasswordNext Topic: Bypassing Security Checking


Prompt for an Assigned ACID

If different instances of the same procedure can be started with different ACIDs with different authorities, the administrator can have the system prompt the operator for the correct ACID to run the task.

If the ACID assigned to the STC is defined with a password, then the user receives a second prompt for the password.

To allow operators, systems programmers, and production control personnel to start STCs that prompt for the ACID under which they are to run, use this model:

TSS ADDTO(STC) PROCNAME(stcname)
               ACID(PROMPT)
               [STCACT]

Now, when an operator starts this STC, the operator is prompted for the ACID supplied on the CREATE command and under which the STC is to run. If the ACID has a password, the operator is also prompted to provide it. If the ACID/password combination is valid, STC runs under the authorizations associated with this ACID. If an undefined ACID or an incorrect password is used, then the STC fails immediately.

When STCACT is designated, an initial TSS7152A message prompts the operator for their own ACID and password. This provides accountability for entering the START command for this task. The accountability ACID and password are usually separate from the PROMPT ACID and password under whose authority the task will execute. The accountability ACID cannot have NOPW as a password.