Applicable versions and levels
Windows versions: V5.0L20 or later
Solaris versions: 5.0 or later
Linux versions: 5.2, V10.0L10 or later
Linux for Itanium versions: V12.0L10 or later
HP-UX versions: 10.0 or later
AIX versions: 10.0 or later
A
If you register a large number of job nets in a single project and if numerous job nets in the same project are to be started at the same time, the job nets may not be able to start on schedule.
Jobscheduler handles a group of job nets for each project. This is because registering a large number of job nets in a particular project results in a broad search scope for each job net and job. Furthermore, if a large number of job nets are started at the same time, a high access volume is concentrated on a particular management book.
To register a large number of job nets, distribute and register them across multiple projects. Registering job nets in a distributed fashion can prevent degradation in schedule performance, because access to the management book for job net information is distributed.
Guides when registering a large number of job nets
Estimate the number of registered job nets and perform a test to verify that the job nets can be successfully started as scheduled.
For example, prepare a provisional business model in which the estimated number of registered job nets and the scheduled start times are specified. Then verify in advance that the job nets can be successfully started as scheduled.
[Example] Business model
Job net registration count | 1,000 |
Scheduled start time | 10:00 |
Started job net count | 100 |
If executing the above business model causes job net startup to be delayed beyond the scheduled start time, change the business model. One way of doing this is by distributing the job nets that are to be started at the same time to multiple projects when registering them. Then verify startup again.
Action when a large number of job nets have been registered
If a large number of job nets have already been registered, check the job net registration count and scheduled start time for each project. Then distribute the job nets to another project as required.
Checking the number of registered job nets
Use the -N option of the jobschprint command to check the job net registration count and scheduled start time for each project.
Refer to the Reference Manual for information on the -N option of the jobschprint command.
Distributing job nets to multiple projects
You must consider the following points before moving job nets to another project.
If you are starting job nets by using the jobschmsgevent command to generate message events, review the project name in the jobschmsgevent command.
If moving job nets that were registered in a group, copy all the job nets contained in the group and then reconfigure the group.
Use the following procedure to move job nets.
Use any of the following methods to copy the job nets to another project:
Use the -ncop option of the jobschsetnet command to copy the job nets.
In the client window of Systemwalker Operation Manager, copy the job nets.
Review the job nets that are in a sequential relationship between copy source and copy destination and that generate message events. If the job nets are registered in a group, reconfigure the group of copy source and copy destination job nets.
Delete the job nets in the copy source project.
If the job nets are layered, use the following procedure to move them.
Use the -r option of the jobschprint command to output all job nets in the first layer and below as definition statements to any file.
Specify the file output at step 1 as an argument of the jobschsetnet command and register the job nets to the copy destination project in order, starting with the lowest job net.
Delete the copy source job nets from the first layer.
Refer to the Reference Manual for information on the jobschmsgevent command, jobschsetnet command, and jobschprint command.
