Hitachi

JP1 Version 12 JP1/Integrated Management 2 - Manager Administration Guide

11.2.4 Log files and directory list

This subsection explains the types of log information that are output by JP1/IM, default file names, and directory names.

Note that the files explained here are output for product maintenance purposes. Therefore, there is no need for the user to view or modify these files. If a problem such as a system error occurs, the user may be asked to temporarily retain these files on site for the purpose of collecting data.

Organization of this subsection

(1) In Windows

The tables below show the default log files and folders that are output by the Windows version of JP1/IM.

The Log type column lists the log types that are output by JP1/IM.

The Default file name and folder name column describes log file names as absolute paths when JP1/IM - Manager, JP1/IM - View, or JP1/Base is installed in the default mode. Default file name and folder name in a cluster operation system describes the log file names of shared folders as absolute paths.

The Maximum disk usage column shows the maximum disk space used by each log file. When there are multiple log files, the combined total is given.

The File-switching timing column shows how JP1/IM times output destination log file switching. When the file reaches the size shown in this column or when the event shown in this column occurs, the output destination is switched. If there are multiple log files and if the maximum disk usage is reached, files are overwritten, beginning with the ones that have the oldest update dates.

Table 11‒3: JP1/IM - Manager (common to all components) log files and folders (Windows)

Log type

Default file name and folder name

Maximum disk usage

File-switching timing

Operation log

Manager-path\log\operationlog\imm_operation{none|1|2...|16}.log#1

55 MB#1

5 MB#1#2

jimnodecount command log#3

Manager-path\log\nodecount\jimnodecount_cmd{1|2}.log

20 MB

10 MB

#1: You can change the output destination, the number of files that can be saved, and the file size. For details, see Operation log definition file (imm_operationlog.conf) (Chapter 2. Definition Files) in the manual JP1/Integrated Management 2 - Manager Command, Definition File and API Reference. The number of bytes shown in the Maximum disk usage and File-switching timing columns are the values used when the number of files that can be saved and the file size are set to initial values.

#2: For details about the operation when switching the operation log file, see K.2 Storage format of operation log output in the JP1/Integrated Management 2 - Manager Overview and System Design Guide.

#3: The logs above are process-by-process trace logs. The process-by-process trace log is the log information that is output by each function of JP1/IM. It is output to a different log file depending on the function that is being used. Since the process-by-process trace log contains product information, its content is not made public.

Table 11‒4: JP1/IM - Manager (Central Console) log files and folders (Windows)

Log type

Default file name and folder name

Maximum disk usage

File-switching timing

Process management log#9

Console-path\log\JCO_SPMD{1|2|3}.log

384 KB

128 KB

Console-path\log\JCO_SPMD_COMMAND{1|2|3}.log

384 KB

128 KB

shared-folder\jp1cons\log\JCO_SPMD{1|2|3}.log

384 KB

128 KB

shared-folder\jp1cons\log\JCO_SPMD_COMMAND{1|2|3}.log

384 KB

128 KB

Stack trace log#9

Console-path\log\javalog0{1|2|3|4}.log

1 MB

At startup or 256 KB

shared-folder\jp1cons\log\javalog0{1|2|3|4}.log

1 MB

At startup or 256 KB

Logical host settings program log#9

Console-path\log\jp1hasetup.{log|log.old}

2,000 KB

1,000 KB

Setup log#9

Console-path\log\command\comdef[_old].log

512 KB

256 KB

Event console log#9

Console-path\log\console\EVCONS{1|2|3}.log

30,720 KB

10,240 KB

Console-path\log\console\jp1cons{1|2|3|4|5|6|7|8}.log

40,960 KB

5,120 KB#1

Console-path\log\console\evtcon_exe{1|2|3}.log

256 KB × 3

256 KB

Console-path\log\console\JCOAPI{1|2|3}.log

96KB

32KB

Console-path\log\console\jp1consM{1|2...|60}.log

300 MB

5 MB#1

Console-path\log\console\jp1eventStormDef{1|2|3|4|5}.log

100 MB

20 MB

Console-path\log\console\jp1filterDef{1|2|3|4|5}.log

100 MB

20 MB

Console-path\log\console\jp1bizGroupDef{1|2}.log

10 MB

5 MB

Console-path\log\console\jp1cmdButtonDef{1|2|3|4|5}.log

25 MB

5 MB

Console-path\log\console\jp1exattrnameDef{1|2|3|4|5}.log

25 MB

5 MB

shared-folder\jp1cons\log\console\EVCONS{1|2|3}.log

30,720 KB

10,240 KB

shared-folder\jp1cons\log\console\jp1cons{1|2|3|4|5|6|7|8}.log

40,960 KB

5,120 KB#1

shared-folder\jp1cons\log\console\evtcon_exe{1|2|3}.log

256 KB × 3

256 KB

shared-folder\jp1cons\log\console\JCOAPI{1|2|3}.log

96 KB

32 KB

shared-folder\jp1cons\log\console\jp1consM{1|2...|60}.log

300 MB

5 MB#1

shared-folder\jp1cons\log\console\jp1eventStormDef{1|2|3|4|5}.log

100 MB

20 MB

shared-folder\jp1cons\log\console\jp1filterDef{1|2|3|4|5}.log

100 MB

20 MB

shared-folder\jp1cons\log\console\jp1bizGroupDef{1|2}.log

10 MB

5 MB

shared-folder\jp1cons\log\console\jp1cmdButtonDef{1|2|3|4|5}.log

25 MB

5 MB

shared-folder\jp1cons\log\console\jp1exattrnameDef{1|2|3|4|5}.log

25 MB

5 MB

Automated action trace log#9

Console-path\log\action\JCAMAIN{1|2|3|4|5}.log

25,600 KB#2

5,120 KB

shared-folder\jp1cons\log\action\JCAMAIN{1|2|3|4|5}.log

25,600 KB#2

5,120 KB

Product information log#9

Console-path\log\hliclib\hliclibtrc{1|2|3|4|5}.log

5 MB

1 MB

Console-path\log\hliclib\hlicliberr{1|2|3|4|5}.log

5 MB

1 MB

Console-path\log\hliclib\hliclibmgrtrc{1|2|3|4|5}.log

5 MB

1 MB

Console-path\log\hliclib\hliclibmgrerr{1|2|3|4|5}.log

5 MB

1 MB

shared-folder\jp1cons\log\hliclib\hliclibtrc{1|2|3|4|5}.log

5 MB

1 MB

shared-folder\jp1cons\log\hliclib\hlicliberr{1|2|3|4|5}.log

5 MB

1 MB

shared-folder\jp1cons\log\hliclib\hliclibmgrtrc{1|2|3|4|5}.log

5 MB

1 MB

shared-folder\jp1cons\log\hliclib\hliclibmgrerr{1|2|3|4|5}.log

5 MB

1 MB

Action information file#9

Console-path\log\action\actinf.log

626 KB#3

No switching

shared-folder\jp1cons\log\action\actinf.log

626 KB#3

No switching

Action host name file#9

Console-path\log\action\acttxt{1|2}.log

48.9 MB#4

When the action information file wraps around

shared-folder\jp1cons\log\action\acttxt{1|2}.log

48.9 MB#4

When the action information file wraps around

Action re-execution file

Console-path\log\action\actreaction

300 MB

When the service is started

shared-folder\jp1cons\log\action\actreaction

300 MB

When the service is started

jcochstat, and jcoevtreport command trace logs#5#9

Console-path\log\command\CMD{1|2|3}.log

3,072 KB

1,024 KB

Console-path\log\command\jp1cons_cmd{1|2}.log

12,288 KB

6,144 KB

Console-path\log\command\jp1consM_cmd{1|2}.log

12,288 KB

6,144 KB

Console-path\log\command\jp1exattrnameDef_cmd{1|2|3|4|5}.log

25 MB

5 MB

Plug-in log#9

Console-path\log\command\jcoplugin{1|2|3}.log

3 MB

1 MB

Reporting status storage file#9

Console-path\log\notice\notice_stat.dat

72B

No switching

shared-folder\jp1cons\log\notice\notice_stat.dat

72B

No switching

Action definition backup file#9

Console-path\log\action\actdefbk.conf

2,048 KB

No switching

shared-folder\jp1cons\log\action\actdefbk.conf

2,048 KB

No switching

Event base trace log#9

Console-path\log\evflow\EVFLOW{1|2|3|4|5|6|7|8|9|10}.log

100 MB

10 MB

Console-path\log\evflow\jp1evflowM{1|2...|60}.log

300 MB

5 MB

Console-path\log\evflow\jp1actDef{1|2|3|4|5}.log

25 MB

5 MB

Console-path\log\evflow\jp1chsevDef{1|2|3|4|5}.log

25 MB

5 MB

Console-path\log\evflow\jp1chmsgDef{1|2|3|4|5}.log

25 MB

5 MB

Console-path\log\evflow\jp1hostmapDef{1|2|3|4|5}.log

25 MB

5 MB

Console-path\log\evflow\evflow_exe{1|2|3}.log

256 KB × 3

256 KB

shared-folder\jp1cons\log\evflow\EVFLOW{1|2|3|4|5|6|7|8|9|10}.log

100 MB

10 MB

shared-folder\jp1cons\log\evflow\jp1evflowM{1|2...|60}.log

300 MB

5 MB

shared-folder\jp1cons\log\evflow\jp1actDef{1|2|3|4|5}.log

25 MB

5 MB

shared-folder\jp1cons\log\evflow\jp1chsevDef{1|2|3|4|5}.log

25 MB

5 MB

shared-folder\jp1cons\log\evflow\jp1chmsgDef{1|2|3|4|5}.log

25 MB

5 MB

shared-folder\jp1cons\log\evflow\jp1hostmapDef{1|2|3|4|5}.log

25 MB

5 MB

shared-folder\jp1cons\log\evflow\evflow_exe{1|2|3}.log

256 KB × 3

256 KB

Matching information file#9

Console-path\log\evflow\evflowinf.log

12B

No switching

shared-folder\jp1cons\log\evflow\evflowinf.log

12B

No switching

Event base error log#9

Console-path\log\evflow\jp1evflow{1|2|3|4|5|6|7|8}.log

40,960 KB

5,120 KB

shared-folder\jp1cons\log\evflow\jp1evflow{1|2|3|4|5|6|7|8}.log

40,960 KB

5,120 KB

