File for Item information entries (Optional)
- Organization of this page
Description
This file contains Item information to be registered in JP1/IM - Service Support. This file must be created in CSV format. To register the contents of this file in JP1/IM - Service Support, you must execute the jssitemimport command.
Format
#comment (Linefeed) "process-work-board-ID","title","severity","impact-level","priority",...(Linefeed) "process-work-board-ID","title","severity","impact-level","priority",...(Linefeed) : :
Lines starting with a hash mark (#) are treated as comments.
- Legend:
-
(Linefeed): Indicates a linefeed character.
File name
Use any file name.
Storage folder
Any folder on the host where the jssitemimport command is executed
When the definition is applied
When the jssitemimport command is executed, the contents of the file for Item information entries are applied to JP1/IM - Service Support.
What is described
Specify Item information in the order shown in the following table.
Specification order |
Element name |
Specifiable characters |
Specifiable number of bytes#1 |
Specify or not |
---|---|---|---|---|
1 |
Process work board ID |
Half-width alphanumeric characters |
1 to 64 bytes |
Y |
2 |
Title |
Other than control characters (0x00 to 0x1F, and 0x7F) |
1 to 512 bytes |
Y |
3 |
Severity |
Values defined by the code mapping file |
-- |
|
4 |
Impact level |
Values defined by the code mapping file |
-- |
|
5 |
Priority |
Values defined by the code mapping file |
-- |
|
6 |
Item type |
Values defined by the code mapping file |
-- |
|
7 |
Problem domain |
Values defined by the code mapping file |
-- |
|
8 |
Status |
Values defined by the code mapping file |
-- |
Y |
9 |
Work status |
Other than control characters (0x00 to 0x1F, and 0x7F) |
No more than 4,096 bytes |
|
10 |
Result |
Values defined by the code mapping file |
-- |
|
11 |
Update date and time#2 |
String in YYYY/MM/DD hh:mm:ss format#3 |
-- |
|
12 |
Occurrence date and time |
String in YYYY/MM/DD hh:mm:ss format#3 |
-- |
|
13 |
Registration date and time |
String in YYYY/MM/DD hh:mm:ss format#3 |
-- |
|
14 |
Start date and time |
String in YYYY/MM/DD hh:mm:ss format#3 |
-- |
|
15 |
Person in charge type |
Either USER or ROLE |
-- |
Y |
16 |
Person in charge |
Other than control characters (0x00 to 0x1F, and 0x7F) |
No more than 255 bytes |
Y |
17 |
Person in charge ID |
Half-width alphanumeric characters and underscores |
No more than 64 bytes |
Y |
18 |
Deadline |
String in YYYY/MM/DD hh:mm:ss format#3 |
-- |
|
19 |
Respondent type |
Either USER or ROLE |
-- |
#4 |
20 |
Respondent |
Other than control characters (0x00 to 0x1F, and 0x7F) |
No more than 255 bytes |
#4 |
21 |
Respondent ID |
Half-width alphanumeric characters |
No more than 64 bytes |
#4 |
22 |
End date and time |
String in YYYY/MM/DD hh:mm:ss format#3 |
-- |
|
23 |
Customer name |
Other than control characters (0x00 to 0x1F, and 0x7F) |
No more than 1,024 bytes |
|
24 |
Inquirer |
Other than control characters (0x00 to 0x1F, and 0x7F) |
No more than 255 bytes |
|
25 |
Cost (planned) |
An integer from 0 to 2147483647 |
-- |
|
26 |
Cost (actual) |
An integer from 0 to 2147483647 |
-- |
|
27 |
Impact service |
Other than control characters (0x00 to 0x1F, and 0x7F) |
No more than 255 bytes |
|
28 |
Overview |
Other than control characters (0x00 to 0x1F, and 0x7F) |
No more than 2,048 bytes |
|
29 |
Occurred type |
Values defined by the code mapping file |
-- |
|
30 |
Cause |
Values defined by the code mapping file |
-- |
|
31 |
Fundamental cause |
Other than control characters (0x00 to 0x1F, and 0x7F) |
No more than 4,096 bytes |
|
32 |
Workaround type |
Values defined by the code mapping file |
-- |
|
33 |
Workaround |
Other than control characters (0x00 to 0x1F, and 0x7F) |
No more than 4,096 bytes |
|
34 |
Solution category |
Values defined by the code mapping file |
-- |
|
35 |
Solution |
Other than control characters (0x00 to 0x1F, and 0x7F) |
No more than 4,096 bytes |
|
36 |
Problem component and version |
Other than control characters (0x00 to 0x1F, and 0x7F) |
No more than 1,024 bytes |
|
37 |
How to avoid the problem in the future |
Other than control characters (0x00 to 0x1F, and 0x7F) |
No more than 4,096 bytes |
|
38 |
Schedule and main steps |
Other than control characters (0x00 to 0x1F, and 0x7F) |
No more than 4,096 bytes |
|
39 |
Impact assessment for change |
Other than control characters (0x00 to 0x1F, and 0x7F) |
No more than 4,096 bytes |
|
40 |
Scale of change |
Values defined by the code mapping file |
-- |
|
41 |
Release type |
Values defined by the code mapping file |
-- |
|
42 |
Discussions result |
Other than control characters (0x00 to 0x1F, and 0x7F) |
No more than 2,048 bytes |
|
43 |
Free memo column |
Other than control characters (0x00 to 0x1F, and 0x7F) |
No more than 4,096 bytes |
|
44 |
Reason for severity |
Other than control characters (0x00 to 0x1F, and 0x7F) |
No more than 512 bytes |
|
45 |
Reason for impact level |
Other than control characters (0x00 to 0x1F, and 0x7F) |
No more than 512 bytes |
|
46 |
Reason for priority |
Other than control characters (0x00 to 0x1F, and 0x7F) |
No more than 512 bytes |
|
47 |
Product name |
Other than control characters (0x00 to 0x1F, and 0x7F) |
No more than 1,024 bytes |
|
48 |
Jobnet name |
Other than control characters (0x00 to 0x1F, and 0x7F) |
No more than 1,024 bytes |
|
49 |
Job name |
Other than control characters (0x00 to 0x1F, and 0x7F) |
No more than 1,024 bytes |
|
50 |
SNMP source |
Other than control characters (0x00 to 0x1F, and 0x7F) |
No more than 1,024 bytes |
|
51 |
Monitored node name |
Other than control characters (0x00 to 0x1F, and 0x7F) |
No more than 255 bytes |
|
52 |
Alarm name |
Other than control characters (0x00 to 0x1F, and 0x7F) |
No more than 255 bytes |
|
53 |
Extended text 01 |
Other than control characters (0x00 to 0x1F, and 0x7F) |
No more than 4,096 bytes |
|
54 |
Extended text 02 |
Other than control characters (0x00 to 0x1F, and 0x7F) |
No more than 4,096 bytes |
|
55 |
Extended text 03 |
Other than control characters (0x00 to 0x1F, and 0x7F) |
No more than 4,096 bytes |
|
56 |
Extended text 04 |
Other than control characters (0x00 to 0x1F, and 0x7F) |
No more than 4,096 bytes |
|
57 |
Extended text 05 |
Other than control characters (0x00 to 0x1F, and 0x7F) |
No more than 4,096 bytes |
|
58 |
Extended text 06 |
Other than control characters (0x00 to 0x1F, and 0x7F) |
No more than 2,048 bytes |
|
59 |
Extended text 07 |
Other than control characters (0x00 to 0x1F, and 0x7F) |
No more than 2,048 bytes |
|
60 |
Extended text 08 |
Other than control characters (0x00 to 0x1F, and 0x7F) |
No more than 2,048 bytes |
|
61 |
Extended text 09 |
Other than control characters (0x00 to 0x1F, and 0x7F) |
No more than 2,048 bytes |
|
62 |
Extended text 10 |
Other than control characters (0x00 to 0x1F, and 0x7F) |
No more than 2,048 bytes |
|
63 |
Extended text 11 |
Other than control characters (0x00 to 0x1F, and 0x7F) |
No more than 2,048 bytes |
|
64 |
Extended text 12 |
Other than control characters (0x00 to 0x1F, and 0x7F) |
No more than 2,048 bytes |
|
65 |
Extended text 13 |
Other than control characters (0x00 to 0x1F, and 0x7F) |
No more than 2,048 bytes |
|
66 |
Extended text 14 |
Other than control characters (0x00 to 0x1F, and 0x7F) |
No more than 2,048 bytes |
|
67 |
Extended text 15 |
Other than control characters (0x00 to 0x1F, and 0x7F) |
No more than 2,048 bytes |
|
68 |
Extended text 16 |
Other than control characters (0x00 to 0x1F, and 0x7F) |
No more than 512 bytes |
|
69 |
Extended text 17 |
Other than control characters (0x00 to 0x1F, and 0x7F) |
No more than 512 bytes |
|
70 |
Extended text 18 |
Other than control characters (0x00 to 0x1F, and 0x7F) |
No more than 512 bytes |
|
71 |
Extended text 19 |
Other than control characters (0x00 to 0x1F, and 0x7F) |
No more than 512 bytes |
|
72 |
Extended text 20 |
Other than control characters (0x00 to 0x1F, and 0x7F) |
No more than 512 bytes |
|
73 |
Extended time data 01 |
String in YYYY/MM/DD hh:mm:ss format#3 |
-- |
|
74 |
Extended time data 02 |
String in YYYY/MM/DD hh:mm:ss format#3 |
-- |
|
75 |
Extended time data 03 |
String in YYYY/MM/DD hh:mm:ss format#3 |
-- |
|
76 |
Extended time data 04 |
String in YYYY/MM/DD hh:mm:ss format#3 |
-- |
|
77 |
Extended time data 05 |
String in YYYY/MM/DD hh:mm:ss format#3 |
-- |
|
78 |
Extended code data 01 |
Values defined by the code mapping file |
-- |
|
79 |
Extended code data 02 |
Values defined by the code mapping file |
-- |
|
80 |
Extended code data 03 |
Values defined by the code mapping file |
-- |
|
81 |
Extended code data 04 |
Values defined by the code mapping file |
-- |
|
82 |
Extended code data 05 |
Values defined by the code mapping file |
-- |
|
83 |
Extended numeric value data 01 |
An integer from 0 to 2147483647 or blank |
-- |
|
84 |
Extended numeric value data 02 |
An integer from 0 to 2147483647 or blank |
-- |
|
85 |
Extended numeric value data 03 |
An integer from 0 to 2147483647 or blank |
-- |
|
86 |
Extended numeric value data 04 |
An integer from 0 to 2147483647 or blank |
-- |
|
87 |
Extended numeric value data 05 |
An integer from 0 to 2147483647 or blank |
-- |
|
88 |
Extended user information type 01#5 |
Either USER or ROLE |
-- |
#6 |
89 |
Extended user information 01#5 |
Other than control characters (0x00 to 0x1F, and 0x7F) |
No more than 255 bytes |
|
90 |
Extended user information ID 01#5 |
Half-width alphanumeric characters |
No more than 64 bytes |
|
91 |
Extended user information type 02#5 |
Either USER or ROLE |
-- |
#6 |
92 |
Extended user information 02#5 |
Other than control characters (0x00 to 0x1F, and 0x7F) |
No more than 255 bytes |
|
93 |
Extended user information ID 02#5 |
Half-width alphanumeric characters |
No more than 64 bytes |
|
94 |
Extended user information type 03#5 |
Either USER or ROLE |
-- |
#6 |
95 |
Extended user information 03#5 |
Other than control characters (0x00 to 0x1F, and 0x7F) |
No more than 255 bytes |
|
96 |
Extended user information ID 03#5 |
Half-width alphanumeric characters |
No more than 64 bytes |
|
97 |
Extended user information type 04#5 |
Either USER or ROLE |
-- |
#6 |
98 |
Extended user information 04#5 |
Other than control characters (0x00 to 0x1F, and 0x7F) |
No more than 255 bytes |
|
99 |
Extended user information ID 04#5 |
Half-width alphanumeric characters |
No more than 64 bytes |
|
100 |
Extended user information type 05#5 |
Either USER or ROLE |
-- |
#6 |
101 |
Extended user information 05#5 |
Other than control characters (0x00 to 0x1F, and 0x7F) |
No more than 255 bytes |
|
102 |
Extended user information ID 05#5 |
Half-width alphanumeric characters |
No more than 64 bytes |
A line indicates information for an Item. Enclose elements of Item information in double-quotation marks ("), and separate elements with commas (,). Elements other than process-work-board-ID, title, status, person-in-charge-type, person-in-charge, and Person in charge ID are optional, but the elements cannot be omitted. Even if you do not want to specify an Item, you need to leave double quotation marks (") for the applicable element. In addition, the order that the Items must be specified in is fixed.
The following is an example when severity is omitted:
"process-work-board-ID","title","","impact-level","priority",...(Linefeed)
Notes
-
process-work-board-ID, title, status, person-in-charge-type, person-in-charge, and person-in-charge-ID must be specified. In addition, you must create a process work board that has the applicable process work board ID before applying the contents of this file to JP1/IM - Service Support.
-
When you specify information for the following elements, you must synchronize it with the values you specified in the code mapping file:
Severity, impact level, priority, Item type, problem domain, status, result, occurrence type, workaround type, solution category, scale of change, and release type
For details, see Code mapping file (jp1imss_itemimport_codemap.conf) in Chapter 12. Definition Files.
-
Element names might be changed due to customization. For details, see Item form definition file (Optional) in Chapter 12. Definition Files. If you customize element names, replace the element names in Table 12-17 with the names after customization. Note that if you customize element names, the specification order does not change.
-
If you specify 103 or more elements as elements in an input file, the first 102 elements are registered. Because elements from 53 to 102 are optional, they will be blank if you omit them.
-
If a control character (0x00) is included in a setting element in an input file, it is not regarded as an invalid definition. In such a case, the characters before the control character in a specified string are treated as specified.
For example, if you specify hitachitaro# as the user name, hitachi becomes the display name.
#: Here, is assumed to be a control character (0x00).
-
The File for Item information entries 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 when you register multiple Item information for the AWebSystem process work board ID:
"AWebSystem","System failure","Emergency","Small","Standard","Failure","Application","Received","Before starting work","Not confirmed","Register","2006/10/30 10:15:30","2006/10/29 23:55:40","2006/10/30 10:15:30"...(Linefeed) "AWebSystem","System failure","Warning","Middle","Standard","Failure","Middleware","Received","Before starting work","Not confirmed","Register","2006/10/30 10:15:30","2006/10/30 08:30:30","2006/10/30 10:15:30"...(Linefeed) "AWebSystem","Abnormal end of process","Critical","Large","Urgent","Failure","Application","Received","Before starting work","Not confirmed","Register","2006/10/30 10:15:30","2006/10/30 09:14:40","2006/10/30 10:15:30"...(Linefeed) :