Job groups
When you submit a job, you can specify which job group it belongs to. If you do not specify a job group, the submitted job uses the following job group: default.
- The name must be unique among the job groups that are defined by you within the instance.
- The name must contain alphanumeric characters. You cannot use the following alphanumeric
characters:
^!#$%&'*+,/;<>=?@[]`{|}~()You also cannot use the following Unicode and hexadecimal characters:u0000;u0001-u001F;u007F-u009F;ud800-uF8FF;uFFF0-uFFFF;x{10000}-x{10FFFF}. - The maximum length for the name is 255 bytes.
default: permissions
for the jobs security object for an instance. The following example shows the
default: permissions for the jobs security object for
instance1:
$ streamtool getacl -d domain3 -i instance1 jobs # object: jobs # parent: instance # owner: nobody # persistent: yes ... default:user:owner:rwsado default:user:streamsadmin:rwsado default:role:InstanceUser:---a-- default:role:DomainAdministrator:rwsado default:role:InstanceAdministrator:rwsado
$ streamtool mkjobgroup -d domain3 -i instance1 -U jobuser groupA CDISC0170I The following job group was created: groupA. The job group was created for the instance1 instance in the domain3 domain. $ streamtool getacl -d smd3 -i instance1 jobgroup_groupA # object: jobgroup_groupA # parent: jobs # owner: joeuser # persistent: yes user:owner:rwsado user:joeuser:rwsado role:InstanceUser:---a-- role:DomainAdministrator:rwsado role:InstanceAdministrator:rwsado
default: permissions on the jobs security object. The following example shows
how to set the delete permission as a default for new job
groups:streamtool setacl -d smd3 -i instance1 default:role:InstanceUser+d jobs CDISC0019I The access control list for the instance1 instance in the smd3 domain was updated.
- ALL
- This privilege is equivalent to having add, read, write, search, delete, and own authority for the jobgroup_name instance object.
- DATAREAD
- Receive data from the jobs in the job group. This privilege is equivalent to having read authority for the jobgroup_name instance object.
- DATAWRITE
- Send data to the jobs in the job group. This privilege is equivalent to having write authority for the jobgroup_name instance object.
- JOBCONTROL
- Submit new jobs or stop jobs in the job group. This privilege is equivalent to having add and delete authority for the jobgroup_name instance object.
- OWN
- Change the permissions of the jobs in the job group. This privilege is equivalent to having own authority for the jobgroup_name instance object.
- SUBMIT
- Submit new jobs in the job group. This privilege is equivalent to having add authority for the jobgroup_name instance object.
To allow jobs to import or export data, the administrator must grant permissions by modifying the job group. The following example shows how an administrator can change the permissions for the job group to allow any jobs that are submitted by the user Alice to export data to any jobs created in the Teracloud® Streams instance:
streamtool grantjobpermission -d StreamsDomain -i StreamsInstance -J default user:Alice:DATAWRITEThe following example shows how an administrator can change the permissions for the job group to allow any jobs that are submitted by the user Bob to import data from any other jobs that are created in the Teracloud® Streams instance:
streamtool grantjobpermission -d StreamsDomain -i StreamsInstance -J default user:Bob:DATAREAD
Alternatively, you can use the streamtool setacl command to change the permissions for the jobgroup_default, or jobgroup_name security objects, where name is the name your job group. If you specify permissions that do not match the pre-defined job group permissions, they are designated as CUSTOM when you run the streamtool lsjobpermission command.