Protecting Resources › Spool Data Sets Protection

Spool Data Sets Protection

You can allow designated users to access the indicated spool data sets in an unlimited or a restricted manner.

Example: protect a spool data set

This example establishes ownership and authorizes access to the spool data set:

TSS ADDTO(DEPT01) JESSPOOL(USG203ME)

TSS PERMIT(USER01) JESSPOOL(MYNODE.USER01.JOB1.STC001.D01)

Spool Data Set Masking

Masking can be used for spool data sets. For example:

• Allowing a user to view output that belongs to him
• Giving users READ access to the spool data sets they own

Output Viewing Permission

You can give a user the authority to view output that belongs to him regardless of the originating node.

Example: view output

In this example, the first mask, *, can be any node. The second mask, %, indicates that the userid of the signed‑on user must match the userid of any job being accessed:

TSS PERMIT(ALL) JESSPOOL(*.%)
                ACCESS(ALL)

READ Access to User Spool Data Sets

You can give users READ access from a particular node to JES spool data sets that they own.

A masked spool data set is treated by CA Top Secret like a generic prefix. Any spool data set that begins with a mask is considered a match by the security validation algorithm, and the associated access authorizations are honored.

Example: access spool data sets

In this example, USG203ME is the node users can access, while % indicates that the userids must match.

TSS PERMIT(ALL) JESSPOOL(USG203ME.%)

Spool Data Sets Access Levels

The access levels that can be specified for spool data sets are:

ALL

Data set can be accessed in any way.

UPDATE

Data set can be updated; READ and WRITE access is implied.

READ

(Default) Data sets can be read.

CONTROL

Data can be requeued.

NONE

Data set cannot be used in any way.