You might want to arrange packages into multiple jobs in order to execute the jobs so that the packages are installed in a specific order. In such a case, follow the above rules, and also keep in mind the following:

• Use the same route (via a relay manager/system) to execute the jobs.
• Specify the same installation mode (GUI or background) for all the packages.
• If you specify Install when system starts as the package installation timing, the package will not be installed until the client system is restarted. Therefore, if you want to schedule the installation of one package with Normal installation specified and another package with Install when system starts specified, be careful about the client restart timing.
• In a configuration consisting of a central manager, relay systems, and clients, if a relay system contains both a job created at the central manager and a job created at the relay system itself, the job created at the central manager is executed first.
• If multiple packages are included in the same job with the same installation time and installation mode, the packages are installed at a client in the order described below.
  

  Basic rule for installing packages:

  Packages are installed in the order determined by the character strings generated by combining a cabinet ID (two characters), package ID (up to 44 characters), version (six characters), and generation (four digits) specified in the Create Job dialog box of Remote Installation Manager. The packages are installed in ascending order of the generated character strings. If you distribute more than one package at the same time, you can specify the attributes such as a cabinet ID and package ID keeping to manage the installation order. The following shows an example for installing packages A and B with the following attributes:

  Attribute	Package A	Package B
  Cabinet ID	'DD'	'AA'
  Package ID	'AAA'	'CCCCC'
  Version	'0100 '	'0100/A'
  Generation	'0000'	'0001'
  String generated from the above attributes	'DDAAA0100 0000'	'AACCCCC0100/A0001'

  Because packages are installed in the ascending order of the generated strings, package B will be installed before package A.

  The Package page in the Job Creation dialog box lists package names in ascending order of the strings generated from the four attributes. The order in which the package names are displayed is the same as the order in which the packages will be installed, so you can use this page to check the package installation order.

  For user programs and data, and other companies' software:

  Assign a package ID that is alphanumerically lower in ASCII codes than that of packages you want to install earlier.

  For Hitachi program products:

  Hitachi program products have fixed package IDs. However, you can control the installation order by changing the cabinet IDs when packaging the products. Assign a cabinet ID that is alphanumerically lower in ASCII codes than that of products you want to install earlier. Note that when you package products, you must create the cabinets keeping in mind the installation order.

  Also note the following points:
  
  • If an installation date/time was specified as a schedule attribute of the package or if a job execution date/time was specified when the job was created, packages will not installed in the order in which Remote Installation Manager executes the jobs. Therefore, if you want to control the package installation order, do not specify an installation date/time or job execution date/time.
  • A package in the background installation mode is installed before a package in the GUI installation mode. Therefore, if there are packages with different installation modes specified, execute different jobs to install the packages of the different installation modes separately. When you execute these jobs, execute one job first, and then execute the other job after the previous job has finished.
  • If a job for which split distribution was specified was started and then a job was started by Remote Installation Manager, the latter job might be executed at the client before the split-distribution job.
  • A job with Distribute specified is executed before a job that has been suspended.