3.7.2 Business impact determination support

The Intelligent Integrated Management Base collects the names of hosts where JP1/AJS - Manager is installed, names of hosts where JP1/AJS - Agent managed by JP1/AJS - Manager is installed, and other information, and shows relations between root jobnets configured by multiple instances of JP1/AJS - Manager.

Visualization allows you to view the duration of time before the operation affected by the failure is scheduled to start as well as the related infrastructure elements. This allows system administrators to identify what time the job following the root jobnet in which the abnormality was detected is scheduled to start and whether the failure has any impact on the subsequent job, enabling prompt identification of the impact of the problem on job operations and a timely response to individual failures in order of priority.

Note that jobnet definitions are used to automatically determine whether the failure has any impact on the subsequent job.

A user can also add a relation between root jobnets.

Figure 3‒18: Overview of business impact determination support

For example, if a failure occurs during operation of a job, the source root jobnet is displayed in red. Just clicking it enables the relationship with other root jobnets to be shown in Job flow tab.

When you click an icon (work impact icon), the Linked unit dialog box appears. You can identify which task is likely to be affected by a failure in the previous task. By checking the scheduled start time of each job, you can identify the urgency of fixing the problem. Furthermore, by clicking the value representing a link to the linked product in either the link or properties of the unit, you can display the JP1/AJS3 - Web Console window and view the details about the jobnet in question.

In a root jobnet definition where root jobnet A, root jobnet B, and then root jobnet A are executed in this order, the root jobnet relationship might appear more than once on the Job flow tab. When the work impact icon is displayed beside a node that appears more than once on the Job flow tab, the Linked unit dialog box displayed from icons displayed beside the nodes having the same root jobnet name presents identical information. In this case, you only have to check the Linked unit dialog box displayed from one of these icons.

If, in properties, you click a link to JP1/AJS3 - Web Console, either the Dashboard window, the List window or the Agent management window, depending on the type of JP1/AJS IM management node selected.

Table 3‒7: Type of JP1/AJS3 - Web Console window and appears of the IM management node
Type of JP1/AJS3 - Web Console window	IM management node
Dashboard window	JP1/AJS - Manager under the AJS3 manager host
List window	Scheduler services under the AJS manager host > JP1/AJS3 - Manager
	Job group under the AJS manager host > JP1/AJS3 - Manager > scheduler services
	Root jobnet under the AJS manager host > JP1/AJS3 - Manager > scheduler services > job group
Execution Agent window	AJS manager host > Management Applications > JP1/AJS3 - Manager
Execution Agent window	AJS manager host > Management Applications > JP1/AJS3 - Agent

Viewing the event going on in the root jobnet in which the failure has occurred allows you to promptly predict the cause of the failure and proactively deal with it, taking into consideration the severity of the failure in relation to other problems on the system.

If you change the definition or content of a job, you can view the statuses of the root jobnet to be changed and the preceding and following ones and understand the range of influence before starting the change task.

Important: To refer to the relations between root jobnets, configure the host names of JP1/AJS - Manager instances in the system so that there is no duplication of the names.

Organization of this subsection

(1) Associating root jobnets with one another

(1) Associating root jobnets with one another

The association of root jobnets with one another is achieved by detecting the combination of each root jobnet with its subsequent job based on the definition information accumulated through the acquisition of configuration information, and by returning the detected combinations in JSON format.

If a combination cannot be associated, it is detected as unknown. In this case, using a text editor, correct the IM management node-related files that are output by the jddcreatetree command. For the format, see the IM management node link definition file (imdd_nodeLink_def.conf). For details about the jddcreatetree command and the IM management node link definition file, see jddcreatetree in Chapter 1. Commands and IM management node link definition file (imdd_nodeLink_def.conf) in Chapter 2. Definition Files in the manual JP1/Integrated Management 2 - Manager Command, Definition File and API Reference.

Important: IM management node related information cannot be displayed for the JP1 event reception monitoring jobs and the JP1 event sending jobs for which a macro variable is specified as the execution agent. This is because the actual execution agent to be used is determined only at the time of job execution.

Associations between root jobnets are dependent on the settings specified in the JP1/AJS3 plug-in settings file (settings.conf). For details, see Setup for linking JP1/IM in the JP1/Automatic Job Management System 3 Linkage Guide.

(a) Linkage of JP1 events

For each root jobnet, the JP1 event sending jobs that match the criteria defined in the JP1 event reception monitoring jobs in the root jobnet are associated.

The following table describes the parameters to which the criteria (on which associations are created) defined in the JP1 event reception monitoring job apply. Note that each of these criteria applies only to the corresponding parameters shown in this table.

