4.2.3 Passing any attribute and string of a JP1 event as incidents
For the registration mode of an incident 3, any attribute and string of a JP1 event can be passed as incidents. In the configuration file for incident inheritance information (incident_info.conf) of JP1/IM - View, you can define which item elements of JP1/Service Support receive attributes and strings of a JP1 event.
The following table lists the information to be passed from the Detailed event information window of JP1/IM - View for the registration mode of an incident 3.
Source element |
Destination item element |
---|---|
Any attribute of a JP1 event |
Any item element |
Any string |
Any item element |
Serial number (B.SEQNO)# |
JP1 serial number (JIMSD_FORM_IMEVENTNO) |
JP1/IM - Manager host name to which JP1/IM - View has logged in# |
JP1/IM - Manager host name (JIMSD_FORM_IMHOSTNAME) |
- Organization of this subsection
(1) Item elements that can be specified
The table below lists the item element specification IDs that can be specified as destination item elements in the configuration file for incident inheritance information (incident_info.conf). For details about information to be defined in the configuration file for incident inheritance information (incident_info.conf), see the manual JP1/Integrated Management - Manager Command and Definition File Reference.
Element name (default display name) |
Item form element ID |
Item element specification ID |
Type |
Limit (in bytes) |
||
---|---|---|---|---|---|---|
Lower |
Upper |
|||||
Title |
JIMSD_FORM_TITLE |
TITLE |
text |
1 |
512 |
|
Severity |
JIMSD_FORM_SEVERITYCODE |
SEVERITYCODE |
code |
-- |
-- |
|
Reason for severity |
JIMSD_FORM_SEVERITYREASON |
SEVERITYREASON |
text |
0 |
512 |
|
Reason for impact level |
JIMSD_FORM_IMPACTREASON |
IMPACTREASON |
text |
0 |
512 |
|
Reason for priority |
JIMSD_FORM_PRIORITYREASON |
PRIORITYREASON |
text |
0 |
512 |
|
Occurrence date and time |
JIMSD_FORM_ACCRUALDATE |
ACCRUALDATE |
datetime |
-- |
-- |
|
Deadline |
JIMSD_FORM_DEADLINE |
DEADLINE |
datetime |
-- |
-- |
|
Start date and time |
JIMSD_FORM_STARTDATE |
STARTDATE |
datetime |
-- |
-- |
|
End date and time |
JIMSD_FORM_COMPDATE |
COMPDATE |
datetime |
-- |
-- |
|
Customer name |
JIMSD_FORM_CUSTOMERNAME |
CUSTOMERNAME |
text |
0 |
1,024 |
|
Inquirer's name |
JIMSD_FORM_INQUIRYNAME |
INQUIRYNAME |
text |
0 |
255 |
|
Impact service |
JIMSD_FORM_EFFECTSERVICE |
EFFECTSERVICE |
textarea |
0 |
255 |
|
Problem component and version |
JIMSD_FORM_FAILURELOCATION |
FAILURELOCATION |
textarea |
0 |
1,024 |
|
Related information#1 |
Display name |
JIMSD_FORM_LINKURL |
LINKURLDISP |
url |
0 |
255 |
Related information |
LINKURL |
0 |
4,096 |
|||
Overview |
JIMSD_FORM_SUMMARY |
SUMMARY |
textarea |
0 |
2,048 |
|
Workaround |
JIMSD_FORM_AVOIDANCE |
AVOIDANCE |
textarea |
0 |
4,096 |
|
Work status |
JIMSD_FORM_SITUATION |
SITUATION |
textarea |
0 |
4,096 |
|
How to avoid the problem in the future |
JIMSD_FORM_MEASURES |
MEASURES |
textarea |
0 |
4,096 |
|
Fundamental cause |
JIMSD_FORM_ROOTCAUSE |
ROOTCAUSE |
textarea |
0 |
4,096 |
|
Solution |
JIMSD_FORM_SOLUTION |
SOLUTION |
textarea |
0 |
4,096 |
|
Schedule and main steps |
JIMSD_FORM_SCHEDULE |
SCHEDULE |
textarea |
0 |
4,096 |
|
Impact assessment for change |
JIMSD_FORM_IMPACTEVAL |
IMPACTEVAL |
textarea |
0 |
4,096 |
|
Discussions result |
JIMSD_FORM_DELIBERATIONRST |
DELIBERATIONRST |
textarea |
0 |
2,048 |
|
Free memo column |
JIMSD_FORM_FREEDESCRIPTION |
FREEDESCRIPTION |
textarea |
0 |
4,096 |
|
Product name |
JIMSD_FORM_JP1PRODUCTNAME |
JP1PRODUCTNAME |
text |
0 |
1,024 |
|
Jobnet name |
JIMSD_FORM_JP1JOBNETNAME |
JP1JOBNETNAME |
text |
0 |
1,024 |
|
Job name |
JIMSD_FORM_JP1JOBNAME |
JP1JOBNAME |
text |
0 |
1,024 |
|
SNMP source |
JIMSD_FORM_JP1SNMPSRC |
JP1SNMPSRC |
text |
0 |
1,024 |
|
Monitored node name |
JIMSD_FORM_JP1NODENAME |
JP1NODENAME |
text |
0 |
255 |
|
Alarm name |
JIMSD_FORM_JP1ALARMNAME |
JP1ALARMNAME |
text |
0 |
255 |
|
Added item: text |
JIMSD_FORM_USERTEXT01 to JIMSD_FORM_USERTEXT05 |
USERTEXT01 to USERTEXT05 |
text or textarea |
0 |
4,096 |
|
JIMSD_FORM_USERTEXT06 to JIMSD_FORM_USERTEXT15 |
USERTEXT06 to USERTEXT15 |
0 |
2,048 |
|||
JIMSD_FORM_USERTEXT16 to JIMSD_FORM_USERTEXT20 |
USERTEXT16 to USERTEXT20 |
0 |
512 |
|||
Added item: date and time |
JIMSD_FORM_USERTIME01 to JIMSD_FORM_USERTIME05 |
USERTIME01 to USERTIME05 |
datetime |
-- |
-- |
|
Additional element: Link#2 |
Display name |
JIMSD_FORM_REFINFO01 to JIMSD_FORM_REFINFO05 |
REFINFO_LINKURLDISP01 to REFINFO_LINKURLDISP05 |
url |
0 |
255 |
Related information |
REFINFO_LINKURL01 to REFINFO_LINKURL05 |
0 |
4,096 |
(2) Specifying the configuration file for incident inheritance information
For details about the basic procedure for specifying the configuration file for incident inheritance information (incident_info.conf), see the manual JP1/Integrated Management - Manager Command and Definition File Reference.
This subsection describes an example of how to specify the file to pass date and time event attributes such as a JP1 event Registered time, and an example of how to specify the file to link with JP1/NP.
To pass the basic attributes of the JP1 event, Registered time (TIME) and Arrived time (ARRIVEDTIME), to datetime type item elements of JP1/Service Support, use the format YYYY/MM/DD hh:mm:ss. However, the number of seconds is truncated because it cannot be input in time fields for item elements of JP1/Service Support. When you want to pass Registered time (TIME) or Arrived time (ARRIVEDTIME) of an event to JP1/Service Support, specify the configuration file for incident inheritance information (incident_info.conf) as follows:
- Example: When the Registered time of a JP1 event is passed to the Occurrence date and time (JIMSD_FORM_ACCRUALDATE) item element of JP1/Service Support
ACCRUALDATE=$EVDATE $EVTIME
Note that the extended attributes of the JP1 event, Start time (START_TIME) and End time (END_TIME), are set the number of seconds since UTC 1970-01-01 00:00:00, you cannot pass to datetime type item elements of JP1/Service Support. You can pass it to text or textarea type item elements.
As is the case with the registration mode of an incident 2, when you want to link with JP1/NP, specify the configuration file for incident inheritance information (incident_info.conf) as follows:
- Example: When mapping for the source host of JP1/IM - Manager is disabled
JP1PRODUCTNAME=$EV"PRODUCT_NAME" SUMMARY=$EVMSG\nHost where the JP1 event has occurred:$EVHOST\nEvent ID of the JP1 event:$EVIDBASE
- Example: When mapping for the source host of JP1/IM - Manager is enabled
JP1PRODUCTNAME=$EV"PRODUCT_NAME" SUMMARY=$EVMSG\nHost where the JP1 event has occurred:$EV"JP1_SOURCEHOST"\nEvent ID of the JP1 event:$EVIDBASE
(3) Notes
This subsection describes the notes about passing any attribute and string of a JP1 event as incidents.
-
Types of JP1/Service Support item elements determine configurable characters. Ensure consistency in types of source elements and destination item elements.
The following table lists configurable characters and behaviors when non-configurable characters are passed for each item element type.
Table 4‒7: Configurable characters and behaviors when non-configurable characters are passed Item element type
Configurable character
Behavior when non-configurable characters are passed
text
Characters other than control characters (0x00 to 0x1F, and 0x7F)
When a control character is specified as a line feed, the line feed is ignored.
When a control character is not specified as a line feed, the character is replaced with a single-byte space.
textarea
Characters other than control characters (0x00 to 0x09, 0x0B to 0x1F, and 0x7F)
Control characters not specified as a line feed are replaced with single-byte spaces.
code#
-
Emergency
-
Alert
-
Critical
-
Error
-
Warning
-
Notice
-
Information
-
Debug
Passed values are not set.
datetime
Strings in YYYY/MM/DD hh:mm:ss format, or null characters
Passed values are not set.
url
Characters other than control characters (0x00 to 0x1F, and 0x7F)
When a control character is specified as a line feed, the line feed is ignored.
When a control character is not specified as a line feed, the character is replaced with a single-byte space.
String configurable for "code"
Selection code
Default display name of a selection code
Emergency
1
Emergency
Alert
2
Alert
Critical
3
Critical
Error
4
Error
Warning
5
Warning
Notice
6
Notice
Information
7
Information
Debug
8
Debug
-
-
If you change the display name of a selection code for JIMSD_FORM_SEVERITYCODE (severity) by customizing the Item form, the severity specified by E.SEVERITY will not be passed as intended to JIMSD_FORM_SEVERITYCODE.
For example, assume that you assign Information as the display name of selection code 1. In that case, information with severity level Emergency will be passed from E.SEVERITY to JIMSD_FORM_SEVERITYCODE as Information.
-
If the length of a string to be passed to an item element exceeds the upper limit of that element, an error occurs when you click the Register button in the New item window. However, for the item element type url, a portion of a string exceeding the upper limit (display name: 255 bytes, related information: 4,096 bytes) is truncated but the remaining string is passed.
-
With the automatic item input function in a process work board enabled, this function is still enabled when an item is created via the JP1/IM - View linkage function. When destination item elements of information to be passed from JP1/IM - View are supported by the automatic item input function, values to be input by this function are assigned higher priority.