Event base stack trace#9

Console-path\log\evflow\javalog0{1|2|3|4}.log

1 MB

At startup or 256 KB

shared-folder\jp1cons\log\evflow\javalog0{1|2|3|4}.log

1 MB

At startup or 256 KB

Automated action error log#9

Console-path\log\action\jp1act{1|2|3}.log

15,360 KB

5,120 KB

shared-folder\jp1cons\log\action\jp1act{1|2|3}.log

15,360 KB

5,120 KB

Correlation event generation history file

Console-path\operation\evgen\egs_discrim{1|2|3}.log#6

30 MB#6

10 MB#6

shared-folder\jp1cons\operation\evgen\egs_discrim{1|2|3}.log#6

30 MB#6

10 MB#6

Common exclusion history file

Console-path\operation\comexclude\comexclude{1|2|3|4|5}.log

100 MB

20 MB

shared-folder\jp1cons\operation\comexclude\comexclude{1|2|3|4|5}.log

100 MB

20 MB

Common exclusion-conditions definition history file

Console-path\operation\comexclude\comexcludeDef{1|2|3|4|5}.log

100 MB

20 MB

shared-folder\jp1cons\operation\comexclude\comexcludeDef{1|2|3|4|5}.log

100 MB

20 MB

Correlation event generation trace log#9

Console-path\log\evgen\EVGEN{1|2|3}.log

15 MB

5 MB

Console-path\log\evgen\evgen_exe{1|2|3}.log

256 KB × 3

256 KB

shared-folder\jp1cons\log\evgen\EVGEN{1|2|3}.log

15 MB

5 MB

shared-folder\jp1cons\log\evgen\evgen_exe{1|2|3}.log

256 KB × 3

256 KB

Correlation event generation individual log#9

Console-path\log\evgen\jp1egs{1|2}.log

20 MB

10 MB

Console-path\log\evgen\jp1egsM{1|2}.log

20 MB

10 MB

shared-folder\jp1cons\log\evgen\jp1egs{1|2}.log

20 MB

10 MB

shared-folder\jp1cons\log\evgen\jp1egsM{1|2}.log

20 MB

10 MB

Correlation event generation individual log (for commands) #9

Console-path\log\evgen\jp1egs_cmd{1|2|3|4}.log

20 MB

5 MB

Console-path\log\evgen\jp1egsM_cmd{1|2|3|4}.log

20 MB

5 MB

Correlation event generation stack trace log#9

Console-path\log\evgen\javalog0{1|2|3|4}.log

1 MB

At startup or 256 KB

shared-folder\jp1cons\log\evgen\javalog0{1|2|3|4}.log

1 MB

At startup or 256 KB

Correlation event generation process inheriting definition file#9

Console-path\log\evgen\egs_discrim_info{1|2|3|4}.dat

312 MB#7

At termination

shared-folder\jp1cons\log\evgen\egs_discrim_info{1|2|3|4}.dat

312 MB#7

At termination

Correlation event generation definition application log#9

Console-path\log\evgen\jp1egsDefine{1|2}.log

10 MB

5 MB

shared-folder\jp1cons\log\evgen\jp1egsDefine{1|2}.log

10 MB

5 MB

File for accumulated response-waiting events#8#9

Console-path\log\response\resevent.dat

40 MB

No switching

shared-folder\jp1cons\log\response\resevent.dat

40 MB

No switching

Backup file for accumulated response-waiting events#9

Console-path\log\response\resevent.dat.dump

40 MB

No switching

shared-folder\jp1cons\log\response\resevent.dat.dump

40 MB

No switching

Command execution history folder#9

Base-path\log\COMMAND\

See the JP1/Base User's Guide.

shared-folder\jp1base\log\COMMAND\

Remote command log#9

Base-path\log\JCOCMD\jcocmd_result{1|2|3}.log

Base-path\log\JCOCMD\jcocmdapi{1|2|3}.log

Base-path\log\JCOCMD\jcocmdapi_trace{1|2|3}.log

Base-path\log\JCOCMD\jcocmdcom{1|2|3}.log

Base-path\log\JCOCMD\jcocmdcom_trace{1|2|3}.log

Base-path\log\JCOCMD\jcocmdexe{1|2|3}.log

Base-path\log\JCOCMD\jcocmdexe_trace{1|2|3}.log

Base-path\log\JCOCMD\jcocmdrouter{1|2|3}.log

Base-path\log\JCOCMD\jcocmdrouter_trace{1|2|3}.log

Base-path\log\JCOCMD\JCOCMDCMD{1|2|3}.log

shared-folder\jp1base\log\JCOCMD\jcocmd_result{1|2|3}.log

shared-folder\jp1base\log\JCOCMD\jcocmdapi{1|2|3}.log

shared-folder\jp1base\log\JCOCMD\jcocmdapi_trace{1|2|3}.log

shared-folder\jp1base\log\JCOCMD\jcocmdcom{1|2|3}.log

shared-folder\jp1base\log\JCOCMD\jcocmdcom_trace{1|2|3}.log

shared-folder\jp1base\log\JCOCMD\jcocmdexe{1|2|3}.log

shared-folder\jp1base\log\JCOCMD\jcocmdexe_trace{1|2|3}.log

shared-folder\jp1base\log\JCOCMD\jcocmdrouter{1|2|3}.log

shared-folder\jp1base\log\JCOCMD\jcocmdrouter_trace{1|2|3}.log

shared-folder\jp1base\log\JCOCMD\JCOCMDCMD{1|2|3}.log

Configuration management log#9

Base-path\log\route\JBSRT{1|2|3}.log

shared-folder\jp1base\log\route\JBSRT{1|2|3}.log

Trace log file#9

Base-path\sys\tmp\event\logtrap\jelallog\jelallog{1|2|3|4|5}.log

Base-path\sys\tmp\event\logtrap\jelalelt\jelalelt{1|2|3|4|5}.log

Integrated monitoring database application log#9

Console-path\log\evflow\EVFLOW_DBAPI{1|2...|16}.log

200 MB

12.5 MB

Console-path\log\console\EVCONS_DBAPI{1|2|3|4|5}.log

50 MB

10 MB

Console-path\log\command\CMD_DBAPI{1|2|3|4|5}.log

50 MB

10 MB

shared-folder\jp1cons\log\evflow\EVFLOW_DBAPI{1|2...|16}.log

200 MB

12.5 MB

shared-folder\jp1cons\log\console\EVCONS_DBAPI{1|2|3|4|5}.log

50 MB

10 MB

API log for the IM Configuration Management database#9

Console-path\log\evflow\EVFLOW_CFDBAPI{1|2|3}.log

30 MB

10 MB

Console-path\log\console\EVCONS_CFDBAPI{1|2|3}.log

30 MB

10 MB

Console-path\log\command\CMD_CFDBAPI{1|2|3}.log

30 MB

10 MB

shared-folder\jp1cons\log\evflow\EVFLOW_CFDBAPI{1|2|3}.log

30 MB

10 MB

shared-folder\jp1cons\log\console\EVCONS_CFDBAPI{1|2|3}.log

30 MB

10 MB

jcodbsetup command log#9

Console-path\log\imdb\jcodbsetup{1|2}.log

512 KB

256 KB

jcodbunsetup command log#9

Console-path\log\imdb\jcodbunsetup{1|2}.log

512 KB

256 KB

jimmail command log#9

Console-path\log\mail\jimmail_cmd{1|2|3}.log

15 MB

5 MB

Console-path\log\mail\jimmail_cmdM{1|2|3}.log

15 MB

5 MB

Console-path\log\mail\JIMMAIL{1|2|3}.log

15 MB

5 MB

Console-path\log\mail\jimmail_exe{1|2|3}.log

15 MB

5 MB

jimmailpasswd command log#9

Console-path\log\mail\jimmailpasswd_cmd{1|2|3}.log

768 KB

256 KB

Console-path\log\mail\jimmailpasswd_cmdM{1|2|3}.log

768 KB

256 KB

Console-path\log\mail\JIMMAILPASSWD{1|2|3}.log

768 KB

256 KB

Console-path\log\mail\jimmailpasswd_exe{1|2|3}.log

768 KB

256 KB

#1: The file size may be dozens of kilobytes larger than this value.

#2: You can set this value to be from 65,536 bytes (64 kilobytes) to 104,857,600 bytes (100 megabytes), as described in Automated action environment definition file (action.conf.update) (in Chapter 2. Definition Files) in the manual JP1/Integrated Management 2 - Manager Command, Definition File and API Reference.

#3: You can set this value to be from 1 to 4,096 kilobytes, as described in Automated action environment definition file (action.conf.update) (in Chapter 2. Definition Files) in the manual JP1/Integrated Management 2 - Manager Command, Definition File and API Reference.

#4: This is the value when the size of the action information file is the default value (626 kilobytes). You can use the following estimation formula to estimate the maximum disk usage by this file. Each time an action is performed, the size increases by 5 kilobytes.

((action information file size ÷ 64 bytes) - 1) × 5 kilobytes

#5: The files are output to the jcochstat and jcoevtreport command trace logs on the physical host in a cluster operation system as well.

#6: You can change the file count and file size as described in the Correlation event generation environment definition file (in Chapter 2. Definition Files) in the manual JP1/Integrated Management 2 - Manager Command, Definition File and API Reference.

#7: This file is used to output the memory information for inheriting data during correlation event generation, and therefore its size varies depending on the correlation event generation condition and the correlation-source event. For details about estimating the size of this file, see the JP1/IM - Manager release notes.

#8: This file is created when you start JP1/IM - Manager after enabling the response-waiting event management function.

#9: The logs above are process-by-process trace logs. The process-by-process trace log is the log information that is output by each function of JP1/IM. It is output to a different log file depending on the function that is being used. Since the process-by-process trace log contains product information, its content is not made public.

Table 11‒5: JP1/IM - Manager (Central Scope) log files and folders (Windows)

Log type

Default file name and folder name

Maximum disk usage

File-switching timing

Central Scope trace log

Scope-path\log\jcsmain{1|2|3}.log

6 MB

2 MB

Scope-path\log\jcsmain_trace{1|2|3}.log

6 MB

2 MB

shared-folder\JP1Scope\log\jcsmain{1|2|3}.log

6 MB

2 MB

shared-folder\JP1Scope\log\jcsmain_trace{1|2|3}.log

6 MB

2 MB

Communication trace log

