Installation FAQs › FAQs

FAQs

If I install a new version of Job Management Manager, what happens to the old version that was running?

The old version of the manager is superseded by the new version. During the installation, you may choose to stop the old manager and restart the new manager. From the DCL prompt, you may stop the manager by entering the following command:

SCHEDULE> STOP

The old job database is preserved across manager versions. To start the manager, run the startup procedure in the file SYS$STARTUP:UJM$MANAGER$STARTUP.COM.

After installing the manager, how do I define the command SCHEDULE?

When you install the manager on a node, only that node has the updated DCL table. The tables on the other nodes are updated when those nodes are rebooted.

You can also update the DCL tables by entering the following command from an account that has the CMKRNL privilege:

$ INSTALL REPLACE SYS$LIBRARY:DCLTABLES.EXE

You can use SYSMAN to perform this task automatically on every node on yourOpenVMS Cluster. If any users are currently logged in, they must log out and log in again for the new DCL tables to take effect for them.

When I install a new version of the manager, do I have to reenter all the jobs that are in the current database?

You should be able to use your current database. In the installation procedure, just specify the manager to be installed in the same area as before—usually SYS$COMMON:[NSCHED].

Will the manager operate in a heterogeneous cluster?

Yes. To run the manager in any cluster, follow the installation instructions to assign files to cluster common devices and to platform specific devices