jbs_log.sh (UNIX only)

Organization of this page

Function
Format
Required execution permission
Command directory
Arguments
Notes
Return values

Function

The jbs_log.sh command is a tool for collecting data if an error occurs in JP1/Base. The command collects data such as JP1/Base maintenance information, system information output by the OS, and integrated trace logs.

This tool is a shell script. It cannot be customized.

This tool archives the specified directories or files in the root directory using the tar command, and then compresses the archive using the compress command (or the gzip command in Linux). The compressed files are stored in the data-directory specified in the -f option, or in the /tmp/jp1base/ directory if you did not set the -f option. The following table shows the directory organization for the compressed files.

Command directory	Collected data
`data-directory/jp1_default_base_1st/var/opt/jp1base/conf/`	Settings and definition files
`data-directory/jp1_default_base_1st/var/opt/jp1base/log/`	Log file
`data-directory/jp1_default_base_1st/var/opt/jp1base/log/sys/`	OS system information `jbs_spmd_status` command execution results
`data-directory/jp1_default_base_1st/var/opt/jp1base/sys/tmp/event/`	Event server settings
`data-directory/jp1_default_base_1st/var/opt/jp1base/sys/OPI`	Information on the operation of services
`data-directory/jp1_default_base_1st/var/opt/jp1base/plugin/conf/`	Plug-in service settings file
`data-directory/jp1_default_base_1st/var/opt/hitachi/HNTRLib2/spool/`	Integrated trace logs
`data-directory/jp1_default_base_1st/opt/jp1/hcclibcnf/`	Common definition information
`data-directory/jp1_default_base_2nd/var/opt/jp1base/Command/`	Command execution log files
`data-directory/jp1_default_base_2nd/var/opt/jp1base/sys/event/`	Event database
`data-directory/jp1_default_base_2nd/usr/tmp/jp1_ses/`	Settings file for compatibility
`data-directory/jp1_default_base_2nd/usr/lib/jp1_ses/`
`data-directory/jp1_default_base_2nd/usr/bin/jp1_ses/`
`data-directory/jp1_default_base_2nd/tmp/`
`data-directory/jp1_default_base_2nd/var/opt/jp1_ses/`
`data-directory/logical-host-name_base_1st/etc/opt/jp1base/log/`	Log files for the logical host
`data-directory/logical-host-name_base_1st/etc/opt/jp1base/conf/`	Settings and definition files for the logical host (if applicable)
`data-directory/logical-host-name_base_1st/shared-directory/event/`	Event server settings for the logical host (if applicable)
`data-directory/logical-host-name_base_1st/shared-directory/jp1base/sys/OPI`	Information on the operation of services for the logical host
`data-directory/logical-host-name_base_2nd/shared-directory/event/`	Event database for the logical host (if applicable)
`data-directory/logical-host-name_base_2nd/var/opt/jp1base/COMMAND/`	Command execution log files for the logical host (if applicable)

For details on the types of data that you can collect with this tool, see 18.3 Data that must be collected when a problem occurs.

To Page Top

Format

jbs_log.sh [-f data-directory]
           [-k]
           [-p]
           [-r]
           [-t]
           [-u]
           [-q]
           [-h logical-host-name]
           [directory-name-or-file-name...]

To Page Top

Required execution permission

Superuser permission or JP1/Base administrator permission

To Page Top

Command directory

/opt/jp1base/tools/

To Page Top

Arguments

`-f` `data-directory`

Specify the directory for storing the collected information by absolute path, without any spaces. If you include a space, the character string before the space is taken as the directory name and the characters after the space are regarded as another argument. However, you cannot specify a path that contains Japanese characters as the storage directory.

If you omit the -f option, JP1/Base creates the following files:

For a physical host:

OS other than Linux

/tmp/jp1base/jp1_default_base_1st.tar.Z

/tmp/jp1base/jp1_default_base_2nd.tar.Z

Linux

/tmp/jp1base/jp1_default_base_1st.tar.gz

/tmp/jp1base/jp1_default_base_2nd.tar.gz

For a logical host:

OS other than Linux

/tmp/jp1base/logical-host-name_base_1st.tar.Z

/tmp/jp1base/logical-host-name_base_2nd.tar.Z

Linux

/tmp/jp1base/logical-host-name_base_1st.tar.gz

/tmp/jp1base/logical-host-name_base_2nd.tar.gz

`-k`

Specify this option if you do not want to collect logs on compatibility settings file.

`-p`

Specify this option if you do not want to collect data in the event database.

`-r`

Specify this option if you do not want to collect command execution logs (ISAM).

`-t`

Specify this option if you do not want to collect data from the /etc/hosts, etc/services, or /etc/passwd files.

`-u`

Specify this option if you do not want to collect analysis information from core files.

`-q`

Specify this option if you do not want the system to wait for your response about whether a data collection process will continue.

When the -q option is omitted, a confirmation message appears and your response is waited.

`directory-name-or-file-name`

Specify this argument to collect one or more specific files or directories using the data collection tool. Specify the name(s) by full path(s). Use spaces to delimit multiple names.

`-h` `logical-host-name`

Specify the logical host if you are using JP1/Base in a cluster system. When this option is specified, the command collects information about the physical hosts and logical host. If you omit this option, the command collects information about the physical hosts only. There is no need to specify this argument unless you are running a cluster system.

You must specify the logical host name in this option if you use JP1/Base on a cluster system. You cannot use the environment variable JP1_HOSTNAME.

To Page Top

Notes

When the name of the directory used by an event server is changed to a full path name in the event server index file (index), the data collection tool does not collect data about the event server. If an error has occurred, collect the information on the directory changed by specifying the following option in the data collection tool:

jbs_log.sh user-specified-option [directory-specified-in-the-index-file]
For operation in an environment in which the core file name is changed, data cannot be collected using the data collection tool. Therefore, collect data separately during data collection.
If the output directory for the integrated trace log is changed, you cannot collect data from the changed output directory for the integrated trace log. If an error occurs, collect the data from the changed integrated trace log directory by specifying the following option:

jbs_log.sh user-specified-option [output-directory-for-the-integrated-trace-log]
In SUSE Linux Enterprise Server 12 SP2 or later, the specifications related to the core dump were changed, so the data collection tool can no longer be used to collect core dump files. For this reason, we might also ask you to collect core dump files separately. The output destination of core dump files is as follows:

/var/lib/systemd/coredump/

To Page Top

Return values

0

Normal end

8

Invalid argument
The specified logical host name does not exist.
The shared directory of the specified logical host is not mounted.
Unable to copy the file because the program has not been installed.
The user replied NO when asked whether the device file is ready.
The user replied NO when asked whether the file being output might overwrite the existing file.
Unable to read the specified additional file.
The specified additional file does not exist.
Unable to write to the output directory.
Unable to create the output directory.

To Page Top