Code mapping file (jp1imss_itementry_codemap.conf)
- Organization of this page
Description
This definition file associates option information specified by using the jssitementry command with the information to be displayed in an Item element of a selection code in the Item form. Do not edit this file because it is associated with selectable Item elements that are defined by default.
If you customize an Item element or a status name, create a new file for the customization.
Note that when you create a new code mapping file, specify the file name described below within 255 bytes in the absolute path.
Format
;comment [SEVERITY] Emergency=1 : [IMPACT] S=1 : [PRIORITY] N=1 : [ITEMCATEGORY] QUE=1 : [ISSUECATEGORY] APP=1 : [CITYPE] HOST=0 :
Lines starting with a semicolon (;) are treated as comments.
File names
-
jp1imss_itementry_codemap.conf (Code mapping file)
-
jp1imss_itementry_codemap.conf.model (Model code mapping file)#
- #
-
You can use the model file to reset the contents of the code mapping file. To do so, delete the existing code mapping file, then copy and rename the model file.
Storage folder
IM-SS-path\conf\command\
When the definition is applied
The definition is applied to JP1/IM - Service Support when you execute the jssitementry command.
What is described
The following is the format of the code mapping file:
[Section] Key=value Key=value :
For Section, specify a name indicating the applicable Item element. This is the name defined in the code mapping file. For Key, specify a value you will specify as an option of the jssitementry command. You can specify a string of half-width or full-width alphanumeric characters for Key. For value, specify the display order of the selection codes that are defined in the Item form definition file.
To use JP1/IM - Service Support with the default Item form, you can use the code mapping file provided with the product as is. The table below lists the sections, keys, and values that can be defined in the file.
If you customize the Item form, you must edit the code mapping file of the customized Item form to create a new file.
Section |
Description |
Key |
Selection code in an Item element |
Value |
---|---|---|---|---|
SEVERITY |
Section for determining the selection value for the Severity Item element |
Emergency |
Emergency |
1 |
Alert |
Alert |
2 |
||
Critical |
Critical |
3 |
||
Error |
Error |
4 |
||
Warning |
Warning |
5 |
||
Notice |
Notice |
6 |
||
Information |
Information |
7 |
||
Debug |
Debug |
8 |
||
IMPACT |
Section for determining the selection value for the Impact level Item element |
S |
Small |
1 |
M |
Middle |
2 |
||
B |
Large |
3 |
||
PRIORITY |
Section for determining the selection value for the Priority Item element |
N |
Normal |
1 |
M |
Urgent |
2 |
||
H |
Very urgent |
3 |
||
ITEMCATEGORY |
Section for determining the selection value for the Item type Item element |
QUE |
Inquiry |
1 |
FAL |
Failure |
2 |
||
CR |
Customer request |
3 |
||
ISSUECATEGORY |
Section for determining the selection value for the Problem domain Item element |
APP |
Application |
1 |
MID |
Middleware |
2 |
||
OS |
OS |
3 |
||
HRD |
Hardware |
4 |
||
NET |
Network |
5 |
||
PRO |
Process |
6 |
||
CITYPE |
Section for determining the selection value for the Asset type Item element |
HOST |
Host name (JP1/AIM) |
0 |
IP |
IP address (JP1 /AIM) |
1 |
||
ASSETID |
Asset number |
2 |
||
USERCODE01 |
User extended code |
Optional |
Optional |
Optional |
USERCODE02 |
||||
USERCODE03 |
||||
USERCODE04 |
||||
USERCODE05 |
Notes
-
Do not customize the PRIORITY section. If you customize and register an Item, the Item will be registered in the customized information in the Item management database, but it will not be displayed in the window.
-
If you add or remove a selection code for an defined selectable element in the Item form definition file, you must modify the keys and values defined in the code mapping file accordingly. For example, if you add display order 4 of the selection code and selection code Very large to the Impact level element in the Item form definition file, you must define the code mapping file as follows:
[IMPACT] S=1 M=2 B=3 BB=4
Note that you will also use BB you defined here as the specification value for the -ipt option of the jssitementry command.
For details about the jssitementry command, see jssitementry (registers an Item) in Chapter 11. Commands.
For details about the Item form definition file, see Item form definition file (Optional) in Chapter 12. Definition Files.
-
The Code mapping file (jp1imss_itementry_codemap.conf) 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 are the contents of the default code mapping file (jp1imss_itementry_codemap.conf):
[SEVERITY] Emergency=1 Alert=2 Critical=3 Error=4 Warning=5 Notice=6 Information=7 Debug=8 [IMPACT] S=1 M=2 B=3 [PRIORITY] N=1 M=2 H=3 [ITEMCATEGORY] QUE=1 FAL=2 CR=3 [ISSUECATEGORY] APP=1 MID=2 OS=3 HRD=4 NET=5 PRO=6 [CITYPE] HOST=0 IP=1 ASSETID=2 UCMDBHOST=3 UCMDBIP=4 UCMDBID=5 [USERCODE01] [USERCODE02] [USERCODE03] [USERCODE04] [USERCODE05]