Scope-path\log\jcsmain_trace_com{1|2|3}.log

6 MB

2 MB

shared-folder\JP1Scope\log\jcsmain_trace_com{1|2|3}.log

6 MB

2 MB

Scope-path\log\jcsmain_trace_ping{1|2|3}.log

6 MB

2 MB

shared-folder\JP1Scope\log\jcsmain_trace_ping{1|2|3}.log

6 MB

2 MB

Logical host settings program log

Scope-path\log\jp1hasetup.{log|log.old}

2,000 KB

1,000 KB

Database operation API trace log

Scope-path\log\jcsmain_trace_db{1|2|3}.log

6 MB

2 MB

shared-folder\JP1Scope\log\jcsmain_trace_db{1|2|3}.log

6 MB

2 MB

jcshostsexport command log

Scope-path\log\jcshostsexport{1|2|3}.log

6 MB

2 MB

shared-folder\JP1Scope\log\jcshostsexport{1|2|3}.log

6 MB

2 MB

jcshostsimport command log

Scope-path\log\jcshostsimport{1|2|3}.log

6 MB

2 MB

shared-folder\JP1Scope\log\jcshostsimport{1|2|3}.log

6 MB

2 MB

jcsdbsetup command log

Scope-path\log\jcsdbsetup{1|2|3}.log

6 MB

2 MB

shared-folder\JP1Scope\log\jcsdbsetup{1|2|3}.log

6 MB

2 MB

jcschstat command log

Scope-path\log\jcschstat{1|2|3}.log

6 MB

2 MB

shared-folder\JP1Scope\log\jcschstat{1|2|3}.log

6 MB

2 MB

jcsdbexport command log

Scope-path\log\jcsdbexport{1|2|3}.log

6 MB

2 MB

shared-folder\JP1Scope\log\jcsdbexport{1|2|3}.log

6 MB

2 MB

jcsdbimport command log

Scope-path\log\jcsdimport{1|2|3}.log

6 MB

2 MB

shared-folder\JP1Scope\log\jcsdbimport{1|2|3}.log

6 MB

2 MB

jcsdbconvert command log

Scope-path\log\jcsdbconvert{1|2|3}.log

6 MB

2 MB

shared-folder\JP1Scope\log\jcsdbconvert{1|2|3}.log

6 MB

2 MB

jp1csverup command log

Scope-path\log\jp1csverup_front{1|2|3}.log

6 MB

2 MB

jp1cshaverup command log

shared-folder\JP1Scope\log\jp1cshaverup_front{1|2|3}.log

6 MB

2 MB

Note: The logs above are process-by-process trace logs. The process-by-process trace log is the log information that is output by each function of JP1/IM. It is output to a different log file depending on the function that is being used. Since the process-by-process trace log contains product information, its content is not made public.

Table 11‒6: JP1/IM - Manager (IM Configuration Management) log files and folders (Windows)

Log type

Default file name and folder name

Maximum disk usage

File-switching timing

IM Configuration Management trace log

Manager-path\log\imcf\jcfallogtrap{1|2|3|4|5|6|7|8|9|10}.log

200 MB

10 MB

Manager-path\log\imcf\jcfallogtrap_VM_trace{1|2|3}.log

3 MB

1 MB

Manager-path\log\imcf\jcfallogtrap_trace_auth{1|2|3|4|5|6|7|8|9|10}.log

20 MB

2 MB

Manager-path\log\imcf\jcfmain{1|2|3|4|5|6|7|8|9|10}.log

20 MB

2 MB

Manager-path\log\imcf\jcfmain_trace{1|2|3|4|5|6|7|8|9|10}.log

20 MB

2 MB

Manager-path\log\imcf\jcfmain_VM_trace{1|2|3}.log

3 MB

1 MB

shared-folder\JP1IMM\log\imcf\jcfallogtrap{1|2|3|4|5|6|7|8|9|10}.log

200 MB

10 MB

shared-folder\JP1IMM\log\imcf\jcfallogtrap_VM_trace{1|2|3}.log

3 MB

1 MB

shared-folder\JP1IMM\log\imcf\jcfallogtrap_trace_auth{1|2|3|4|5|6|7|8|9|10}.log

20 MB

2 MB

shared-folder\JP1IMM\log\imcf\jcfmain{1|2|3|4|5|6|7|8|9|10}.log

20 MB

2 MB

shared-folder\JP1IMM\log\imcf\jcfmain_trace{1|2|3|4|5|6|7|8|9|10}.log

20 MB

2 MB

shared-folder\JP1IMM\log\imcf\jcfmain_VM_trace{1|2|3}.log

3 MB

1 MB

Communication trace log

Manager-path\log\imcf\jcfmain_trace_com{1|2|3|4|5|6|7|8|9|10}.log

20 MB

2 MB

Manager-path\log\imcf\jcfmain_ping{1|2|3|4|5|6|7|8|9|10}.log

20 MB

2 MB

shared-folder\JP1IMM\log\imcf\jcfmain_trace_com{1|2|3|4|5|6|7|8|9|10}.log

20 MB

2 MB

shared-folder\JP1IMM\log\imcf\jcfmain_ping{1|2|3|4|5|6|7|8|9|10}.log

20 MB

2 MB

Authentication trace log

Manager-path\log\imcf\jcfmain_trace_auth{1|2|3|4|5|6|7|8|9|10}.log

20 MB

2 MB

shared-folder\JP1IMM\log\imcf\jcfmain_trace_auth{1|2|3|4|5|6|7|8|9|10}.log

20 MB

2 MB

Logical host settings program log

Manager-path\log\imcf\jp1hasetup.{log|log.old}

2,000 KB

1,000 KB

Database operation API trace log

Manager-path\log\imcf\jcfmain_trace_db{1|2|3|4|5|6|7|8|9|10}.log

20 MB

2 MB

shared-folder\JP1IMM\log\imcf\jcfmain_trace_db{1|2|3|4|5|6|7|8|9|10}.log

20 MB

2 MB

Command common log

Manager-path\log\imcf\jcfcommand{1|2|3}.log

3 MB

1 MB

shared-folder\JP1IMM\log\imcf\jcfcommand{1|2|3}.log

3 MB

1 MB

jcfallogstart command log

Manager-path\log\imcf\jcfallogstart{1|2|3}.log

9 MB

3 MB

Manager-path\log\imcf\jcfallogstart_VM_trace{1|2|3}.log

3 MB

1 MB

shared-folder\JP1IMM\log\imcf\jcfallogstart{1|2|3}.log

9 MB

3 MB

shared-folder\JP1IMM\log\imcf\jcfallogstart_VM_trace{1|2|3}.log

3 MB

1 MB

jcfallogstat command log

Manager-path\log\imcf\jcfallogstat{1|2|3}.log

9 MB

3 MB

Manager-path\log\imcf\jcfallogstat_VM_trace{1|2|3}.log

3 MB

1 MB

shared-folder\JP1IMM\log\imcf\jcfallogstat{1|2|3}.log

9 MB

3 MB

shared-folder\JP1IMM\log\imcf\jcfallogstat_VM_trace{1|2|3}.log

3 MB

1 MB

jcfallogstop command log

Manager-path\log\imcf\jcfallogstop{1|2|3}.log

9 MB

3 MB

Manager-path\log\imcf\jcfallogstop_VM_trace{1|2|3}.log

3 MB

1 MB

shared-folder\JP1IMM\log\imcf\jcfallogstop{1|2|3}.log

9 MB

3 MB

shared-folder\JP1IMM\log\imcf\jcfallogstop_VM_trace{1|2|3}.log

3 MB

1 MB

jcfallogreload command log

Manager-path\log\imcf\jcfallogreload{1|2|3}.log

9 MB

3 MB

Manager-path\log\imcf\jcfallogreload_VM_trace{1|2|3}.log

3 MB

1 MB

shared-folder\JP1IMM\log\imcf\jcfallogreload{1|2|3}.log

9 MB

3 MB

shared-folder\JP1IMM\log\imcf\jcfallogreload_VM_trace{1|2|3}.log

3 MB

1 MB

jcfallogdef command log

Manager-path\log\imcf\jcfallogdef{1|2|3}.log

9 MB

3 MB

Manager-path\log\imcf\jcfallogdef_VM_trace{1|2|3}.log

3 MB

1 MB

shared-folder\JP1IMM\log\imcf\jcfallogdef{1|2|3}.log

9 MB

3 MB

shared-folder\JP1IMM\log\imcf\jcfallogdef_VM_trace{1|2|3}.log

3 MB

1 MB

jcfaleltstart command log

Manager-path\log\imcf\jcfaleltstart{1|2|3}.log

6 MB

2 MB

Manager-path\log\imcf\jcfaleltstart_VM_trace{1|2|3}.log

3 MB

1 MB

shared-folder\JP1IMM\log\imcf\jcfaleltstart{1|2|3}.log

6 MB

2 MB

shared-folder\JP1IMM\log\imcf\jcfaleltstart_VM_trace{1|2|3}.log

3 MB

1 MB

jcfaleltstat command log

Manager-path\log\imcf\jcfaleltstat{1|2|3}.log

6 MB

2 MB

Manager-path\log\imcf\jcfaleltstat_VM_trace{1|2|3}.log

3 MB

1 MB

shared-folder\JP1IMM\log\imcf\jcfaleltstat{1|2|3}.log

6 MB

2 MB

shared-folder\JP1IMM\log\imcf\jcfaleltstat_VM_trace{1|2|3}.log

3 MB

1 MB

jcfaleltstop command log

Manager-path\log\imcf\jcfaleltstop{1|2|3}.log

6 MB

2 MB

Manager-path\log\imcf\jcfaleltstop_VM_trace{1|2|3}.log

3 MB

1 MB

shared-folder\JP1IMM\log\imcf\jcfaleltstop{1|2|3}.log

6 MB

2 MB

shared-folder\JP1IMM\log\imcf\jcfaleltstop_VM_trace{1|2|3}.log

3 MB

1 MB

jcfaleltreload command log

Manager-path\log\imcf\jcfaleltreload{1|2|3}.log

6 MB

2 MB

Manager-path\log\imcf\jcfaleltreload_VM_trace{1|2|3}.log

3 MB

1 MB

shared-folder\JP1IMM\log\imcf\jcfaleltreload{1|2|3}.log

6 MB

2 MB

