Configuration of AS400JobMntrTest

This test auto-discovers the jobs according to a specific pattern that has been configured by administrators. For each pattern, this test reports the following metrics:

• the number of active jobs;

• the jobs held in the queues;

• the number of threads required to perform the jobs;

• how long the CPU resources were utilized by the jobs;

• the amount of temporary storage allocated for executing the jobs.

This way, administrators are alerted to slowness in processing the jobs, a processing bottleneck on the queues and the CPU resource contention created when the jobs use the resources for a prolonged time. Thus, administrators can initiate the remedial measures before the users complaint about any performance lag.

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.

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

• Specify the name of the user whose jobs should be added for monitoring in the USERNAME text box. The user name should be a fully qualified name of the user on the AS400 server. By default, this is set as none indicating that this test will monitor the jobs from all users.

• Sometimes, administrators may want to monitor only a particular type of jobs. To achieve this, administrators should enter the type of the jobs to be monitored in the JOB TYPE text box. To monitor more than one type of jobs, specify the job types in a comma-separated list - for instance, Autostart,Batch,Interactive. You can even provide the job types in the following format: *Autostart*,*Batch*. By default, this is set as none indicating that this test will report metrics for the jobs of all types.

• In order to monitor the print jobs from a specific sub system, administrators should specify the name of that particular sub system against the SUB SYSTEM parameter. Administrators can also monitor the jobs from multiple subsystems by specifying the names of the subsystems in a comma-separated list in the SUB SYTEM text box. By default, this is set as none indicating that this test will monitor the jobs running in all the subsystems.

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