jim_log.sh (UNIX only)

Organization of this page

Function
Format
Execution permission
Storage directory
Arguments
Notes
Return values
Example 1
Example 2
Example 3

Function

This is a tool for collecting data in the event of a failure in JP1/IM - Manager. The data collected by this tool includes maintenance information for JP1/IM - Manager and JP1/Base, system information from the OS, and integrated trace logs.

This tool is a shell script, which cannot be customized by the user.

When you execute this tool, it classifies the target directories or files used for data collection into primary and secondary data categories, uses the tar command to archive the data directly under the specified data storage directory, and then uses the compress command to create compressed files.

The primary data is collected for such purposes as identifying a failure and investigating the causes of minor failures. It consists of the minimum amount of logs and settings files. The secondary data provides the detailed information needed for an in-depth investigation of a failure. It consists of such data as core analysis information and data from the JP1/Base event database.

If you execute the jim_log.sh command while a core dump and a thread dump of JP1/IM - Manager (Central Console) are available, the tool displays the KAVB8941-I and KAVB8942-I messages asking whether you want to delete the core dump or the thread dump. If you enter y or yes, the tool deletes the core dump or thread dump.

For details about the data that can be collected by this tool, see 11.3 Data that needs to be collected when a problem occurs in the JP1/Integrated Management 2 - Manager Administration Guide.

The following table lists and describes the compressed files containing the collected data.

Table 1‒43: Compressed files containing the collected data
File name	Description
`jp1_default_imm_1st.tar.Z`	Primary data for the physical host
`jp1_default_imm_2nd.tar.Z`	Secondary data for the physical host
`logical-host-name_imm_1st.tar.Z`^#	Primary data for the logical host
`logical-host-name_imm_2nd.tar.Z`^#	Secondary data for the logical host

#: Created only when a logical host was specified in the -h option.

The compressed files are stored in the data storage directory. The following tables show the organization of the internal directories for the compressed files.

Table 1‒44: Organization of the internal directories for the primary data of the physical host
Directory and file name	Stored data
`./etc/opt/jp1base`	Automated startup and stop scripts for JP1/Base
`./etc/opt/jp1base/conf`	JP1/Base settings and definition files
`./etc/opt/jp1base/default`	Common definition information for JP1/Base
`./etc/opt/jp1cons`	Automated startup and stop scripts for JP1/IM - Manager (Central Console)
`./etc/opt/jp1cons/conf`	JP1/IM - Manager (Central Console) settings and definition files
`./etc/opt/jp1cons/default`	Common definition information for JP1/IM - Manager (Central Console)
`./etc/opt/jp1imm/conf/tools`	JP1/IM - Manager settings and definition files
`./etc/opt/jp1imm/conf/imcf`	IM Configuration Management settings and definition files
`./etc/opt/jp1imm/conf/imdb`	IM database settings and definition files
`./etc/opt/jp1imm/conf/imdd`	Settings and definition files for JP1/IM - Manager (Intelligent Integrated Management Base)
`./etc/opt/jp1imm/plugin`	Plug - in for JP1/IM - Manager (Intelligent Integrated Management Base)
`./etc/opt/jp1imm/default/imcf`	Common definition information for IM Configuration Management
`./etc/opt/jp1scope/conf`	JP1/IM - Manager (Central Scope) settings and definition files
`./etc/opt/jp1scope/default`	Common definition information for JP1/IM - Manager (Central Scope)
`./opt/jp1/hcclibcnf`	Common definition information
`./opt/jp1base`	Patch application history and patch log information for JP1/Base
`./opt/jp1base/conf`	Settings file for JP1/Base plug-in services
`./opt/jp1imm`	Patch application history and patch log information for JP1/IM - Manager
`./var/opt/jp1base/log`	Log files for JP1/Base
`./var/opt/jp1base/sys/tmp`	Logs and temporary files for JP1/Base
`./var/opt/hitachi/HNTRLib2/spool`	Integrated trace logs
`./var/opt/jp1cons/log`	Log files for JP1/IM - Manager (Central Console)
`./var/opt/jp1imm/database/imdb`	Detailed log information for the IM database
`./var/opt/jp1imm/log/imcf`	Log files for IM Configuration Management
`./var/opt/jp1imm/log/imdb`	Log files for the IM database
`./var/opt/jp1imm/log/imdd`	Log files for JP1/IM - Manager (Intelligent Integrated Management Base)
`./var/opt/jp1imm/log/_jp1_default/oslog`	OS log information
`./var/opt/jp1imm/log/_jp1_default/operationlog`	JP1/IM - Manager operation log
`./var/opt/jp1scope/log`	Log files for JP1/IM - Manager (Central Scope)

