PX Engine information and files to collect
PX configuration files
The PX configuration file describes the machine resources available to the PX engine, including the number of nodes (physical and virtual), and scratch and permanent disk resources, etc.
A default configuration file is created at installation time, located at: <IS_HOME>/Server/Configurations/default.apt
A job can override this configuration file location by setting the environment variable APT_CONFIG_FILE (recommended by the ACG Best Practices). This allows the file to be placed anywhere in the file system. However, most installations store configuration files in IS_HOME/Server/Configurations. Since configuration files are small, collect all of the files in IS_HOME/Server/Configurations.
Exported job
The Designer allows a job (such as a failing job) to be exported to a .dsx file. IBM Support uses this file to understand the problem or reproduce it. You must specify the name of the .dsx file at the time of the export.
Director log
The log for a failing job should be printed to a file using the Director's log print dialog. You must specify the name of the file to be produced when you print the log. The "detailed" option must be specified.
Debugging directory
If a job fails consistently, and you can edit the job, collect a Debugging directory for the job. To create this directory:
Collecting PX Engine specific information
AIX, Solarix, Linux, or HP-UX
The PX configuration file describes the machine resources available to the PX engine, including the number of nodes (physical and virtual), and scratch and permanent disk resources, etc.
A default configuration file is created at installation time, located at: <IS_HOME>/Server/Configurations/default.apt
A job can override this configuration file location by setting the environment variable APT_CONFIG_FILE (recommended by the ACG Best Practices). This allows the file to be placed anywhere in the file system. However, most installations store configuration files in IS_HOME/Server/Configurations. Since configuration files are small, collect all of the files in IS_HOME/Server/Configurations.
Exported job
The Designer allows a job (such as a failing job) to be exported to a .dsx file. IBM Support uses this file to understand the problem or reproduce it. You must specify the name of the .dsx file at the time of the export.
Director log
The log for a failing job should be printed to a file using the Director's log print dialog. You must specify the name of the file to be produced when you print the log. The "detailed" option must be specified.
Debugging directory
If a job fails consistently, and you can edit the job, collect a Debugging directory for the job. To create this directory:
Commands
|
|
Files and Data to collect |
A directory is produced in IS_HOME/<project>/Debugging/<job name>. This directory contains every artifact created in the process of running the job, including:
|
Collecting PX Engine specific information
AIX, Solarix, Linux, or HP-UX
Command
|
Collects
|
ls -ltr IS_HOME/Server/PXEngine/lib
| File sizes and modification dates of the PX Engine shared libraries. |
strings IS_HOME/Server/PXEngine/lib/*.so | grep '\$Version' | sort -u | Lists the embedded compile date, time and compilation host name. This is useful for verifying patch levels |
c++ -v
| Version information about the C++ compiler |