A.2 List of log files output by JP1/IM - Service Support
The table below shows the types of log information output by JP1/IM - Service Support and the default file names and folder names.
The File switching trigger column indicates when JP1/IM - Service Support switches the output destination log file. JP1/IM - Service Support switches the output destination or overwrites the file when the file size reaches the value indicated in this column or when the event indicated in this column occurs. If there are multiple log files and the amount of used disk space reaches the maximum, the file with the oldest update date is overwritten.
If a cluster system, these log files are stored on a shared disk. When you use a cluster system, replace IM-SS-path\log\ in the following table with shared-folder\log\.
|
Log type |
File name and folder name |
Maximum disk space requirement |
File switching trigger |
|---|---|---|---|
|
JP1/IM - Service Support portlet log |
IM-SS-path\log\Server\jp1imssmain{1|2|3|4|5|6|7|8}.log |
32 megabytes |
4 megabytes |
|
User management portlet log |
IM-SS-path\log\Server\jp1imssuser{1|2|3|4|5|6|7|8}.log |
32 megabytes |
4 megabytes |
|
Log of the Item list output command |
IM-SS-path\log\command\jssitemlist{1|2|3|4}.log |
16 megabytes |
4 megabytes |
|
Log of the Item history output command |
IM-SS-path\log\command\jssitemhistory{1|2|3|4}.log |
16 megabytes |
4 megabytes |
|
Log of the Item registration command |
IM-SS-path\log\command\jssitementry{1|2|3|4}.log |
16 megabytes |
4 megabytes |
|
Log of the user import command |
IM-SS-path\log\command\jssuserimport{1|2|3|4}.log |
16 megabytes |
4 megabytes |
|
Log of the Item import command |
IM-SS-path\log\command\jssitemimport{1|2|3|4}.log |
16 megabytes |
4 megabytes |
|
Log of the Item form registration command (for C language) |
IM-SS-path\log\command\jssformdefc{1|2|3|4}.log |
16 megabytes |
4 megabytes |
|
Log of the Item form registration command (for Java) |
IM-SS-path\log\command\jssformdefj{1|2|3|4}.log |
16 megabytes |
4 megabytes |
|
Log of the deletion command (for C language) |
IM-SS-path\log\command\jssdelrecc{1|2|3|4}.log |
16 megabytes |
4 megabytes |
|
Log of the deletion command (for Java) |
IM-SS-path\log\command\jssdelrecj{1|2|3|4}.log |
16 megabytes |
4 megabytes |
|
Log of the Item registration command using emails |
IM-SS-path\log\command\jssitementrybymail{1|2|3|4}.log |
16 megabytes |
4 megabytes |
|
Log of the command for exporting extended Item information (for C language) |
IM-SS-path\log\command\jssitemexportExc{1|2|3|4}.log |
16 megabytes |
4 megabytes |
|
Log of the command for exporting extended Item information (for Java) |
IM-SS-path\log\command\jssitemexportExj{1|2|3|4}.log |
16 megabytes |
4 megabytes |
|
Log of the command for importing extended Item (for C language) |
IM-SS-path\log\command\jssitemimportExc{1|2|3|4}.log |
16 megabytes |
4 megabytes |
|
Log of the command for importing extended Item (for Java) |
IM-SS-path\log\command\jssitemimportExj{1|2|3|4|5|6|7|8|9|10|11|12}.log |
96 megabytes |
8 megabytes |
|
Log of the command for creating a master system and a temporary receipt process work board (for C language) |
IM-SS-path\log\command\jsscreatesysandpwbc{1|2|3|4}.log |
16 megabytes |
4 megabytes |
|
Log of the command for creating a master system and a temporary receipt process work board (for Java) |
IM-SS-path\log\command\jsscreatesysandpwbj{1|2|3|4}.log |
16 megabytes |
4 megabytes |
|
Log of the Item information count command (for C language) |
IM-SS-path\log\command\jsscollectdatac{1|2|3|4}.log |
16 megabytes |
4 megabytes |
|
Log of the Item information count (for Java) |
IM-SS-path\log\command\jsscollectdataj{1|2|3|4}.log |
16 megabytes |
4 megabytes |
|
Log of the expiration notification command |
IM-SS-path\log\command\jssinformperiod{1|2|3|4}.log |
16 megabytes |
4 megabytes |
|
Log of database upgrading (for C language) |
IM-SS-path\log\command\jssvupdbdatac{1|2|3|4}.log |
16 megabytes |
4 megabytes |
|
Log of database upgrading (for Java) |
IM-SS-path\log\command\jssvupdbdataj{1|2|3|4}.log |
16 megabytes |
4 megabytes |
|
Log of the batch Item deletion command (for C language) |
IM-SS-path\log\command\jssitemdeletionc{1|2|3|4}.log |
16 megabytes |
4 megabytes |
|
Log of the batch Item deletion command (for Java) |
IM-SS-path\log\command\jssitemdeletionj{1|2|3|4}.log |
16 megabytes |
4 megabytes |
|
Log of the command for canceling batch deletion of Items (for C language) |
IM-SS-path\log\command\jssrevc{1|2|3|4}.log |
16 megabytes |
4 megabytes |
|
Log of the command for canceling batch deletion of Items (for Java) |
IM-SS-path\log\command\jssrevj{1|2|3|4}.log |
16 megabytes |
4 megabytes |
|
Log of the Item editing command |
IM-SS-path\log\command\jssitemedit{1|2|3|4}.log |
16 megabytes |
4 megabytes |
|
Log of the command to export access-permission information (for C language) |
IM-SS-path\log\command\jssaclexportc{1|2|3|4}.log |
16 megabytes |
4 megabytes |
|
Log of the command to export access-permission information (for Java) |
IM-SS-path\log\command\jssaclexportj{1|2|3|4}.log |
16 megabytes |
4 megabytes |
|
Log of the command to import access-permission information (for C language) |
IM-SS-path\log\command\jssaclimportc{1|2|3|4}.log |
16 megabytes |
4 megabytes |
|
Log of the command to import access-permission information (for Java) |
IM-SS-path\log\command\jssaclimportj{1|2|3|4}.log |
16 megabytes |
4 megabytes |
|
Log of the command to count Items (for C language) |
IM-SS-path\log\command\jssitemcountc{1|2|3|4}.log |
16 megabytes |
4 megabytes |
|
Log of the command to count Items (for Java) |
IM-SS-path\log\command\jssitemcountj{1|2|3|4}.log |
16 megabytes |
4 megabytes |
|
Log of the command to set up view permission settings for individual Items (for C language) |
IM-SS-path\log\command\jssrefaclsetupc{1|2|3|4}.log |
16 megabytes |
4 megabytes |
|
Log of the command to set up view permission settings for individual Items (for Java) |
IM-SS-path\log\command\jssrefaclsetupj{1|2|3|4}.log |
16 megabytes |
4 megabytes |
|
Log of the database initialization command#1 |
IM-SS-path\log\command\jssdbinit{None#2|2|3|4|5}.log |
100 kilobytes |
The command is executed |
|
Database reorganization command |
IM-SS-path\log\command\jssdbrorg.log |
100 kilobytes |
The command is executed |
|
Log of the command for releasing the free space in the Item management database |
IM-SS-path\log\command\jssdbreclaim.log |
20 kilobytes |
The command is executed |
|
Log of the database backup command#1 |
IM-SS-path\log\command\jssdbbackup.log Note that output log files increase depending on the option specified for the command. 1. With -f -maint specified: IM-SS-path\log\command\jssdbbackupresult.log 2. With -o -maint specified: IM-SS-path\log\command\jssdbbackupMdb.log IM-SS-path\log\command\jssdbbackupSdbA.log IM-SS-path\log\command\jssdbbackupSdbB.log |
10 kilobytes |
The command is executed |
|
Log of the database recovery command#1 |
IM-SS-path\log\command\jssdbrecovery.log Note that output log files increase depending on the option specified for the command. 1. With -f -maint specified: IM-SS-path\log\command\jssdbrecoveryresult.log 2. With -o -maint specified: IM-SS-path\log\command\jssdbrecoveryMdb.log IM-SS-path\log\command\jssdbrecoverySdbA.log IM-SS-path\log\command\jssdbrecoverySdbB.log |
10 kilobytes |
The command is executed |
|
Log of the database backup file |
IM-SS-path\log\command\jssdbbackupresult.log |
10 kilobytes |
The command is executed |
|
Log of the recovered RDAREA |
IM-SS-path\log\command\jssdbrecoveryresult.log |
20 kilobytes |
The command is executed |
|
Log of the setup command#1 |
IM-SS-path\log\command\jsssetup{None#2|2|3|4|5}.log |
1 megabytes |
The command is executed |
|
Log of the setup cancellation command#1 |
IM-SS-path\log\command\jssunsetup{None#2|2|3|4|5}.log |
10 kilobytes |
The command is executed |
|
Log of the environment settings for files |
IM-SS-path\log\command\jsswebconconf{None#2|2|3|4|5}.log |
20 kilobytes |
The command is executed |
|
Log of the setup check processing |
IM-SS-path\log\command\jsssetupcheckinfo{None#2|2|3|4|5}.log |
10 kilobytes |
The command is executed |
|
Log of the command to check the database status (for batch) |
IM-SS-path\log\command\jssdbstatchkb{None#2|2|3|4|5}.log |
10 kilobytes |
The command is executed |
|
Log of the command to check the database status (for Java) |
IM-SS-path\log\command\jssdbstatchkj{1|2|3|4}.log |
16 megabytes |
4 megabytes |
|
Log of the command to store Items (for C language) |
IM-SS-path\log\command\jssitemstorec{1|2|3|4}.log |
16 megabytes |
4 megabytes |
|
Log of the command to store Items (for Java) |
IM-SS-path\log\command\jssitemstorej{1|2|3|4|5|6|7|8|9|10|11|12}.log |
96 megabytes |
8 megabytes |
|
Log of the command to expand an Item storage database |
IM-SS-path\log\command\jssitemstoredbexpand{None#2|2|3|4|5}.log |
100 megabytes |
The command is executed |
|
Log of the command to set up an Item storage database |
IM-SS-path\log\command\jssitemstoredbsetup{None#2|2|3|4|5}.log |
100 megabytes |
The command is executed |
|
Log of the command to rotate Item storage databases (for C language) |
IM-SS-path\log\command\jssitemstoredbrotatec{1|2|3|4}.log |
16 megabytes |
4 megabytes |
|
Log of the command to rotate Item storage databases (for Java) |
IM-SS-path\log\command\jssitemstoredbrotatej{1|2|3|4}.log |
16 megabytes |
4 megabytes |
|
Log of the command to delete stored Items |
IM-SS-path\log\command\jssstoreitemdel{None#2|2|3|4|5}.log |
5 megabytes |
The command is executed |
|
Log of the database initialization command for the cluster |
IM-SS-path\log\command\jsshadbinit{None#2|2|3|4|5}.log |
100 kilobytes |
The command is executed |
|
Log of the setup command for the cluster |
For the log of the setup command for the cluster, the output destination and contents vary depending on whether the command was executed on the primary server or secondary server and the options specified for the command. If the command was executed on the primary server: 1. With the -c online option specified: shared-folder\log\command\online\jsshasetup{None#2|2|3|4|5}.log shared-folder\log\command\online\jsshadbinit{None#2|2|3|4|5}.log shared-folder\log\command\online\jsshaconconf{None#2|2|3|4|5}.log shared-folder\log\command\online\jsshasetupcheckinfo{None#2|2|3|4|5}.log shared-folder\log\command\online\jsswebconconf{None#2|2|3|4|5}.log 2. With the -r option specified: shared-folder\log\command\online\jsshasetup{1|2|3|4|5}.log 3. With the -vup option specified: shared-folder\log\command\online\jsshasetup{None#2|2|3|4|5}.log shared-folder\log\command\online\jsshaconconf{None#2|2|3|4|5}.log shared-folder\log\command\online\jsswebconconf{None#2|2|3|4|5}.log shared-folder\log\command\jssvupdbdatac{1|2|3|4}.log shared-folder\log\command\jssvupdbdataj{1|2|3|4}.log If the command was executed on the secondary server: 1. With the -c standby option specified: shared-folder\log\command\standby_secondary-server-name\jsshasetup{None#2|2|3|4|5}.log shared-folder\log\command\standby_secondary-server-name\jsshadbinit{None#2|2|3|4|5}.log shared-folder\log\command\standby_secondary-server-name\jsshaconconf{None#2|2|3|4|5}.log shared-folder\log\command\standby_secondary-server-name\jsshasetupcheckinfo{None#2|2|3|4|5}.log shared-folder\log\command\standby_secondary-server-name\jsswebconconf{None#2|2|3|4|5}.log 2. With the -r option specified: shared-folder\log\command\standby_secondary-server-name\jsshasetup{None#2|2|3|4|5}.log 3. With the -vup option specified: shared-folder\log\command\standby_secondary-server-name\jsshasetup{None#2|2|3|4|5}.log shared-folder\log\command\standby_secondary-server-name\jsshadbinit{None#2|2|3|4|5}.log shared-folder\log\command\standby_secondary-server-name\jsshaconconf{None#2|2|3|4|5}.log shared-folder\log\command\standby_secondary-server-name\jsswebconconf{None#2|2|3|4|5}.log |
1 megabytes |
The command is executed |
|
Log of the setup cancellation command for the cluster |
The output destination of the log of the setup cancellation command for the cluster varies depending on whether the command was executed on the primary server or secondary server. If the command was executed on the primary server: shared-folder\log\command\online\jsshaunsetup{None#2|2|3|4|5}.log If the command was executed on the secondary server: shared-folder\log\command\standby_secondary-server-name\jsshaunsetup{None#2|2|3|4|5}.log |
10 kilobytes |
The command is executed |
|
Log of the setup command for the cluster (updates the cluster definition file ) |
IM-SS-path\log\command\jsshaconconf{None#2|2|3|4|5}.log |
20 kilobytes |
The command is executed |
|
Log of registration, startup, and deletion of services#1 |
IM-SS-path\log\system\jssService{1|2}.log |
2 megabytes |
1 megabytes |
|
Log of registration, startup, and deletion of task services#1 |
IM-SS-path\log\system\jssTaskService{1|2|3|4}.log |
4 megabytes |
1 megabytes |
- #1
-
Even if you use a cluster system, you do not have to replace the output destination path with shared-folder\log\.
- #2
-
A number is not added to the name of the first log file.
In addition to the log files output by the system, JP1/IM - Service Support provides public logs that are open to users. Users can specify whether to output the public logs to a file, the file size, and the number of files. By default, the public logs are not output. Note that the names of the public log files and folders and their sizes in the following table are the default values.
|
Log type |
File name and folder name |
Size |
Log file format |
|---|---|---|---|
|
Public log of the Item registration command |
IM-SS-path\log\command\jssitementry\jssitementry_info{1|2}.log |
8,192 kilobytes |
Trace file for multi-processing |
|
Operation log |
IM-SS-path\log\public\acceslog\jp1imssaccesslog{1|2|3|4|5|6|7|8|9|10|11|12|13|14|15|16|17|18|19|20|21|22|23|24}.log |
16,384 kilobytes |
Wraparound file (WRAP2) |
|
Operation log for the cluster |
shared-folder\log\public\acceslog\jp1imssaccesslog{1|2|3|4|5|6|7|8|9|10|11|12|13|14|15|16|17|18|19|20|21|22|23|24}.log |
16,384 kilobytes |
Wraparound file (WRAP2) |
|
Public log of the Item registration command using emails |
IM-SS-path\log\public\jssitementrybymail\jssitementrybymail_info{1|2}.log |
8,192 kilobytes |
Trace file for multi-processing |
|
Public log of the JP1 event issuing function |
IM-SS-path\log\public\jp1imssevent{1|2|3|4|5|6|7|8}.log |
4,096 kilobytes |
Wraparound file (WRAP2) |
|
Public log of the expiration notification command |
IM-SS-path\log\public\jssinformperiod_info{1|2}.log |
8,192 kilobytes |
Trace file for multi-processing |
|
Public log of the auxiliary input function |
IM-SS-path\log\public\jssinputassist_info{1|2}.log |
8,192 kilobytes |
Wraparound file (WRAP2) |
|
Public log of the email notification function |
IM-SS-path\log\public\jssmailnotification_info{1|2}.log |
8,192 kilobytes |
Trace file for multi-processing |
|
Public log of the Item editing command |
IM-SS-path\log\command\jssitemedit\jssitemedit_info{1|2}.log |
8,192 kilobytes |
Trace file for multi-processing |
|
Public log of the notification command for held Items |
IM-SS-path\log\public\jssinformleave_info{1|2}.log |
8,192 kilobytes |
Trace file for multi-processing |
|
Public log of the command for exporting extended Item information |
IM-SS-path\log\public\jssitemexportEx_info{1|2|3|4|5|6|7|8}.log |
8,192 kilobytes |
Trace file for multi-processing |
|
Public log of the command for importing extended Item information |
IM-SS-path\log\public\jssitemimportEx_info{1|2|3|4|5|6|7|8}.log |
8,192 kilobytes |
Trace file for multi-processing |
|
Public log of the command to export access-permission information |
IM-SS-path\log\public\jssaclexport_info{1|2}.log |
8,192 kilobytes |
Trace file for multi-processing |
|
Public log of the command to import access-permission information |
IM-SS-path\log\public\jssaclimport_info{1|2}.log |
8,192 kilobytes |
Trace file for multi-processing |
|
Public log of the command to count Items |
IM-SS-path\log\public\jssitemcount_info{1|2}.log |
8,192 kilobytes |
Trace file for multi-processing |
|
Public log of the command to set up view permission settings for individual Items |
IM-SS-path\log\public\jssrefaclsetup_info{1|2}.log |
8,192 kilobytes |
Trace file for multi-processing |
|
Public log of the command to store Items |
IM-SS-path\log\public\jssitemstore_info{1|2|3|4|5|6|7|8}.log |
8,192 kilobytes |
Trace file for multi-processing |
|
Public log of the command to expand an Item storage database |
IM-SS-path\log\public\jssitemstoredbexpand_info{1|2|3|4|5}.log |
10 kilobytes |
Sequential file (SEQ2) |
|
Public log of the command to rotate Item storage databases |
IM-SS-path\log\public\jssitemstoredbrotate_info{1|2|3|4|5}.log |
8,192 kilobytes |
Trace file for multi-processing |
|
Public log of the command to set up an Item storage database |
IM-SS-path\log\public\jssitemstoredbsetup_info{1|2|3|4|5}.log |
20 kilobytes |
Sequential file (SEQ2) |
|
Public log of the command to set up an Item storage database for the cluster |
shared-folder\log\public\jssitemstoredbsetup_info{1|2|3|4|5}.log |
20 kilobytes |
Sequential file (SEQ2) |
|
Public log of the command to delete stored Items |
IM-SS-path\log\public\jssstoreitemdel_info{1|2|3|4|5}.log |
10 kilobytes |
Sequential file (SEQ2) |
The log file format is information that is required in order to use the JP1/Base log file trap function. For details about this function, see the Job Management Partner 1/Base User's Guide.