Defining CONS Event Objects

Console event objects are always in Sleeping status. They only include the Repeatedly and Repeat until first match execution options as these permanently monitor the Console.

This Event object type monitors the target system according to the specifications made in this page. The script statements and functions that are specified in the Process page are executed if conditions such as the Event ID or message filter apply.

Message filter specifications must always start with a wildcard character.

You define Console Event objects on two pages:

Console Event Page

Section Description
Console Event

Console event objects monitor the input of the following objects:

  • Console output in BS2000
  • Console output in z/OS (Multiple Console Support - MCS)
  • Message queue in OS/400
  • Events in SAP
  • Status changes of XI communication channels
  • Windows Event Viewer

Depending on the agent you select for monitoring, the input fields in this section vary:

ClosedTo Define Console Events for BS2000 Agents

  1. In Agent do one of the following
    • Select BS2000. The Agent Type dropdown list below is then disabled and displays BS2000.
    • Enter the name of an agent and select BS2000 in Agent Type below.

    You can also specify an Agent Groups (HOSTG).

  2. In the Events table specify the filter for the console output that should be searched for.

    You can use the wildcard characters "*" and "?". "*" stands for any number of characters, "?" for one specific character.

    To add/edit a row you must first click its checkbox to activate it. You have then the following options:

    Option

    Description

    Inserts a new row at the bottom of the table

    Deletes the row

    Removes the entry from the list and pastes it to the clipboard. Click Paste to add it to the bottom of the table.

    Duplicates the entry. Click Paste to add it to the bottom of the table.
    Activates all rows in the table.

To be bale to monitor BS2000 console outputs you must install the UCXEB2xU utility for the console, which should run parallel to the BS2000 agent.

ClosedTo Define Console Events for OS/390 Agents

  1. In Agent do one of the following
    • Select OS/390. The Agent Type dropdown list below is then disabled and displays MVS.
    • Enter the name of an agent and select MVS in Agent Type below.

    You can also specify an Agent Groups (HOSTG).

  2. In System Name specify a filter for the user-defined system name that can be used to distinguish various OS instances. It can be up to 8 characters long.

  3. Set a filter for the OS name as defined by IBM. Currently, it is always MVS. It can be up to 8 characters long.
  4. In the Events table specify the job (maximum 32 characters) and the filter for the console output that should be searched for.

    You can use the wildcard characters "*" and "?". "*" stands for any number of characters, "?" for one specific character.

    To add/edit a row you must first click its checkbox to activate it. You have then the following options:

    Option

    Description

    Inserts a new row at the bottom of the table

    Deletes the row

    Removes the entry from the list and pastes it to the clipboard. Click Paste to add it to the bottom of the table.

    Duplicates the entry. Click Paste to add it to the bottom of the table.
    Activates all rows in the table.

In z/OS, you can monitor the console output (Multiple Console Support - MCS). To do so, you must install the Event Monitor UCXEMxx and start it with a corresponding entry in the z/OS agent's INI file.

ClosedTo Define Console Events for OS/400 Agents

  1. In Agent do one of the following
    • Select OS/400. The Agent Type dropdown list below is then disabled and displays OS400.
    • Enter the name of an agent and select OS400 in Agent Type below.

    You can also specify an Agent Groups (HOSTG).

  2. Specify the Message Type, which can be:

    "01" - Completion
    "02" - Diagnostic
    "04" - Informational
    "05" - Inquiry
    "06" - Sender's copy
    "08" - Request
    "10" - Request with prompting
    "14" - Notify (handled exception)
    "15" - Escape (handled exception)
    "16" - Notify (unhandled exception)
    "17" - Escape (unhandled exception)
    "21" - Reply, not validity checked
    "22" - Reply, validity checked
    "23" - Reply, message default used
    "24" - Reply, system default used
    "25" - Reply, from system reply list

  3. In the Events table specify a filter for the message ID.

    You can use the wildcard characters "*" and "?". "*" stands for any number of characters, "?" for one specific character.

    To add/edit a row you must first click its checkbox to activate it. You have then the following options:

    Option

    Description

    Inserts a new row at the bottom of the table

    Deletes the row

    Removes the entry from the list and pastes it to the clipboard. Click Paste to add it to the bottom of the table.

    Duplicates the entry. Click Paste to add it to the bottom of the table.
    Activates all rows in the table.

In z/OS you can monitor message queues. Use the OS/400 agent's INI file to define the particular message queue that should be monitored

