jajs_log or _04 (UNIX only)

Organization of this page

Format
Description
Execution privileges
Storage directory
Arguments
Notes
Return values
Messages
Example 1
Example 2
Example 3
Data that can be collected

Format

jajs_log | _04
     [-h logical-host-name]
     [-f storage-directory]
     [-s]
     [-t]
     [-u]
     [-e]
     [-b]
     [additional-file]

To Page Top

Description

The data collection tool obtains maintenance information, such as the JP1/AJS3 definitions, operating information, and information about the OS.

_04 is the data collection tool for JP1/AJS3 10-10 or earlier. For JP1/AJS3 10-50 or later, you can also use jajs_log as the data collection tool.

Both data collection tools have the same basic functionality. Use either tool depending on the purpose of use and whether customization is required.

The following table describes the purpose of jajs_log and _04, and whether they can be customized.

Table 2‒22: Purpose of data collection tools and whether they can be customized
Data collection tool	Purpose	Customization
`jajs_log`	Use this tool if the log output destinations have not been changed from the defaults, or if you need to collect data by default only.	N
`_04`	Customize this tool before using it if you have changed log output destinations from the defaults, or if you need to collect data other than the default data.^#	Y

Legend:

Y: The tool can be customized.

N: The tool cannot be customized.

#

For details about the customization method, see 16.1.1 Setting up the data collection tools in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.

By default, the results of executing the data collection tool are output to the following files under /tmp/jp1ajs2/trouble/.

For physical hosts:

JP1_DEFAULT_1st.tar.Z

The data for the first reports is output.
JP1_DEFAULT_2nd.tar.Z

The data for the second reports is output.
JP1_DEFAULT_3rd.tar.Z

All the other data is output.

For logical hosts:

logical-host-name_1st.tar.Z

The data for the first reports is output.
logical-host-name_2nd.tar.Z

The data for the second reports is output.
logical-host-name_3rd.tar.Z

All the other data is output.

To Page Top

Execution privileges

Superuser privilege

To Page Top

Storage directory

For jajs_log: /opt/jp1ajs2/tools
For _04: /opt/jp1ajs2/lib/sample_script

To Page Top

Arguments

`-h` `logical-host-name`

Specify the name of the target logical host.

The data collection tool collects the data on the physical host in addition to the data on the specified logical host.

If you do not specify a name, the data collection tool obtains the physical host logs.

`-f` `storage-directory`

Use a full path without space characters to specify the directory used to store the collected information. If the specified directory name contains a space character, the system assumes that the character string before the space is the storage directory name and treats the characters after the space as other arguments.

When you use a relative path to specify a storage directory, the specified path is created under the root directory and the collected data is stored there.

If you specify a directory that does not exist, a new directory with that name is created. If data has already been collected in the specified storage directory, a message asking whether you want to overwrite the data appears.

If you omit this option, the collected data is output to /tmp/jp1ajs2/trouble/.

`-s`

Specify this option if you do not want to collect information about the database used by JP1/AJS3.

If you do not specify this option, the data collection tool collects information about the database.

`-t`

Specify this option if you do not want to obtain the hosts, services, and passwd files.

`-u`

Specify this option if you do not want to obtain the core file.

Although you specify this option, the back trace information is collected.

`-e`

Specify this option if you do not want to collect detailed information about the embedded database.

The detailed information about the embedded database is the data for the second report, which is output to the embdbinfo directory.

If you do not specify this option, the data collection tool collects detailed information about the embedded database.

When this option is not specified, it is automatically determined whether to collect the information. Therefore, do not specify this option if you are unsure about whether detailed information about the embedded database needs to be collected.

Specify this option only when you want to suppress the collection of detailed information about the embedded database.

`-b`

Specify this option if you do not want to collect detailed information about JP1/Base.

The detailed information about JP1/Base is the data for the second report, which is output to the JP1BASE_INFO directory.

If you do not specify this option, the data collection tool collects detailed information about JP1/Base.

Specify this option only when you want to suppress the collection of detailed information about JP1/Base.

If free disk space at the output destination is insufficient, execute the data collection tool with the -b option specified, and then execute the data collection tool for JP1/Base (jbs_log) to collect detailed information about JP1/Base. For details about the data collection tool for JP1/Base (jbs_log), see the Job Management Partner 1/Base User's Guide.

