Creating an AIX Patching Job

Use the following procedure to create a AIX Patching Job.

1. In the console's Folders view, expand the Jobs folder.

2. Under Jobs, navigate to an existing folder or create a new folder for your AIX Patching Job. The examples in this procedure use the folder structure Jobs\PK99\Workspace.

   Recommendation

   In a production environment, BMC recommends you create a top-level folder called Patching, and give access to that folder and the objects within it to the end users who are responsible for patching functions.

3. Right-click the folder in which you want to store the new catalog and select New > Patching Jobs > AIX Patching Job.
   
4. On the General panel, do the following:
   1. In the Name field, provide a name for this job.
   2. Optionally, in the Description field, describe the job.
   3. Verify that the auto-populated value in the Save in field is where you want to store this job. You can browse to another location if necessary.
   4. In the Specify a Catalog field, browse to a patch catalog in the Depot folder. An updated catalog must already exist. (See Creating and updating patch catalogs.)
   5. Under Number of Targets to Process in Parallel, select the number of systems on which you want the analysis Job to run simultaneously.
   6. Click Next.
      
5. On the Analysis Options panel, define the set of patches that you want to analyze.
   

   1. Choose one of the following Analysis 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).
   2. In the Analysis mode field, select either Install Mode or Update Mode:
      • Install Mode: In this mode, the patching job ensures that at least an earlier version of the patch is present on the target. If an earlier version of the patch is not found on the target then it is shown as missing.
        For example, patch abc_0.1.2.bff  is present in the catalog. If an earlier version of the patch abc_0.1.1.bff is not present on the target, the patch is shown as missing on the target.

      • Update Mode: In this mode, the patching job ensures the if the patch is present on the target, it must be the latest version of the patch.
        For example, a patch "abc_0.1.2.bff " is present in the catalog. If  an earlier version of the patch abc_0.1.1.bff is not present on the target, the patch is not shown as missing. However, If a lower version of the patch abc_0.1.1.bff is present on the target, the patch is shown as missing.

   3. From the Upgrade Installp during analysis option, select either one of the following:
      • 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 higher 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 higher version available in the catalog during the analysis. ‘bos.rte.install’ is deployed on the target in the committed state.

   4. In the Additional Installp option field, enter any additional options that you want to use with the Installp command. By default, BMC 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 BMC Server Automation. You cannot modify these default options.
      • The options entered in this field are directly passed to the Installp command.

   5. Select either Group or List.

      • Select Group to start with an entire catalog of patches. Then limit the set of patches.
      • Select List to start with one or more smart groups/Containers in the catalog. Use the Includes/Excludes filter at the bottom of the panel to include or exclude the smart groups (see Analyzing Servers for Specific Containers).
        The following example creates a AIX Patching Job that analyzes patches for group based analysis.
        
        
        
6. When you finish specifying analysis options, click Next.

7. On the Remediation Options panel, ensure that the Create remediation artifacts field is cleared, and click Next.

   Do not select Create remediation artifacts. You are running an analysis-only process at this point. You can ignore the other fields on this AIX.

   

8. On the Targets panel, select the servers that are the targets of this AIX Patching Job.
   1. In the left panel, navigate to a server smart group or to an individual server.
   2. Click the > button to move the selection from the left panel to the right panel.
   3. Continue to select groups or servers until you have a complete list of servers for the analysis.
   4. Click Next.
      
9. On the Default Notifications panel, configure default settings. The defaults are used for all runs of this job unless you override them with notification settings for a scheduled job. You can:
   • Send e-mails to one or more addresses for one or more selected job status values. To separate multiple e-mail addresses, use semicolons. By default, the e-mail includes a summary of the patch analysis, including the number of servers scanned and the number of patches missing
   • Append detailed patch analysis results with the e-mail. You can limit the size of the attachment.
   • List the servers that failed the analysis.
   • Send SNMP trap information to objects that you select using the browse button.
     
10. Click Next to continue.
11. On the Schedules panel, either:
    • Select the Execute Job Now check box to execute the job immediately after you finish creating it
    • Select a previously defined schedule from the Schedule list. (The example below does not show any items in the Schedule list.)
    • Click Add to define a new schedule and add it to the list.
      
      The Add New Schedule panel opens.
    • Define the new job schedule.
      
    • (Optional) Click the Scheduled Job Notifications tab to define notifications to associate with this job schedule. If you skip this tab, the default notification settings from Step 10 are used.
      
    • Make your selections and click OK to return to the Schedules panel.
12. Click Finish to complete the AIX Patching Job creation wizard and create your job.