After Installing Job Management Manager › Entering a Proxy for Each User Account

Entering a Proxy for Each User Account

To enable WAN support via DECnet, you need to perform these three procedures:

• Create a network object
• Add an account for the network object
• Add a proxy for each cluster account or local account that will be using the manager

For the manager to function correctly with WAN support, both the network object and the corresponding account must be added, as described below. If they are not, the environment is at risk and may not function correctly.

The passwords for the SCHED_DECNET object and the SCHED$DECNET UAF account need to match in order to properly facilitate the communication between manager instances across the WAN. The commands to do this are as follows:

$ MCR NCP
NCP> define object SCHED_DECNET password yourpassword
NCP> set object SCHED_DECNET password yourpassword
NCP> exit

$ SET DEF SYS$SYSTEM
$ RUN AUTHORIZE
UAF> MOD SCHED$DECNET/password=yourpassword
UAF> exit

These commands will properly synchronize the passwords between the object and the account.

To create the network object, enter these commands:

$ MCR NCP
NCP> SHOW EXEC CHAR
NCP> SET EXEC INCOMING TIMER 120
NCP> SET EXEC OUTGOING TIMER 120
NCP> SHOW KNOWN OBJECT
NCP> DEFINE OBJECT SCHED_DECNET NUMBER 0 -_
NCP> FILE SYS$COMMON:[SYSEXE]SCHED_DECNET.COM -_
NCP> USER SCHED$DECNET -_
NCP> ALIAS INCOMING ENABLED -_
NCP> ALIAS OUTGOING ENABLED
NCP> SET OBJECT SCHED_DECNET NUMBER 0 -_
NCP> FILE SYS$COMMON:[SYSEXE]SCHED_DECNET.COM -_
NCP> USER SCHED$DECNET -_
NCP> ALIAS INCOMING ENABLED -_
NCP> ALIAS OUTGOING ENABLED
NCP> SET NODE local-node ACCESS BOTH
NCP> EXIT

To add the account for the network object, first determine a UIC that is in the same group as the default DECnet account, or is in a group by itself. Then, run AUTHORIZE as follows:

$ RUN AUTHORIZE
UAF> ADD SCHED$DECNET/FLAGS=DISUSER/UIC=uic-spec
UAF> EXIT

Enter these commands to add a proxy for each account that will be using the manager:

$ RUN AUTHORIZE
UAF> ADD/PROXY local_node::local_user local_user/DEFAULT
UAF> EXIT

Note: On cluster member nodes, this proxy needs to be added for each cluster account only, and not for each cluster node account. This configuration allows DECnet to operate in cases such as use of the following command:

$ SCHEDULE MODIFY remote-node::job1/SYNC=(local-node::job2)

Refer to the CA Job Management for OpenVMS 3.1.00 Administrator Guide for standard proxy needs and setup. Those specified here are in addition to those specified in the Administrator Guide. Both sets of instructions must be followed.