Configuring iSeries monitor type

This topic provides information about configuring PATROL for iSeries KM in the Central Monitoring Administration and TrueSight console. To configure the KM, set the following preferences on the Add Monitoring Configuration dialog.

Monitoring Solution	Version	Monitor Profile	Monitor Type
iSeries	4.1.00	iSeries Remote Monitoring	iSeries

Click button to add the Remote Host Configuration details.

Field	Description
Remote Host Configuration
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 (with or without publish host names) that have common credentials. The file must be located on the host which is running the PATROL Agent. BMC 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. Information You can add a publish hostname to represent the host with different a 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 BMC PATROL Agent to apply the changes.
User Name	Enter the username. Note: For information about user privileges, see System-requirements.
Password	Enter 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.
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* *indicates additional configuration is required before enabling these monitor types. See, Configuring-PGMs-on-the-iSeries-host.

Click a tab to view the next step.

Active Jobs: Select the Active Jobs check box to enable active jobs monitoring. Click button to add the configuration details. The configuration will be 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 28 characters. You must enter a name with no slashes, semicolons, or colons. Embedded blank spaces will be replaced with underscores. Input must match '^[^:;\\\/]{1,28}$' regular expression pattern.
Job Name	Enter the name of the job, using one of the following conventions: * - All job names. <name>* - The jobs whose names begin with the string you specify. <name> - The exact name of the job. Input must match '^[A-Za-z0-9](\)*$' regular expression pattern.
Job User	Enter the name of the user associated with the job, using one of the following conventions: * - All user names. <user>* - All users whose names begin with the string you specify. <user> - The exact name of the user. Input must match '^[A-Za-z0-9](\)*$' regular expression pattern.
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 <number> - 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.

Message Queue: Select the Message Queue check box to enable message queue monitoring. Click button to add the configuration details. The configuration will be 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.
List Search Criteria: Click to configure the message selection criteria.
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 will be 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 checkbox to indicate whether a reply should be sent 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 should cause the counter associated with Maximum Autoreplies to get reset. The counter is reset if the time elapsed in 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 should 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: Maximum auto reply is reached option should be selected 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 should cause 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. 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 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.

History Log: Select the History Log check box to enable history log monitoring. The configuration will be applied to all remote hosts added in Hosts Name/File Path field.

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 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 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 checkbox 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 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.

Output Queue: Select the Output Queue check box to enable output queue monitoring.

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 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.

Scheduled Jobs: Select the check box to enable scheduled jobs monitoring.

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 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.

Subsystem: Select the Subsystem check box to enable subsystem monitoring. Click the Subsystem button to add the configuration details. The configuration will be 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.

Objects: Select the Objects check box to enable object monitoring. Click the Objects button to add the configuration details. The configuration will be 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. <name>** - The objects whose names begin with the string you specify. <name> - The exact name of the object.
Library	Specify the library where the objects are located using one of the following conventions: <Library> - 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. <Type>* - 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.

Job Queue: Select the Job Queue check box to enable job queue monitoring. Click the Job Queue button to add the configuration details. The configuration will be 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.

Enter the administration details before you save the remote host configuration.

Field	Description
JAVA Home	By default, BMC 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.
Debug	Select this check box to enable the debug.
OK	Click to save the configuration.
Cancel	Click to close the configuration window.

Configuring iSeries monitor type

BMC PATROL for iSeries 4.1

On this page