Job Management Partner 1/Software Distribution Client Description and User's Guide

2.6.5 Required settings in distribution-destination systems and required checking at installation

This subsection describes the settings required in the distribution-destination systems before you install the distributed OS patch and the item to be checked in the distribution-destination systems at the installation of the OS patch.

Organization of this subsection

(1) Required settings in distribution-destination systems before an OS patch is installed

(2) Required settings in distribution-destination systems when an OS patch is distributed

(3) Item to be checked in distribution-destination systems when an OS patch is installed

(4) Items to be checked when JP1/Software Distribution is used to distribute an AIX Maintenance Package

(1) Required settings in distribution-destination systems before an OS patch is installed

In the PATH environment variable at the startup of JP1/Software Distribution Client, specify the folder containing the installation commands for OS patches and the options in the installation commands listed in Table 2-12.

Table 2-12 Installation commands and options for OS patches

Operating system Installation command for OS patches Option to be used

HP-UX swinstall -s, -x autoreboot=false, -x patch_match_target=true

Solaris patchadd None

AIX installp (for bff files) -a, -c, -d, -g, -q, -v, -N, -X

geninstall (for a Maintenance Package) -d, -Z, all

Specify the maximum monitoring time for OS patch installation commands. The maximum monitoring time for the OS patch installation commands is set for the following item in the settings file: the monitoring time for the external program processing for installation or external program processing after market software installation (APWatchTimer). If the processing of the installation command exceeds this time, the distribution job results in an error.

Note

Depending on how the existing OS patch was installed, the distributed OS patch may not be successfully installed. Table 2-13 describes whether a new OS patch can be installed if the same OS patch already exists.

Table 2-13 Whether a new OS patch can be installed if the same OS patch already exists

Installation status Type of distribution job

Normal installation Overwrite installation

Installed manually. N -

Installed using JP1/Software Distribution. - -

Not installed. Y Y

Legend:

N: The distribution job ends successfully but the OS patch is not installed.

-: The distribution jobs results in an error and the OS patch is not installed.

Y: The distribution job ends successfully and the OS patch is installed.

Operating system	Installation command for OS patches	Option to be used
HP-UX	swinstall	-s, -x autoreboot=false, -x patch_match_target=true
Solaris	patchadd	None
AIX	installp (for bff files)	-a, -c, -d, -g, -q, -v, -N, -X
geninstall (for a Maintenance Package)	-d, -Z, all

Installation status	Type of distribution job
Normal installation	Overwrite installation
Installed manually.	N	-
Installed using JP1/Software Distribution.	-	-
Not installed.	Y	Y

(2) Required settings in distribution-destination systems when an OS patch is distributed

To display the packages of OS patches waiting to be installed or those that are already installed in the local system, specify the u option in the rdsrsclst command and execute the command.

(3) Item to be checked in distribution-destination systems when an OS patch is installed

When the installation command for the target OS patch ends successfully, the end code is 0. Use the end code to determine whether the installation command has ended successfully.

(4) Items to be checked when JP1/Software Distribution is used to distribute an AIX Maintenance Package

If the geninstall command fails to install one or more file sets, the command returns a termination code other than 0 (normal termination) and the job results in an error. If the job has resulted in an error, check whether the necessary file sets are installed, and decide if any action is required.

You can check whether the necessary file sets are installed from the following information:

Patch installation status acquired by executing the Get installed package status job

Contents of the log file for the OS patch installation (/NETMRDS/rdsprm/OSPATCH.LOGF)

Maintenance level output by executing the oslevel command

The following explains the methods for enabling the file sets of the distributed Maintenance Package:

When you create a Distribution job for the Maintenance Package, specify that the OS is automatically restarted after installation.

After installation, manually restart the OS.

[Contents][Back][Next]

[Trademarks]