Table 1‒45: Organization of the internal directories for the secondary data of the physical host
Directory and file name	Stored data
`./var/opt/jp1base/log/COMMAND`	Command execution log files for JP1/Base
`./var/opt/jp1base/sys/event/servers/default`	Event database for JP1/Base
`./var/opt/jp1cons/operation/comexclude`	Common exclusion history file and common exclusion-conditions definition history file for JP1/IM - Manager (Central Console)
`./var/opt/jp1cons/operation/evgen`	Correlation event generation history files for JP1/IM - Manager (Central Console)
`./var/opt/jp1imm/log/_jp1_default/oslog`	OS log information
`./var/opt/jp1imm/log/_jp1_default/core`	Core file
`./var/opt/jp1scope/database`	Database information for JP1/IM - Manager (Central Scope)
`./var/opt/jp1imm/data/imcf`	Data files for IM Configuration Management
`./var/opt/jp1imm/database/imdb/imdbbackup.dat`	Backup files of the IM database
`./var/opt/jp1imm/data/imdd`	Data files for JP1/IM - Manager (Intelligent Integrated Management Base)
`./tmp/.JP1_SES` `./usr/tmp/jp1_ses` `./usr/lib/jp1_ses/log` `./usr/lib/jp1_ses/sys` `./usr/bin/jp1_ses/jp` `./var/opt/jp1_ses`	Log for JP1/SES compatibility

Table 1‒46: Organization of the internal directories for the primary data of the logical host
Directory and file name	Stored data
`./shared-disk/jp1base/../event`	Event server settings for the logical host of JP1/Base
`./shared-disk/jp1base/conf`	Logical host settings and definition files for JP1/Base
`./shared-disk/jp1base/log`	Log files for the logical host of JP1/Base
`./shared-disk/jp1cons/conf`	Logical host settings and definition files for JP1/IM - Manager (Central Console)
`./shared-disk/jp1cons/log`	Log files for the logical host of JP1/IM - Manager (Central Console)
`./shared-disk/jp1scope/conf`	Logical host settings and definition files for JP1/IM - Manager (Central Scope)
`./shared-disk/jp1scope/log`	Log files for the logical host of JP1/IM - Manager (Central Scope)
`./var/opt/jp1imm/log/_logical-host-name/oslog`	OS log information
`./var/opt/jp1imm/log/_logical-host-name/operationlog`	JP1/IM - Manager operation log
`./shared-disk/jp1imm/conf/imcf`	IM Configuration Management settings and definition files
`./shared-disk/jp1imm/conf/imdd`	Settings and definition files for JP1/IM - Manager (Intelligent Integrated Management Base)
`./var/opt/jp1imm/database/imdb`	Detailed log information for the IM database
`./shared-disk/jp1imm/log/imcf`	Log files for IM Configuration Management
`./shared-disk/jp1imm/log/imdd`	Log files for JP1/IM - Manager (Intelligent Integrated Management Base)
`./var/opt/jp1imm/log/imdb`	Log files for the IM database

