Job Management Partner 1/Automatic Job Management System 3 Command Reference 1

ajs2collectcore (UNIX only)

Format

ajs2collectcore
     [-b]
     [-c]
     [-f output-path-name]
     [-l]
     [-s]
     [core-dump-directory-or-core-dump-file...]

Description

Searches for core dump files (names beginning with core, core-, or core.) placed under the following directories and collects analysis information from those core dump files, if any.

/opt/jp1ajs2/

/var/opt/jp1ajs2/

/opt/jp1ajs2cm/

/opt/jp1ajs2v/

/opt/jp1base/bin/

/var/opt/jp1base/log/

/tmp/jp1ajs2/ajs2gencore_create/

The following table describes the information you can collect with the ajs2collectcore command.

Table 2-1 Information that can be collected with the ajs2collectcore command

Information category Description Output file name^#1

Core dump Obtains a core dump file (core). core.Z

Backtrace information Outputs primary analysis information about the core dump. coreinfo.backtrace.Z^#2

Shared memory information Outputs the content of shared memory used by ISAM and the scheduler service. coreinfo-ISAM.shmdump.tar.Z
coreinfo-scheduler.shmdump.Z

Shared library information Obtains information about existing shared libraries, excluding the following:

/opt/jp1ajs2/lib/

/opt/jp1ajs2v/lib/

/opt/jp1ajs2cm/lib/

/opt/jp1base/lib/

coreinfo-analyze.tar.Z^#2

#1

Use ajs2collectcore to compress the collected data.

JP1/AJS3 uses the compress command to compress data. The file extension is .Z. If compress is not installed, and the gzip command is installed, JP1/AJS3 uses the gzip command to compress data instead of the compress command. In this case, the extension of the output file name is .gz. If neither the compress command nor the gzip command is installed, no data is compressed. In this case, neither extension .Z nor .gz is added to the output file name.

#2

There will be as many outputs as there are core dumps.

The collected files are output, as shown in the following example, under the output-destination directory (the default is /tmp/jp1ajs2/core_analyze/).
Example

In the following example, the command is executed when there are core dump files under /opt/jp1ajs2/bin/ (the output destination is the default):
 
/tmp/jp1ajs2/core_analyze/opt/jp1ajs2/bin/
 
The file list for the information collected is output at the same time. The file list is output immediately under the output-destination directory. The file name is shown below:

Ajs2collectcore_filelist.log

Information category	Description	Output file name^#1
Core dump	Obtains a core dump file (core).	core.Z
Backtrace information	Outputs primary analysis information about the core dump.	coreinfo.backtrace.Z^#2
Shared memory information	Outputs the content of shared memory used by ISAM and the scheduler service.	coreinfo-ISAM.shmdump.tar.Z coreinfo-scheduler.shmdump.Z
Shared library information	Obtains information about existing shared libraries, excluding the following: /opt/jp1ajs2/lib/ /opt/jp1ajs2v/lib/ /opt/jp1ajs2cm/lib/ /opt/jp1base/lib/	coreinfo-analyze.tar.Z^#2

Execution privileges

Superuser privileges

Storage directory

/opt/jp1ajs2/tools/

Arguments

-b

Collects only the backtrace information in the core dump file to be collected.

Specifying this option together with the -c, -l, or -s option enables you to collect non-backtrace information as well. If you specify the -c, -l, or -s option but omit this option, backtrace information is not collected.

-c

Collects only the core dump file.

Specifying this option together with the -b, -l, or -s option enables you to collect non-backtrace information as well. If you specify the -b, -l, or -s option but omit this option, backtrace information is not collected.

-f output-path-name

Specify where to store the core dump information to be collected. Use an absolute path that does not contain space characters. Specifying the name with a relative path causes the command to terminate abnormally due to an argument error. If the specified path name contains a space character, the string before the space character is handled as the output path name and the string after the space character is regarded as another argument.

If you specify this option, core dump information is stored under the output path. If the specified output path does not exist, a message asking you whether to create the directory is output. To create the directory, enter y. If you enter n, the command does not collect the information.

If you omit this option, the default is /tmp/jp1ajs2/core_analyze.

-l

Collects only shared library information that excludes the target library supplied by JP1/AJS3.

Specifying this option together with the -b, -c, or -s option enables you to collect non-shared-library information as well. If you specify the -b, -c, or -s option but omit this option, the shared library information is not collected.

-s

Collects only the shared memory information to be collected.

At this time, if coreinfo-ISAM.shmdump_* or coreinfo-Scheduler.shmdump_* exists immediately under the destination directory path, back up the file, adding the extension .bk.

