|
|
|
|
|
Initial Entry to Screen A
IOA checks authorization:
No distinction is made between the authority to perform actions on missions that are present in the Active Missions file, and the authority to submit a job.
This is equivalent to asking if the current user has the authority to submit jobs with USER parameter equal to that of the mission’s owner. If a user is authorized to submit a job on behalf of other users, then the user is also authorized to perform the specific action (hold, free, delete, and so on) on missions belonging to other users. If the mission’s owner is the current user, the security check is bypassed.
For RACF:
When an action is performed on missions that are present in the Active Missions file, the entity checked is owner.SUBMIT using the SURROGAT class.
For TopSecret:
When an action is performed on missions that are present in the Active Missions file, the TopSecret Application Interface module (TSSAI) is called with the following parameters:
Resource Class: ACIDCHK
Resource Name: ownerid
For ACF2/SAF:
When an action is performed on missions that are present in the Active Missions file, the entity checked is $SUBMIT.owner using the FACILITY class.
Parent Topic |