An Overview of Job Management Manager › Wide Area Network Support

Wide Area Network Support

You can use Job Management Manager to control and coordinate the processing of jobs among nodes in a wide area network. Note the following requirements:

• The manager must be installed on both the sending and receiving nodes of the network.
• When you install the manager on each node, answer yes to the wide area network support question in the installation procedure.

The manager can be installed with support for executing jobs on remote OpenVMS nodes. If you want to use the manager to control jobs on one or more of these remote nodes, answer YES to this question. This feature of the manager requires that a supported TCP/IP stack is installed and running. For details on supported TCP/IP products and version, see the CA Job Management for OpenVMS Installation Guide.

The TCP/IP network startup procedure must execute before the manager startup procedure in the system startup procedure.

In a wide area network, users can:

• Enter commands for the manager on remote nodes, if they have either a proxy account or valid account and password to access the remote nodes.
• Add remote job dependencies if they have READ access to the remote jobs.

In a wide area network, system managers can:

• Set the interval and expiration time for attempting to resend job-dependency notifications between remote nodes when communication failures occur.
• Control the information that the manager enters in the event log on remote nodes.

For functions that involve timing between different nodes, such as maximum run time and start time for remote or batch mode jobs, system times must be synchronized.

The manager keeps a record of network information in two files:

NSCHED$:RETRY.LOG

This file contains a history of all network operations that the manager has retried. You can type or print this file. The system manager can delete the file when it becomes too large.

NSCHED$:RETRY.DAT

This file is present only when retry activity is pending.

The manager uses this file to control operations for resending mail notifications over the network. Deleting this file stops all retry attempts currently in progress. You cannot type or print the file. Instead, use the SCHEDULE SHOW NETWORK command to display its contents.

Remote job termination message contents are the same as regular termination messages except:

• Peak page is not used.
• BIO is total IOS.
• DIO is not used.
• Volumes are not used.

When you show a job locally, it always knows the correct exit status (success or failure) of remote mode jobs. When showing that same job from across the net, the mode can be unknown and the exit status tests for SUCCESS/FAILURE/UNKNOWN based on the status number (odd or even).

Changing the mode of a currently running job can cause the results of the current run to be improperly reported. The termination information is discarded if the job starts with one mode and exits with another. Changing can also cause some internal counters to not be properly updated, such as the number of currently running jobs. Always verify that a job is not currently running before changing its mode. Available modes are DETACHED, BATCH, and REMOTE.

Prefunctions and postfunctions are not supported for remote mode jobs, which run on remote agents. For remote OpenVMS jobs, prefunctions and postfunctions work as usual.

The following fields are not accessible remotely; to control them the user must log directly in to the remote account:

SJOB EXID QUEUE-NAME

TJOB WRID CPU-LIMIT

RDID MODE REMOTE-USER/NODE