Patching Job - Analysis options for AIX


A Patching Job checks the configuration of patches on specific servers according to the filters defined as part of the job definition.

Note

A Patch Analysis Job on AIX does not show any fileset or BFF file dependency issues in the analysis log files and the Deploy Job might fail. You must ensure that all the required filesets and BFF files are installed on the target computer.

You can create an Include/Exclude List for specific patch containers (PTFs or APARs) through the Include-or-Exclude-Selection dialog box, or choose from one of the following options:

Analysis Option

Choose one of the following options for the Patch Analysis:

  • Stop Analysis if any applied fileset found
    Stop analysis on any target server that has filesets in the applied state (installed but not committed).
  • Use Patch global configuration settings
    Use the settings in the Global configuration parameters.
  • Continue Analysis if any applied fileset found
    Continue analysis on any target server that has filesets in the applied state (installed but not committed).

Analysis Mode

Choose either Install Mode or Update Mode.

For AIX, the Patch Analysis Job fails in the Install Mode because of missing rpms in the repository. A single repository will contain updates for all available packages. The Install Mode is intended to install new packages on the target. Hence, BMC recommends the use of Install Mode on selective packages, rather than using the Install Mode on the complete repository.

Upgrade Installp during analysis

 

Depending on how you want to upgrade the ‘bos.rte.install’ package, choose one of the following options:

  • Skip: The ‘bos.rte.install’ package on the target is not upgraded.
  • Apply: The ‘bos.rte.install’ package on the target is upgraded to the later version available in the catalog during the analysis. ‘bos.rte.install’ is deployed on the target in the applied state.
  • Apply and Commit: The ‘bos.rte.install’ package on the target is upgraded to the later version available in the catalog during the analysis. ‘bos.rte.install’ is deployed on the target in the committed state.

Note: Using Apply and Apply and Commit options, the Patch analysis is done in one pass only.

Additional Installp option

(Optional)

 

Enter any additional options that you want to use with the Installp command. By default, TrueSight Server Automation passes the following options: -V -e -p -a -Y -g -d -f to the Installp command.

Warning:

  • The options that you enter here are passed in addition to the default options passed by TrueSight Server Automation. You cannot modify these default options.
  • The options entered in this field are directly passed to the Installp command.

New in 8.9.03.001Analyse with efix/ifix

Select this option if you want to run the patch analysis job when an eFix/iFix is installed on the target machine. The efix must be part of a service pack. By default, the checkbox is not selected.

Note: If the eFix on the target server machine is not part of a service pack, BMC recommends you to remove the efix and execute the analysis job.

Group

Select to use the entire patch catalog for patch analysis.

List

Create an Include List or an Exclude List, depending on your requirements. For an APAR or PTF-based catalog, you can create an Include List for specific APAR or PTF IDs. You can also create an Exclude List for a specific fileset. Use this option if inclusion of the fileset would lead to deployment failure, such as if the fileset had dependency issues, whereas exclusion of the fileset would result in successful analysis and deployment.

Analysis of a specific APAR or PTF includes the entire service pack. Therefore, the version of the target server is upgraded to the same version as the service pack that was analyzed.
Note: Exclusion is the only action you can perform at the fileset level.


Where to go from here

Patching-Job-Remediation-Options

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*