Configuring iSeries in TrueSight

Use the Add Monitoring Configuration page in the TrueSight console to configure PATROL for iSeries and monitor your iSeries OS.

From the Remote Host Configuration page, you can achieve the following goals:

  • Configure remote monitoring of iSeries OS
  • Enable or disable monitoring of individual resources (System, User, Pool, Batch, ASP, Network Interface, Active Jobs, Message Queue, History Log, Output Queue, Scheduled Jobs, Subsystem, Objects, Job Queue, Network Connection)
  • Configure individual resources for monitoring

Before you begin

  • Ensure that your computer meets all the requirements listed in the System requirements topic.
  • If you want to monitor ASP, Network Interface, Message Queue, History Log, Scheduled Jobs, Job Queue, and Network Connection monitor types, ensure that the relevant PGMs are configured on the remote iSeries host.

     For detailed steps, see configuring PGMs on the iSeries host

      Page not found for multiexcerpt macro.
    The page: .Configuring PGMs on the iSeries host v4.2.10 was not found. Please check/update the page name used in the 'multiexcerpt-include macro.

  • Ensure that you have created the monitoring policy for this configuration. For information about to create a monitoring policy, see Defining a monitoring policy.

To configure monitoring of iSeries remote host (video)

Click to view a short video (3:47) of how to configure remote monitoring of iSeries host.

 https://youtu.be/YV7HFk1j6Xw