Table 1‒47: Organization of the internal directories for the secondary data of the logical host
Directory and file name	Stored data
`./shared-disk/event`	Event database for the logical host of JP1/Base
`./shared-disk/jp1base/log/COMMAND`	Command execution log files for the logical host of JP1/Base
`./shared-disk/jp1cons/operation/evgen`	Correlation event generation history files for the logical host of JP1/IM - Manager (Central Console)
`./shared-disk/jp1cons/operation/comexclude`	Common exclusion history file and common exclusion-conditions definition history file for the logical host of JP1/IM - Manager (Central Console)
`./shared-disk/jp1scope/database`	Database information for the logical host of JP1/IM - Manager (Central Scope)
`./var/opt/jp1imm/log/_logical-host-name/oslog`	OS log information
`./var/opt/jp1imm/log/_logical-host-name/core`	Core file
`./shared-disk/jp1imm/data/imcf`	Data files for IM Configuration Management
`./shared-disk/jp1imm/database/imdb/imdbbackup.dat`	Backup files of the IM database
`./shared-disk/jp1imm/data/imdd`	Data files for JP1/IM - Manager (Intelligent Integrated Management Base)

To Page Top

Format

jim_log.sh -f data-storage-directory
           [-h logical-host-name]
           [-t]
           [-u]
           [-n]
           [-p]
           [-r]
           [-g]
           [-a]
           [-s]
           [-c]
           [-d]
           [-x]
           [-q]
           [-b]
           [directory-name-or-file-name...]

The -a option is used for linking with BJEX or JP1/AS. For details about the -a option, see 10.5.3 jim_log.sh (UNIX only)in the JP1/Integrated Management 2 - Manager Administration Guide.

To Page Top

Execution permission

Superuser permissions

To Page Top

Storage directory

/opt/jp1imm/tools/

To Page Top

Arguments

-f data-storage-directory

