12.14.6 Notes on the Jobnet Monitor window
-
Displaying the manager jobnet
An error will occur if any unit other than a jobnet has been specified as the destination's unit name.
-
Before operating units in the Jobnet Monitor window
Because the unit status might have been updated, we recommend that before operating units you execute Refresh to update the display.
-
Starting the Jobnet Monitor window from another window
A new window will always be displayed, irrespective of the unit or execution ID.
-
Selecting units
If the focus is in the tree area, those units selected in the tree area become the target of operation. Otherwise, the target refers to those units selected in the map area. If no units have been selected in the map area and the focus is outside the tree area, you cannot operate any unit.
-
Updating the state of execution
The state of execution displayed in the map area is read only in the following cases.
-
Reading the map area information in the jobnet
-
Automatic updating
-
If the generation shown in the map area is different from the generation of what is to be monitored
Unless the target generation to be monitored has been updated, the state of execution will not be updated even if you reselect a jobnet whose state has been acquired.
-
-
Updating generation values
The target generation is actually updated if the monitor mode is "monitoring the latest state" or "monitoring the latest result." Note, however, that the updating process occurs only when the jobnet's map information is read and during automatic updating. No search is made with new generations even if you reselect a jobnet whose state has been acquired.
-
Updating comments
Comments are not updated by automatic update. To update the comment display, perform Refresh.
-
What takes place when the monitor generation is lost in acquiring the state
Automatic updating will be discontinued if an error occurs during the process of state acquisition so that the system concludes that there are no more generations to be monitored. The process of automatic updating will be restarted after the state has been successfully acquired.
-
Asynchronous communication
Operation is possible even during communication because of asynchronous communication with the JP1/AJS3 - Manager host. However, some elements of the operation must be conducted only after the communication process has been completed. Note that automatic updating will not take place during communication.
-
Displaying the Jobnet Monitor window from JP1/IM - View
When you display the Jobnet Monitor window on the JP1/IM - View main console by selecting an event that has been output by the remote jobnet, you should pay attention to the following:
-
Displaying remote jobnets in the Jobnet Monitor window causes two JP1/AJS3 - View processes to be started. This will consume an increasingly large amount of memory or system resources. It is recommended, therefore, that you close the Jobnet Monitor window once monitoring has been completed.
-
To display a remote jobnet in the Jobnet Monitor window, you need to internally log in to both the remote jobnet manager's JP1/AJS3 - Manager and the remote jobnet agent's JP1/AJS3 - Manager.
For this reason, two Login screens may be displayed, depending on the configuration of the certificate authority. In this case, you must assign a valid set of the user name and password to the remote jobnet manager's JP1/AJS3 - Manager and the remote jobnet agent's JP1/AJS3 - Manager.
-
-
Displaying the Monitor Details dialog box for a jobnet connector or its connection-destination jobnet
Note the following when you display the Monitor Details dialog box for a generation of a jobnet connector or a generation of a connection-destination jobnet if connection of the generation is not fixed.
-
If the unit to be connected exists on a host that is managed by a different authentication server, you need to log in to the host with the unit to be connected to obtain a connection target execution ID or connection source execution ID. If that is the case, the Login screen appears. Log in to the host with the unit to be connected. When you click Refresh or perform automatic update while the Monitor Details dialog box is displayed, you might need to log in to obtain a connection target execution ID or connection source execution ID. The Login screen will not appear when you display the Monitor Details dialog box for a generation with a fixed connection.
When you click Cancel in the Login screen, the Exec. ID (Destination) or Exec. ID (Source) text box in the Monitor Details dialog box displays Unknown.
When the Exec. ID (Destination) or Exec. ID (Source) text box displays Unknown, redisplay or automatic update of the Monitor Details dialog box does not obtain a connection target execution ID or connection source execution ID. Therefore, the Exec. ID (Destination) or Exec. ID (Source) text box continues to display Unknown. To display an execution ID in the Exec. ID (Destination) or Exec. ID (Source) text box, click View and then Refresh to update the display.
-
Because the local host needs to communicate with the host with the unit to be connected, the JP1/AJS3 service must be started on the host with the unit to be connected. If the JP1/AJS3 service is not active, a communication error occurs. Other operations cannot be performed until the communication error is detected.
-
-
Displaying a connection-destination jobnet from a jobnet connector in the Jobnet Monitor window
Note the following when you select a jobnet connector, and click View, Jobnet for Destination, and then Jobnet Monitor.
-
When you display a connection-destination jobnet in the Jobnet Monitor window, two JP1/AJS3 - View processes might be started. If that occurs, large amounts of memory and system resources are consumed.
We recommend that you close the Jobnet Monitor window when monitoring is ended.
-
When a jobnet connector and its connection-destination jobnet exist on different hosts that are managed by different authentication servers, the Login screen appears when you display the connection-destination jobnet from the jobnet connector in the Jobnet Monitor window. Log in to the host with the connection-destination jobnet.
When you display the Monitor Details dialog box for the connection-destination jobnet from the Jobnet Monitor window being displayed, the Login screen appears for each Jobnet Monitor window for the generations without a fixed connection. Log in to the host with the jobnet connector.
Note that the Login screen will not appear when you display the Monitor Details dialog box for the generations with a fixed connection.
-
Because the host with the jobnet connector needs to communicate with the host with the connection-destination jobnet, the JP1/AJS3 service must be started on the host with the connection-destination jobnet. If the JP1/AJS3 service is not active, a communication error occurs.
Other operations cannot be performed until the communication error is detected.
-
The host with the jobnet connector uses one of the following host names to communicate with the host with the connection-destination jobnet. Configure the hosts file so that host names can be resolved on the JP1/AJS3 - View hosts.
For generations without fixed connection
The host with the jobnet connector uses the name of the host specified as the connection target host.
For generations with a fixed connection
The host with the jobnet connector uses the name of the host# with the connection-destination jobnet.
#: The actual host name to be used is as follows:
- For a physical host, host name returned by the hostname command
- For a logical host, logical host name
-