Defining nodes as local input sources

You can use RACF® to treat nodes the same as locally attached devices. To do this, use the &RACLNDE profile in the RACFVARS class to identify the nodes that you want RACF to consider as local. See Setting up NODES profiles. A node name defined to &RACLNDE either shares your RACF database or is the value you are using to rename your node when you are changing node names.

To do this perform the following steps:

Ask your JES system programmer for the names of the nodes to be treated as local.
Define profile &RACLNDE in class RACFVARS:
```
RDEFINE RACFVARS &RACLNDE UACC(NONE)
```
Using the ADDMEM operand on the RALTER command, identify which nodes are to be treated as local nodes:
```
RALTER RACFVARS &RACLNDE ADDMEM(node1 node2 node3…)
```
Note:
1. If you define a node as a local node, you must ensure that its RACF database is identical to the one on your node.
2. Because there are no defaults for &RACLNDE profiles in the RACFVARS class, you must identify your own local node using the ADDMEM operand.
When you are ready to start using the protection defined in the profiles, activate the RACFVARS class and activate SETROPTS RACLIST processing for the class. You can do these two actions in one command:
```
SETROPTS CLASSACT(RACFVARS) RACLIST(RACFVARS)
```
Note:
1. Any time you make a change to a RACFVARS profile, you must also refresh SETROPTS RACLIST processing for the RACFVARS class for the change to take effect.
2. This also activates other functions that are administered through the RACFVARS class.