Definition file for status-change JP1 events (hptl_jp1_imss_jp1event_status.properties)
- Organization of this page
Description
This file defines information held by an Item as an extended attribute of the status change JP1 event. By editing this file, you can define Item information to be stored in a JP1 event.
For details about JP1 events, see Appendix E. List of JP1 Events.
Format
hptl_jp1_imss_je_status_num=Number of extended attributes (index value) hptl_jp1_imss_je_status_extattr_index_value=Extended attribute name
File names
-
hptl_jp1_imss_jp1event_status.properties (Definition file for status-change JP1 events)
-
hptl_jp1_imss_jp1event_status.properties.model (Model definition file for status-change JP1 events)#
- #
-
You can use the model file to reset the contents of the definition file for status-change JP1 events. To do so, delete the existing definition file for status-change JP1 events, then copy and rename the model file.
Storage folder
IM-SS-path\conf\event\
When the definition is applied
The definition is applied after the JP1/IM - Service Support service is restarted.
What is described
You can edit the specification keys described in the table below. Use an equal sign (=) to connect a specifiable key and its value.
Specification key name |
Description |
Default value |
---|---|---|
hptl_jp1_imss_je_status_num |
Specify an integer from 0 to 90 for n so that hptl_jp1_imss_je_status_extattr_n becomes valid. If the value is out of the specifiable range, 0 is assumed. |
0 |
hptl_jp1_imss_je_status_extattr_n |
Specify the extended attribute name applicable for an Item element. The element you specify is stored as an extended attribute of a JP1 event. You can comment out the property of each extended attribute by using #. For details about specifiable values, see Table 12-38. |
-- |
- Legend:
-
--: No default value
No. |
Item related element |
Extended attribute |
Extended attribute of the storage destination |
Specification |
Remarks |
---|---|---|---|---|---|
1 |
Title (Item name) |
TITLE |
Fixed |
Y |
-- |
2 |
System name |
SYSTEM |
Fixed |
Y |
-- |
3 |
System ID |
SYSTEMID |
Fixed |
Y |
-- |
4 |
Process name |
PROCESS |
Fixed |
Y |
-- |
5 |
Process work board ID |
PWBID |
Fixed |
Y |
-- |
6 |
Item ID |
OBJECT_ID |
Common |
N |
Cannot be specified in the definition file (must be stored in a JP1 event). |
7 |
Inter-process ID |
PROCESS_SEPID |
Fixed |
Y |
-- |
8 |
Escalation source Item ID |
FRESC_ITEMID |
Fixed |
Y |
-- |
9 |
Escalation-destination Item ID |
TOESC_ITEMID |
Fixed |
Y |
If there are multiple escalation destinations, separate them with commas to store them. |
10 |
Severity |
ITEMSEVERITY |
Fixed |
Y |
-- |
11 |
Reason for severity |
ITEMSEVERITY_REASON |
Fixed |
Y |
-- |
12 |
Impact level |
IMPACT |
Fixed |
Y |
-- |
13 |
Reason for impact level |
IMPACT_REASON |
Fixed |
Y |
-- |
14 |
Priority |
PRIORITY |
Fixed |
Y |
-- |
15 |
Reason for priority |
PRIORITY_REASON |
Fixed |
Y |
-- |
16 |
Item type |
ITEM_CATEGORY |
Fixed |
Y |
-- |
17 |
Problem domain |
ISSUE_CATEGORY |
Fixed |
Y |
-- |
18 |
Scale of change |
CHANGE_SCALE |
Fixed |
Y |
-- |
19 |
Release type |
RELEASE_TYPE |
Fixed |
Y |
-- |
20 |
Status |
STATUS |
Fixed |
Y |
-- |
21 |
Result |
RESULT |
Fixed |
Y |
-- |
22 |
Occurrence date and time |
ACCRUALDATE |
Fixed |
Y |
-- |
23 |
Occurred type#1 |
PHENOMENON |
Fixed |
Y |
-- |
24 |
Solution category |
SOLUTIONCODE |
Fixed |
Y |
-- |
25 |
Registrant |
REGISTRANT |
Fixed |
Y |
-- |
26 |
Registrant ID |
REGISTRANT ID |
Fixed |
Y |
-- |
27 |
Registrant's email address |
REGISTRANT_ADDRESS |
Fixed |
Y |
-- |
28 |
Registrant's telephone number#2 |
REGISTRANT_TEL |
Fixed |
Y |
-- |
29 |
Registration date and time |
CREATIONDATE |
Fixed |
Y |
-- |
30 |
Person in charge |
ASSIGNED |
Fixed |
Y |
-- |
31 |
Person in charge type |
ASSIGNEDTYPE |
Fixed |
Y |
-- |
32 |
Person in charge ID |
ASSIGNEDID |
Fixed |
Y |
-- |
33 |
Email address of person in charge#3 |
ASSIGNED_ADDRESS |
Fixed |
Y |
-- |
34 |
Telephone number of person in charge#2, #3 |
ASSIGNED_TEL |
Fixed |
Y |
-- |
35 |
Deadline |
DEADLINE |
Fixed |
Y |
-- |
36 |
Respondent |
RESPONDENT |
Fixed |
Y |
-- |
37 |
Respondent type |
RESPONDENTTYPE |
Fixed |
Y |
-- |
38 |
Respondent ID |
RESPONDENTID |
Fixed |
Y |
-- |
39 |
Email address of respondent#3 |
RESPONDENT_ADDRESS |
Fixed |
Y |
-- |
40 |
Phone number of respondent#2, #3 |
RESPONDENT_TEL |
Fixed |
Y |
-- |
41 |
Editor |
USER_NAME |
Common |
N |
Cannot be specified in the definition file (must be stored in a JP1 event). |
42 |
Editor ID |
CREATOR_ID |
Fixed |
Y |
-- |
43 |
Editor's email address |
CREATOR_ADDRESS |
Fixed |
Y |
-- |
44 |
Editor's telephone number#2 |
CREATOR_TEL |
Fixed |
Y |
-- |
45 |
Process work board manager |
PWB_ADMIN |
Fixed |
Y |
-- |
46 |
Process work board manager ID |
PWB_ADMINID |
Fixed |
Y |
-- |
47 |
Email address of the process work board manager#3 |
PWB_ADMIN_ADDRESS |
Fixed |
Y |
-- |
48 |
Phone number of the process work board manager#2, #3 |
PWB_ADMIN_TEL |
Fixed |
Y |
-- |
49 |
Start date and time |
STARTDATE |
Fixed |
Y |
-- |
50 |
End date and time |
COMPDATE |
Fixed |
Y |
-- |
51 |
Customer name |
CUSTOMER |
Fixed |
Y |
-- |
52 |
Inquirer |
INQUIRY |
Fixed |
Y |
-- |
53 |
Cost (planned) |
ESTIMATEDCOST |
Fixed |
Y |
-- |
54 |
Cost (actual) |
ACTUALCOST |
Fixed |
Y |
-- |
55 |
Impact service#1 |
EFFECTSRV |
Fixed |
Y |
-- |
56 |
Hardware information 01 to 20#4, #5 |
EQUIPMENT01 to EQUIPMENT20 |
Fixed |
Y |
-- |
57 |
Device type 01 to 20#4, #5 |
EQUIPMENTTYPE01 to EQUIPMENTTYPE20 |
Fixed |
Y |
-- |
58 |
Server name 01 to 20#4, #5 |
AIMSRV01 to AIMSRV20 |
Fixed |
Y |
-- |
59 |
Problem component and version |
FAILLOCATION |
Fixed |
Y |
-- |
60 |
Related item(s) 01 to 20#4, #5 |
REFITEM01 to REFITEM20 |
Fixed |
Y |
-- |
61 |
Related information (Display name) 01 to 20#4, #5 |
REFINFODISP01 to REFINFODISP20 |
Fixed |
Y |
-- |
62 |
Related information01 to 20#4, #5 |
REFINF01 to REFINF20 |
Fixed |
Y |
-- |
63 |
Overview |
SUMMARY |
Fixed |
Y |
-- |
64 |
Workaround type |
AVOIDANCETYPE |
Fixed |
Y |
-- |
65 |
Workaround |
AVOIDANCE |
Fixed |
Y |
-- |
66 |
Work status |
SITUATION |
Fixed |
Y |
-- |
67 |
How to avoid the problem in the future#1 |
MEASURES |
Fixed |
Y |
-- |
68 |
Cause |
CAUSE |
Fixed |
Y |
-- |
69 |
Fundamental cause |
ROOTCAUSE |
Fixed |
Y |
-- |
70 |
Solution |
SOLUTION |
Fixed |
Y |
-- |
71 |
Schedule and main steps |
SCHEDULE |
Fixed |
Y |
-- |
72 |
Impact assessment for change |
IMPACTEVAL |
Fixed |
Y |
-- |
73 |
Discussions result |
DELIBERATIONRST |
Fixed |
Y |
-- |
74 |
Free memo column |
FREEDESC |
Fixed |
Y |
-- |
75 |
Product name |
PRODUCTNAME |
Fixed |
Y |
-- |
76 |
Jobnet name |
JOBNETNAME |
Fixed |
Y |
-- |
77 |
Job name |
JOBNAME |
Fixed |
Y |
-- |
78 |
SNMP source |
SNMPSRC |
Fixed |
Y |
-- |
79 |
Monitored node name |
NODENAME |
Fixed |
Y |
-- |
80 |
Alarm name |
ALARMNAME |
Fixed |
Y |
-- |
81 |
Update date and time |
LASTUPDATE |
Common |
N |
Cannot be specified in the definition file (must be stored in a JP1 event). |
82 |
Link source event database serial number |
ITEMENTRY_SEQNO |
Fixed |
Y |
-- |
83 |
JP1/IM-M host name |
ITEMENTRY_ACTHOST |
Fixed |
Y |
-- |
84 |
Extended text 01 to 05#4 |
USERTEXT01 to USERTEXT05 |
Fixed |
Y |
-- |
85 |
Extended text 06 to 15#4 |
USERTEXT06 to USERTEXT15 |
Fixed |
Y |
-- |
86 |
Extended text 16 to 20#4, #5 |
USERTEXT16 to USERTEXT20 |
Fixed |
Y |
-- |
87 |
Extended numeric value data 01 to 05#4 |
USERINT01 to USERINT05 |
Fixed |
Y |
-- |
88 |
Extended user/role type 01 to 05#4 or Extended user/role ID 01 to 05#4 |
USEREXTNAME01 to USEREXTNAME05 |
Fixed |
Y |
-- |
89 |
Extended user information ID 01 to 05#4 |
USEREXTINF01 to USEREXTINF05 |
Fixed |
Y |
-- |
90 |
Extended user type 01 to 05#4 |
USEREXTTYPE01 to USEREXTTYPE05 |
Fixed |
Y |
-- |
91 |
Extended code data 01 to 05#4 |
USERCODE01 to USERCODE05 |
Fixed |
Y |
-- |
92 |
Extended time data 01 to 05#4 |
USERTIME01 to USERTIME 05 |
Fixed |
Y |
-- |
93 |
Extended link data Hardware information 1 to 5_01 to 20#4, #5 |
USERLINK_EQUIPMENT01_01 to USERLINK_EQUIPMENT01_20 USERLINK_EQUIPMENT02_01 to USERLINK_EQUIPMENT05_20 |
Fixed |
Y |
-- |
94 |
Extended link data Device type 1 to 5_01 to 20#4, #5 |
USERLINK_EQUIPMENTTYPE01_01 to USERLINK_EQUIPMENTTYPE01_20 USERLINK_EQUIPMENTTYPE02_01 to USERLINK_EQUIPMENTTYPE05_20 |
Fixed |
Y |
-- |
95 |
Extended link data Server names 1 to 5_01 to 20#4, #5 |
USERLINK_AIMSRV01_01 to USERLINK_AIMSRV01_20 USERLINK_AIMSRV02_01 to USERLINK_AIMSRV05_20 |
Fixed |
Y |
-- |
96 |
Extended link data Related item(s) 1 to 5_01 to 20#4, #5 |
USERLINK_REFITEM01_01 to USERLINK_REFITEM01_20 USERLINK_REFITEM02_01 to USERLINK_REFITEM05_20 |
Fixed |
Y |
-- |
97 |
Extended link data Related information (Display name) 1 to 5_01 to 20#4, #5 |
USERLINK_REFINFODISP01_01 to USERLINK_REFINFODISP01_20 USERLINK_REFINFODISP02_01 to USERLINK_REFINFODISP05_20 |
Fixed |
Y |
-- |
98 |
Extended link data Related information 1 to 5_01 to 20#4, #5 |
USERLINK_REFINFO01_01 to USERLINK_REFINFO01_20 USERLINK_REFINFO02_01 to USERLINK_REFINFO05_20 |
Fixed |
Y |
-- |
- Legend:
-
Y: Elements that can be specified in a definition file.
N: Elements that cannot be specified in a definition file.
--: None
- #1
-
This element is not displayed by default.
- #2
-
The phone number in the applicable user information is set. Information for Phone number 2 is not set.
- #3
-
If the person in charge, a respondent, and a process work board manager are roles, the applicable information is not stored.
- #4
-
Indicates multiple extended attributes.
- #5
-
Corresponds to the number assigned to the applicable Item.
Notes
-
The property (hptl_jp1_imss_je_status_extattr_n) of an extended attribute that has an index value (n) which is greater than the value specified for hptl_jp1_imss_je_status_num is ignored.
-
If the index value of a property (hptl_jp1_imss_je_status_extattr_n) for an extended attribute is smaller than the value specified for hptl_jp1_imss_je_status_num, the properties to n are valid.
-
If a property (hptl_jp1_imss_je_status_extattr_n) for an extended attribute is specified more than once, the value that is specified later is valid.
-
Because lines beginning with the hash marks (#) are commented out, they are ignored.
-
If you specify an extended attribute that does not exist for hptl_jp1_imss_je_status_extattr_n, it is ignored.
-
If the total size of the basic attribute value and the extended attribute value for a JP1 event to be issued is equal to or greater than 10,000 bytes, an error message is output to the error window and to the log file when the event is issued. When the specified string contains a full-width character, it is converted to two bytes, but the Item is registered in the Item database correctly.
-
Even if issuing a JP1 event fails, the Item is registered in the Item database correctly.
-
When an Item element stored in an extended attribute contains linefeed characters, tab characters, or control characters, they are replaced with spaces before the element is stored in a JP1 event.
-
The Definition file for status-change JP1 events (hptl_jp1_imss_jp1event_status.properties) must be created or edited with a character encoding that is compatible with the system locale of the machine on which JP1/IM - Service Support is installed. You can use one of the following character encodings:
-
In a Japanese environment: MS932
-
In an English environment: ISO-8859-1
-
In a Chinese environment: GB18030
-
Definition example
The following is a definition example of Item information (extended attributes) to be stored in a JP1 event:
#Number of extended attributes to be stored in a JP1 event to be issued hptl_jp1_imss_je_status_num=5 #Item title hptl_jp1_imss_je_status_extattr_1=TITLE #Item - Priority hptl_jp1_imss_je_status_extattr_2=PRIORITY #Phone number of the person in charge of the Item hptl_jp1_imss_je_status_extattr_3=ASSIGNED_TEL #Problem domain of the Item hptl_jp1_imss_je_status_extattr_4=ISSUE_CATEGORY #Item - Occurrence date and time hptl_jp1_imss_je_status_extattr_5=ACCRUALDATE