When registering a large number of job nets in a project and there are multiple job nets scheduled to be started simultaneously in the project, startup of the job nets may be delayed. Also, if a job is executed under such a heavy load, there may be a time lag between the job execution history that is recorded in Jobscheduler logs (jobdb1.log, jobdb2.log, or jobdb3.log) and the job execution history that is output with the mjsview log file output command.
The Jobscheduler manages these job nets in the unit of projects. This cause to increase the range to be searched when you register a large number of job nets in a single project. When searching for an individual job net and starting a large number of job nets simultaneously will put a heavy demand on a certain management log.
When registering a large number of job nets, distribute the job nets to multiple projects. This distributes accesses to management logs and prevents the schedule performance from being reduced.
If there are only a limited number of job net operations to be performed per day, such as when there are a large volume of jobs and job net definitions, but many of those are executed only once a month, the Master Schedule Management function can be used to prevent the schedule performance from deteriorating. This is achieved because the Master Schedule Management function extracts only the data required for the operation day from the master information to create the management book, so the size of the management book that is accessed when a job net is started is reduced.
Refer to the Systemwalker Operation Manager User's Guide - Master Schedule Management for details on the Master Schedule Management function.
Guides when registering a large number of job nets
Estimate the registered number of job nets and make sure that they are started as scheduled.
A maximum of 15000 is recommended as the number of job nets to be registered per project. However this will vary depending on the execution environment. For example, use a provisional business model in which an estimated number of job nets and the scheduled startup times are specified, and confirm in advance that the job nets are started without any problem as scheduled.
[Example] Business model
Number of registered job nets | 1,000 |
Scheduled startup time | 10:00 |
Number of job nets to be started | 100 |
If startup of any job net is delayed as a result of executing the above business model, change the business model by distributing the job nets to be started simultaneously to multiple projects and test again.
Solutions when a large number of job nets are registered
When a large number of job nets have already registered, confirm the numbers of registered job nets per project and their scheduled startup time and distribute the job nets to different projects if necessary.
Confirming the number of registered job nets
To confirm the number of registered job nets per project and their scheduled startup times, use the jobschprint -N command.
For details on the jobschprint -N command, see the Systemwalker Operation Manager Reference Guide.
Distributing job nets to multiple projects
To move job nets to different project, take the following into account.
When the job nets are started by issuing message events by the jobschmsgevent command, review the jobschmsgevent command project name.
To move the job nets registered in a group, copy all the job nets registered in the group, then configure the group again.
The following describes how to move job nets.
Copy the job nets to another project using one of the following methods.
Copy by the jobschsetnet -ncpy command
From the Systemwalker Operation Manager client's screen, select Copy Job Nets.
Among the source and destination job nets having preceding and succeeding relationship, review the job nets which can issue message events. When the job nets are registered in groups, configure again the group in which the destination job net belongs to.
Delete the job nets of the copy source project.
Enable the copy destination job nets.
If the job nets are multiple levels, use the following procedure to move them.
Output all the job nets on the first level and lower to an optional file as the definition statement, using the jobschprint -r command.
Specify the file output in the Step 1 above as the jobschsetnet command argument, and register the job nets from the lower levels to the destination project.
Delete the copy source job nets from the first level.
For details on the jobschmsgevent, jobschsetent and jobschprint commands, see the Systemwalker Operation Manager Reference Guide.
