7.2.1 Objects used in JP1/AJS3 Console
With JP1/AJS3 Console, you can monitor jobnets defined under JP1/AJS3 using business scopes and AJS3 unit monitored objects. You can use two types of objects in JP1/AJS3 Console:
-
AJS3 unit monitored objects
-
Business scopes
The following figure shows the Scope window of JP1/AJS3 Console, containing the different objects you can use.
|
|
![[Figure]](GRAPHICS/ZUF07050.GIF)
Below is a description of the different object types.
- Organization of this subsection
(1) AJS3 unit monitored objects
An AJS3 unit monitored object is an object that defines information about a jobnet to be monitored (such as the full name of the jobnet, the name of the host where the jobnet is defined). An AJS3 unit monitored object is displayed as an icon in the Scope window. You can monitor the status of the jobnet by watching for changes in the color of the icon.
(2) Business scopes
A business scope is an object that lets you group monitored objects together.
If required, you can establish hierarchies for business scopes. In a hierarchy, the business scope at the highest level is called the root business scope, and lower-level business scopes are called nested business scopes.
(a) Root business scopes
The root business scope is the highest-level business scope. It is displayed in the Scope window when you first log in to JP1/AJS3 Console Manager with JP1/AJS3 Console View.
In the root business scope, the JP1 user who is logged in to JP1/AJS3 Console Manager can define what objects to monitor on a user-specific basis.
(b) Nested business scopes
A nested business scope is a business scope that is defined below the root business scope in the hierarchy.
You can create up to three levels of nested business scopes. Nested business scopes are displayed as icons when an upper-level business scope is selected.