To configure monitoring of iSeries remote host (steps)

  1. Access the Infrastructure Policies tab on the TrueSight console
    1. Log on to the TrueSight console.
    2. Expand the Configuration menu and select Infrastructure Policies.
      The Infrastructure Policies page is displayed. 
    3. Click Create Policy
      The Create Monitoring Policy page is displayed.
    4. Enter the policy details as described in the Defining a monitoring policy section. 

  2. Set the JAVA Home location, enable device mapping, and enter additional JVM arguments

    Administration

    Enter the administration details before you begin with the remote host configuration. 

    FieldDescription
    JAVA Home

    By default, PATROL for iSeries uses Java Runtime Environment (JRE) that is installed in the PATROL_HOME directory. To use your own JRE that is installed in a different location, specify the path for the Java home directory.

    For example, if your Java executable exists in the /usr/java/jdk1.7.0_71/jre/bin/java path, specify /usr/java/jdk1.7.0_71/jre as the value of this field.

    Enable DebugSelect this check box to enable the debug. The logs file is generated in the <PATROL_HOME>/akn/log directory on the PATROL Agent server.
    JVM Arguments

    Enter the additional Java Virtual Machine arguments for the Java collector.

    For example, to set the Java max heap size to 512 MB or 1024 MB, enter -Xmx512m or -Xmx1024m


  3. Define the configuration for the iSeries remote host

    Specify the values for the following fields to configure your iSeries remote host.

    FieldDescription
    Remote Host Details
    Host Names/File Path

    Specify the hostname of the server in either of the following ways:

    • Single hostname or IP address.
    • If you want to use the same configuration for multiple hosts, enter a comma-separated list of host names or IP addresses with common credentials.
    • If you want to use the same configuration for large number of hosts, you can configure the remote hosts from a file. Enter the absolute path to the file that includes a comma-separated list of host names or IP addresses.
      • The file must contain a list of comma-separated host names or IP addresses info(with or without publish host names) that have common credentials. 
      • The file must be located on the host which is running the PATROL Agent. PATROL default account must have read permission on the directory where the file is located. The Status of Configuration parameter indicates errors related to the input file.

    You can add a publish hostname to represent the host with a different hostname or, if the fully qualified domain name of the remote host cannot be retrieved. The publish hostname can be added in <hostname>;<publish_hostname> format. This format can be used in any of the above options.

    Note: If you modify the file, restart the PATROL Agent to apply the changes.

    User Name

    Enter the username.

    Note: For information about user privileges, see System requirements.

    PasswordEnter the password.
    Confirm Password Re-enter the password for confirmation.
    Enable secure connection

    Select to enable secure connection to iSeries host over SSL. You must establish a trust relationship between iSeries host and JRE running on PATROL Agent machine for this option to work.

     For detailed steps, see establishing trust relationship for SSL

    Use the following steps to establish a trust relationship between the iSeries host and JRE running on the PATROL Agent system. These steps must be followed if you select the Enable Secure Connection option while configuring the iSeries KM.

    On the iSeries host 

    1. In the IBM System Director Navigator, create a certificate using the Digital Certificate Manager option. You may use the default Certificate Authority (CA), external Certificate Authority (CA), or Client/Server type of certificate.

      Note

      The Client/Server type of certificate is supported on iSeries V7R3 only.

    2. Export and save the certificate in .crt file format.
    3. This step is applicable only if you are using the default Certificate Authority (CA) or external Certificate Authority (CA) type of certificate. 
      Assign the certificate to the following servers as required by the Java Toolbox:
      1. Database Server
      2. SignOn Server
      3. Central Server
      4. Data Queue Server
      5. Network Print Server
      6. Remote Command Server
      7. File Server
      8. i5/OS DDM/DRDA Server - TCP/IP application

    On the PATROL Agent system

    1. Copy the .crt certificate file on the PATROL Agent system.
    2. Navigate to <JAVA_HOME>/bin directory that is used by the PATROL Agent system and the PATROL for iSeries KM. If you have installed the JRE package using the repository with the PATROL Agent then the JRE is available at <PATROL_HOME>/jre64 location.
    3. Import the certificate using the JAVA keytool utility. Enter the following command to import the certificate:

      keytool -import -keystore  lib/security/cacerts -file <certificate_file_path>

    Note

    On the iSeries host if you have used an external Certificate Authority (CA) to create the certificate, ensure that the CA is copied in lib/security/cacerts directory before executing the above command.


  4. Enable or disable monitoring of individual resources and configure the resources for monitoring

    Specify the values for the following fields to configure monitoring of the resources. 

    FieldDescription
    Configure Monitor Types
    Monitoring Options

    Select the type of monitoring.

    • Standard Monitoring - This option enables monitoring of SYSTEM, POOL, USER and BATCH monitor types only.
    • Advanced Monitoring - This option allows you to select and configure individual monitor types. These configurations need to be enabled explicitly. 
    Advanced Configuration

    This option allows you to configure monitor types other than the standard monitor types. In the Advanced Configuration dialog box, select the monitor types that you want to monitor:

    Ensure that Advanced Monitoring option has been selected in Monitoring Options field on the Add Monitor Types screen. 

    Monitor type Selection/Configuration

    • SYSTEM
    • USER
    • POOL
    • BATCH
    • ASP*
    • Network Interface*
    • Active Jobs
    • Message Queue*
    • History Log*
    • Output Queue
    • Scheduled Jobs*
    • SubSystem
    • Objects
    • Job Queue*
    • Network Connection*

    *indicates additional configuration is required before enabling these monitor types.

     For detailed steps, see configuring PGMs on the iSeries host

    Before enabling monitoring of of ASP, Network Interface, Message Queue, History Log, Scheduled Jobs, Job Queue, and Network Connection application class, ensure that these binaries are configured on the remote iSeries host.

    To configure the iSeries binaries on the remote host:

    1. Log in to the iSeries system. 
    2. Delete the BMC_TSIM library that exists due to earlier installations of the KM by using the following command:
      DLTLIB BMC_TSIM


    3. Create the BMC_TSIM library on the iSeries system by using the following command:

      CRTLIB BMC_TSIM

    4. Create SAVF_4220 save file under the BMC_TSIM library using the following command:
      CRTSAVF FILE(BMC_TSIM/SAVF_4220) TEXT('Contains BMC PGMs to be called remotely')

    5. Copy the SAVF_4220 save file from <PATROL_HOME>/akn directory to the iSeries system in the BMC_TSIM library by using the FTP utility in binary mode as follows:
      1. Open command prompt and navigate to the <PATROL_HOME>/akn directory. 
      2. Enter ftp <iSeries hostname> command where <iSeries hostname> is the name of your iSeries system.
      3. Connect to the iSeries system by providing credentials
      4. Change mode to binary by using the bi command
      5. Navigate to BMC_TSIM library on iSeries system using the following command:
        cd BMC_TSIM

      6. Copy the SAVF_4220 save file using the following command:
        mput SAVF_4220

      7. End the FTP session by entering the following command:
        bye


    6. Copy the BMC_TSIM_4_2_20.qsh file from <PATROL_HOME>/akn directory to the iSeries system in the /tmp directory by using the FTP utility in ASCII mode as follows:

      1. Open command prompt and navigate to the <PATROL_HOME>/akn directory. 
      2. Enter ftp <iSeries hostname> command where <iSeries hostname> is the name of your iSeries system.
      3. Connect to the iSeries system by providing credentials
      4. Navigate to /tmp directory on iSeries system using the following command:
        cd /tmp

      5. Copy the BMC_TSIM_4_2_20.qsh file using the following command:
        mput BMC_TSIM_4_2_20.qsh

      6. End the FTP session by entering the following command:
        bye

    7. Login to the iSeries system.

    8. Open QSHELL on iSeries system using qsh command.

    9. On qsh prompt, navigate to the IFS path /tmp where the BMC_TSIM_4_2_20.qsh script is copied. Use the following command:
      cd /tmp


    10. Ensure that /usr/bin path is set in the environment variable PATH.

      1. To verify, enter the following command:
        echo $PATH

      2. If the environment variable PATH is not set, use the following command to set the PATH:
        export PATH=$PATH:/usr/bin


    11. Execute the BMC_TSIM_4_2_20.qsh script. The script can be used as follows:
      ./BMC_TSIM_4_2_20.qsh


    12. The configuration is complete when the script execution ends.

    13. Use the DSPLIB  BMC_TSIM command to verify if the the PGM files and MSGQ files are restored and created on the remote iSeries host. 
      The following PGM files are restored when you execute the script:

      1.  ASPCOLLECT
      2.  JBQCOLLECT
      3.  MSQCOLLECT
      4.  NETCONCOLL
      5.  NETSTATCOL
      6.  QHTCOLLECT
      7.  SCHCOLLECT 

    The following MSGQ files are created when you execute the script:

      1. ASP_DATA 
      2. CONN_DATA
      3. INTF_DATA
      4. JOBQ_DATA
      5. MSGQ_DATA
      6. QHST_DATA
      7. SCHD_DATA 


  5. After you choose Standard or Advanced monitoring option, you can configure filters for the Active Jobs, Message Queue, History Log, Output Queue, Scheduled Jobs, SubSystem, Objects, Job Queue, and Network Connection monitor types. 

    Click a tab to view the respective configuation. 


    Active Jobs: Select this check box to enable Active Jobs monitoring. Click Add to enter the configuration details. The configuration is applied to all remote hosts added in Hosts Name/File Path field.

    Job Cpu Threshold: Specify the percent CPU usage above which a job should be listed in the Jobs with CPU Above Threshold report. Enter a value between 0.0 and 100.0, inclusive.

    Field Description
    Group Label

    Enter a unique name to be used for a group instance and to identify this set of qualifiers when you want to change or remove it. Special chcaracters other than underscore are not supported. Embedded blank spaces will be replaced with underscores. Input must match ^[a-zA-Z0-9\\_]{1,28}$ regular expression pattern. This field is required and can be a maximum of 28 characters.

    Job Name

    Enter the name of the job, using one of the following conventions:

    • * - All job names.
    • jobname* - The jobs whose names begin with the string you specify.
    • jobname - The exact name of the job.
    Job User

    Enter the name of the user associated with the job, using one of the following conventions:

    • * - All user names.
    • username* - All users whose names begin with the string you specify.
    • username - The exact name of the user.
    Job Subsystem

    Enter the name of the subsystem associated with the job, using one of the following conventions:

    • * - All subsystem names.
    • jobsubsystemname* - All subsystems whose names begin with the string you specify.
    • jobsubsystemname - The exact name of the subsystem.
    Job Status

    Enter a comma-separated list of the status to filter the jobs by Job Status. Enter * (asterisk) to include all the statuses. All the jobs with the specified status are included for monitoring.

    Example: PRTA,OPTA,SIGW,END, and so on.

      Additional information about the status codes

    Status code Status Description
    100 INACTIVE Indicates that the job has completed or ended.
    75 MTXW Indicates that the job is waiting for access to shared data.
    58 OSIW

    Indicates that the job is waiting for the completion of an OSI Communications Subsystem for OS/400 operation.

     41 PRTA

    Indicates that the job is waiting in a pool activity level for output to a printer to complete.

    31  OPTA

    Indicates that the job is waiting in a pool activity level for the completion of an I/O operation to an optical device.

    17  SIGW

    Indicates that the job is waiting for a signal.

    93  END

    Indicates that the job ended with the *IMMED option or its delay time has ended with the *CNTRLD option.

    71  GRP

    Indicates that the job has been suspended by a Transfer Group Job (TFRGRPJOB) command.

    57  MXDW

    Indicates that the job is waiting for the completion of an I/O operation to a mixed device.

    40 PRTW

    Indicates that the job is waiting for output to a printer to complete.

    30 OPTW

    Indicates that the job is waiting for the completion of an I/O operation to an optical device.

    16 EVTW

    Indicates that the job is waiting for an event.

    92 EOJ

    Indicates that the job ended for a reason other than running the End Job (ENDJOB) or End Subsystem (ENDSBS) command, such as SIGNOFF, End Group Job (ENDGRPJOB), or an exception that is not handled.

    70 INEL

    Indicates that the job is ineligible and not currently in a pool activity level.

    56 ICFA

    Indicates that the job is waiting in a pool activity level for the completion of an I/O operation to an intersystem communications function file.

    38 CMTW

    Indicates that the job is waiting for the completion of save-while-active checkpoint processing in another job.

    29 CLDW

    Indicates that the job is waiting for status information pertaining to one of its child processes.

    15 DEQA

    Indicates that the job is waiting in a pool activity level for completion of a dequeue operation.

    91 DSC

    Indicates a disconnection from a workstation display.

    66 JVAA

    Indicates that the job is waiting in a pool activity level for a Java program operation to complete.

    55 ICFW

    Indicates that the job is waiting for the completion of an I/O operation to an intersystem communications function file.

    37 SVFA

    Indicates that the job is waiting in a pool activity level for the completion of a save file operation.

    28 CNDW

    Indicates that the job is waiting on a handle-based condition.

    14 DEQW

    Indicates that the job is waiting for completion of a dequeue operation.

    90 SIGS

    Indicates that the job stopped as the result of a signal.

    65 JVAW

    Indicates that the job is waiting for a Java program operation to complete.

    54 BSCA

    Indicates that the job is waiting in a pool activity level for the completion of an I/O operation to a binary synchronous device.

    36 SVFW

    Indicates that the job is waiting for the completion of a save file operation.

    27 THDW

    Indicates that the job is waiting for a thread.

    13 SELW

    Indicates that the job is waiting for a selection to complete.

    85 MSGW

    Indicates that the job is waiting for a message from a message queue.

    62 EOFA

    Indicates that the job is waiting in the activity level to retry a read operation on a database file after the end of file has been reached.

    53 BSCW

    Indicates that the job is waiting for the completion of an I/O operation to a binary synchronous device.

    35 TAPA

    Indicates that the job is waiting in a pool activity level for completion of an I/O operation to a tape device.

    25 SRQ

    Indicates the suspended half of a system-request job pair.

    60 MLTA

    Indicates that the job is waiting in a pool activity level for the completion of an I/O operation to multiple files.

    80 HLDT

    Indicates that the job is held due to a suspended thread.

    11 DSPA

    Indicates that the job is waiting in a pool activity level for input from a workstation display.

    21 TIMA

    Indicates that the job is waiting in a pool activity level for a time interval to end.

    34 TAPW

    Indicates that the job is waiting for completion of an I/O operation to a tape device.

    52 CMNA

    Indicates that the job is waiting in a pool activity level for the completion of an I/O operation to a communications device.

    61 EOFW

    Indicates that the job is waiting to retry a read operation on a database file after the end of file has been reached.

    81 HLD

    Indicates that the job is held.

    12 DLYW

    Indicates that the job is waiting for the Delay Job (DLYJOB) command to complete.

    51 CMNW

    Indicates that the job is waiting for the completion of an I/O operation to a communications device.

    33 DKTA

    Indicates that the job is waiting in a pool activity level for the completion of an I/O operation to a diskette unit.

    20 TIMW

    Indicates that the job is waiting for a time interval to end.

    10 DSPW

    Indicates that the job is waiting for input from a workstation display.

    76 LCKW

    Indicates that the job is waiting for a lock.

    59 MLTW

    Indicates that the job is waiting for the completion of an I/O operation to multiple files.

    50 CPCW

    Indicates that the job is waiting for the completion of a Common Programming Interface (CPI) Communications call.

    32 DKTW

    Indicates that the job is waiting for the completion of an I/O operation to a diskette unit.

    18 PSRW

    Indicates that the initial job thread is a prestart job waiting for a program start request.

    3 RUN

    Indicates that the job is currently running in the pool activity level.

    Job Type

    Select any one of the displayed job types. Available job types are:

    • * - All job types
    • AUTO (AutoStart)
    • BATCH (Batch Jobs)
    • INTER (Interactive)
    • SBS (Subsystem Monitor)
    • RDR (Spool Reader)
    • SYS (System)
    • WTR (Spool Writer)
    • SCPF (SCPF Jobs)
    Job Number

    Enter the number of the job, using one of the following conventions.

    • * - All job numbers
    • jobnumber*--The job numbers that begin with the string you specify.

    • jobnumber - The exact number of the job.

    Input must match '^(?:[0-9]*|(\*)*)$' regular expression pattern.

    Creation mode
    Aggregate resource usage for jobs matching the qualifiers

    Select this check box to track the number of matching jobs as well as their aggregate resource usage.

    Create an instance for each job that matches the qualifiers

    Select to create an instance for each job that matches the qualifiers. This allows you to keep track of the job status.

    OK Click to save the configuration.
    Cancel Click to close the configuration window.

    Back to top  , Back to monitor type configuration 


    Message Queue: Select this check box to enable Message Queue monitoring. Click Add to enter the configuration details. The configuration is applied to all remote hosts added in Hosts Name/File Path field.

    Field Description
    Message Queue

    Enter the name of the message queue you want to monitor.

    Library

    Enter the name of the library in which the message queue resides.

    Prior Minutes to Scan for Messages Enter the number of minutes that PATROL should look back in the message queue to process new messages. Default value is 10 minutes.

    Search Criteria: Expand and enter the search criteria details.

    List Search Criteria Click Add to enter the configuration details.
    Enable Single Match

    Select this option to enable single match from the search criteria list. The KM does not process further search criteria when it finds the first matched message.

    If this option is selected and the Search Criteria List For Prioritization field is left blank then the search criteria list is processed as it appears in the pconfig variable. By default, the search criteria list in the pconfig variable is sorted alphabetically.

    Search Criteria List for Prioritization

    This field is active only if the Enable Single Match option is selected.

    Providing details of all the search criteria is not mandatory. You can enter only the search criteria which you want to consider for the matching order. The KM processes the remaining search criteria in the order in which they appear in the pconfig variable. By default, the search criteria list in the pconfig variable is sorted alphabetically.

    For example, if the Search Criteria List for Prioritization list contains Criteria1, Criteria3, Criteria4, and Criteria2 then the messages are matched in Criteria1, Criteria3, Criteria4, Criteria2 order.

    Report Configuration: Expand and enter the report configuration details.
    Enable Report Select this option to generate a report of the messages that match the defined search criteria.
    Maximum number of matched messages to display Enter the maximum number of messages that must be displayed in the report after the defined search criteria is met.

    Search Criteria Label

    Enter a unique name to be used for the search criteria. This field is required and can be a maximum of 28 characters. You must enter a name with no slashes, semicolons, or colons. Embedded blank spaces are replaced with underscores.

    Message Details
    Include Message IDs

    Enter the message IDs to search. By default all message IDs are included in the search.

    You can also use regular expressions to search for multiple matching instances.

    Exclude Message IDs

    Enter the message IDs to exclude from the search.

    You can also use regular expressions to search for multiple matching instances.

    Minimum Severity

    Enter the minimum severity of the selected messages. Specify a number between 0 and 99, inclusive, to indicate the minimum severity level on which to filter.

    Select Include/Exclude for Text to Search

    Select whether to include or exclude the text search results.

    Text to Search

    Enter a text string to search for in the message queue. The search text can be part of a word, an entire word, or a phrase.

    You can also use regular expressions to search for multiple matching instances.

    Select Include/Exclude for Message File and Library

    Select whether to include or exclude search results if they match the Message File and Library criteria.

    Message File

    Enter the message file names to include or exclude from the search. By default all the message files are included in the search.

    You can also use regular expressions to search for multiple matching instances.

    Library

    Enter the name of the library in which the message queue resides. By default all the libraries are included in the search.

    You can also use regular expressions to search for multiple matching instances.

    Select Include/Exclude for Job Name and User Name Select whether to include or exclude the search results if they match the Job Name and User Name criteria.
    Job Name

    Enter the job names to include or exclude from the search. By default all the job names are included in the search.

    You can also use regular expressions to search for multiple matching instances.

    User Name

    Enter the name of the user associated with the job. By default all the user names are included in the search.

    You can also use regular expressions to search for multiple matching instances.

    Message Type

    Specify the message types to search. You can select or clear individual message types. By default, all the message types are selected.

    • *INFO - A message that provides general non error-related information.
    • *INQ - A message that conveys information but also asks for a reply.
    • *RQS - A message that contains a command for processing by a request processor, such as command entry.
    • *COMP - A message that conveys completion status of work.
    • *DIAG - A message that indicates errors in a system function, errors in an application, or errors in input data.
    • *NOTIFY - A message that describes a condition for which a program requires corrective action or a reply.
    • *ESCAPE - A message that describes a condition for which a program must end abnormally.
    • *RPY - A message that is a response to a received inquiry or notify message.
    • *COPY - A copy of an inquiry or notify message that is kept in the sender's message queue.
    Auto Reply Configuration
    Auto reply to message

    Select the check box to indicate whether to send a reply automatically for messages that satisfy the selection criteria and that require a reply.

    Reply using text

    Indicates what reply is sent automatically for messages that satisfy the selection criteria and that require a reply.

    Compose a reply to send instead of the default reply. The default reply is Hello.

    OS command or CL program Enter the OS command or CL program to be invoked on the remote iSeries host when an auto reply is generated.
    Maximum auto replies

    Enter the maximum number of consecutive replies automatically sent by PATROL. If there is no limit, leave this field blank.

    Reset auto replies counter after (seconds) Enter the time, in seconds, that causes the counter associated with Maximum auto replies to get reset. The counter is reset if the time elapsed between consecutive matching messages needing a reply exceeds the specified number of seconds. By default, this value is set to 60 seconds.
    Auto reply wait time (seconds) Enter the time, in seconds, after which an auto reply must be sent. By default, this value is set to 0 seconds.
    Event Trigger Configuration
    Trigger an event

    Select this option to instruct PATROL to trigger an event when the message is matched or the maximum number of auto replies are sent.

    Select when to trigger an event

    Specify the event trigger criteria:

    • Matched messages are at the least (Select this option to trigger an event when matched messages are greater than or equal to the value specified in Matched message count.)
    • Maximum auto reply is reached

    Note: Select the Maximum auto reply is reached option only when Auto Reply is configured

    Matched message count

    Enter a value in the field to instruct PATROL to execute the event triggering actions specified when the number of matching messages is equal to the entered value.

    Reset matched message count after (seconds)

    Enter the time, in seconds, that causes the number of matching messages counter to get reset. The counter is reset if the time elapsed in between consecutive matching messages exceeds the specified number of seconds.

    Event class

    If you want to send an event to the PATROL Event Manager, select the event class for which to send the event. The available event classes are:

    • AKN_MSGQ_INFO
    • AKN_MSGQ_WARN
    • AKN_MSGQ_ALARM
    • Custom
    Event catalog (Custom) If you have selected custom option in the Event class field, specify the custom event catalog name.
    Event class (Custom) If you have selected custom option in the Event class field, specify the custom event class name.
    Event Data

    If you want to send an event to the PATROL Event Manager, select the event data to include. If an Event Class and Event Data are specified for a message selection entry, the event data is passed to the event manager as a single argument. Within the argument, each selected piece of event data is included in the order specified below with each field separated from the next by a tab. For example, when Message Id and Message Type are specified, description of the event appears as follows:
    Id\t\tType

    The following event data are available for selection:

    • Message Id
    • Message Key
    • Message Type
    • Message Severity
    • Message Keyword
    • Message Full Text
    • Sending Job Id
    • Sending Program
    • Message Parameter
    • Message File/Library
    • Auto Reply Text
    • Specified Below - Specify the custom message that should be included in the event data.
    OK Click to save the configuration.
    Cancel Click to close the configuration window.

    Note: In search criteria, we have verified 50 search criteria with 250 matched messages, for processing of 1000 new messages per polling cycle.

    Back to top  , Back to monitor type configuration 


    History Log: Select this check box to enable History Log monitoring. Click Add to enter the configuration details. The configuration is applied to all remote hosts added in Hosts Name/File Path field.

    Enable Report: Select this check box to enable history log report. Selecting this option enables the following History Log agent actions:

    • List System Value Changes - Displays all the system value change messages that have been saved. It stores the system value change messages up to 30 days.
    • List Critical Abended Jobs - Displays the critical jobs that ended abnormally and have been saved. It stores the critical jobs ended abnormally up to 7 days. Critical jobs are those job name and user ID combinations that you specify as critical.
    • List Abnormally Ended Jobs - Displays all the abnormally ended job messages that have been saved. It stores the abnormally ended job messages up to 7 days.
    Field Description
    Abnormally Ended Jobs Configuration
    Monitor abnormally ended jobs

    Select this option to enable monitoring of abnormally ended jobs. Select one of the following options to include or exclude the abnormally ended jobs from monitoring.

    • Include all abnormally ended jobs - Select to collect information on all jobs ending abnormally on the system.
    • Exclude specified jobs - Select to exclude certain jobs from consideration when collecting abnormally ended job information. The excluded jobs are indicated when you specify their Job name and User name in Exclude Jobs List Configuration.

    By default, all the abnormally ended jobs are included for monitoring.

    Exclude Jobs List Configuration

    If you have selected Exclude specified jobs option in the above field, click Add button to exclude jobs from monitoring.

    Job name: Enter the Job name to exclude from consideration when processing abnormally ended jobs information. Input may also be a regular expression pattern.

    User name: Enter the user name to exclude from consideration when processing abnormally ended job information. Input may also be a regular expression pattern.

    OK: Click to save the configuration.

    Cancel: Click to close the configuration window.

    Note: If a job is added in the Critical Jobs List Configuration then that job will not be considered in Exclude Jobs List Configuration.

    End code threshold

    Enter the end code threshold. All jobs that end with an end code equal to or greater than this threshold are considered to have ended abnormally.

    Critical Jobs List Configuration

    Click Add to add Job name and User name combinations that will cause an alert if they end abnormally.

    Job name: Enter the the job name to add from the list of job names that will cause an alert if they end abnormally. Input may also be a regular expression pattern.

    User name: Enter the the user name to add from the list of user names that will cause an alert if they end abnormally. Input may also be a regular expression pattern.

    OK: Click to save the configuration.

    Cancel: Click to close the configuration window.

    Monitor system value changes

    Select this check box to enable monitoring of system value changes. It displays number of system value changes detected during that interval in System Value Changes parameter.

    History Log Search Criteria Configuration
    List History Log Search Criteria

    Click Add to specify the selection criteria including, message IDs, search string, severity and type of the messages arriving in the history log that are to be monitored.

    Search Criteria Label: Enter a unique name to be used for the search criteria. You must enter a name with no slashes, semicolons, or colons. Embedded blank spaces will be replaced with underscores. This name will be used to identify the instance of this search criteria under history log monitor.

    Include Message IDs: Enter the message IDs to search. By default all message IDs are included in the search. Input may also be a regular expression pattern.

    Exclude Message IDs: Enter the message IDs to exclude from the search. Input may also be a regular expression pattern.

    Minimum Severity: Enter the minimum severity of the selected messages. Specify a number between 0 and 99, inclusive, to indicate the minimum severity level on which to filter.

    Text to Search: Enter a text string to search for in the history log messages. The search text can be part of a word, an entire word, or a phrase. Input may also be a regular expression pattern.

    Message Type: Enter the message types to search. You can select or clear individual message types. By default, all the message types are selected.

    • *INFO - A message that provides general non error-related information.
    • *INQ - A message that conveys information but also asks for a reply.
    • *RQS - A message that contains a command for processing by a request processor, such as command entry.
    • *COMP - A message that conveys completion status of work.
    • *DIAG - A message that indicates errors in a system function, errors in an application, or errors in input data.
    • *NOTIFY - A message that describes a condition for which a program requires corrective action or a reply.
    • *ESCAPE - A message that describes a condition for which a program must end abnormally.
    • *RPY - A message that is a response to a received inquiry or notify message.
    • *COPY - A copy of an inquiry or notify message that is kept in the sender's message queue.

    Trigger an event: Select this option to instruct PATROL to trigger an event when the message is matched.

    Event class: If you want to send an event to the PATROL Event Manager, select the event class for which to send the event. The available event classes are:

    • AKN_QHIST_OK
    • AKN_QHIST_INFO
    • AKN_QHIST_WARN
    • AKN_QHIST_ALARM
    • AKN_QHIST_NOTIFY

    Event Data: If you want to send an event to the PATROL Event Manager, select the event data to include. When an Event Class and Event Data are specified for a message selection entry, the event data is passed to the event manager as a single argument. Within the argument, each selected piece of event data is included in the order specified below with each field separated from the next. by a tab. For example, when Message Id and Message Type are specified, description of the event appears as follows:
    Id\t\tType

    The following event data are available for selection:

    • Message Id
    • Message Type
    • Message Severity
    • Sending Job Id
    • Sending Job Name
    • User Name
    • Description

    OK: Click to save the configuration.

    Cancel: Click to close the configuration window.

    Back to top  , Back to monitor type configuration 


    Output Queue: Select this check box to enable Output Queue monitoring. Click Add to enter the configuration details. The configuration is applied to all remote hosts added in Hosts Name/File Path field.

    Field Description
    Specify output queues to monitor

    Select an option to discover output queues for monitoring.

    • Monitor output queues specified below: If you select this option, click Add to enter the output queue and the library details in the Output Queue Configuration dialog.
      • Output Queue: Enter the name of the output queue that you want to monitor. Input may also be a regular expression pattern.
      • Library: Enter the name of the library where the output queue is located. Input may also be a regular expression pattern.
      • OK: Click to save the configuration.
      • Cancel: Click to close the configuration window.
    • Monitor all output queues with files: Monitor all output queues that contain spool files.
    • Monitor all HELD output queues with files: Monitor all HELD output queues that contain spool files.
    • Monitor all RELEASED output queues with files: Monitor all RELEASED output queues that contain spool files.
    • Monitor all output queues with writer associated: Monitor all output queues associated with a writer.
    Exclude Output Queue Configuration
    Output Queue

    Enter the name of the output queue that you want to exclude from monitoring. Input may also be a regular expression pattern.

    Library Enter the name of the library where the output queue is located. Input may also be a regular expression pattern.
    OK Click to save the configuration.
    Cancel

    Click to close the configuration window.

    Back to top  , Back to monitor type configuration 


    Scheduled Jobs: Select the check box to enable Scheduled Jobs monitoring. Click Add to enter the configuration details. The configuration is applied to all remote hosts added in Hosts Name/File Path field.

    Field Description
    Specify scheduled jobs to monitor

    Select an option to discover scheduled jobs for monitoring

    • Monitor scheduled jobs specified below: If you select this option, click Add to enter scheduled job details in the Scheduled Job Configuration dialog.
      • Scheduled Jobs: Enter the scheduled job name.
      • OK: Click to save the configuration.
      • Cancel: Click to close the configuration dialog.
    • Monitor all scheduled jobs
    • Monitor all scheduled jobs with status HLD
    • Monitor all scheduled jobs with status SAV
    • Monitor all scheduled jobs with status SCD
    Exclude Scheduled Jobs Configuration

    Scheduled Jobs

    Enter the scheduled job name.
    OK Click to save the configuration.
    Cancel

    Click to close the configuration dialog.

    Back to top  , Back to monitor type configuration 


    Subsystem: Select this check box to enable Subsystem monitoring. Click Add to enter the configuration details. The configuration is applied to all remote hosts added in Hosts Name/File Path field.

    Field Description
    Name

    Enter the name of the subsystem that you want to monitor.

    Library

    Enter the name of the library where the subsystem is located.

    Add to List Click this option to confirm the configuration and add it to the list of configured subsystems.
    Modify Selection Select one of the items that you added to the list in the preceding step, and click this option to modify details.
    Remove from List Select the items added earlier and click this option to delete that item from the list of configured subsystems.
    Close Click to close the subsystem configuration window.

    Back to top  , Back to monitor type configuration 


    Objects: Select this check box to enable Objects monitoring. Click Add to enter the configuration details. The configuration is applied to all remote hosts added in Hosts Name/File Path field.

    Field Description
    Group Label

    Enter a unique name to be used for a group instance and to identify this set of qualifiers when you want to change or remove it. This field is required and can be a maximum of 25 characters. You must enter a name with no slashes, semicolons, or colons. Embedded blank spaces will be replaced with underscores. Input must match '^[^:;\\\/]{1,25}$' regular expression pattern.

    Object Name

    Specify the name of the objects to monitor using one of the following conventions:

    • *ALL - All object names. Note that at least one field must not contain the wildcard character.
    • objectname* - The objects whose names begin with the string you specify.
    • objectname - The exact name of the object.
    Library

    Specify the library where the objects are located using one of the following conventions:

    • libraryname - The exact name of the library.
    • *ALLUSR - All user libraries. All libraries with names that do not begin with the letter Q are searched, with some exceptions. See IBM Help for more information on the exceptions.
    • *ALL - All library names. Note that at least one field must not contain the wildcard character.
    Object Type

    Specify the type of object to monitor using one of the following conventions:

    • *ALL - All object types. Note that at least one field must not contain the wildcard character. For supported types, see the PATROL Command Line Interface Reference Manual for the OBJTYPE parameter.
    • objectype - The type of object to monitor.
    Create a single instance, representing the group of objects matching the qualifiers Select to create a group instance. This group instance represents the group of objects that matches the qualifiers, allowing you to track the number of matching objects.
    Create an instance for each object that matches the qualifiers Select to create an instance for each objects that matches the qualifiers. This allows you to keep track of its individual status.
    Add to List Click this option to confirm the configuration and add it to the list of configured objects.
    Modify Selection Select one of the items that you added to the list in the preceding step, and click this option to modify details.
    Remove from List Select the items added earlier and click this option to delete that item from the list of configured objects.
    Close Click to close the object configuration window.

    Back to top  , Back to monitor type configuration 


    Job Queue: Select this check box to enable Job Queue monitoring. Click Add to enter the configuration details. The configuration is applied to all remote hosts added in Hosts Name/File Path field.

    Field Description
    Job Queue Enter the name of the job queue that you want to add for monitoring. Input may also be a regular expression pattern. 
    Library Enter the name of the library where the job queue is located. Input may also be a regular expression pattern. 
    Add to List Click this option to confirm the configuration and add it to the list of configured job queues.
    Modify Selection Select one of the items that you added to the list in the preceding step, and click this option to modify details.
    Remove from List Select the items added earlier and click this option to delete that item from the list of configured job queues.
    Close Click to close the job queue configuration window.

    Back to top  , Back to monitor type configuration 

    Network Connection: Select this check box to enable Network Connection monitoring. Click Add to enter the configuration details. The configuration is applied to all remote hosts added in Hosts Name/File Path field.

    Field Description
    Connection Label

    Enter a unique name to be used for this search criteria and to identify this search criteria below the network connection monitor.

    Connection Details

    The range of the remote IP address of the connections that you want to monitor with this connection ID. If you only want to monitor a single remote IP address, enter it in the first field. If you do not want to select by remote IP address, leave both fields blank.
    Remote Lower IP Enter the lowest remote IP address to include for this connection ID.
    Remote Upper IP Enter the highest remote IP address to include for this connection ID.
    The range for the local ports of the connection. If you only want to monitor a single local port, enter it in the first field. If you do not want to select by local port, leave both fields blank.
    Local Lower Port Enter the lower range for the local port to include for this connection ID.
    Local Upper Port Enter the upper range for the local port to include for this connection ID.
    Connection Type

    Indicates the type of connection being monitored by this connection ID.

    *All - Monitor connections of all types

    *TCP - Monitor a transmission control protocol connection or listening socket

    *UDP - Monitor a User Datagram Protocol socket

    *IPI - Monitor an Internet Protocol over Internetwork Packet Exchange connection or socket

    *IPS - Monitor an Internet Protocol over SNA connection or socket

    OK Click to save the configuration.
    Cancel Click to close the dialog box.


    Back to top  , Back to monitor type configuration 

Was this page helpful? Yes No Submitting... Thank you

Comments