Table 3‒8: Criteria on which associations are created
No.	JP1 event reception monitoring job		JP1 event sending job		Criteria
No.	Defined parameter	Defined?	Parameter to be compared	Defined?	Criteria
1	`evhst="event-issue-source-host-name"`^#3#4	C	`ex="execution-agent-name"`^#1	A	An association is created if either one is matched.
2	`ex="execution-agent-name"`^#1	A	`evhst="event-destination-host-name"`^#4	Y	Matching result of `evhst` is prioritized.
2	`ex="execution-agent-name"`^#1	A	`ex="execution-agent-name"`^#1	If `evhst` is not defined	An association is created if either one is matched.
3	`evwid=event-ID`	C	`evSid=event-ID`	N	No association is created if none of them are matched.
3	`evwid=event-ID`	C	`evSid=event-ID`	Y	An association is created for a perfect match.
4	`evwms="message"`^#3	C	`evSms="message"`^#4	N	No association is created if none of them are matched.
4	`evwms="message"`^#3	C	`evSms="message"`^#4	Y	An association is created for a perfect match.
5	`evwsv=event-level` (multiple values can be set)	C	`evSsv=event-level`	N	No association is created if none are matched.
5	`evwsv=event-level` (multiple values can be set)	C	`evSsv=event-level`	Y	An association is created if one of them is matched.
6	`evwfr=extended-attribute` (multiple values can be set)^{#3 #4}	C	`evSfr=extended-attribute`^#4	N	No association is created if none are matched.
6		C	`evSfr=extended-attribute`^#4	Y	An association is created if one of them is matched.
7	`evipa="event-source-IP-address"`^#2	C	`ex="execution-agent-name"`^#1	N	No association is created if at least one parameter exists.
7	`evipa="event-source-IP-address"`^#2	C	`ex="execution-agent-group-name"`^#1	Y	An association is created if one of them is matched.

Legend:

C: Compare if defined

A: Always Yes (Always set regardless of whether it is defined)

Y: Yes

N: No

#1

The criterion applies to a list of execution target host names corresponding to the execution agents (execution agent group).

#2

The criteria apply only when the associations with IP addresses are specified in the configuration file.

#3

When associations with regular expressions are specified in the configuration file, an association is created by using regular expressions. For details about the available regular expressions, see Appendix G.1 Types of regular expressions.

#4

When, in the configuration file, the use of macro variables is specified as a condition for not creating an association, no association is created when macro variable names are specified. For details about the formats of strings that are treated as macro variable names, see the explanations provided under macro-variable-specification in the manual JP1/Automatic Job Management System 3 Command Reference.

(b) Waiting

JP1/AJS - Manager version 12-50 or later allows both root jobnets and units with wait conditions inside the root jobnets to be associated with units whose end is being waited for defined in the units with wait conditions. These associations are created on a root jobnet-by-root jobnet basis.

Units with wait conditions are associated with units whose end is being waited for regardless of the settings specified for the JP1/AJS - Manager environment setting parameters PREWAITUSE and PREWAITEXTEND or the presence/absence of the units whose end is being waited for.

When a planning group or a unit under a planning group is defined as the name of the unit whose end is being waited for, the unit with wait conditions is associated with the related unit described in the following table.

Table 3‒9: Units to be associated with units with wait conditions
No.	Specified unit	Units to be associated with units with wait conditions
1	Planning group	A root jobnet under the planning group that has been registered for execution when the configuration information was collected
2	A unit under a planning group	A unit under the root jobnet under the planning group that has been registered for execution when the configuration information was collected

(c) Jobnet connector

JP1/AJS - Manager version 12-50 or later allows the destination root jobnets and the jobnet connectors inside root jobnets to be associated when they match the same conditions. These associations are created on a root jobnet-by-root jobnet basis.

The following table describes the conditions for associating jobnet connectors with destination root jobnets. No association is created when a planning group is specified as the destination root jobnet name.

Table 3‒10: Conditions for associating jobnet connectors with destination root jobnets
No.	Destination root jobnet	Jobnet connector	Criterion
No.	Information used for comparison (definition parameter)	Information used for comparison (definition parameter)	Criterion
1	Full name of the unit	Name of the destination root jobnet (`ncr`)	An association is created when a perfect match is found.
2	Whether to link one scheduler service with another (`ncex`)	Whether to link one scheduler service with another (`ncex`)	An association is created when a perfect match is found.
3	Name of the manager host	Connection host name (`nchn`)^#1	An association is created when a perfect match is found.
3	Name of the manager host	Manager host name^#2	An association is created when a perfect match is found.
4	Connection host name (`nchn`)	Manager host name	An association is created when a perfect match is found.^#3
5	Scheduler service name	Destination service name (`ncsv`)^#1	An association is created when a perfect match is found.
5	Scheduler service name	Scheduler service name^#2	An association is created when a perfect match is found.
6	Destination service name (`ncsv`)	Scheduler service name	An association is created when a perfect match is found.^#3
7	Jobnet connector name (`ncn`)	Full name of the unit	An association is created when a perfect match is found.

#1: This item is used for comparison when y is specified as the value for no. 2.
#2: This item is used for comparison when n is specified as the value for no. 2.
#3: This criterion is applied only when y is specified as the value for no. 2.

When either the destination root jobnet or the jobnet connector supports a version of JP1/AJS - Manager earlier than 12-50, the association between the two is detected as unknown.

To Page Top