cDSCHEDULE Automated Job Submission System Guide and Reference �ManualD

SCHEDULE
Automated Job Submission System
Guide and Reference Manual

o T Y

2.3.9 Access controls

EEach job and each directory can have a set of protection settings to 'control who can access the information.FThe access information that can be associated with each job is listed below. &
Data Description
Owner N This field indicates the UIC that controls the job. This can be either # an IDENTIFIER or a UIC code.
ACL N An Access Control List (or ACL) can optionally be associated with each job.
Protection M This field is a bitmap that grants access to the system, owner, group B and world classes. The protection bits are used as follows:

; D - Delete access allowed to the job
: W - Write access allowed to the job
9 R - Read access allowed to the job
J E - Submit, initiate or prerequisite access allowed
R The access modes are nested as follows: D -> W -> R -> E. In other D words W access gives you W, R and E access but not D.

Data	Description
Owner	N This field indicates the UIC that controls the job. This can be either # an IDENTIFIER or a UIC code.
ACL	N An Access Control List (or ACL) can optionally be associated with each job.
Protection	M This field is a bitmap that grants access to the system, owner, group B and world classes. The protection bits are used as follows: ; D - Delete access allowed to the job : W - Write access allowed to the job 9 R - Read access allowed to the job J E - Submit, initiate or prerequisite access allowed R The access modes are nested as follows: D -> W -> R -> E. In other D words W access gives you W, R and E access but not D.

EFor example, to allow everyone on the system to examine your job but Gmake no changes, grant read access at the world level. To do this just issue the following command.

"
4$ SCHEDULE MODIFY MY_JOB/GENERAL=PROTECTION=WORLD:R

=For example, to grant a specific user (SMITH in this example)Bread access to your job via an ACL entry just issue the following command.

"
D$ SCHEDULE MODIFY MY_JOB/GENERAL=ACL=(IDENTIFIER=SMITH,ACCESS=READ)

;To remove an access control list use the following command.

"
'$ SCHEDULE MODIFY MY_JOB/GENERAL=NOACL

9To view the access information use the following command.

"
-$ SCHEDULE DIRECTORY/GENERAL=SECURITY MY_JOB Job directory [JOHNSON] 1 MY_JOB[JOHNSON] S:RWEDC,O:RWEDC,G:RW,W:R # (IDENTIFIER=[SMITH],ACCESS=READ)

2.4 Configuring Schedule

>Descriptions of how to set up and configure some of the basic @operations of the SCHEDULE system are described in the following sections.;

2.4.1 Scheduling groups

GA group is all the processes and data files that are needed to perform :any scheduling function. Up to ten completely independent DSCHEDULE Systems can be running on any one computer system.@When the distribution tape is loaded a group 0 is automatically Fcreated. Each copy is given a group number between 0 and 9. A group 0 @process can talk to any other group 0 process in the cluster or Hnetwork. Each group is totally independent there is no way ¹⁰Fdata files and executable images. This separation is very useful, if, Gfor example, both a development group and a production group are using 2the same machine and total separation is required.

N Note

¹⁰ A job can be extracted from one P group and then inserted into another. Use the SCHEDULE_EXTRACT.COM

o V T Y

Contents

Index

SCHEDULE Automated Job Submission System Guide and Reference Manual

2.3.9 Access controls

2.4 Configuring Schedule

2.4.1 Scheduling groups

10 A job can be extracted from one P group and then inserted into another. Use the SCHEDULE_EXTRACT.COM

SCHEDULE
Automated Job Submission System
Guide and Reference Manual

¹⁰ A job can be extracted from one P group and then inserted into another. Use the SCHEDULE_EXTRACT.COM