NODES Resource Class— Control NJE Jobs and SYSOUT

Resources › NODES Resource Class— Control NJE Jobs and SYSOUT

NODES Resource Class— Control NJE Jobs and SYSOUT

Valid on z/OS and z/VM.

Use NODES to control incoming NJE jobs and SYSOUT, and optionally, to assign a userid as the owner of the job or SYSOUT on this system.

When used with TSS ADDTO/REMOVE, this resource class has the following format:

TSS ADDTO(acid) NODES(node,...)

Prefix length: Two to twenty‑six characters
Capacity of list: One to five node names or prefixes per TSS command

Generic prefixing allows the administrator to group a set of similar nodes together, and define them by one generic prefix.

When used with TSS PERMIT/REVOKE, this resource class has the following format:

TSS PERMIT(acid) NODES(node(s))
                 ACCESS(levels)
                [NJEACID(acid)]

Prefix length: Two to forty‑four characters
Capacity of list: One to five nodes per TSS command

Note: A fully qualified node is PERMITted to an ACID by enclosing in single quotation marks. This will indicate that it is defined to CA Top Secret, not as a prefix, but by its fully qualified name.

This keyword is used with:

The commands CREATE, ADDTO, REMOVE, PERMIT, REVOKE, ADMIN, DEADMIN, WHOOWNS, and WHOHAS
The NODES ACID types User, Profile, Department, Division, Zone, DCA, VCA, ZCA, LSCA, SCA, and MSCA when used with TSS ADD/REMOVE
The NODES ACID types User, Profile, DCA, VCA, ZCA, LSCA, SCA, and MSCA when used with TSS PERMIT/REVOKE
NODES(OWN) authority to ADD or REMOVE ownership of nodes from ACIDs

The administrator can:

Use any of the following methods to control access to data sets: Expiration, Facility, Program Pathing, Time/Day, and Actions.
Specify the access levels: CONTROL, NONE, READ, and UPDATE. If ACCESS is not specified, CA Top Secret defaults to ALL access.

Masking

Node masking is another method of reducing the number of node definitions to implement widespread node protection.

Examples: NODES resource class

This example gives USER01 ownership of jobs submitted from ALPHA2.USERJ:

TSS ADDTO(USER01) NODES(ALPHA.USERJ*)

This example removes ownership:

TSS REMOVE(USER01) NODES(ALPHA.USERJ*)

If node ALPHA is not allowed to execute jobs on node ALPHA.USERJ:

TSS PERMIT(ALL) NODES(ALPHA.USERJ.) ACCESS(NONE)

If an exception is made for userid X123:

TSS PERMIT(ALL) NODES(ALPHA.USERJ.X123) ACCESS(UPDATE)

If any job submitted from node BETA is to run without any password checking:

TSS PERMIT(ALL) NODES(BETA.USERJ) ACCESS(CONTROL)