Specifying this option together with the -b, -c, or -l option enables you to collect non-shared-memory information as well. If you specify the -b, -c, or -l option but omit this option, the shared memory information is not collected.

core-dump-directory-or-core-dump-file

Other than for a search path for core dumps to be searched for in a standard configuration (see the Description section), specify the core-dump directory path or file name you want to additionally search for by using an absolute path that does not contain space characters. Specifying the name with a relative path causes the command to terminate abnormally due to an argument error. If the specified path name contains a space character, the string before the space character is handled as an output path name and the string after the space character is regarded as another argument.

If the search path contains core dump files (names beginning with core, core-, or core.), the command obtains the backtrace information and shared library information.

If you do not specify the core-dump directory or core dump file, the target of search is core dumps under the following directory paths.

/opt/jp1ajs2/ directory path

/var/opt/jp1ajs2/ directory path

/opt/jp1ajs2cm/ directory path

/var/jp1ajs2cm/ directory path

/opt/jp1ajs2v/ directory path

/opt/jp1base/bin/ directory path

/tmp/jp1ajs2/ajs2gencore_create/ directory path

Notes

When you execute this command, if a file having the same name exists in the output path, an overwrite message appears. Entering y in response enables the overwrite; entering n cancels the process of collecting information.

When you execute this command, if the output path specified by the -f option does not exist, a message appears asking you to confirm creation of the directory. Entering y in response enables creation of the directory; entering n cancels the process of collecting information.

If there are two or more core dump files, information about all the files is collected.

If you use these arguments to specify a core-dump directory or core dump file, execute the command after confirming that the files being placed at the destination and beginning with core, core-, or core. are limited to core dump files.

Specifying the -f option enables you to start two or more instances of this command simultaneously if you specify individual directories for output destination.

When you collect ISAM shared memory information, you may fail to output it in a coreinfo-ISAM.shmdump.tar file because of the capacity shortage in the output destination directory. If this occurs, check to see if there are coreinfo-ISAM.shmdump_* files without the .bk extension. If you find such files, which serve as ISAM shared memory information, execute the tar command in a different disk area and then send the information as data.

If the system updates the very file that is executed in the target process after core-dump files are discharged, note that you will fail to properly collect analysis information from these core-dump files.

To collect backtrace information, the ajs2collectcore command uses the module name that is output from the file command. This means that you cannot collect backtrace information from core dumps for which the module name is not displayed by the file command.

Return values

0 All data items have been collected successfully.

4 Some of the data items have been collected successfully.

Other values The process has terminated abnormally.

Output messages

Return value Output message Meaning Operation Action

0 Collection of the backtrace data [ file-name ] was successful.
OutputPath:
output-path-name Normal collection (backtrace) Normal termination or continued processing to obtain next information (Not applicable)

0 Collection of the core dump file [ file-name ] was successful.
OutputPath:
output-path-name Normal collection (core-dump files) Normal termination or continued processing to obtain next information (Not applicable)

0 Collection of the shared library data [ file-name ] was successful.
OutputPath:
output-path-name Normal collection (library information) Normal termination or continued processing to obtain next information (Not applicable)

0 Collection of the {ISAM | Scheduler} shared memory dump was successful.
Output Path:
output-path-name Normal collection (shared memory information) Normal termination or continued processing to obtain next information (Not applicable)

4 or 8 Error!!The input parameter [ argument ] is invalid.
<< ### Usage ### >>
ajs2collectcore [ -b ] [ -c ] [ -l ] [ -s ] [ -f output_fullpath ] [ additional_search_fullpath ... ] Parameter error Abnormal termination or continued processing (if there is an error in the additionally specified path) Check the required parameters and re-execute the command.

16 Error!!
The specified directory [ destination-directory ] could not be created. Failure to create a destination directory Abnormal termination The destination disk might have reached its full capacity.
Check the capacity of the destination disk. After taking steps to remedy the problem, re-execute the command.

4 or 8 Error!!
The specified file [ file-name ] does not have overwrite permissions. Failure to overwrite an existing file Continued processing (Continuing to collect something other than the target file) Assign write privileges to the target file and re-execute the command.

4 or 8 Error!!
The backtrace data for the core dump file could not be collected.
Corefile:
corresponding-core-dump-file-name Failure to collect backtrace information Continued processing (Continuing to collect something other than the target backtrace information) The destination disk might have reached its full capacity.
Check the capacity of the destination disk. After taking steps to remedy the problem, re-execute the command.

