Creating monitor definitions

About this task

To create an output queue monitor definition:

Procedure

  1. Access IBM Navigator for i.
  2. Click Content Manager OnDemand, and verify the current instance.
  3. Click Output Queue Monitors and then click Add.
    You can also create directory monitor definitions, but the system configuration example that is described previously uses an output queue monitor to archive spooled files.
  4. When the Output Queue Monitor Definition window appears, the general page will be displayed. Specify the name and library of the output queue to monitor.
    For this example, specify the output queue as MONITORQ in library MYLIB. The job name is automatically set to the same name as the monitored output queue you specified. This can be changed, but for the example leave it blank so that the job name is set to MONITORQ. You can also provide a brief description for the output queue monitor definition. For this example, leave the default job description name and library, or click Browse to select a different job description.

    When the monitor job selects a spooled file from the specified output queue for processing, it needs to determine which application group to associate with the spooled file so that the file can be archived correctly. The only data available to the monitor are the attributes of the selected spooled file. The application group name must be derived from the contents of one of these attributes.

  5. Use the pull down to select the attribute that the monitor should use for comparing to find the application group with the matching name.
    For the example, use Spooled file name. You can also specify what the monitor should check next and last if it does not find a match on check first. In this example, leave Check next and Check last with the default value of (none).
  6. You can check the box to have the monitor job determine the application name used or you can specify what the monitor should check for comparing to find the application name.
    In this example, check the box and let the monitor job determine the application name.
  7. Once the general page has been completed you can click on the Start and End Method tab.
    There are several options for starting and ending the monitor job. Accept the defaults for this example which are to start and end the monitor manually. However you can specify whether the monitor will be started from a job scheduler or when a subsystem starts. You can also specify to have the monitor job end at a specific time of day, after a certain period of time, after all entries have been processed from the output queue, or you can specify the end time as a parameter when the monitor is started.
    Tip: The first time you start a monitor for a particular output queue, it is best to do it when there are no spooled files in the output queue. When a monitor is started for the first time, an empty data queue with the same name as the output queue is created, which will receive entries for all spooled files that appear in the output queue in Ready status. Once the output queue monitor has been started (and therefore the data queue has been created), you can then begin moving the spooled files that you want to capture into the output queue. The data queue entries that get created will trigger the monitor to process each spooled file.
  8. Next click on the Actions To Take After Archiving tab.
    This specifies what Content Manager OnDemand should do with a spooled file once it has been processed. If the spooled file is processed successfully, the options are to have it deleted from the system or moved to an output queue you specify. In the example, the spooled file will be moved to a processed output queue called PROCESSED in library QUSRRDARS. You must also specify where you want the spooled files to be sent should they fail to process. In the example, specify ERROR in library QUSRRDARS as the error queue.
  9. Click OK to create the output queue monitor definition.