shared-folder\JP1IMM\log\imcf\jcfaleltreload_VM_trace{1|2|3}.log

3 MB

1 MB

jcfaleltdef command log

Manager-path\log\imcf\jcfaleltdef{1|2|3}.log

6 MB

2 MB

Manager-path\log\imcf\jcfaleltdef_VM_trace{1|2|3}.log

3 MB

1 MB

shared-folder\JP1IMM\log\imcf\jcfaleltdef{1|2|3}.log

6 MB

2 MB

shared-folder\JP1IMM\log\imcf\jcfaleltdef_VM_trace{1|2|3}.log

3 MB

1 MB

jcfcolvmesx command log

Manager-path\log\imcf\jcfcolvmesx_trace{1|2|3}.log

3 MB

1 MB

jcfcolvmscvmm command log

Manager-path\log\imcf\jcfcolvmscvmm_trace{1|2|3}.log

3 MB

1 MB

jcfcolvmvirtage command log

Manager-path\log\imcf\jcfcolvmvirtage_trace{1|2|3}.log

3 MB

1 MB

jcfcolvmvc command log

Manager-path\log\imcf\jcfcolvmvc_trace{1|2|3}.log

3 MB

1 MB

jcfcolvmkvm command log

Manager-path\log\imcf\jcfcolvmkvm_trace{1|2|3}.log

3 MB

1 MB

jcfcolvmhcsm command log

Manager-path\log\imcf\jcfcolvmhcsm_trace{1|2|3}.log

3 MB

1 MB

jcfexport command log

Manager-path\log\imcf\jcfexport_VM_trace{1|2|3}.log

3 MB

1 MB

shared-folder\JP1IMM\log\imcf\jcfexport_VM_trace{1|2|3}.log

3 MB

1 MB

jcfimport command log

Manager-path\log\imcf\jcfimport_VM_trace{1|2|3}.log

3 MB

1 MB

shared-folder\JP1IMM\log\imcf\jcfimport_VM_trace{1|2|3}.log

3 MB

1 MB

jcfmkhostsdata command log

Manager-path\log\imcf\jcfmkhostsdata_trace{1|2|3}.log

3 MB

1 MB

Stack trace log

Manager-path\log\imcf\javalog{1|2|3|4}.log

1 MB

At startup or 256 KB

Note: The logs above are process-by-process trace logs. The process-by-process trace log is the log information that is output by each function of JP1/IM. It is output to a different log file depending on the function that is being used. Since the process-by-process trace log contains product information, its content is not made public.

Table 11‒7: Intelligent Integrated Management Base log files and folders

Log type

Default file name and folder name

Maximum disk usage

File-switching timing

Intelligent Integrated Management Base service individual log

Manager-path\log\imdd\jddmain\jddmain.log{.1-7}

1 GB

128 MB

shared-folder\jp1imm\log\imdd\jddmain\jddmain.log{.1-7}

Definition file#1, node file history log

Manager-path\log\imdd\jddmain\jimddDef.log{.1-10}

80 MB

8 MB

shared-folder\jp1imm\log\imdd\jddmain\jimddDef.log{.1-10}

Manager-path\log\imdd\jddmain\jimddMaster.log{.1-30}

240 MB

8 MB

shared-folder\jp1imm\log\imdd\jddmain\jimddMaster.log{.1-30}

jddsetaccessuser command trace log

Manager-path\log\imdd\jddsetaccessuser\jddsetaccessuser.log{.1-6}

70 MB

10 MB

shared-folder\jp1imm\log\imdd\jddsetaccessuser\jddsetaccessuser.log{.1-6}

Manager-path\log\imdd\jddsetaccessuser\jddsetaccessuser_exe{1|2|3}.log

768 KB

256 KB

shared-folder\jp1imm\log\imdd\jddsetaccessuser\jddsetaccessuser_exe{1|2|3}.log

Manager-path\log\imdd\jddsetaccessuser\javalog0{1|2|3|4}.log

1,024 KB

At startup or 256 KB

shared-folder\jp1imm\log\imdd\jddsetaccessuser\javalog0{1|2|3|4}.log

jddcreatetree command trace log

Manager-path\log\imdd\jddcreatetree\jddcreatetree.log{.1-6}

70 MB

10 MB

shared-folder\jp1imm\log\imdd\jddcreatetree\jddcreatetree.log{.1-6}

Manager-path\log\imdd\jddcreatetree\jddcreatetree_exe{1|2|3}.log

768 KB

256 KB

shared-folder\jp1imm\log\imdd\jddcreatetree\jddcreatetree_exe{1|2|3}.log

Manager-path\imdd\jddcreatetree\javalog0{1|2|3|4}.log

1,024 KB

At startup or 256 KB

shared-folder\jp1imm\log\imdd\jddcreatetree\javalog0{1|2|3|4}.log

jddupdatetree command trace log

Manager-path\log\imdd\jddupdatetree\jddupdatetree.log{.1-6}

70 MB

10 MB

shared-folder\jp1imm\log\imdd\jddupdatetree\jddupdatetree.log{.1-6}

Manager-path\log\imdd\jddupdatetree\jddupdatetree_exe{1|2|3}.log

768 KB

256 KB

shared-folder\jp1imm\log\imdd\jddupdatetree\jddupdatetree_exe{1|2|3}.log

Manager-path\log\imdd\jddupdatetree\javalog0{1|2|3|4}.log

1,024 KB

256 KB

shared-folder\jp1imm\log\imdd\jddupdatetree\javalog0{1|2|3|4}.log

jddsetproxyuser command trace log

Manager-path\log\imdd\jddsetproxyuser\jddsetproxyuser.log{.1-6}

70 MB

10 MB

shared-folder\jp1imm\log\imdd\jddsetproxyuser\jddsetproxyuser.log{.1-6}

Manager-path\log\imdd\jddsetproxyuser\jddsetproxyuser_exe{1|2|3}.log

768 KB

256 KB

shared-folder\log\imdd\jddsetproxyuser\jddsetproxyuser_exe{1|2|3}.log

Manager-path\log\imdd\jddsetproxyuser\javalog0{1|2|3|4}.log

1,024 KB

256 KB

shared-folder\log\imdd\jddsetproxyuser\javalog0{1|2|3|4}.log

jddupdatesuggestion command trace log

Manager-path\log\imdd\jddupdatesuggestion\jddupdatesuggestion.log{.1-6}

70MB

10MB

shared-folder\jp1imm\log\jddupdatesuggestion\jddupdatesuggestion.log{.1-6}

Manager-path\log\imdd\jddupdatesuggestion\jddupdatesuggestion_exe{1|2|3}.log

768KB

256KB

shared-folder\log\imdd\jddupdatesuggestion\jddupdatesuggestion_exe{1|2|3}.log

Manager-path\log\imdd\jddupdatesuggestion\javalog0{1|2|3|4}.log

1,024KB

256KB

shared-folder\log\imdd\jddupdatesuggestion\javalog0{1|2|3|4}.log

jddsetopinfo command trace log

Manager-path\log\imdd\jddsetopinfo\jddsetopinfo.log{.1-6}

70MB

10MB

shared-folder\jp1imm\log\jddsetopinfo\jddsetopinfo.log{.1-6}

Manager-path\log\imdd\jddsetopinfo\jddsetopinfo_exe{1|2|3}.log

768KB

256KB

shared-folder\log\imdd\jddsetopinfo\jddsetopinfo_exe{1|2|3}.log

Manager-path\log\imdd\jddsetopinfo\javalog0{1|2|3|4}.log

1,024KB

256KB

shared-folder\log\imdd\jddsetopinfo\javalog0{1|2|3|4}.log

jddupdatessomap command trace log

Manager-path\log\imdd\jddupdatessomap\jddupdatessomap.log{.1-6}

70MB

10MB

shared-folder\jp1imm\log\jddupdatessomap\jddupdatessomap.log{.1-6}

Manager-path\log\imdd\jddupdatessomap\jddupdatessomap_exe{1|2|3}.log

768KB

256KB

shared-folder\log\imdd\jddupdatessomap\jddupdatessomap_exe{1|2|3}.log

Manager-path\log\imdd\jddupdatessomap\javalog0{1|2|3|4}.log

1,024KB

256KB

shared-folder\log\imdd\jddupdatessomap\javalog0{1|2|3|4}.log

Logs of the response action execution history file #4

Manager-path\log\suggestion\jddSuggestionHistory.log{.1-3}

240MB

60MB

shared-folder\jp1imm\log\suggestion\jddSuggestionHistory.log{.1-3}

User-created plug-ins

Manager-path\log\imdd\user-created-plug-in-name\user-created-plug-in.log{1-21}#3

220MB

10MB

shared-folder\JP1IMM\log\imdd\user-created-plug-in-name\user-created-plug-in.log{1-21}#3

Other logs

Manager-path\log\imdd\jddmain\jddmain_exe{1|2|3}.log

768 KB

256 KB

shared-folder\jp1imm\log\imdd\jddmain\jddmain_exe{1|2|3}.log

Manager-path\log\imdd\jddmain\javalog0{1|2|3|4}.log

1,024 KB

At startup or 256 KB

shared-folder\jp1imm\log\imdd\jddmain\javalog0{1|2|3|4}.log

Manager-path\log\imdd\jcoapi{1-50}.log

500 MB

10 MB

shared-folder\jp1imm\log\imdd\jddmain\jcoapi{1-50}.log

Manager-path\log\imdd\jcoapiM{1-50}.log

500 MB

10 MB

shared-folder\jp1imm\log\imdd\jddmain\jcoapiM{1-50}.log

Manager-path\log\imdd\component-name#2\component-name#2{1-21}.log

220 MB

10 MB

shared-folder\log\imdd\component-name#2\component-name#2{1-21}.log

Note: The logs above are process-by-process trace logs. The process-by-process trace log is the log information that is output by each function of JP1/IM. It is output to a different log file depending on the function that is being used. Since the process-by-process trace log contains product information, its content is not made public.

#1

The logs for the following definition files are output to the definition file log for the Intelligent Integrated Management Base:

System node definition file, category name definition file for IM management nodes, host name definition file, target host definition file for configuration collection, IM management node link definition file, IM management node link file, IM management node tree file, IM management node file

#2

One of the following is displayed as the component name:

- jp1ajs

- jp1pfm

- jp1im

#3

{1-21} indicates the file count. You can view the log files in a text editor of your choice.

#4

