Code mapping file (jp1imss_itemimport_codemap.conf)

Description

This definition file associates the file for Item information entries that is specified by using the jssitemimport command with information that is displayed as Item elements of selection codes in an 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.

To Page Top

Format

;comment
[SEVERITY]
Emergency=1
  :
[IMPACT]
Small=1
  :
[PRIORITY]
Standard=1
  :
[ITEMCATEGORY]
Inquiry=1
  :
[ISSUECATEGORY]
Application=1
  :
[PHENOMENON]
-
[STATUS]
Received=JIMSS_STAT_INQUIRY
  :
[CAUSE]
New software error=1
  :
[RESULT]
Completed=1
  :
[SOLUTION]
Knowledge=1
  :
[AVOIDANCE]
None=1
  :
[CHANGESCALE]
Small scale=1
  :
[RELEASETYPE]
Package release=1
  :

Lines starting with a semicolon (;) are treated as comments.

Legend:

--: Not specified

To Page Top

File names

• jp1imss_itemimport_codemap.conf (Code mapping file)

• jp1imss_itemimport_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.

To Page Top

Storage folder

JP1/SS-path\conf\command\

To Page Top

When the definition is applied

The definition is applied to JP1/Service Support when you execute the jssitemimport command.

To Page Top

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 a name determined in the code mapping file. For Key, specify a value defined in the file for Item information entries and specified as an option of the jssitemimport 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/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 for the customized Item form to create a new file.

To Page Top

Notes

• Do not customize the PRIORITY section. If you customize and import an Item, the Item will be registered as the customized information in the Item management database, but it will not be displayed in a window.

• You can specify a total of 48 statuses by using the jssitemimport command including eight default statuses provided by JP1/Service Support, and 40 statuses that can be customized by users. If you specify any other status, the KNAB26013-E error occurs. An Item status registered by using the jssitemimport command will be registered regardless of whether it is used in the process work board at the registration destination.

• For selectable elements defined in the Item form definition file, if you add or remove a selection code, 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]
  Small=1
  Middle=2
  Large=3
  Very large=4

  Note that Very large which is defined here will also be used as the specification value of the Impact level element to be entered in the Item information file. This Very large value is also used as an argument of the jssitemimport command.

  For details about the jssitemimport command, see jssitemimport (imports Item information) in Chapter 12. Commands.

  For details about the Item form definition file, see Item form definition file (Optional) in Chapter 13. Definition Files.

• If you edit a status name, edit the code mapping file and the file for Item information entries in the following order:

  1. Edit the status name.

  2. Edit the code mapping file.

  3. Edit the file for Item information entries.

  Edit a defined key in the code mapping file according to the status name after the edit. For example, if you change Close to End, you must define the code mapping file as follows:

  [STATUS]
  Received=JIMSD_STAT_INQUIRY
  End=JIMSD_STAT_CLOSE

  If the status name and the key defined in the code mapping file are different, no error occurs. But, if a key in the code mapping file and the matching key in the file for Item information entries are different, an error occurs.

• The Code mapping file (jp1imss_itemimport_codemap.conf) must be created or edited with a character encoding that is compatible with the system locale of the machine on which JP1/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

To Page Top

Definition example

The following example shows the default contents of the code mapping file (jp1imss_itemimport_codemap.conf):

[SEVERITY]
Emergency=1
Alert=2
Critical=3
Error=4
Warning=5
Notice=6
Information=7
Debug=8
 
[IMPACT]
Small=1
Middle=2
Large=3
 
[PRIORITY]
Standard=1
Urgent=2
Very urgent=3
 
[ITEMCATEGORY]
Inquiry=1
Failure=2
Customer request=3
 
[ISSUECATEGORY]
Application=1
Middleware=2
OS=3
Hardware=4
Network=5
Process=6
 
[PHENOMENON]
 
[STATUS]
Received=JIMSD_STAT_INQUIRY
Close=JIMSD_STAT_CLOSE
 
[CAUSE]
New software error=1
Known software error=2
New hardware error=3
Known hardware error=4
Documentation error=5
Document missing=6
User error=7
Specifications=8
Third-party error=9
Process error=10
Customer request=11
Function extension=12
Business requirement=13
Incident and problem fix=14
Process improvement=15
 
[RESULT]
Completed=1
Canceled=2
Not confirmed=3
Change completed=4
Known problem=5
Unknown cause=6
Succeeded=7
Failed (planning error)=8
Failed (human error)=9
Failed (others)=10
 
[SOLUTION]
Knowledge=1
Document=2
User solution=3
Secondary support=4
Problem management=5
Third-party investigation=6
 
[AVOIDANCE]
None=1
Not operated=2
Operated in degraded mode=3
Restarted=4
File recovered=5
Change rolled back=6
Others=7
 
[CHANGESCALE]
Small scale=1
Middle scale=2
Large scale=3
 
[RELEASETYPE]
Package release=1
Full release=2
Delta release=3
 
[USERCODE01]
 
[USERCODE02]
 
[USERCODE03]
 
[USERCODE04]
 
[USERCODE05]

To Page Top