Starting production plan processing
About this task
- Log in as TWS_user on the master domain manager.
- At a command prompt, run the script command
. ./TWS_home/tws_env.sh
in UNIX® orTWS_home\tws_env.cmd
in Windows® to set up the environment, then run theJnextPlan
job by entering, for example on a UNIX® workstation, the following command:JnextPlan.sh -from 05/03/06 0400 tz Europe/Rome -to 06/06/06
This creates a new production plan that starts on the third of May 2006 at 4:00 a.m. (Europe/Rome time) and stops on the sixth of June 2006 at 3:59 a.m. The processing day will start at the time specified on the master domain manager in the variable startOfDay.
- When the
JnextPlan
job completes, check the status of HCL Workload Automation:
If HCL Workload Automation started correctly, the status isconman status
Batchman=LIVES
If mailman is still running a process on the remote workstation, you might see that the remote workstation does not initialize immediately. This happens because the workstation needs to complete any ongoing activities involving the mailman process before re-initializing. After the interval defined in the mm retry link parameter set in the
TWS_home/localopts
configuration file elapses, the domain manager tries again to initialize the workstation. As soon as the ongoing activities complete, the activities for the next day are initialized. For information about thelocalopts
configuration file, refer to HCL Workload Automation Administration Guide. - Increase the limit to allow jobs to run. The default job limit
after installation is zero. This means no jobs will run.
conman "limit;10"