The log is created when a response action is taken. Users can check the logs of response actions by themselves in order to examine the causes of failures, for example.

Table 11‒8: JP1/IM - View log files and folders

Log type

Default file name and folder name

Maximum disk usage

File-switching timing

JP1/IM - View log#1

View-path\log\VIEW{1|2|3}.log

30,720 KB

10,240 KB

View-path\log\jp1conv{1|2|3|4}.log

20,480 KB

5,120 KB#2

View-path\log\jp1convM{1|2...|60}.log

102,400 KB

5,120 KB#2

View-path\log\jp1csov[_old].log

6,144 KB

3,072 KB#2

View-path\log\jp1csovM[_old].log

6,144 KB

3,072 KB#2

View-path\log\imrm\jp1rmJP1-IM-RM View{1|2|3}.log#3

3,072 KB

1,024 KB

View-path\log\imrm\jp1rmJP1-IM-RM View_dbg{1|2|3}.log#3

3,072 KB

1,024 KB

View-path\log\jrmview\view{1|2|3}.log#3

3,072 KB

1,024 KB

Stack trace log#1

View-path\log\javalog0{1|2}.log

512 KB

At startup or 256 KB

Integrated trace log

system-drive:\Program Files\Hitachi\HNTRLib2\spool\hntr2{1|2|3|4}.log

1,024 KB

256 KB

Product information log#1

View-path\log\hliclib\hliclibtrc{1|2|3|4|5}.log

5 MB

1 MB

View-path\log\hliclib\hlicliberr{1|2|3|4|5}.log

5 MB

1 MB

View-path\log\hliclib\hliclibmgrtrc{1|2|3|4|5}.log

5 MB

1 MB

View-path\log\hliclib\hliclibmgrerr{1|2|3|4|5}.log

5 MB

1 MB

Note: When you use Windows, replace View-path\log\ with system-drive:\ProgramData\Hitachi\jp1\jp1_default\JP1CoView\log\.

#1: This log is a process-by-process trace log. The process-by-process trace log is the log information that is output by each function of JP1/IM. It is output to a different log file depending on the function that is being used. Since the process-by-process trace log contains product information, its content is not made public.

#2: The file size may be dozens of kilobytes larger than this value.

#3: This log is output only when JP1/IM - Rule Operation is linked.

Table 11‒9: JP1/IM - IM Configuration Management - View log files and folders

Log type

Default file name and folder name

Maximum disk usage

File-switching timing

IM Configuration Management trace log#

View-path\log\jcfview\VIEW{1|2|3}.log

30 MB

10 MB

Stack trace log#

View-path\log\jcfjavalog{1|2}.log

512 KB

At startup or 256 KB

Integrated trace log

system-drive:\Program Files\Hitachi\HNTRLib2\spool\hntr2{1|2|3|4}.log

1,024 KB

256 KB

Note: When you use Windows, replace View-path\log\ with system-drive:\ProgramData\Hitachi\jp1\jp1_default\JP1CoView\log\.

For Windows, the location represented by system-drive:\Program Files is determined at installation by an OS environment variable and might differ depending on the environment.

#: This log is a process-by-process trace log. The process-by-process trace log is the log information that is output by each function of JP1/IM. It is output to a different log file depending on the function that is being used. Since the process-by-process trace log contains product information, its content is not made public.

To Page Top

(2) In UNIX

The tables below show the default log files and folders that are output by the UNIX version of JP1/IM.

The Log type column lists the log types that are output by JP1/IM.

The Default file name and folder name column describes log file names as absolute paths when JP1/IM - Manager or JP1/Base is installed in the default mode. Default file name and folder name in a cluster operation system describes the log file names of shared folders as absolute paths.

The Maximum disk usage column shows the maximum disk space used by each log file. When there are multiple log files, the combined total is given.

The File-switching timing column shows how JP1/IM times output destination log file switching. When the file reaches the size shown in this column or when the event shown in this column occurs, the output destination is switched. If there are multiple log files and if the maximum disk usage is reached, files are overwritten, beginning with the ones that have the oldest update dates.

Table 11‒10: JP1/IM - Manager (common to all components) log files and folders (UNIX)

Log type

Default file name and folder name

Maximum disk usage

File-switching timing

Operation log

/var/opt/jp1imm/log/operationlog/imm_operation{none|1|2...|16}.log#1

55 MB#1

5 MB#1#2

jimnodecount command log#3

/var/opt/jp1imm/log/nodecount/jimnodecount_cmd{1|2}.log

20 MB

10 MB

#1: You can change the output destination, the number of files that can be saved, and the file size. For details, see Operation log definition file (imm_operationlog.conf) (Chapter 2. Definition Files) in the manual JP1/Integrated Management 2 - Manager Command, Definition File and API Reference. The number of bytes shown in the Maximum disk usage and File-switching timing columns are the values used when the number of files that can be saved and the file size are set to initial values

#2: For details about the operation when switching the operation log file, see K.2 Storage format of operation log output in the JP1/Integrated Management 2 - Manager Overview and System Design Guide.

#3: The logs above are process-by-process trace logs. The process-by-process trace log is the log information that is output by each function of JP1/IM. It is output to a different log file depending on the function that is being used. Since the process-by-process trace log contains product information, its content is not made public.

Table 11‒11: JP1/IM - Manager (Central Console) log files and directories (UNIX)

Log type

Default file name and directory name

Maximum disk usage

File-switching timing

Process management log#1

/var/opt/jp1cons/log/JCO_SPMD{1|2|3}.log

384 KB

128 KB

/var/opt/jp1cons/log/JCO_SPMD_COMMAND{1|2|3}.log

384 KB

128 KB

shared-directory/jp1cons/log/JCO_SPMD{1|2|3}.log

384 KB

128 KB

shared-directory/jp1cons/log/JCO_SPMD_COMMAND{1|2|3}.log

384 KB

128 KB

Stack trace log#1

/var/opt/jp1cons/log/javalog0{1|2|3|4}.log

1 MB

At startup or 256 KB

shared-directory/jp1cons/log/javalog0{1|2|3|4}.log

1 MB

At startup or 256 KB

JP1/IM startup log#1

/var/opt/jp1cons/log/jco_start.log[.old]

1 KB

At startup

shared-directory/jp1cons/log/jco_start_logical-host-name.log[.old]

1 KB

At startup

JP1/IM kill log#1, #2

shared-directory/jp1cons/log/jco_killall.cluster{none|1|2|3|4}

2 KB

When the jco_killall.cluster command is executed

Setup log#1

/var/opt/jp1cons/log/JCO_SETUP/jco_setup.log

100 KB

During installation

/var/opt/jp1cons/log/JCO_SETUP/jco_inst.log

100 KB

During installation

/var/opt/jp1cons/log/jco_setup/logical-host-name/jco_setup.log

100 KB

During installation

/var/opt/jp1cons/log/jco_setup/logical-host-name/reg.txt

100 KB

During installation

/var/opt/jp1cons/log/jco_setup/logical-host-name/reg_def.txt

100 KB

During installation

/var/opt/jp1cons/log/command/comdef[_old].log

512 KB

256 KB

Event console log#1

/var/opt/jp1cons/log/console/EVCONS{1|2|3}.log

30,720 KB

10,240 KB

/var/opt/jp1cons/log/console/jp1cons{1|2|3|4|5|6|7|8}.log

40,960 KB

5,120 KB#3

/var/opt/jp1cons/log/console/JCOAPI{1|2|3}.log

96 KB

32 KB

/var/opt/jp1cons/log/console/jp1consM{1|2...|60}.log

300 MB

5 MB#3

/var/opt/jp1cons/log/console/jp1eventStormDef{1|2|3|4|5}.log

100 MB

20 MB

/var/opt/jp1cons/log/console/jp1filterDef{1|2|3|4|5}.log

100 MB

20 MB

/var/opt/jp1cons/log/console/jp1bizGroupDef{1|2}.log

10 MB

5 MB

/var/opt/jp1cons/log/console/evtcon_exe{1|2|3}.log

256 KB × 3

256 KB

/var/opt/jp1cons/log/console/jp1cmdButtonDef{1|2|3|4|5}.log

25 MB

5 MB

/var/opt/jp1cons/log/console/jp1exattrnameDef{1|2|3|4|5}.log

25 MB

5 MB

shared-directory/jp1cons/log/console/EVCONS{1|2|3}.log

30,720 KB

10,240 KB

shared-directory/jp1cons/log/console/jp1cons{1|2|3|4|5|6|7|8}.log

40,960 KB

5,120 KB#3

shared-directory/jp1cons/log/console/JCOAPI{1|2|3}.log

96 KB

32 KB

shared-directory/jp1cons/log/console/jp1consM{1|2...|60}.log

300 MB

5 MB#3

shared-directory/jp1cons/log/console/jp1eventStormDef{1|2|3|4|5}.log

100 MB

20 MB

shared-directory/jp1cons/log/console/jp1filterDef{1|2|3|4|5}.log

100 MB

20 MB

shared-directory/jp1cons/log/console/jp1bizGroupDef{1|2}.log

10 MB

5 MB

shared-directory/jp1cons/log/console/evtcon_exe{1|2|3}.log

256 KB × 3

256 KB

shared-directory/jp1cons/log/console/jp1cmdButtonDef{1|2|3|4|5}.log

25 MB

5 MB

shared-directory/jp1cons/log/console/jp1exattrnameDef{1|2|3|4|5}.log

25 MB

5 MB

Automated action trace log#1

/var/opt/jp1cons/log/action/JCAMAIN{1|2|3|4|5}.log#4

25,600 KB

5,120 KB

shared-directory/jp1cons/log/action/JCAMAIN{1|2|3|4|5}.log#4

25,600 KB

5,120 KB

Action information file#1

/var/opt/jp1cons/log/action/actinf.log

626 KB#5

No switching

shared-directory/jp1cons/log/action/actinf.log

626 KB#5

No switching

Action host name file#1

/var/opt/jp1cons/log/action/acttxt{1|2}.log

48.9 MB#6

When the action information file wraps around

shared-directory/jp1cons/log/action/acttxt{1|2}.log

48.9 MB#6

When the action information file wraps around

Action re-execution file

/var/opt/jp1cons/log/action/actreaction

300 MB

When the service is started

shared-directory/jp1cons/log/action/actreaction

300 MB

When the service is started

