Deployment for a single Repository

The recommended procedure for deploying the Inquisitor and Usage Monitor to collect raw data is to deploy both components on every system in your organization.

After you deploy both components to each system in your organization, perform data collection in the following sequence:
  1. Use the Inquisitor Job to scan all available DASD on each z/OS System.
  2. Import Inquisitor data by running the Inquisitor Import job.
  3. Ensure that the Usage Monitor is active on all z/OS® systems, directly after IPL.
  4. Import Usage data by running the Usage Import job. Run this job after Inquisitor data has been imported.

Z Asset Optimizer displays products that have been discovered. Usage data collected from every system by the Usage Monitor is imported and usage events are assigned to the discovered products, enabling analysis of product use by system.

The first step in deploying Z Asset Optimizer is to run the SMP/E (System Modification Program/Extended) installation of the product, followed by the customization and creation of the database resources.

The next step is to create a test Repository. This deployment exercise is useful as it helps you to:
  • Gain familiarity with the product.
  • Check that your Repositories are defined correctly in terms of your business requirements and that the DASD VOLSERs and SMF IDs are unique.
  • Ensure that data-sizing is adequate.
  • Analyze the integrity of the data.

As part of this test implementation, you can then deploy the Inquisitor and Usage Monitor to all systems in your organization. It is advisable to first start the Usage Monitor on every system, in order to gather a significant amount of usage data. Place the test repository on a test or development Db2 subsystem.

At this point you can start the Z Asset Optimizer Analyzer and connect to the Repository. To verify the data collected by the Inquisitor and Usage Monitor, log on to the Analyzer and navigate to the Discovery menu tab. From this menu you can proceed to various reports on discovered products and module usage.

After you move your Repositories to their final location, you should consider setting up automation of the product.