Running software scans and gathering scan results on IBM i systems

Available from 9.2.5. The script that is responsible for the software scan collects the results of the catalog-based, package data, and software ID tags scan as well as retrieves results of the capacity scan and the computer.yml file. All these results are combined and compressed into a common ZIP package that can be imported to BigFix Inventory.

Before you begin

  • To perform this task, you must have *ALLOBJ authority.
  • Each time you update the software catalog in BigFix Inventory, run an import of data or wait for the scheduled import. Next download the newest version of software catalog to an endpoint to run the software scan on it. For more information, see: Preparing the disconnected scanner package..

About this task

  • The scan takes around 30 minutes. The exact time depends on the computer load, file system size, and the CPU threshold if you set it.
  • For information about default and minimal scan frequency, see: Frequency of scans and uploads of data.
  • By default, no limit is set on the processor usage during the scan. To limit processor usage, set the CPU threshold. For more information, see: Optimizing the processor utilization.


  1. Go to the directory where you uploaded the disconnected scanner package.
  2. To initiate the software scan, and pack software and capacity scan results, run the following script:

    Starting from application update 10.0.2, which includes IBM i disconnected scanner package 9.2.20, you can run the software scan and pack scan results independently.
    • To run the software scan without generating the package with scan result, run the following command:
      • SBMJOB JOB(BFI_PKG) CMD(QSH CMD('/cit/automation/'))

    • To pack scan results, run the following command:
      • SBMJOB JOB(BFI_PKG) CMD(QSH CMD('/cit/automation/'))

    The script packs results of the software scan and capacity scan generated since the last time the package with scan results was created. If no new scan results are available, the outcome is as follows.
    • The script returns error code 5.
  3. To monitor the progress of the scan, check the run_sw_and_pack_std.log file that is created during the scan in the directory where you installed the disconnected scanner, or monitor the scanner logs. For more information, see: Monitoring the scan progress


A compressed package with scan results is created in the package output directory. The default directory are:
  • /cit
Names of results packages use the following naming convention.
  • <YYYYMMDDHHMM>-<endpoint_ID>.zip

What to do next

Important: Do not change names of results packages. Otherwise, they will not be imported to BigFix Inventory.
Import the package to BigFix Inventory. After it is successfully imported, delete it from the endpoint to save disk space.