jcochafmode, jcochstat, and jcoevtreport command trace logs#1, #7

/var/opt/jp1cons/log/command/CMD{1|2|3}.log

3,072 KB

1,024 KB

/var/opt/jp1cons/log/command/jp1cons_cmd{1|2}.log

12,288 KB

6,144 KB

/var/opt/jp1cons/log/command/jp1consM_cmd{1|2}.log

12,288 KB

6,144 KB

/var/opt/jp1cons/log/command/jp1exattrnameDef_cmd{1|2|3|4|5}.log

25 MB

5 MB

Plug-in log#1

/var/opt/jp1cons/log/command/jcoplugin{1|2|3}.log

3 MB

1 MB

Reporting status storage file#1

/var/opt/jp1cons/log/notice/notice_stat.dat

72B

No switching

shared-directory/jp1cons/log/notice/notice_stat.dat

72B

No switching

Action definition backup file#1

/var/opt/jp1cons/log/action/actdefbk.conf

2,048 KB

No switching

shared-directory/jp1cons/log/action/actdefbk.conf

2,048 KB

No switching

Event base trace log#1

/var/opt/jp1cons/log/evflow/EVFLOW{1|2|3|4|5|6|7|8|9|10}.log

100 MB

10 MB

/var/opt/jp1cons/log/evflow/jp1evflowM{1|2...|60}.log

300 MB

5 MB

/var/opt/jp1cons/log/evflow/jp1actDef{1|2|3|4|5}.log

25 MB

5 MB

/var/opt/jp1cons/log/evflow/jp1chsevDef{1|2|3|4|5}.log

25 MB

5 MB

/var/opt/jp1cons/log/evflow/jp1chmsgDef{1|2|3|4|5}.log

25 MB

5 MB

/var/opt/jp1cons/log/evflow/jp1hostmapDef{1|2|3|4|5}.log

25 MB

5 MB

/var/opt/jp1cons/log/evflow/evflow_exe{1|2|3}.log

256 KB × 3

256 KB

shared-directory/jp1cons/log/evflow/EVFLOW{1|2|3|4|5|6|7|8|9|10}.log

100 MB

10 MB

shared-directory/jp1cons/log/evflow/jp1evflowM{1|2...|60}.log

300 MB

5 MB

shared-directory/jp1cons/log/evflow/jp1actDef{1|2|3|4|5}.log

25 MB

5 MB

shared-directory/jp1cons/log/evflow/jp1chsevDef{1|2|3|4|5}.log

25 MB

5 MB

shared-directory/jp1cons/log/evflow/jp1chmsgDef{1|2|3|4|5}.log

25 MB

5 MB

shared-directory/jp1cons/log/evflow/jp1hostmapDef{1|2|3|4|5}.log

25 MB

5 MB

shared-directory/jp1cons/log/evflow/evflow_exe{1|2|3}.log

256 KB × 3

256 KB

Matching information file#1

/var/opt/jp1cons/log/evflow/evflowinf.log

12B

No switching

shared-directory/jp1cons/log/evflow/evflowinf.log

12B

No switching

Event base error log#1

/var/opt/jp1cons/log/evflow/jp1evflow{1|2|3|4|5|6|7|8}.log

40,960 KB

5,120 KB

shared-directory/jp1cons/log/evflow/jp1evflow{1|2|3|4|5|6|7|8}.log

40,960 KB

5,120 KB

Automated action error log#1

/var/opt/jp1cons/log/action/jp1act{1|2|3}.log

15,360 KB

5,120 KB

shared-directory/jp1cons/log/action/jp1act{1|2|3}.log

15,360 KB

5,120 KB

Correlation event generation history file

/var/opt/jp1cons/operation/evgen/egs_discrim{1|2|3}.log#8

30 MB#8

10 MB#8

shared-directory/jp1cons/operation/evgen/egs_discrim{1|2|3}.log#8

30 MB#8

10 MB#8

Common exclusion history file

/var/opt/jp1cons/operation/comexclude/comexclude{1|2|3|4|5}.log

100 MB

20 MB

shared-directory/jp1cons/operation/comexclude/comexclude{1|2|3|4|5}.log

100 MB

20 MB

Common exclusion-conditions definition history file

/var/opt/jp1cons/operation\comexclude/comexcludeDef{1|2|3|4|5}.log

100 MB

20 MB

shared-directory/jp1cons/operation/comexclude/comexcludeDef{1|2|3|4|5}.log

100 MB

20 MB

Correlation event generation trace log #1

/var/opt/jp1cons/log/evgen/EVGEN{1|2|3}.log

15 MB

5 MB

/var/opt/jp1cons/log/evgen/evgen_exe{1|2|3}.log

256 KB × 3

256 KB

shared-directory/jp1cons/log/evgen/EVGEN{1|2|3}.log

15 MB

5 MB

shared-directory/jp1cons/log/evgen/evgen_exe{1|2|3}.log

256 KB × 3

256 KB

Correlation event generation individual log (for Event Generation Service)#1

/var/opt/jp1cons/log/evgen/jp1egs{1|2}.log

20 MB

10 MB

/var/opt/jp1cons/log/evgen/jp1egsM{1|2}.log

20 MB

10 MB

shared-directory/jp1cons/log/evgen/jp1egs{1|2}.log

20 MB

10 MB

shared-directory/jp1cons/log/evgen/jp1egsM{1|2}.log

20 MB

10 MB

Correlation event generation individual log (for commands)#1

/var/opt/jp1cons/log/evgen/jp1egs_cmd{1|2|3|4}.log

20 MB

5 MB

/var/opt/jp1cons/log/evgen/jp1egsM_cmd{1|2|3|4}.log

20 MB

5 MB

Correlation event generation stack trace log#1

/var/opt/jp1cons/log/evgen/javalog0{1|2|3|4}.log

1 MB

At startup or 256 KB

shared-directory/jp1cons/log/evgen/javalog0{1|2|3|4}.log

1 MB

At startup or 256 KB

Correlation event generation process inheriting definition file#1

/var/opt/jp1cons/log/evgen/egs_discrim_info{1|2|3|4}.dat

312 MB#9

At termination

shared-directory/jp1cons/log/evgen/egs_discrim_info{1|2|3|4}.dat

312 MB#9

At termination

Correlation event generation definition application log#1

/var/opt/jp1cons/log/evgen/jp1egsDefine{1|2}.log

10 MB

5 MB

shared-directory/jp1cons/log/evgen/jp1egsDefine{1|2}.log

10 MB

5 MB

File for accumulated response-waiting events#1, #10

/var/opt/jp1cons/log/response/resevent.dat

40 MB

No switching

shared-directory/jp1cons/log/response/resevent.dat

40 MB

No switching

Backup file for accumulated response-waiting events#1, #10

/var/opt/jp1cons/log/response/resevent.dat.dump

40 MB

No switching

shared-directory/jp1cons/log/response/resevent.dat.dump

40 MB

No switching

Integrated monitoring database application log#1

/var/opt/jp1cons/log/evflow/EVFLOW_DBAPI{1|2...|16}.log

200 MB

12.5 MB

/var/opt/jp1cons/log/console/EVCONS_DBAPI{1|2|3|4|5}.log

50 MB

10 MB

/var/opt/jp1cons/log/command/CMD_DBAPI{1|2|3|4|5}.log

50 MB

10 MB

shared-directory/jp1cons/log/evflow/EVFLOW_DBAPI{1|2...|16}.log

200 MB

12.5 MB

shared-directory/jp1cons/log/console/EVCONS_DBAPI{1|2|3|4|5}.log

50 MB

10 MB

API log for the IM Configuration Management database#1

/var/opt/jp1cons/log/evflow/EVFLOW_CFDBAPI{1|2|3|4|5}.log

30 MB

10 MB

/var/opt/jp1cons/log/console/EVCONS_CFDBAPI{1|2|3}.log

30 MB

10 MB

/var/opt/jp1cons/log/command/CMD_CFDBAPI{1|2|3}.log

30 MB

10 MB

shared-directory/jp1cons/log/evflow/EVFLOW_CFDBAPI{1|2|3|4|5}.log

30 MB

10 MB

shared-directory/jp1cons/log/console/EVCONS_CFDBAPI{1|2|3}.log

30 MB

10 MB

jcodbsetup command log#1

/var/opt/jp1cons/log/imdb/jcodbsetup{1|2}.log

512 KB

256 KB

jcodbunsetup command log#1

/var/opt/jp1cons/log/imdb/jcodbunsetup{1|2}.log

512 KB

256 KB

Command execution history directory#1

/var/opt/jp1base/log/COMMAND/

See the JP1/Base User's Guide.

shared-directory/jp1base/log/COMMAND

Remote command log#1

/var/opt/jp1base/log/JCOCMD/jcocmd_result{1|2|3}.log

/var/opt/jp1base/log/JCOCMD/jcocmdapi{1|2|3}.log

/var/opt/jp1base/log/JCOCMD/jcocmdapi_trace{1|2|3}.log

/var/opt/jp1base/log/JCOCMD/jcocmdcmc{1|2|3}.log

/var/opt/jp1base/log/JCOCMD/jcocmdcmc_trace{1|2|3}.log

/var/opt/jp1base/log/JCOCMD/jcocmdcom{1|2|3}.log

/var/opt/jp1base/log/JCOCMD/jcocmdcom_trace{1|2|3}.log

/var/opt/jp1base/log/JCOCMD/jcocmdexe{1|2|3}.log

/var/opt/jp1base/log/JCOCMD/jcocmdexe_trace{1|2|3}.log

/var/opt/jp1base/log/JCOCMD/jcocmdrouter{1|2|3}.log

/var/opt/jp1base/log/JCOCMD/jcocmdrouter_trace{1|2|3}.log

/var/opt/jp1base/log/JCOCMD/JCOCMDCMD{1|2|3}.log

shared-directory/jp1base/log/JCOCMD/jcocmd_result{1|2|3}.log

shared-directory/jp1base/log/JCOCMD/jcocmdapi{1|2|3}.log

shared-directory/jp1base/log/JCOCMD/jcocmdapi_trace{1|2|3}.log

shared-directory/jp1base/log/JCOCMD/jcocmdcmc{1|2|3}.log

shared-directory/jp1base/log/JCOCMD/jcocmdcmc_trace{1|2|3}.log

shared-directory/jp1base/log/JCOCMD/jcocmdcom{1|2|3}.log

