1.3.7 Job execution sequence
When multiple jobs are executed on a managed computer at the same time, the rules below govern the sequence in which they are executed. Here, jobs for which an execution time (installation date and time) is specified are referred to as scheduled jobs, and other jobs are referred to as real-time jobs.
-
Scheduled jobs are executed in order of their scheduled times.
-
Real-time jobs are executed in the order in which they were executed in Remote Install Manager.
-
When the system contains real-time jobs and scheduled jobs, if Remote Install Manager executes a real-time job before a scheduled job, the real-time job is executed before the scheduled job on the managed computer.
- Organization of this subsection
(1) Executing multiple packages according to a schedule
In some circumstances, you might need packages to be installed in a certain order. To achieve this, keep the above rules in mind and follow the conventions below when you execute each job:
-
Use the same route (via relay systems and management relay servers) to execute each job.
-
Specify the same installation mode (GUI or background) for each package.
-
If you specify When System Starts up as the execution timing of the package, the package is not installed until the managed computer is restarted. Therefore, if you want to install packages with When System Starts up specified and those with Immediately specified in a specific order in relation to each other, be careful about the timing with which the managed computer restarts.
-
If multiple packages in the same job have the same execution timing and installation mode, the packages are installed on the computer in the sequence described below.
- Basic rules for package installation sequence:
-
Packages are installed in ascending order of a character string generated from information specified in the Create Job dialog box of Remote Install Manager. This character string consists of the cabinet ID (two digits), package ID (44 digits), version (6 digits), and generation number (4 digits). When distributing several packages at once, set the cabinet IDs, package IDs, and other information in a way that results in the desired installation sequence. For example, suppose that packages called Package A and Package B are registered with the following attributes:
ID
Package A value
Package B value
Cabinet ID
'DD'
'AA'
Package ID
'AAA'
'CCCCC'
Version
'0100 '
'0100/A'
Generation number
'0000'
'0001'
String generated from these values
'DDAAA0100 0000'
'AACCCCC0100/A0001'
Because the packages are installed in ascending order of the generated string, Package B is installed before Package A.
The Package page of the Create Job dialog box lists packages in ascending order of these generated strings. This means that you can use this page to identify the sequence in which packages will be installed.
- For user programs and data and other companies' software:
-
For packages to be installed, assign package IDs in ascending order of alphanumeric characters in the ASCII encoding.
- For Hitachi program products:
-
Hitachi program products have fixed package IDs. However, you can control the installation sequence by changing the cabinet ID when you package the product. For software products to be installed, assign cabinet IDs in ascending order of alphanumeric characters in the ASCII encoding. Note that when you package products, you must keep the installation order in mind when selecting the cabinet in which each package is stored.
Also note the following points:
-
If you specify an installation date and time as a package attribute or specify an execution date and time when creating jobs, packages will not be installed in the order in which Remote Install Manager executes the jobs. If you want to control the package installation order, do not specify an installation date and time or job execution date and time.
-
Packages in background installation mode are installed before packages in GUI installation mode. If there are packages with different installation modes, use different jobs to execute them. When executing these jobs, execute one job first, and then execute the other job after the previous job has finished.
-
If you execute a job for which split distribution is specified, and another job is then started by Remote Install Manager, the latter job might be executed on the managed computer before the split-distribution job.
-
A job with Distribute specified will be executed before a job that has been suspended.