NetBatch Manual

Attributes
NetBatch Manual—522460-004
7-77
LOCALNAMES Scheduler Attribute
LOCALNAMES Scheduler Attribute
The LOCALNAMES scheduler attribute makes the scheduler treat jobs submitted from
licensed requesters on specified nodes as local jobs, not as remote jobs. (An example
of such a requester is NetBatch-Plus.) The remotely submitted jobs gain, through the
scheduler, the same access privileges on the scheduler’s node as locally submitted
jobs.
remote-node
is the name of a node remote to the scheduler. LOCALNAMES can specify up to
30 remote nodes.
Specifying LOCALNAMES without remote-node in an ALTER SCHEDULER
command removes the LOCALNAMES attribute from the scheduler.
Considerations
•
The LOCALNAMES attribute can be set only by the local super ID (255,255).
•
A RUN NETBATCH cold-start command that includes the remote-node
parameter sets the LOCALNAMES attribute to the specified nodes. For example:
> NETBATCH /NAME $ZBAT, NOWAIT/ $DATA7.ZBAT ! \DEV \PROD
> BATCHCOM $ZBAT; INFO SCHEDULER, LOCALNAMES
SCHEDULER ATTRIBUTES
localnames: \DEV
\PROD
LO[CALNAMES]BBC[( AALVS1(\remote-node,( \remote-node [ ,
\remote-node ]… )))
Caution. Before specifying the LOCALNAMES attribute, consider these security-related
issues:
•
You must license remote-node requester programs before using them to submit “local”
jobs.
•
A remote-node user with access by way of a licensed requester to the scheduler’s node
gains local access to that node through the scheduler. For example, the remote-node
super ID (255,255) could have the same access privileges on the scheduler’s node as the
local super ID.
•
The file security of remote-node requester programs must restrict write and purge access
to the programs to local users. (The recommended minimum file security is “A-A-”.) This
requirement ensures that requests can be made from remote-node only. To prevent
unauthorized access to the scheduler’s node, make sure the super ID owns the programs
and secures them appropriately.