`additional-file`

Use a full path without space characters to specify a file that is not usually obtained by using the data collection tool, such as the core file of the JP1/AJS3 commands. If the specified file name contains a space character, the system assumes that the character string before the space is an additional file name and treats the characters after the space as other arguments.

Using this argument, you can collect information that is not automatically collected by the data collection tool.

If the core file is specified as an additional file, the core file is collected even if you specify the -u option.

You can specify a directory name for additional-file. If you specify a directory, all the data in the specified directory is collected.

To Page Top

Notes

If you collect data about a logical host in a cluster system, you must mount the shared disk for the logical host.
The data collection tool compresses the collected data as follows for each OS.

In Linux:

The data collection tool uses the gzip command to compress the data. If the gzip command is not installed in the environment in which the data collection tool is executed, the data collection tool uses the tar command to compress and output the data; it does not use the compress command. If the tar command is not installed, the data collection tool terminates abnormally, and processing ends.

In UNIX other than Linux:

The data collection tool uses the compress command to compress the data. If the compress command is not installed in the environment in which the data collection tool is executed, the tool uses the gzip command instead. If neither the compress command nor the gzip command is available, the data collection tool uses the tar command to archive and output the data. If the tar command is not installed, the data collection tool terminates abnormally, and processing ends.
Because the user might not have reference permission for a file contained in the script, the superuser must execute the script.
If you have already created a file containing the results of executing the script, JP1/AJS3 outputs a message asking for permission to overwrite the file. Enter y to overwrite the file. If you do not want to overwrite the file, enter n.
If no core dump file is output, a message (Status of tar: core? is unknown. The file is not dumped.) appears. This is not a problem.
If the target product is not installed or is being used by another process, or a file that cannot be accessed because of its file attribute is detected, a message reporting that there is no applicable directory or file or that the target file cannot be accessed might appear during the collection of data. This is not a problem.
Because the ajs2collectcore command is executed internally while the data collection tool is being executed, some data cannot be collected, depending on the OS.For details, see ajs2collectcore (UNIX only) in 2. Commands.
If there is no data to be collected, a file containing the execution result of the data collection tool is not created.
Do not execute more than one data collection tool at the same time. Do not execute jajs_log and _04 at the same time.
The data collection tool executed by an AJS administrator cannot collect information that requires superuser privileges. We recommend that a user with superuser privileges executes the data collection tool.

To execute the data collection tool, the following operations must be performed:
- The output destination file must be deleted before the data collection tool is executed.
- The JP1 administrator group must be granted write permissions for the output destination directory.
- The JP1 administrator group must be granted access permissions for the root directory.
- To add the additionally collected data, the JP1 administrator group must be granted access permissions.
When you specify options, do not specify characters or symbols that have special meanings in the script. If you specify such characters and symbols, an unexpected error might occur.

To Page Top

Return values

0	Normal end
Value other than 0	Abnormal end

To Page Top

Messages

Message	Description	System action
`Directory` `directory-name` `is created`	A directory is created.	Continues processing.
`Some data could not be collected by AJS Administrator.`	Some data could not be collected because an AJS administrator executed the data collection tool.	Continues processing.
`Overwrite file (file-name) ok?`	This message asks you whether you want to overwrite `file-name`. Press `y` to continue the processing, or press `n` to cancel the processing.	Waits for a user response.
`[CAUTION]` `When a target program is not installed, or when file access fails because some other process is using the file or because a necessary file-access permission is lacking, a message might be output that states that file access failed or a directory or file does not exist. Such a message does not indicate a problem`.	This message is displayed when the specified file is being used or was not found during data collection. However, there is no problem.	Continues processing.
`Output file name :(file-name)`	The file indicated by `file-name` has been created.	Terminates the processing.
`Write permission error (directory-name)`	You do not have write permission. Possible reasons are as follows: You do not have permission to create a directory. The directory is being used by another process. Correct the error, and then re-execute the data collection tool.	Terminates the processing.
`Make directory (directory-name) is unsuccessful`	The directory could not be created. Possible reasons are as follows: You do not have permission to create a directory. The directory is being used by another process. Correct the error, and then re-execute the data collection tool.	Terminates the processing.
`Read permission error(file-name)`	You do not have read permission. Obtain read permission, and then re-execute the data collection tool.	Terminates the processing.
`File` `file-name` `is not found`	The directory or file specified as the additional file was not found. Specify a correct path, and then re-execute the data collection tool.	Terminates the processing.
`[ -s ] [ -f` `output-file` `] [ -h` `Logical-Host-Name` `] [ -t ] [ -u ] [ -e ] [ -b ] [` `add-in-file` `... ]`	The options are specified incorrectly. Specify the options correctly, and then re-execute the data collection tool.	Terminates the processing.
`The collection of detailed information on EmbedDB _JF*`^# `begins.`	Collection of detailed information about the embedded database has started.	Continues processing.
`The collection of detailed information on EmbedDB_JF*`^# `ended.`	Collection of detailed information about the embedded database has ended.	Continues processing.
`The collection of detailed information on JP1/Base begins.`	Collection of detailed information about JP1/Base has started.	Continues processing.
`The collection of detailed information on JP1/Base ended.`	Collection of detailed information about JP1/Base has ended.	Continues processing.

