Edit your system startup command file to cause an automatic startup of the manager when your system is rebooted.
Add the following command line to the system startup file, SYS$MANAGER:SYSTARTUP_VMS.COM:
$ @SYS$STARTUP:UJM$MANAGER$STARTUP.COM
If you are activating the Integration software as well, you only need to add the following to your system startup file:
@SYS$STARTUP:CAPOLY$STARTUP
CAPOLY$STARTUP checks for the presence of each component and, if installed, will start it.
Place this new command line after the line that invokes the network startup command procedure. For example:
$ @SYS$MANAGER:STARTNET.COM . . . $ @SYS$STARTUP:UJM$MANAGER$STARTUP.COM
You may want to edit the local startup files to change default values for Max_jobs, to enable load balancing, or perform any other customization. For more information, see the Custom Startup Files. Users who are currently logged on must log off and then back on again to gain access to the Job Management Manager DCL command interface.
In addition, if you have a supported TCP/IP stack installed and you asked for remote Agent command execution support during the installation, you must place the Job Management Manager startup command after the line that invokes the TCP/IP Startup command procedure. For example, when using TCPIP Services:
$ @SYS$STARTUP:TCPIP$STARTUP.COM . . . $ @SYS$STARTUP:UJM$MANAGER$STARTUP.COM
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |