After Installing Job Management Manager › Setting Up a Proxy in AUTHORIZE database

Setting Up a Proxy in AUTHORIZE database

For job synchronization on remote nodes, an additional proxy must exist in the AUTHORIZE database of the dependent job’s node to allow that job to receive job completion synchronization messages from its predecessor jobs. You need to set up only one proxy for each node that must receive job completion messages. If the proxies are not set up, jobs with the status DEP WAIT will never run.

The proxy must define the predecessor job’s node and the account on that node under which the manager was started (usually the SYSTEM account). The proxy must be set up to access the dependent job’s node through the account on that node under which the manager was started (also usually the SYSTEM account).

To add the proxy, run AUTHORIZE as follows:

$ RUN AUTHORIZE
UAF> ADD/PROXY predecessor_job_node::pred_node_startup_account - 
UAF> dependent_job_node_startup_account/DEFAULT

For example, if the manager was started under the SYSTEM account on both nodes, type:

$ RUN AUTHORIZE
UAF> ADD/PROXY predecessor_job_node::SYSTEM SYSTEM/DEFAULT

If the manager was started under the XYZ account on the predecessor job node, type:

$ RUN AUTHORIZE
UAF> ADD/PROXY predecessor_job_node::XYZ SYSTEM/DEFAULT

If the manager was started under the account XYZ on the predecessor job node and also started under the account SMITH on the dependent job node, type:

$ RUN AUTHORIZE
UAF> ADD/PROXY predecessor_job_node::XYZ SMITH/DEFAULT