16.4 Cautionary notes on JP1/AJS3 Console View

Note the following when you use JP1/AJS3 Console View:

• Icon file name specified in the Define Details dialog box

  • If you specify the same icon file name for an AJS3 unit monitored object and a business scope, the icons will not be distinguishable. Do not specify the same icon image for an AJS3 unit monitored object and a business scope.

  • If you want to change the image in an icon image file, terminate JP1/AJS3 Console View first.

• When you choose View and then Refresh

  When you choose View and then Refresh in JP1/AJS3 Console View, the monitor status changes to Refreshing Status. When updating is complete, the monitor status changes to Monitoring.

  Note that a status update might take some time.

  The following are the likely causes of a lengthy status update:

  1. The time required to establish a connection from JP1/AJS3 Console Manager to JP1/AJS3 Console Agent

  2. The time required to establish a connection from JP1/AJS3 Console Agent to the authentication server

  3. The number of units monitored on one JP1/AJS3 Console Agent host

  Details about the above causes are as follows:

  1. Time required to establish a connection from JP1/AJS3 Console Manager to JP1/AJS3 Console Agent

     When you choose Refresh, JP1/AJS3 Console Manager attempts to establish a connection with JP1/AJS3 Console Agent that is not currently connected. If the JP1/AJS3 Console Agent host is not running, it might take some time before JP1/AJS3 Console Manager determines that connection is impossible.

     Use the formula below to calculate the approximate time (in seconds) that is needed for JP1/AJS3 Console Manager to determine that it cannot connect to a JP1/AJS3 Console Agent host when the host is not running. If necessary, configure JP1/AJS3 Console Manager accordingly. Note that the length of this time is not proportional to the number of JP1/AJS3 Console Agents to which connection is not possible.

     

     The following table describes the meaning of the elements in the above formula.

     Table 16‒9: Meaning of the elements in the formula

     Element	Description	Environment setting parameter	Default value
     T	Length of time required to determine that JP1/AJS3 Console Agent cannot be connected	--	--
     T1	Total connection timeout time	--	--
     T2	Total connection retry interval	--	--
     a	Connection timeout value	IPC_CONNECTTIMEOUT	20 (seconds)
     b	Number of connection retries	IPCRETRYCOUNT	3 (times)
     c	Retry interval	IPCRETRYINTERVAL	1 (second)
     n	Number of IP addresses#	--	--

     Legend:

     --: Not applicable.

     #

     The number of IP addresses managed by a JP1/AJS3 Console Agent host. If there are multiple JP1/AJS3 Console Agent hosts, use the number of IP addresses of the JP1/AJS3 Console Agent host that has the most IP addresses.

     Example

     If a JP1/AJS3 Console Agent host to which connection is not possible has one IP address and the environment settings of JP1/AJS3 Console Manager are the default values, it takes approximately 90 seconds for JP1/AJS3 Console Manager to determine that it cannot connect to the JP1/AJS3 Console Agent host.

     For details about the environment settings of JP1/AJS3 Console Manager, see 2.8 Setting up the JP1/AJS3 Console environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2.

  2. Time required to establish a connection from JP1/AJS3 Console Agent to an authentication server

     If JP1/AJS3 Console Agent needs to check whether it has an appropriate permission for a target unit when it wants to obtain the unit's status, JP1/AJS3 Console Agent queries the authentication server. If the authentication server host is not running, it might take some time for JP1/AJS3 Console Agent to determine that it cannot connect to the authentication server host.

     Note that the length of this time is proportional to the number of scheduler services containing the units that are monitored by JP1/AJS3 Console Agent hosts, but it does not depend on the number of units to be monitored.

     If both of the following conditions are satisfied, JP1/AJS3 Console Agent queries the authentication server about access permission:

     - The OS user mapped to the JP1 user who uses JP1/AJS3 Console Agent to perform monitoring is a general user.

     - A resource group is specified as the upper-level unit containing the units to be monitored.

  3. Number of units monitored on one JP1/AJS3 Console Agent host

     Status update processing does not finish until the status of units that are monitored by all JP1/AJS3 Console Agents has been obtained. Therefore, the time required for status update increases in proportion to the number of units monitored by one JP1/AJS3 Console Agent host.

• Restoring definition data during updating

  If JP1/AJS3 Console Manager terminates abnormally while definition data is being updated, the definition data might have been only partially updated. If so, the definition data will be restored at the next login to its status before the updating began.

• Point at which the environment settings of related programs take effect

  The settings you change by using JP1/Base or JP1/AJS3 - Manager take effect when you restart JP1/AJS3 Console View.

• Starting JP1/AJS3 - View from JP1/AJS3 Console View

  If you start JP1/AJS3 - View from JP1/AJS3 Console View, and there is no unit to be monitored, an error message (KAVV257-E The specified (job-group-name|jobnet-name|unit-name) was not found. (unit-name)) appears. If the name of the AJS3 unit specified as an AJS3 unit monitored object exceeds the maximum length of a unit full name, the KAVV296-E error message appears.

To Page Top