shared-directory/jp1base/log/JCOCMD/jcocmdcom_trace{1|2|3}.log

shared-directory/jp1base/log/JCOCMD/jcocmdexe{1|2|3}.log

shared-directory/jp1base/log/JCOCMD/jcocmdexe_trace{1|2|3}.log

shared-directory/jp1base/log/JCOCMD/jcocmdrouter{1|2|3}.log

shared-directory/jp1base/log/JCOCMD/jcocmdrouter_trace{1|2|3}.log

shared-directory/jp1base/log/JCOCMD/JCOCMDCMD{1|2|3}.log

Configuration management log#1

/var/opt/jp1base/log/route/JBSRT{1|2|3}.log

shared-directory/jp1base/log/route/JBSRT{1|2|3}.log

Trace log file#1

/var/opt/jp1base/sys/tmp/event/logtrap/jeallog/jeallog{1|2|3|4|5}.log

#1: This log is a process-by-process trace log. The process-by-process trace log is the log information that is output by each function of JP1/IM. It is output to a different log file depending on the function that is being used. Since the process-by-process trace log contains product information, its content is not made public.

#2: This log is created only in a cluster environment.

#3: The file size may be dozens of kilobytes larger than this value.

#4: You can set this value to be from 64 kilobytes to 100 megabytes, as described in Automated action environment definition file (action.conf.update) (in Chapter 2. Definition Files) in the manual JP1/Integrated Management 2 - Manager Command, Definition File and API Reference.

#5: You can set this value to be from 1 to 4,096 kilobytes as described in Automated action environment definition file (action.conf.update) (in Chapter 2. Definition Files) in the manual JP1/Integrated Management 2 - Manager Command, Definition File and API Reference.

#6: This is the value when the size of the action information file is the default value (626 kilobytes). You can use the following estimation formula to estimate the maximum disk usage by this file. Each time an action is performed, the size increases by 5 kilobytes.

((action information file size ÷ 64 bytes) - 1) × 5 kilobytes

#7: The files are output to the jcochstat and jcochafmode command trace logs on the physical host in a cluster operation system as well.

#8: You can change the file count and file size as described in Correlation event generation environment definition file (in Chapter 2. Definition Files) in the manual JP1/Integrated Management 2 - Manager Command, Definition File and API Reference.

#9: This file is used to output the memory information for inheriting data during correlation event generation, and therefore its size varies depending on the correlation event generation condition and the correlation-source event. For details about estimating the size of this file, see the JP1/IM - Manager release notes.

#10: This file is created when you start JP1/IM - Manager after enabling the response-waiting event management function.

Table 11‒12: JP1/IM - Manager (Central Scope) log files and directories (UNIX)

Log type

Default file name and directory name

Maximum disk usage

File-switching timing

Central Scope trace log

/var/opt/jp1scope/log/jcsmain{1|2|3}.log

6 MB

2 MB

/var/opt/jp1scope/log/jcsmain_trace{1|2|3}.log

6 MB

2 MB

shared-directory/jp1scope/log/jcsmain{1|2|3}.log

6 MB

2 MB

shared-directory/jp1scope/log/jcsmain_trace{1|2|3}.log

6 MB

2 MB

Communication trace log

/var/opt/jp1scope/log/jcsmain_trace_com{1|2|3}.log

6 MB

2 MB

shared-directory/jp1scope/log/jcsmain_trace_com{1|2|3}.log

6 MB

2 MB

/var/opt/jp1scope/log/jcsmain_trace_ping{1|2|3}.log

6 MB

2 MB

shared-directory/jp1scope/log/jcsmain_trace_ping{1|2|3}.log

6 MB

2 MB

Database operation API trace log

/var/opt/jp1scope/log/jcsmain_trace_db{1|2|3}.log

6 MB

2 MB

shared-directory/jp1scope/log/jcsmain_trace_db{1|2|3}.log

6 MB

2 MB

jcshostsexport command log

/var/opt/jp1scope/log/jcshostsexport{1|2|3}.log

6 MB

2 MB

shared-directory/jp1scope/log/jcshostsexport{1|2|3}.log

6 MB

2 MB

jcshostsimport command log

/var/opt/jp1scope/log/jcshostsimport{1|2|3}.log

6 MB

2 MB

shared-directory/jp1scope/log/jcshostsimport{1|2|3}.log

6 MB

2 MB

jcsdbsetup command log

/var/opt/jp1scope/log/jcsdbsetup{1|2|3}.log

6 MB

2 MB

shared-directory/jp1scope/log/jcsdbsetup{1|2|3}.log

6 MB

2 MB

jcschstat command log

/var/opt/jp1scope/log/jcschstat{1|2|3}.log

6 MB

2 MB

shared-directory/jp1scope/log/jcschstat{1|2|3}.log

6 MB

2 MB

jcsdbimport command log

/var/opt/jp1scope/log/jcsdbimport{1|2|3}.log

6 MB

2 MB

shared-directory/jp1scope/log/jcsdbimport{1|2|3}.log

6 MB

2 MB

jcsdbexport command log

/var/opt/jp1scope/log/jcsdbexport{1|2|3}.log

6 MB

2 MB

shared-directory/jp1scope/log/jcsdbexport{1|2|3}.log

6 MB

2 MB

Setup log

/var/opt/jp1scope/log/JCS_SETUP/jcs_setup.log

100 KB

During installation

/var/opt/jp1scope/log/jcs_setup/logical-host-name/jcs_setup.log

100 KB

During installation

/var/opt/jp1scope/log/jcs_setup/logical-host-name/reg.txt

100 KB

During installation

/var/opt/jp1scope/log/jcs_setup/logical-host-name/reg_def.txt

100 KB

During installation

Note: This log is a process-by-process trace log. The process-by-process trace log is the log information that is output by each function of JP1/IM. It is output to a different log file depending on the function that is being used. Since the process-by-process trace log contains product information, its content is not made public.

Table 11‒13: JP1/IM - Manager (IM Configuration Management) log files and folders (UNIX)

Log type

Default file name and directory name

Maximum disk usage

File-switching timing

IM Configuration Management trace log

/var/opt/jp1imm/log/imcf/jcfallogtrap{1|2|3|4|5|6|7|8|9|10}.log

200 MB

10 MB

/var/opt/jp1imm/log/imcf/jcfallogtrap_VM_trace{1|2|3}.log

3 MB

1 MB

/var/opt/jp1imm/log/imcf/jcfallogtrap_trace_auth{1|2|3|4|5|6|7|8|9|10}.log

20 MB

2 MB

/var/opt/jp1imm/log/imcf/jcfmain{1|2|3|4|5|6|7|8|9|10}.log

20 MB

2 MB

/var/opt/jp1imm/log/imcf/jcfmain_trace{1|2|3|4|5|6|7|8|9|10}.log

20 MB

2 MB

/var/opt/jp1imm/log/imcf/jcfmain_VM_trace{1|2|3}.log

3 MB

1 MB

shared-directory/jp1imm/log/imcf/jcfallogtrap{1|2|3|4|5|6|7|8|9|10}.log

200 MB

10 MB

shared-directory/jp1imm/log/imcf/jcfallogtrap_VM_trace{1|2|3}.log

3 MB

1 MB

shared-directory/jp1imm/log/imcf/jcfallogtrap_trace_auth{1|2|3|4|5|6|7|8|9|10}.log

20 MB

2 MB

shared-directory/jp1imm/log/imcf/jcfmain{1|2|3|4|5|6|7|8|9|10}.log

20 MB

2 MB

shared-directory/jp1imm/log/imcf/jcfmain_trace{1|2|3|4|5|6|7|8|9|10}.log

20 MB

2 MB

shared-directory/jp1imm/log/imcf/jcfmain_VM_trace{1|2|3}.log

3 MB

1 MB

Communication trace log

/var/opt/jp1imm/log/imcf/jcfmain_trace_com{1|2|3|4|5|6|7|8|9|10}.log

20 MB

2 MB

/var/opt/jp1imm/log/imcf/jcfmain_ping{1|2|3|4|5|6|7|8|9|10}.log

20 MB

2 MB

shared-directory/jp1imm/log/imcf/jcfmain_trace_com{1|2|3|4|5|6|7|8|9|10}.log

20 MB

2 MB

shared-directory/jp1imm/log/imcf/jcfmain_ping{1|2|3|4|5|6|7|8|9|10}.log

20 MB

2 MB

Authentication trace log

/var/opt/jp1imm/log/imcf/jcfmain_trace_auth{1|2|3|4|5|6|7|8|9|10}.log

20 MB

2 MB

shared-directory/jp1imm/log/imcf/jcfmain_trace_auth{1|2|3|4|5|6|7|8|9|10}.log

20 MB

2 MB

Database operation API trace log

/var/opt/jp1imm/log/imcf/jcfmain_trace_db{1|2|3|4|5|6|7|8|9|10}.log

20 MB

2 MB

shared-directory/jp1imm/log/imcf/jcfmain_trace_db{1|2|3|4|5|6|7|8|9|10}.log

20 MB

2 MB

Command common log

/var/opt/jp1imm/log/imcf/jcfcommand{1|2|3}.log

3 MB

1 MB

shared-directory/jp1imm/log/imcf/jcfcommand{1|2|3}.log

3 MB

1 MB

jcfallogstart command log

/var/opt/jp1imm/log/imcf/jcfallogstart{1|2|3}.log

9 MB

3 MB

/var/opt/jp1imm/log/imcf/jcfallogstart_VM_trace{1|2|3}.log

3 MB

1 MB

shared-directory/jp1imm/log/imcf/jcfallogstart{1|2|3}.log

9 MB

3 MB

shared-directory/jp1imm/log/imcf/jcfallogstart_VM_trace{1|2|3}.log

3 MB

1 MB

jcfallogstat command log

/var/opt/jp1imm/log/imcf/jcfallogstat{1|2|3}.log

9 MB

3 MB

/var/opt/jp1imm/log/imcf/jcfallogstat_VM_trace{1|2|3}.log

3 MB

1 MB

shared-directory/jp1imm/log/imcf/jcfallogstat{1|2|3}.log

9 MB

3 MB

shared-directory/jp1imm/log/imcf/jcfallogstat_VM_trace{1|2|3}.log

3 MB

1 MB

jcfallogstop command log

/var/opt/jp1imm/log/imcf/jcfallogstop{1|2|3}.log

9 MB

