Previous Topic: Operator Commands and Their Security Calls

Next Topic: Command Security for Consoles That Are Not Logged On

Security Considerations › Command Security › Examples of SAF Security Calls—Command Security

Examples of SAF Security Calls—Command Security

Suppose that a console operator issues an ENABLE command for the control library member BOBSPC to a CA XCOM Data Transport server that has APPLSEC=PRODXCOM in its Default Options Table. In this case, when the CA XCOM Data Transport server calls the security package, the resource name takes the following form:

XCOM.PRODXCOM.ENABLE.BOBSPC

CA XCOM Data Transport executes the ENABLE command if the security package finds the access level UPDATE defined in the security profile of the console operator issuing the command.

Next, suppose a user wants to use the ISPF menus to suspend an active transfer to LU25 running under the authority of the user ID TOM. Assume the server is started with APPLSEC=PRODXCOM. In this case, when the CA XCOM Data Transport server calls the security package, the resource name takes the following form:

XCOM.PRODXCOM.SUSPEND.LU25.TOM

Again, before CA XCOM Data Transport executes the SUSPEND command, the security package must determine that the access level UPDATE has been defined for the user ID TOM.