Specifies the name of the directory or device to which the collected data is to be output, expressed as a full path or a path relative to the root directory. If you specify a directory name, the tool creates the files containing the collected data under that directory. If the path contains a space, enclose the entire path in double-quotation marks ("). This option is mandatory.

If a nonexistent directory is specified, a new directory with the specified name is created. If an existing directory is specified, that directory is deleted and the specified directory is created.

If a device name is specified, a write operation occurs on that device for each file that is created. If a device file name such as for a tape device is specified, the collected data is stored on the device without being compressed.

If you specify a device name and the -q option, the tool assumes that you have chosen yes for user confirmation. In such a case, you must set the device before you execute the command.

-h logical-host-name

When you are operating in a cluster system, this option specifies a logical host name and that the command is to collect data for that logical host as well as for the physical host. If this option is omitted, the command collects data for the physical host only. If you are not using a cluster system, there is no need to specify this option.

Note that this command will not use the logical host name that is set in the JP1_HOSTNAME environment variable. Therefore, if you use this command in a cluster system, make sure that you specify the logical host name in this option.

-t

Specifies that the hosts, services, and passwd files are not to be collected.

-u

Specifies that core analysis information is not to be collected. The core analysis information consists of a file obtained by using the car command of the Seraph tool to analyze a core dump file.

-n

Specifies that maintenance data for JP1/Base is not to be collected.

-p

Specifies that the event database for JP1/Base is not to be collected.

-r

Specifies that the command execution log files for JP1/Base are not to be collected.

-g

Specifies that the correlation event generation history file is not to be collected.

-a

Specifies that the file for accumulated response-waiting events is not to be collected.

-s

Specifies that maintenance data for JP1/IM - Manager (Central Scope) is not to be collected.

-c

Specifies that maintenance data for IM Configuration Management is not to be collected.

-d

Specifies that maintenance data for the IM database is not to be collected.

This argument cannot be specified together with the -x option.

-x

Specifies that IM database backup files are to be collected.

This argument cannot be specified together with the -d option.

The IM database backup files are not included in the maintenance data for the IM database that is collected by default. If the IM database service is not running, the maintenance data is not collected. In such a case, start the IM database service and then re-execute the data collection command. The backup files can be collected even when JP1/IM - Manager is running.

-q

Specifies that the command is to be executed without requesting confirmation from the user.

-b

Specifies that maintenance data for Intelligent Integrated Management Base is not to be collected.

directory-name-or-file-name

Specifies a file or directory to be collected by the data collection tool. Specify a full path name. To specify multiple names, use the space character to separate the names.

Note that this option must be the last option specified in the command. Specify it after you have specified all the other options that you need to specify. The collected data is stored as the primary data for the physical host.

To Page Top

Notes

This tool might collect a large amount of data. Before you execute this tool, you need to estimate the amount of disk space required and check the capacity available on your machine. For details, see 11.4 Collecting data in the JP1/Integrated Management 2 - Manager Administration Guide.
Do not execute this tool more than once. If it is executed multiple times, previously collected data might be overwritten or data collection might fail.
When you run the tool to collect the data, it places a certain amount of load on the computer (on disk I/O and other resources).
If you send data to the support service without using this tool or send it with some of it excluded, detailed investigation may not be possible.

To Page Top

Return values

`0`	Normal termination
`8`	Abnormal termination

To Page Top

Example 1

Collect data for the physical host and the logical host hostA into /tmp/jp1log:

jim_log.sh -f /tmp/jp1log -h hostA

The output result is as follows:

KAVB8925-I The directory does not exist. (/var/opt/jp1imm/log/_jp1_default).
           The directory will be created.
KAVB8925-I The directory does not exist. (/var/opt/jp1imm/log/_hostA).
           The directory will be created.
KAVB8926-I Data acquisition processing will start.
KAVB8921-I The physical host's first material will be acquired.
KAVB8922-I The physical host's first material has been acquired.
KAVB8921-I The physical host's second material will be acquired.
KAVB8922-I The physical host's second material has been acquired.
KAVB8921-I The logical host(hostA)'s first material will be acquired.
KAVB8922-I The logical host(hostA)'s first material has been acquired.
KAVB8921-I The logical host(hostA)'s second material will be acquired.
KAVB8922-I The logical host(hostA)'s second material has been acquired.
KAVB8918-I The data was successfully acquired.

To Page Top

Example 2

Collect data for the physical host into the nonexistent directory /tmp/jp1log/, but do not specify the existing logical host (hostA):

jim_log.sh -f /tmp/jp1log

The output result is as follows:

KAVB8925-I The directory does not exist. (/tmp/jp1log).
           The directory will be created.
KAVB8925-I The directory does not exist. (/var/opt/jp1imm/log/_jp1_default).
           The directory will be created.
KAVB8926-I Data acquisition processing will start.
KAVB8921-I The physical host's first material will be acquired.
KAVB8922-I The physical host's first material has been acquired.
KAVB8921-I The physical host's second material will be acquired.
KAVB8922-I The physical host's second material has been acquired.
KAVB8918-I The data was successfully acquired.
KAVB8935-I The following logical host(s) exist on this machine:
hostA
To acquire information about a logical host, execute "jim_log.sh -f output-directory-name -h logical-hostname".

To Page Top

Example 3

Collect data for the physical host into the /tmp/jp1log/ directory, which contains the jp1_default_imm_1st.tar.Z and jp1_default_imm_2nd.tar files, but do not specify the existing logical host (hostA):

jim_log.sh -f /tmp/jp1log

The output result is as follows (when y is entered for all responses):

KAVB8925-I The directory does not exist. (/var/opt/jp1imm/log/_jp1_default).
           The directory will be created.
KAVB8926-I Data acquisition processing will start.
KAVB8921-I The physical host's first material will be acquired.
KAVB8922-I The physical host's first material has been acquired.
KAVB8921-I The physical host's second material will be acquired.
KAVB8944-I (/tmp/jp1log/jp1_default_imm_2nd.tar.Z) already exists. Do you want to overwrite it? [yes/no]y
KAVB8922-I The physical host's second material has been acquired.
KAVB8918-I The data was successfully acquired.
KAVB8944-I (/tmp/jp1log/jp1_default_imm_1st.tar.Z) already exists. Do you want to overwrite it? [yes/no]y
KAVB8935-I The following logical host(s) exist on this machine:
hostA
To acquire information about a logical host, execute "jim_log.sh -f output-directory-name -h logical-hostname".

To Page Top