You should note the following points about split distribution:

When the higher system is UNIX:

• When the higher system is UNIX JP1/Software Distribution Manager, the split size is specified exclusively by the higher system.
• When the higher system is UNIX JP1/Software Distribution Client (relay system), split packages cannot be distributed to systems directly under the UNIX JP1/Software Distribution Client (relay system).
• When the higher system is UNIX JP1/Software Distribution Manager and a subsystem is Windows JP1/Software Distribution SubManager, the split size and distribution interval specified by the transfer destination system become valid when split packages are distributed to systems under the JP1/Software Distribution SubManager.

When multiple split distribution jobs execute concurrently:

When multiple jobs for which split distribution is specified are executing concurrently, the packages of the jobs are not transferred simultaneously between the transfer source and the transfer destinations. Jobs are run sequentially one by one. Thus, jobs that are not transferring packages are placed in package download wait status (job execution status 20%).

Notes on the method of specifying destinations

• When you intend to run an Install package job for which split distribution is specified for a relay manager or a relay system, the specified destinations must not include any relay managers or relay systems defined in the system configuration. You must always specify the destinations as clients located under a relay manager or relay system in the system configuration. If a relay manager or relay system in the system configuration is specified as a destination, regular distribution, not split distribution, is executed.
• If you use split distribution for an ID group job, the ID of the relay manager itself must be set at the local host.
• To distribute split packages of an Install package job to a relay manager or a relay system, you must specify a client on the relay manager or relay system in the system configuration as the destination. In such a case, split distribution is not performed between the relay manager or relay system and the client on the system.
• If an attempt is made to execute multiple jobs specified for split distribution at the same time, the jobs are usually executed sequentially for each combination of a source and a destination. However, if a job for which a destination is specified manually at job registration coexists with a job for which a destination is specified based on system configuration or destination information, multiple jobs may end up transferring packages concurrently.

Conditions under which package installation order is not guaranteed

If multiple packages are specified for an Install package job, they are installed in a distribution destination system in the order of cabinet IDs, package IDs, versions, and generation numbers of the packages specified for the job. However, a job for which split distribution is specified might not be maintained in that order under the following circumstances:

• The packages to be distributed to a relay manager en route to the destination have already been stored in that relay manager.
• A job for which split distribution is specified is terminated forcibly during execution.

Download display for split distribution

If the split distribution size is small, 0% may be displayed in the download message dialog on the client. If split distribution jobs are run consecutively, 0% may be displayed for jobs waiting for split distribution in the download message dialog on the client.

Forcibly enabling split distribution specified at job registration

If you use the default settings for split package distribution in the setup of a relay manager, relay system, and clients, you can forcibly transfer packages to the distribution destination systems using split distribution with the settings specified at job registration. The defaults at setup are as follows:

• The Split package and then distribute check box is selected.
• Split size: 2,097,151 KB
• Distribution interval: 1 hour

Relationship between split package distribution and Client Control facility

If split package distribution is specified and an Install package job for which client control is specified is run, the operation is as follows:

If both the Boot the client at the job destination option and the Shut down the client after the job execution option are specified:

1. The client's power is turned on.
2. The first split package is transferred.
3. The client's power is turned off.
4. Steps 1-3 are repeated.

If only the Boot the client at the job destination option is specified:

1. The client's power is turned on.
2. The first split package is transferred.
3. Packages transfer continues, and the client's power remains on.

Notes on JP1/Software Distribution Client (relay system)

The values of the split size and distribution interval specified at job creation are checked against the values specified in the setup at the lower-level systems. If they differ, split package distribution uses the smaller values. Depending on the reference time, the Job Status dialog box may display the values specified at job creation even if they are not smaller. However, this display-related problem does not affect the actual processing of split package distribution.

You should note the following points about job suspension and resumption:

• Whether or not the Suspend or Resume menu of Remote Installation Manager is enabled is determined at startup of Remote Installation Manager and when the menu is selected.
  For example, when Remote Installation Manager is started at a relay manager that is not suspended, Suspend is enabled but Resume is disabled. These menu settings are not updated even if the relay manager is suspended by an instruction from a higher system while Remote Installation Manager is being used. The menus will be updated if Remote Installation Manager is restarted or when Suspend is selected.
  
• On the Relay System Customization page in the relay system's setup and the Server Customization page in the server's (relay manager's) setup, you can specify so that Suspend file transfer and Resume file transfer jobs can be accepted from systems other than the higher system that was specified as the default connection destination. However, if file transfer is resumed from a higher system that is different from the higher system that caused the suspension, Remote Installation Manager of the latter higher system will still show Suspended for the Suspend file transfer attribute of the lower system which resumed file transfer.
• If you restart file transfer to the manager itself by choosing Remote Installation Manager's Execute menu, Suspend/Resume File Transfer, then Resume, the execution status display might change. For example, if Packager's distribution job changes from suspended status to execution status, the execution status display also changes (such as from 50% to 20%).

In an environment that does not use the job suspension facility, executing a job for which Distribute is selected has no effect. Because such a job will behave in the same way as jobs for which Distribute is not selected, the job distribution order will not change.

The following notes apply to distributing jobs to a UNIX relay system or client.

A postprocessing program has executed in the following cases:

• The specification for the postprocessing program was released by Remote Installation Manager for a package that was created with the installation date/time and postprocessing program specified by Windows Packager or the dcmpack command.
• At the UNIX client, the specification for the postprocessing program was released by Remote Installation Manager for a package that was created with the NETM_DM_GF generator type and a postprocessing program specified.

A postprocessing program has not executed in the following case:

• At the UNIX client, a postprocessing program was specified by Remote Installation Manager for a package that was created with the NETM_DM_GF generator type specified, but for which neither an installation date/time nor a postprocessing program was specified.

The job results in an error in the following case:

• At the UNIX client, the specification of the installation date/time was released by Remote Installation Manager for a package that was created with the NETM_DM_GF generator type and an installation date/time specified.