3 MB

/var/opt/jp1imm/log/imcf/jcfallogstop_VM_trace{1|2|3}.log

3 MB

1 MB

shared-directory/jp1imm/log/imcf/jcfallogstop{1|2|3}.log

9 MB

3 MB

shared-directory/jp1imm/log/imcf/jcfallogstop_VM_trace{1|2|3}.log

3 MB

1 MB

jcfallogreload command log

/var/opt/jp1imm/log/imcf/jcfallogreload{1|2|3}.log

9 MB

3 MB

/var/opt/jp1imm/log/imcf/jcfallogreload_VM_trace{1|2|3}.log

3 MB

1 MB

shared-directory/jp1imm/log/imcf/jcfallogreload{1|2|3}.log

9 MB

3 MB

shared-directory/jp1imm/log/imcf/jcfallogreload_VM_trace{1|2|3}.log

3 MB

1 MB

jcfallogdef command log

/var/opt/jp1imm/log/imcf/jcfallogdef{1|2|3}.log

9 MB

3 MB

/var/opt/jp1imm/log/imcf/jcfallogdef_VM_trace{1|2|3}.log

3 MB

1 MB

shared-directory/jp1imm/log/imcf/jcfallogdef{1|2|3}.log

9 MB

3 MB

shared-directory/jp1imm/log/imcf/jcfallogdef_VM_trace{1|2|3}.log

3 MB

1 MB

jcfcolvmesx command log

/var/opt/jp1imm/log/imcf/jcfcolvmesx_trace{1|2|3}.log

3 MB

1 MB

shared-directory/jp1imm/log/imcf/jcfcolvmesx_trace{1|2|3}.log

jcfcolvmvirtage command log

/var/opt/jp1imm/log/imcf/jcfcolvmvirtage_trace{1|2|3}.log

3 MB

1 MB

shared-directory/jp1imm/log/imcf/jcfcolvmvirtage_trace{1|2|3}.log

jcfcolvmvc command log

/var/opt/jp1imm/log/imcf/jcfcolvmvc_trace{1|2|3}.log

3 MB

1 MB

shared-directory/jp1imm/log/imcf/jcfcolvmvc_trace{1|2|3}.log

jcfcolvmkvm command log

/var/opt/jp1imm/log/imcf/jcfcolvmkvm_trace{1|2|3}.log

3 MB

1 MB

shared-directory/jp1imm/log/imcf/jcfcolvmkvm_trace{1|2|3}.log

jcfcolvmhcsm command log

/var/opt/jp1imm/log/imcf/jcfcolvmhcsm_trace{1|2|3}.log

3 MB

1 MB

shared-directory/jp1imm/log/imcf/jcfcolvmhcsm_trace{1|2|3}.log

jcfexport command log

/var/opt/jp1imm/log/imcf/jcfexport_VM_trace{1|2|3}.log

3 MB

1 MB

shared-directory/jp1imm/log/imcf/jcfexport_VM_trace{1|2|3}.log

3 MB

1 MB

jcfimport command log

/var/opt/jp1imm/log/imcf/jcfimport_VM_trace{1|2|3}.log

3 MB

1 MB

shared-directory/jp1imm/log/imcf/jcfimport_VM_trace{1|2|3}.log

3 MB

1 MB

jcfmkhostsdata command log

/var/opt/jp1imm/log/imcf/jcfmkhostsdata_trace{1|2|3}.log

3 MB

1 MB

Stack trace log

/var/opt/jp1imm/log/imcf/javalog0{1|2|3|4}.log

1 MB

At startup or 256 KB

Setup log

/var/opt/jp1imm/log/imcf/JCF_SETUP/jcf_setup.log

100 KB

During installation

/var/opt/jp1imm/log/imcf/JCF_SETUP/logical-host-name/jcf_setup.log

100 KB

During installation

Note: The logs above are process-by-process trace logs. The process-by-process trace log is the log information that is output by each function of JP1/IM. It is output to a different log file depending on the function that is being used. Since the process-by-process trace log contains product information, its content is not made public.

Table 11‒14: Intelligent Integrated Management Base log files and folders

Log type

Default file name and directory name

Maximum disk usage

File-switching timing

Intelligent Integrated Management Base service individual log

/var/opt/jp1imm/log/imdd/jddmain/jddmain.log{.1-7}

1 GB

128 MB

shared-directory/jp1imm/log/imdd/jddmain/jddmain.log{.1-7}

Definition file#1, node file history log

/var/opt/jp1imm/log/imdd/jddmain/jimddDef.log{.1-10}

80 MB

8 MB

shared-directory/jp1imm/log/imdd/jddmain/jimddDef.log{.1-10}

/var/opt/jp1imm/log/imdd/jddmain/jimddMaster.log{.1-30}

240 MB

8 MB

shared-directory/jp1imm/log/imdd/jddmain/jimddMaster.log{.1-30}

jddsetaccessuser command trace log

/var/opt/jp1imm/log/imdd/jddsetaccessuser/jddsetaccessuser.log{.1-6}

70 MB

10 MB

shared-directory/jp1imm/log/imdd/jddsetaccessuser/jddsetaccessuser.log{.1-6}

/var/opt/jp1imm/log/imdd/jddsetaccessuser/jddsetaccessuser_exe{1|2|3}.log

768 KB

256 KB

shared-directory/jp1imm/log/imdd/jddsetaccessuser/jddsetaccessuser_exe{1|2|3}.log

/var/opt/jp1imm/log/imdd/jddsetaccessuser/javalog0{1|2|3|4}.log

1,024 KB

At startup or 256 KB

shared-directory/jp1imm/log/imdd/jddsetaccessuser/javalog0{1|2|3|4}.log

jddcreatetree command trace log

/var/opt/jp1imm/log/imdd/jddcreatetree/jddcreatetree.log{.1-6}

70 MB

10 MB

shared-directory/jp1imm/log/imdd/jddcreatetree/jddcreatetree.log{.1-6}

/var/opt/jp1imm/log/imdd/jddcreatetree/jddcreatetree_exe{1|2|3}.log

768 KB

256 KB

shared-directory/jp1imm/log/imdd/jddcreatetree/jddcreatetree_exe{1|2|3}.log

/var/opt/jp1imm/log/imdd/jddcreatetree/javalog0{1|2|3|4}.log

1,024 KB

At startup or 256 KB

shared-directory/jp1imm/log/imdd/jddcreatetree/javalog0{1|2|3|4}.log

jddupdatetree command trace log

/var/opt/jp1imm/log/imdd/jddupdatetree/jddupdatetree.log{.1-6}

70 MB

10 MB

shared-directory/jp1imm/log/imdd/jddupdatetree/jddupdatetree.log{.1-6}

/var/opt/jp1imm/log/imdd/jddupdatetree/jddupdatetree_exe{1|2|3}.log

768 KB

256 KB

shared-directory/jp1imm/log/imdd/jddupdatetree/jddupdatetree_exe{1|2|3}.log

/var/opt/jp1imm/log/imdd/jddupdatetree/javalog0{1|2|3|4}.log

1,024 KB

256 KB

shared-directory/jp1imm/log/imdd/jddupdatetree/javalog0{1|2|3|4}.log

jddproxyuser command trace log

/var/opt/jp1imm/log/imdd/jddproxyuser/jddproxyuser.log{.1-6}

70MB

10MB

shared-directory/jp1imm/log/imdd/jddproxyuser/jddproxyuser.log{.1-6}

/var/opt/jp1imm/log/imdd/jddproxyuser/jddproxyuser_exe{1|2|3}.log

768KB

256KB

shared-directory/jp1imm/log/imdd/jddproxyuser/jddproxyuser_exe{1|2|3}.log

/var/opt/jp1imm/log/imdd/jddproxyuser/javalog0{1|2|3|4}.log

1,024KB

256KB

shared-directory/jp1imm/log/imdd/jddproxyuser/javalog0{1|2|3|4}.log

Logs of the response action execution history file#4

/var/opt/jp1imm/log/suggestion/jddSuggestionHistory.log{.1-3}

240MB

60MB

shared-directory/jp1imm/log/suggestion/jddSuggestionHistory.log{.1-3}

User-created plug-ins

/var/opt/jp1imm/log/imdd/user-created-plug-in-name/user-created-plug-in.log{1-21}#3

220MB

10MB

shared-directory/jp1imm/log/imdd/user-created-plug-in-name/user-created-plug-in.log{1-21}#3

Other logs

/var/opt/jp1imm/log/imdd/jddmain/jddmain_exe{1|2|3}.log

768 KB

256 KB

shared-directory/jp1imm/log/imdd/jddmain/jddmain_exe{1|2|3}.log

/var/opt/jp1imm/log/imdd/jddmain/javalog0{1|2|3|4}.log

1,024 KB

At startup or 256 KB

shared-directory/jp1imm/log/imdd/jddmain/javalog0{1|2|3|4}.log

/var/opt/jp1imm/log/imdd/jcoapi{1-50}.log

500 MB

10 MB

shared-directory/jp1imm/log/imdd/jddmain/jcoapi{1-50}.log

/var/opt/jp1imm/log/imdd/jcoapiM{1-50}.log

500 MB

10 MB

shared-directory/jp1imm/log/imdd/jddmain/jcoapiM{1-50}.log

/var/opt/jp1imm/log/imdd/component-name#2/component-name#2{1-21}.log

220MB

10MB

shared-directory/jp1imm/log/imdd/component-name#2/component-name#2{1-21}.log

Note: The logs above are process-by-process trace logs. The process-by-process trace log is the log information that is output by each function of JP1/IM. It is output to a different log file depending on the function that is being used. Since the process-by-process trace log contains product information, its content is not made public.

#1: The logs for the following definition files are output to the definition file log for the Intelligent Integrated Management Base:

System node definition file, category name definition file for IM management nodes, host name definition file, target host definition file for configuration collection, IM management node link definition file, IM management node link file, IM management node tree file, IM management node file

#2: One of the following is displayed as the component name:

- jp1ajs

- jp1pfm

- jp1im

#3: {1-21} indicates the file count. You can view the log files in a text editor of your choice.

#4: The log is created when a response action is taken. Users can check the logs of response actions by themselves in order to examine the causes of failures, for example.

To Page Top

Copyright (C) 2019, 2021, Hitachi, Ltd.

Copyright (C) 2019, 2021, Hitachi Solutions, Ltd.