Configuration of AS400JobContTest

This test monitors different types of jobs that are currently running on the target AS400 server and reveals the wealth of information on the jobs. This test reports the number of jobs in each type and also reveals the number of jobs that are in clear, critical and warning states.

The default parameters associated with this test are as follows:

• The TEST PERIOD list box helps the user to decide how often this test needs to be executed.

• In the HOST text box, the host for which the test is to be configured has to be specified.

• In the PORT text box, enter the port number at which the target host being monitored listens. By default, this is NULL.

• This test connects to the AS400 server being monitored to extract the required metrics. Therefore, specify the name of the AS400 server to connect to in the SERVERNAME text box.

• To enable the test to login to the specified AS400 server, you need to provide the test with the credentials of a valid user to the AS400 server. Hence, specify a valid userID in the USERID text box.

• Provide the password that corresponds to the specified USERID in the PASSWORD text box.

• Confirm the password by retyping it in the CONFIRM PASSWORD text box.

• In the JOB NAME text box, specify the job names to be monitored, in any one of the following formats: Description:fullyQualJobName, Description:partiallyQualJobName, fullyQualifiedJobName and partiallyQualifiedJObName. Here, Description refers to the display name of the job pattern that will appear as a descriptor of this test in the eG monitoring console. Pattern can be the full name of the job, or can include wild cards. For instance, to monitor all jobs that begin with the string GLNK, your Job specification would be: DMIRROR:GLNK*. Note that your job patterns cannot include wild card characters in the middle or at the beginning - i.e., for the example above, your specification cannot be: DMIRROR:*GLNK or DMIRROR:G*LNK. Multiple job patterns can be provided as a comma-separated list.

• This test enables administrators to sort the jobs based on CPU Time used, Job Type, Job Number, Job Name and User Name. Administrators can achieve this by simply choosing any one of the options from the SORT VALUE drop-down list. For instance, if administrators want to list the jobs on the basis of the type of the jobs, they can do so by selecting the Job Type option from the Sort Value drop-down list. The CPU Time used option is chosen as a default value for this parameter.

• The SORT ORDER list helps administrators to organize the jobs, that are listed on the basis of the value chosen against the SORT VALUE parameter, in an ascending or descending order. By default, “Descending” is chosen from this list for sorting the jobs.

• By default, 1000 is set as the JOB LIMIT. This implies that the test will report the metrics only for the 1000 jobs performed during the measument period. If required, you can change the value of this parameter.

• The DD FREQUENCY refers to the frequency with which detailed diagnosis measures are to be generated for this test. The default is 1:1. This indicates that, by default, detailed measures will be generated every time this test runs, and also every time the test detects a problem. You can modify this frequency, if you so desire. Also, if you intend to disable the detailed diagnosis capability for this test, you can do so by specifying none against DD FREQUENCY.

• To make diagnosis more efficient and accurate, eG embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test, by default, for a particular server, choose the Onoption against DETAILED DIAGNOSIS. To disable the capability, click on the Off option.

  The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:

  • The eG manager license should allow the detailed diagnosis capability.

  • Both the bad and normal frequencies configured for the detailed diagnosis measures should not be 0.

• If multiple components of the same component type are awaiting configuration, then an APPLY TO OTHER COMPONENTS check box will appear in this page. Clicking on this check box will allow you to apply the configuration to all/selected components of that type.

• Once the necessary values have been provided, clicking on the UPDATE button will register the changes made.

When changing the configuration for specific servers, a “*” beside the text box corresponding to the parameter signifies that these values have to be manually configured by the user. The parameter values that require to be configured will typically be prefixed with a “$” or contain a series of “*”. A value of “none” in the parameter value indicates that the corresponding parameter value can be changed if required.