Running FF Stand-alone DB Sensor

To run FF Stand-alone DB Sensor, code DB Sensor JCL statements and submit the job.

Before you begin

Ensure that the following components are available:

  • If you want to store sensor data or reports in the IMS Tools KB repositories, ensure that the IMS Tools KB server and all the repositories, including the Sensor Data repository, are available.
  • If you want to run DB Sensor for online databases to retrieve the latest VSAM statistics, make IMS Tools Online System Interface configuration available.
  • If you want to run DB Sensor and a policy evaluation by using the Autonomics Director scheduling calendar, start the Autonomics Director servers.

To make these components available, see the following information:

  • IMS Tools Base Configuration Guide
  • IMS Tools Base IMS Tools Common Services User’s Guide
  • IMS Tools Base Autonomics Director User’s Guide
Tip: Stand-alone DB Sensor provides the Site Default Generation utility. You can use this utility to set your own default values for your site. See Setting site default values for FF Stand-alone DB Sensor for information about setting default values.

Procedure

  1. Write the EXEC and the DD statements.

    See EXEC and DD statements for FF Stand-alone DB Sensor for information about the format of the EXEC statement and the input and the output DD statements.

  2. Specify the GLOBAL command and keywords in the BBESIN DD.

    The GLOBAL command controls the behavior of the job.

    See GLOBAL command keywords for FF Stand-alone DB Sensor for information about the keywords that can be specified for the GLOBAL command.

  3. Specify the DATABASE commands and keywords in the BBESIN DD.

    The DATABASE command specifies the database to process.

    See DATABASE command keywords for FF Stand-alone DB Sensor for information about the keywords that can be specified for the DATABASE command.

  4. Submit the job.

    Ensure that the return code is 0. If the return code is other than 0, check the write-to-operator (WTO) messages or the messages that are printed in the Runtime Summary report, and take the appropriate actions by referring to the troubleshooting information.