Agents Administration - Tests
 

Default Parameters for 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.

This page depicts the default parameters that need to be configured for the AS400JobContTest test.

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

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

  • Once the above values are provided, click on the UPDATE button to register the changes made.

When changing default configurations of tests, the values with “$” indicate variables that will be replaced by the eG system according to the specific server being managed - for instance, $hostName is the host/nickname of the target host, $port is the port number of the server being monitored. E.g., for a server xyz:80, $hostName will be changed automatically by the eG manager to “xyz*” and $port will be changed to “80” when configuring a test.