Winmostar/JM is the job manager for the Windows PC equipped with Dual Core, Quad Core, Xeon or SMP. Winmostar/JM is launched from Winmostar and provides efficient job management system for the execution of GAMESS ( WinGAMESS, Firefly(former PC-GAMESS) ) or MOPAC.
1) Launching Winmostar/JM
Upon the placement of a new
job order ( e.g., execute G03W or GAMESS ), the following JM window will pop up
showing your new job order atop the queue list marked as status waiting.
Former job list will be shifted down ward. All job orders are at first listed as
wait and then executed orderly according to their priority setting and
core number assignment.
Time stamp of the queue list is the time at which the job was placed and this will be rewrote with the new time stamp when the job become run state.
Though JM is automatically launched from WM with the new job order, it will not be halted by terminating WM operation. >refer to 7) for detail.
MOPAC can be executed either directly or through JM. In case MOPAC is executed directly, the output will be automatically transferred to WM, while in case JM is used, the output must be transferred to WM by import menu.
2) Setting MaxCores
MaxCore is the upper limit
of the number of cores that the job can occupy during the execution. Assign the
number lower than the actual core number of your PC.
For example, 3 or 4 will be a reasonable number for 4-core PC. Setting the MaxCore=3, CPU will reserve some extra power for other jobs while at MaxCore=4 you can use maximum power of your PC only for the calculation.
3) Job Sequence and direct execution
The sequence of execution
is basically from the older job to the newer. You can modify the sequence by
changing priority number. The numbers are from 0 to 9 and the smaller number has
Actual execution timing will be also governed by the core number asssignment. For example, in the sample job list shown above, job #4 is currently running with 1-core and the next job will be job#2. Since job#2 requires 2 cores, it will stay waiting until 2 cores become available after job#4 is over. If you set higher priority ( i.e., smaller priority number) to job#1, say 4, then job#1 will be executed immediately, because job#1 requires only one core and which is available while job#4 is running.
4) Suspending the jobs
Normal termination of the
job will be automatically detected by JM and status will be switched to
end. You can also terminate the job intentionally by clicking the close
button [X] of the corresponding DOS-window. Jobs may also be terminated from queue
list by entering endinto the status colum of the running job, though it
will not always effective. MOPAC2009 can be terminated only by closing
Each of the running jobs has assigned a unique name according to the start time. By cricking the job name in the queue list, corresponding DOS-window will move to the front-most position, and you can observe the progress of the job through this window.
5) Scheduling and direct execution of the jobs
You can schedule the
execution of the jobs by setting the starting time, e.g., you can set to start
jobs at midnight avoiding busy hour. Running jobs can be re-scheduled by
terminating them, then enter new starting time and change their status to
In case there are waiting jobs at the time of the starting time, all jobs having younger number will remain wait status until the scheduled job is over. This is the same situation with core-waiting jobs. Execution sequence of the waiting jobs can be modified by setting priority number.
It is recommended to check errors first by test run of jobs. For this purpose, you can execute a certain job immediately by setting status to run. The job will be executed regardless of their queue sequence or priority. The jobs in end status also switch to run for immediate execution.
6) Parallel computation
Core number for execution can be set by %nproc= in G03W or NCPUS in GAMESS. As for G03W, you need multi-thread version and maximum core number is limited up to 4 cores. Multi jobs can be executed with such parallel computation.
7) Launching and terminating JM
JM is launched when you
place a job order in WM. But JM is a separate routine from WM and, therefore, JM
will not be terminated even if you terminate WM. A new job order can be placed
from WM while other job is running. Dual launching of JM is avoided by itself
and you need not worry about double launching.
If you terminate JM from JM menu, remaining wait jobs will not be executed. You can re-start JM from [JobManager] menu of WM in case you terminate it not on purpose. Re-started JM will start executing wait jobs and collect information on end jobs. Since only one queue list is in your system, multiple job placement from different WM session will be handled properly and cause no trouble.
8) Queue list
Maximum number of job queue is 50.
If you place more than 50 jobs in the list, the oldest job will be removed from the queue list.
In case the job is running at the time the queue list is removed, the job is continue to run until it ends.
[Edit]-[Delete Job] menu or press Delete key to delete selected queue from the queue list. Changing status from wait to end, the job will never go into run-state. Execution sequence of the jobs can be modified by setting the starting time or the priorities.
9) Energy saving schedule of PC
JM will override energy
saving schedule of your PC in order to avoid your PC entering into stand-by or
sleep. Of course, you can switch to energy saving condition from your key board,
but be sure JM has no wake-up function for automatic recovery when the jobs
If you place a check mark on AutoShutdown, your PC will be automatically shut down and power-off when all jobs completed.
.........End of JM manual © X-Ability Co.,Ltd. 2012-2015 All rights reserved.