4 or 8 Error!!
The core dump file could not be collected.
Corefile:
corresponding-core-dump-file-name Failure to collect core-dump files Continued processing (Continuing to collect something other than the target core-dump file)

4 or 8 Error!!
Shared library data for the core dump file could not be collected.
Corefile:
corresponding-core-dump-file-name Failure to collect shared library information Continued processing (Continuing to collect something other than the target shared library information)

4 or 8 Error!!
{ISAM | Scheduler} shared memory data could not be collected. Failure to collect shared memory information Continued processing (Continuing to collect something other than the target shared memory information) The following are possible errors:

Memory is running short.

The destination disk has reached its capacity.

Check the state of memory use and the capacity of the destination disk. After taking steps to remedy the problem, re-execute the command.

4, 8, or 124 An error occurred!!
ErrorCause: [ error-factor ]
ErrorInfo: [ error-information ] Other error Continued processing (Continuing to collect something other than the target information) (Not applicable)

(Not applicable) There are no core dump files in default directories. No core dumps found in a standard search path (Not applicable) (Not applicable)

(Not applicable) There are no core dump files in the specified path. No core dumps found in an additionally specified path (Not applicable) (Not applicable)

Return value	Output message	Meaning	Operation	Action
0	Collection of the backtrace data [ file-name ] was successful. OutputPath: output-path-name	Normal collection (backtrace)	Normal termination or continued processing to obtain next information	(Not applicable)
0	Collection of the core dump file [ file-name ] was successful. OutputPath: output-path-name	Normal collection (core-dump files)	Normal termination or continued processing to obtain next information	(Not applicable)
0	Collection of the shared library data [ file-name ] was successful. OutputPath: output-path-name	Normal collection (library information)	Normal termination or continued processing to obtain next information	(Not applicable)
0	Collection of the {ISAM \| Scheduler} shared memory dump was successful. Output Path: output-path-name	Normal collection (shared memory information)	Normal termination or continued processing to obtain next information	(Not applicable)
4 or 8	Error!!The input parameter [ argument ] is invalid. << ### Usage ### >> ajs2collectcore [ -b ] [ -c ] [ -l ] [ -s ] [ -f output_fullpath ] [ additional_search_fullpath ... ]	Parameter error	Abnormal termination or continued processing (if there is an error in the additionally specified path)	Check the required parameters and re-execute the command.
16	Error!! The specified directory [ destination-directory ] could not be created.	Failure to create a destination directory	Abnormal termination	The destination disk might have reached its full capacity. Check the capacity of the destination disk. After taking steps to remedy the problem, re-execute the command.
4 or 8	Error!! The specified file [ file-name ] does not have overwrite permissions.	Failure to overwrite an existing file	Continued processing (Continuing to collect something other than the target file)	Assign write privileges to the target file and re-execute the command.
4 or 8	Error!! The backtrace data for the core dump file could not be collected. Corefile: corresponding-core-dump-file-name	Failure to collect backtrace information	Continued processing (Continuing to collect something other than the target backtrace information)	The destination disk might have reached its full capacity. Check the capacity of the destination disk. After taking steps to remedy the problem, re-execute the command.
4 or 8	Error!! The core dump file could not be collected. Corefile: corresponding-core-dump-file-name	Failure to collect core-dump files	Continued processing (Continuing to collect something other than the target core-dump file)
4 or 8	Error!! Shared library data for the core dump file could not be collected. Corefile: corresponding-core-dump-file-name	Failure to collect shared library information	Continued processing (Continuing to collect something other than the target shared library information)
4 or 8	Error!! {ISAM \| Scheduler} shared memory data could not be collected.	Failure to collect shared memory information	Continued processing (Continuing to collect something other than the target shared memory information)	The following are possible errors: Memory is running short. The destination disk has reached its capacity. Check the state of memory use and the capacity of the destination disk. After taking steps to remedy the problem, re-execute the command.
4, 8, or 124	An error occurred!! ErrorCause: [ error-factor ] ErrorInfo: [ error-information ]	Other error	Continued processing (Continuing to collect something other than the target information)	(Not applicable)
(Not applicable)	There are no core dump files in default directories.	No core dumps found in a standard search path	(Not applicable)	(Not applicable)
(Not applicable)	There are no core dump files in the specified path.	No core dumps found in an additionally specified path	(Not applicable)	(Not applicable)

[Contents][Back][Next]

[Trademarks]

0	All data items have been collected successfully.
4	Some of the data items have been collected successfully.
Other values	The process has terminated abnormally.