SOURCE checking for routed batch jobs using Top Secret

Products

• Top Secret

Issue/Introduction

Will a SOURCE restriction carry-over to a batch job that is routed to an LPAR that the ACID is not authorized to access?

Environment

Release : 16.0

Component : Top Secret for z/OS

Resolution

The security check to determine if the user is allowed to access the system is done before the SOURCE restriction security check.

If the user is not authorized for the remote system, the user will NOT be able to signon.So, it won’t matter if the user has a SOURCE restriction or not, since they cannot signon.

The batch job will be cancelled or pick up the batch default acid, if you have one setup with Top Secret.

If the user is authorized to submit to the remote node, authorization to the SOURCE will be granted based on the security file authorization on the remote system.

If the originating system and destination system share the same security file, then the user will have the same SOURCE restriction on both systems.

If the originating system and destination system dont share the security file, then the SOURCE restriction must also be added on the remote system's Top Secret Security File.