5.8.2 Utilizing guide information tailored to the system operation
In the Guide window, you can choose to display any type of information as guide information, according to how the system is to be monitored.
For example, guide information could be utilized in the following ways.
Guide information tailored to system operation (examples)
-
Guide information about troubleshooting procedures
First, suggest ways of handling particular problems, and advise what action to take in a crisis. Register these ideas as guide information.
Investigate the problem in detail at the follow-up stage, using all the various JP1/IM functions.
-
Guide information about particular problems (JP1 events)
Prepare guide information about the causes of particular problems.
As a display condition, you can use information about the JP1 event that caused a status change in the monitoring node. Register this information as guide information
You can also set different types of guide information for different types of monitoring nodes. For example, you could display troubleshooting procedures for monitoring groups, and details about error causes for monitoring objects.
- Organization of this subsection
(1) Guide information about action procedures
To display guide information about action procedures, you must register information with the relevant monitoring nodes (that is, the monitoring viewpoints associated with a jobnet or other processing).
Each monitoring node has its own ID. Set guide information using the node ID as a condition.
Monitoring node IDs are unique to a node and are assigned automatically when a node is created. The node ID does not change when a node is moved in a monitoring tree.
-
Verify the monitoring node ID.
In the Monitoring Tree window, verify the ID of the node that you want to set guide information for in either of the following ways:
-
Select the node, and then right-click and choose Properties from the pop-up menu. View the General page in the displayed Properties window. The node ID appears in the Monitoring node ID field.
-
Execute a node search: Choose View and then Search to open the Search window, and then search for the monitoring node you require. The node ID appears in the Monitoring node ID field in the search results.
-
-
Write guide information using the monitoring node ID as the condition.
In the guide information file (jcs_guide.txt), write guide information specifying the monitoring node ID (T.MONNODEID) as the condition (EV_COMP specified).
For example, write the guide information as follows.
Coding example:
[EV_GUIDE_1]
NUM=1
EV_COMP_1=T.MONNODEID:(monitoring-node-ID)
EV_TITLE=Action for error in Accounts_DailyTotals
EV_GUIDE=Action procedure when an error occurs in Accounts_DailyTotals\nSee: User's Guide 3.11 Troubleshooting\nSummary: (For details, see the User's Guide.)\nCheck the error cause. If the error has major impact, suspend related jobs and contact the administrator (contact route C).
[END]
Explanation of coding example:
In T.MONNODEID:(monitoring-node-ID), specify the node ID you verified above.
(2) Guide information about an error (JP1 event)
To display guide information about an error, you must register information about the JP1 event that caused a status change in the monitoring node.
-
Investigate the JP1 event.
Investigate the JP1 event related to the problem.
As a display condition, you can use the event ID (B.ID) or other attribute of the JP1 event.
If you want to include a message (B.MESSAGE) or other JP1 event information in the guide information, also check message contents and attribute names.
-
Write guide information using the JP1 event as the condition.
In the guide information file (jcs_guide.txt), write guide information specifying the JP1 event ID (B.ID) or other JP1 event information as the condition (EV_COMP specified).
For example, write the guide information as follows.
Coding example:
[EV_GUIDE_1]
NUM=1
EV_COMP_1=B.ID:00004107
EV_TITLE=Abnormal job termination
EV_GUIDE=The job ended abnormally.\nJob name: $E.OBJECT_NAME\nJob execution host:$E.C0\nMessage--\n$B.MESSAGE\n--\n<Case>\nIf job A and job B are executed concurrently, job B will end abnormally because there is insufficient work area: Check the log (jobexe.log).
[END]