#: _JF* indicates an embedded database identifier (_JF0, _JF1, _JF2, and so on). Detailed information is collected for each identifier.

To Page Top

Example 1

The following command collects data about a physical host:

For jajs_log:

jajs_log

If you use _04 customized to trouble.sh:

trouble.sh

To Page Top

Example 2

The following command collects data about a logical host (cluster):

For jajs_log:

jajs_log -h cluster

If you use _04 customized to trouble.sh:

trouble.sh -h cluster

To Page Top

Example 3

The following command outputs information, including the core file (/tmp/core), to a specified file (/tmp/trouble):

For jajs_log:

jajs_log -f /tmp/trouble /tmp/core

If you use _04 customized to trouble.sh:

trouble.sh -f /tmp/trouble /tmp/core

To Page Top

Data that can be collected

For physical hosts:

The data for first reports (/tmp/jp1ajs2/trouble/JP1_DEFAULT_1st.tar.Z^#1)

Name of directory or file containing collected data	Description
`/etc/hosts`	`hosts` file
`/etc/passwd`	`passwd` file
`/etc/services`	`services` file
`/etc/.hitachi`	Information about installed Hitachi products
`/etc/opt/jp1ajs2/conf` `/etc/opt/jp1ajs2cm/conf` `/etc/opt/jp1base/conf`	Directories containing the environment settings files
`/opt/jp1/hcclibcnf/regdir`	Common definition
`/opt/jp1ajs2/PatchHistory` `/opt/jp1ajs2/PatchLog` `/opt/jp1ajs2v/PatchHistory` `/opt/jp1ajs2v/PatchLog`	Patch information
`/var/adm/syslog/syslog.log` (for HP-UX) `/var/adm/messages` (for Solaris) `/var/adm/syslog` (for AIX) `/var/adm/messages*` (for Linux)	`syslog` and the directories containing `syslog`
`/opt/hitachi/HNTRLib/spool` `/var/opt/hitachi/HNTRLib2/spool`	Integrated trace logs
`/var/opt/jp1ajs2/log`	Directory containing log files
`/var/opt/jp1ajs2/log/_04.filelist`	List of files
`/var/opt/jp1ajs2/log/_04.osinfo`	OS-related information
`/var/opt/jp1ajs2/log/_04.processlist`	List of processes
`/var/opt/jp1ajs2/log/_04.backtrace`	Back trace information
`/var/opt/jp1ajs2/log/ajsagtshow.txt`	Execution result of the `ajsagtshow` command
`/var/opt/jp1ajs2/log/ajsagtprint.txt`	Execution result of the `ajsagtprint` command
`/var/opt/jp1ajs2/log/jajs_status.txt`	Execution result of the `jajs_status` command
`/var/opt/jp1ajs2/log/jajsadminusr_{1\|2}.log`	Setting and reference log for AJS administrators
`/var/opt/jp1ajs2/log/ajsprof_scheduler-service-name_agent_stat.txt`^#2	Execution result of the `ajsprofstatus` (`-t agent -s` option)
`/var/opt/jp1ajs2/log/ajsprof_scheduler-service-name_agent_def.txt`^#2	Execution result of the `ajsprofstatus` (`-t agent -p` option)
`/var/opt/jp1ajs2/log/ajsprof_scheduler-service-name_unit_stat.txt`^#2	Execution result of the `ajsprofstatus` (`-t unit -s` option)
`/var/opt/jp1ajs2/log/ajsprof_scheduler-service-name_unit_def.txt`^#2	Execution result of the `ajsprofstatus` (`-t unit -p` option)
`/var/opt/jp1ajs2/log/jajs_pmtcon_m.txt`	Execution result of the `jajs_pmtcon` (`-m -v` option)
`/var/opt/jp1ajs2/log/jajs_pmtcon_a.txt`	Execution result of the `jajs_pmtcon` (`-a -v` option)
`/var/opt/jp1ajs2/sys`	Directory containing the system files
`/var/opt/jp1ajs2/tmp/schedule/pd*.trc`	Trace information related to the embedded database
`/var/opt/jp1ajs2cm/log` `/var/opt/jp1ajs2v/log` `/var/opt/jp1base/log`	Directories containing log files
`/tmp/jp1ajs2/trouble`^#1`/EMBDB/_JF*`^#3`/conf`	Embedded database definition file
`/tmp/jp1ajs2/trouble`^#1`/EMBDB/_JF*`^#3`/spool`	Embedded database failure investigation file
`/tmp/jp1ajs2/trouble`^#1`/EMBDB/_JF*`^#3`/etc`	Other information related to the embedded database that is needed for investigation

#1: Output destination when the -f option is omitted.
#2: Information about all scheduler services on the host is collected.
#3: _JF* indicates an embedded database identifier (_JF0, _JF1, _JF2, and so on). A directory is created for each identifier.

The data for second reports (/tmp/jp1ajs2/trouble/JP1_DEFAULT_2nd.tar.Z^#1)

Name of directory or file containing collected data	Description
`/tmp/jp1ajs2/trouble`^#1`/CARDIR/coreinfo-ISAM.shmdump.tar.Z`^#2 `/tmp/jp1ajs2/trouble`^#1`/CARDIR/coreinfo-Scheduler.shmdump.tar.Z`^#2 `/tmp/jp1ajs2/trouble`^#1`/CARDIR/../../core.Z`^#2 `/tmp/jp1ajs2/trouble`^#1`/CARDIR/../../coreinfo-analyze.tar.Z`^#2 `/tmp/jp1ajs2/trouble`^#1`/CARDIR/ProgMon.shmdump` `/tmp/jp1ajs2/trouble`^#1`/CARDIR/coreinfo-host.shmdump` `/tmp/jp1ajs2/trouble`^#1`/CARDIR/coreinfo-hostprof.shmdump` `/tmp/jp1ajs2/trouble`^#1`/CARDIR/coreinfo-pmtcon_m.shmdump` `/tmp/jp1ajs2/trouble`^#1`/CARDIR/coreinfo-pmtcon_a.shmdump`	Shared memory information used by ISAM and the scheduler, core dump files, shared library information, operation profile information, and information about the shared memory for the connection source restriction function
`/var/opt/jp1ajs2/database` `/var/opt/jp1ajs2cm/database` `/tmp/jp1ajs2/trouble`^#1`/embdatabase/_JF*`^#3	Database storage directories
`/tmp/jp1ajs2/trouble`^#1`/embdbinfo/_JF*`^#3	Detailed information about the embedded database
`/tmp/jp1ajs2/trouble`^#1`/JP1BASE_INFO`^#5	Detailed information about JP1/Base
`/additionally-collected-data`^#4	Additionally collected data

#1: Output destination when the -f option is omitted.
#2: This file is output to the directory containing the core dump file that has been obtained.
#3: _JF* indicates an embedded database identifier (_JF0, _JF1, _JF2, and so on). A directory is created for each identifier.
#4: This file is created when additional-file is specified as the argument.
#5: The detailed information about JP1/Base is created as data for the second physical hosts report, regardless of the data for physical hosts or logical hosts.

The data for third reports (/tmp/jp1ajs2/trouble/JP1_DEFAULT_3rd.tar.Z^#)

Name of directory or file containing collected data	Description
`/var/opt/jp1ajs2/jobinf`	Directory containing information about jobs

#: Output destination when the -f option is omitted

For logical hosts:

The data for first reports (/tmp/jp1ajs2/trouble/logical-host-name_1st.tar.Z^#1)

Name of directory or file containing collected data	Description
`/shared-directory-name/jp1ajs2/backup`	Directory containing backup files
`/shared-directory-name/jp1ajs2/conf`	Directory containing environment settings files
`/shared-directory-name/jp1ajs2/log`	Directory containing log files
`/shared-directory-name/jp1ajs2/sys`	Directory containing the system files
`/shared-directory-name/jp1ajs2/tmp`	Directory containing work files
`/shared-directory-name/jp1base/conf`	Directory containing the environment settings files
`/shared-directory-name/jp1base/log`	Directory containing log files
`/shared-directory-name/jp1ajs2/log/ajsagtshow.txt`	Execution result of the `ajsagtshow` command
`/shared-directory-name/jp1ajs2/log/ajsagtprint.txt`	Execution result of the `ajsagtprint` command
`/shared-directory-name/jp1ajs2/log/jajs_status.txt`	Execution result of the `jajs_status` command
`/shared-directory-name/jp1ajs2/log/ajsprof_scheduler-service-name_agent_stat.txt`^#2	Execution result of the `ajsprofstatus` command (`-t agent -s` option)
`/shared-directory-name/jp1ajs2/log/ajsprof_scheduler-service-name_agent_def.txt`^#2	Execution result of the `ajsprofstatus` command (`-t agent -p` option)
`/shared-directory-name/jp1ajs2/log/ajsprof_scheduler-service-name_unit_stat.txt`^#2	Execution result of the `ajsprofstatus` command (`-t unit -s` option)
`/shared-directory-name/jp1ajs2/log/ajsprof_scheduler-service-name_unit_def.txt`^#2	Execution result of the `ajsprofstatus` command (`-t unit -p` option)
`/shared-directory-name/jp1ajs2/log/jajs_pmtcon_m.txt`	Execution result of the `jajs_pmtcon` (`-m -v` option)
`/shared-directory-name/jp1ajs2/log/jajs_pmtcon_a.txt`	Execution result of the `jajs_pmtcon` (`-a -v` option)
`/tmp/jp1ajs2/trouble`^#1`/EMBDB_logical-host-name/_JF*`^#3`/conf`	Embedded database definition file
`/tmp/jp1ajs2/trouble`^#1`/EMBDB_logical-host-name/_JF*`^#3`/spool`	Embedded database failure investigation file
`/tmp/jp1ajs2/trouble`^#1`/EMBDB_logical-host-name/_JF*`^#3`/etc`	Other information related to the embedded database that is needed for investigation

#1: Output destination when the -f option is omitted.
#2: Information about all scheduler services on the host is collected.
#3: _JF* indicates an embedded database identifier (_JF0, _JF1, _JF2, and so on). A directory is created for each identifier.

The data for second reports (/tmp/jp1ajs2/trouble/logical-host-name_2nd.tar.Z^#1)

Name of directory or file containing collected data	Description
`/tmp/jp1ajs2/trouble`^#1`/CARDIR_logical-host-name/ProgMon.shmdump` `/tmp/jp1ajs2/trouble`^#1`/CARDIR_logical-host-name/coreinfo-host.shmdump`	Shared memory dumps
`/shared-directory-name/jp1ajs2/database` `/shared-directory-name/jp1ajs2cm/database` `/tmp/jp1ajs2/trouble#1/embdatabase_logical-host-name/_JF*`^#2	Database storage directories
`/tmp/jp1ajs2/trouble`^#1`/embdbinfo_logical-host-name/_JF*`^#2	Detailed information about embedded database

#1: Output destination when the -f option is omitted.
#2: _JF* indicates an embedded database identifier (_JF0, _JF1, _JF2, and so on). A directory is created for each identifier.

The data for third reports (/tmp/jp1ajs2/trouble/logical-host-name_3rd.tar.Z^#)

Name of directory or file containing collected data	Description
`/shared-directory-name/jp1ajs2/jobinf`	Directory containing information about jobs

#: Output destination when the -f option is omitted

To Page Top