ClosedTo Define Console Events for SAP Agents

  1. Select the Agent that is connected to the SAP system and whose events should be monitored. You can also specify an Agent Groups (HOSTG).
  2. The SAP Console event distinguishes several data sources:

    • ABAP Event history

      Column Description
      Event ID

      Filters the name of the SAP ABAP event.

      Event Parameter Filters the parameter of the SAP ABAP event.
      Event Server Filters the batch server name of the SAP ABAP event.
    • Comments

      XBP 3.0 is required in order to monitor SAP events via the event type "Console". The XBP interface version that is used must be specified in the SAP agent's Connection object ( Connection Objects).

      the agent periodically polls the SAP system for occurred SAP events and reports them to the active Console events. The administrator can define the required interval in the variable UC_HOSTCHAR_DEFAULT, key JOB_CHECKINTERVAL.

      As of version 8.00A, the SAP agent always uses the XBP interface. This includes that the SAP criteria profiles must be adjusted in order to ensure that the selected triggered events are logged in the Event History. Otherwise, the Console event cannot react.

      Use the SM64 transaction in order to create a criteria profile for the Event History.

      The GET_EVENT_INFO script function provides additional information about the SAP event.

    • XI communication channels
      1. In Login select the object that contains the XI object. Use different Login objects for SAP and XI systems if both are installed on the same agent. Otherwise, the login entry would not be unique. The Login object overrules the user specified in the Connection object.
      2. Specify the event filters. You can use the wildcard character "*".

        The possible values for State are: ERROR, OK, INACTIVE, UNKNOWN and UNREGISTERED.

        The possible values for Activation state are: STARTED and STOPPED.

      To add/edit a row you must first click its checkbox to activate it. You have then the following options:

      Option

      Description

      Inserts a new row at the bottom of the table

      Deletes the row

      Removes the entry from the list and pastes it to the clipboard. Click Paste to add it to the bottom of the table.

      Duplicates the entry. Click Paste to add it to the bottom of the table.
      Activates all rows in the table.

      The filter list describes the nominal status of one or several communication channels. An event is triggered for each communication channel that

      • does not meet the nominal status when the Event object starts
      • dwitches to a different status (regardless if nominal status or different).

      No event is triggered if the communication channel meets the nominal condition when the Event object starts.

      The script function GET_EVENT_INFO supplies additional information about the XI communication channel.

    • Java event history

      Specify the event filters:

      Column Description
      Event Type

      Filter for the type of SAP Java Scheduler event.

      The content of this list is retrieved from the UC_SAP_XJBP_EVENTTYPES variable , which is available in client 0. The Variable object is supplied with all possible event types and should not be changed by users.

      Event Parameter

      Filter for the parameters of the SAP Java Scheduler event.

      You can use the wildcard characters "*" and "?". "?" stands for exactly one, "*" for any number of characters.

      Event Additional Parameter

      Filter for additional parameters of the SAP Java Scheduler event.

      You can use the wildcard characters "*" and "?". "?" stands for exactly one, "*" for any number of characters.

Time Parameters

You define event monitoring parameters in this section.

ClosedTo Define the Time Parameters

In Frequency you have the following options to determine how often the event object should be activated:

  • Repeatedly

    It is activated periodically, depending on the setting you define below.

  • Repeat until first match

    It is activated until the specified conditions applies.

Time and Date Conditions

These conditions are always checked and an event will only be triggered if at least one of them is met or if no condition has been defined here. The current date and time are used as reference. The Time Zone assigned to the event is considered as well. This means that activating an event and specifying a logical time does not make sense.

Time specifications are checked for full minutes, i.e. the ending time 23:59 hours lasts until 23:59:59. Hence, the event can also be triggered in the last 59 seconds.

ClosedTo Define the Time and Date Conditions

  1. Click the first row to activate it and, in the Calendar column select an entry from the dropdown list.
  2. Select the Calendar Event you want to apply.
  3. To edit a row you must first click its checkbox to activate it. You have then the following options:

    To add/edit a row you must first click its checkbox to activate it. You have then the following options:

    Option

    Description

    Inserts a new row at the bottom of the table

    Deletes the row

    Removes the entry from the list and pastes it to the clipboard. Click Paste to add it to the bottom of the table.

    Duplicates the entry. Click Paste to add it to the bottom of the table.
    Activates all rows in the table.

 

A database event process cannot contain JCL lines.

See also: