8.2.2 Data to be collected about the InfoPackage control function or the process chain control function

Windows event log

Obtain the application log and the system log collected by Windows for the period of time during which the problem occurred (contents of System Log and Application Log in the Event Viewer window of Windows).

System information

Collect the system information managed by Windows (choose Accessories and then System Tools, and collect the contents of System Information).

Dump information

If an application error occurs during execution of a custom job for the SAP BW system or a command provided by JP1/AJS3 for EAP:

Collect the following log file (*.log) and dump file (*.dump):

Collect the following problem report and user dump.

(1) Problem report

If the JP1/AJS3 for EAP process stops due to an application error, use the following procedure to collect the problem report.

1. In the System and Security category of the Control Panel, click Review your computer's status.

The Action Center window opens.

2. From the right-hand side of the window, click Maintenance.

Options including Check for solutions to problem reports are displayed.

3. Under Check for solutions to problem reports, click View reliability history.

The Reliability Monitor window opens.

4. From the bottom of the window, click View all problem reports.

The Problem Reports window opens, and the problem history is displayed in a list.

5. Double-click the relevant problem.

A report detailing the problem is displayed.

6. Select Copy to clipboard.

7. Copy and save the copied content to a text file.

8. The saved problem report is collected as data for problem investigation.

(2) User dump

If the JP1/AJS3 for EAP process stops due to an application error and an error dialog box appears, use the following procedure to collect the problem report.

Note

Collect the problem report while the error dialog box is displayed.

1. Start Task Manager.

2. From the Task Manager dialog box, click Process.

3. Right-click the JP1/AJS3 for EAP process name that stopped due to an application error, and then select Create dump file.

4. When a dialog box appears asking you to specify the path to the user dump output destination, collect data from there.

Hosts file, Services file

Following files

• %systemroot%/system32/drivers/etc/hosts

• %systemroot%/system32/drivers/etc./services

Host name

Execution result of hostname command.

Communication status

Execution result of following commands

• Output of netstat -a

• Output of netstat -r

• netsh interface ip address

• netsh interface ipv6 address

• Execution result of ipconfig /all

• netsh advfirewall show currentprofile

• netsh advfirewall firewall show rule name=all verbose

List of environment variable

Execution result of following command

• set

Process

information

Execution result of following commands

• tasklist /svc

• tasklist /v

Trace information

Collect the following files:

When a file name is specified for the TargetFile key in the trace section in the conf file:

File specified by the TargetFile key

When a file name is not specified for the TargetFile key in the trace section in the conf file:

Files in installation-folder\Bwsta\Log

In addition to the above files, collect all the files in the following folders regardless of the conf file setting:

Files in installation-folder\Log

Files in Windows-folder\Temp\jp1common\jp1amr3

If a KAJM0992-E error occurs during the execution of a custom job for the R/3 system or a command of JP1/AJS3 for EAP:

Files in temporary-folder*\HLICLIB

*: %TMP%, %TEMP%, or %USERPROFILE%

If a KAJM0992-E error occurs during the execution of a custom job for the SAP BW system or a command of JP1/AJS3 for EAP:

Files in temporary-folder*\HLICLIB

*: %TMP%, %TEMP%, or %USERPROFILE%

Standard error output information

If a command provided by JP1/AJS3 for EAP ends abnormally:

Obtain the error message text that is output to the standard error output.

Standard error output

When a command is executed from the command line:

File specified in the window where the command is executed or file specified by the -se option

When a command is executed by JP1/AJS:

File defined as the standard error output by JP1/AJS, file defined as the standard error output by a JP1/AJS custom job, or file specified in the -se option of the command

Model, version, and patch information

Collect the following version, patchlog.txt, and Version.txt files:

installation-folder\system\version

installation-folder\system\patchlog.txt

installation-folder\Version.txt

Environment setup file

Collect the following conf file:

installation-folder\bwsta\conf\conf

RFC trace file

If an error occurs during the execution of a custom job for the SAP BW system or a command of JP1/AJS3 for EAP:

Collect the file named dev_rfc.trc containing the trace information about the communication with the SAP BW system. This file is created in the work directory of JP1/AJS3 for EAP.

RFC library status management file

Collect the following jr3chrfc file:

installation-folder\system\jr3chrfc

Product information file

Collect the following jp1amr3.dat file:

system-drive\Program Files (x86)\Hitachi\jp1common\jp1amr3\jp1amr3.dat

Product information

Collect the following ProductInfo.txt file:

installation-folder\ProductInfo.txt

Product information file

Collect the following file:

/etc/opt/.hlic/116C.dat

Product information

Collect the following ProductInfo.txt file:

/etc/opt/jp1_am_r3/ProductInfo.txt

Product file, List of access permissions

Execution result of following commands:

• dir /A:- /S installation-folder

• cacls installation-folder /T

Configuration file of RFC library

Following files:

When sapnwrfc.ini has specified to RFC_INI environment value

sapnwrfc.ini specified to RFC_INI environment value

When sapnwrfc.ini has not specified to RFC_INI environment value

sapnwrfc.ini file located in JP1/AJS3 for EAP working directory

Install log

Following files:

Files located under

• Windows-folder\Temp\jp1common\jp1amr3

All files located under

• Windows-folder\temp\HCDINST

System log

Run transaction SM21 via the SAP front-end software to collect the data matching the following criteria:

• User: Not specified

• Transaction code: Not specified

• SAP process: Not specified

• Error class: All messages

• Starting and ending dates and times: Period during which the target error occurred

For details about the system log, see the SAP BW documentation and the online help.

Release and patch information

• Start the SAP front-end software and choose System and then Status from the menu. Obtain a hard copy of the displayed window.

• Obtain hard copies of the following windows that can opened from the above window:

  System: Status window

  System: Component Information window

  System: Kernel Information window

Execution result of InfoPackage (for InfoPackage control)

If an error occurs during the execution of a custom job for the SAP BW system or InfoPackage using the jbwipsta command:

Run transaction RSA1 via the SAP front-end software and display the monitor window. Obtain the execution result of the InfoPackage with the problem (header, status, contents of the Details page) from the window.

Execution result of a process chain (for process chain control)

If an error occurs during the execution of a custom job for the SAP BW system or a process chain using the jbwipsta command:

Run transaction RSPC via the SAP front-end software and display the log view. Obtain the execution result of the process chain and the execution logs of the process with the problem (process log (contents of the Process page) and the job log of the process (contents of the Backg page)).

Developer trace

If an error occurs during the execution of a custom job for the SAP BW system or a command provided by JP1/AJS3 for EAP:

Obtain the developer trace in the SAP BW system (dev_w*, dev_rfc*, and dev_rd files that are collected by running transaction ST11 via the SAP front-end software).

Job execution status (Result of Trcd:SM37)

Collect the detail information of job execution and failure jobs by using job list of SM37 transaction from SAP front end software.

syslog file

/var/log/messages*

Version information

Obtain the execution result of the uname -a command.

Information about the installed Hitachi products

Collect the /etc/.hitachi/pplistd/pplistd file.

Kernel version information

Execution result of following command.

• ls -l /boot

Linux distribution name

Execution result of following command.

• ls -l /etc./*-release

Time zone information

Execution result of following commands.

• cat /etc/sysconfig/clock

• timedatectl

Hosts file, Services file

Following files.

• /etc/hosts

• /etc/services

Host name

Execution result of following commands.

• hostname

• uname -a

Communication Status

Execution result of following commands.

• netstat -a

• netstat -r

• ip addr

List of installed PP

Execution result of following command.

• /bin/rpm -qa

Kernel parameter

Execution result of following command.

• /sbin/sysctl -a

User resource restriction

Execution result of following command.

• ulimit -a

Kernel message

Execution result of following command.

• dmesg

Disk capacity

Execution result of following command.

• df -k

Disk mount information

The following file.

• /etc/fstab

Network interface information

Execution result of following commands.

• ifconfig -a

• ip addr show

Firewall information

Execution result of following commands.

• iptables -v -n -L --line-numbers

• firewall-cmd --list-all-zones

• SuSEfirewall2 status (SUSE Linux only)

Environment variable

Execution result of following command.

• env

Process information

Execution result of following command.

• ps -elfa

User list

The following file.

• /etc/passwd

Core information

Collect the following files.

• Output core file

• OS shared library files appeared by executing following file

  ldd /opt/jp1_am_r3/bin/<core that output the command>

Trace information

Collect the following files:

When a file name is specified for the TargetFile key in the trace section in the conf file:

File specified by the TargetFile key

When no file name is specified for the TargetFile key in the trace section in the conf file:

Files in /var/opt/jp1_am_r3/bwsta/log

In addition to the above files, collect the following file:

/var/opt/jp1_am_r3/log/jr3chrfc.log

Files in /var/opt/jp1_am_r3/bwsta/log

Standard error output information

If a command provided by JP1/AJS3 for EAP ends abnormally:

Obtain the error message text that is output to the standard error output.

Model, version, and patch information

Collect the following .version and .patch_hist files:

/etc/opt/jp1_am_r3/.version

/etc/opt/jp1_am_r3/.patch_hist

Environment setup file

Collect the following conf file:

/etc/opt/jp1_am_r3/bwsta/conf/conf

RFC trace file

If an error occurs during the execution of a custom job for the SAP BW system or a command of JP1/AJS3 for EAP:

Collect the file named dev_rfc containing the trace information about the communication with the SAP BW system. This file is created in the work directory of JP1/AJS3 for EAP.

RFC library status management file

Collect the following .jr3chrfc file:

/etc/opt/jp1_am_r3/.jr3chrfc

Install log

Collect the following files.

/etc/.hitachi/.hitachi.log{01|02|03|04|05}

/etc/.hitachi/.install.log{01|02|03|04|05}

/etc/.hitachi/.uninstall.log{01|02|03|04|05}

Files in /etc/.hitachi/.hliclog

Product file, List of access permissions

Execution results of following commands:

• ls -lR /etc/.hitachi/

• ls -lR /etc/opt/jp1_am_r3/

• ls -lR /opt/jp1_am_r3/

• ls -lR /var/opt/jp1_am_r3/

Configuration file of RFC library

Following files:

When sapnwrfc.ini has specified to RFC_INI environment value

sapnwrfc.ini specified to RFC_INI environment value

When sapnwrfc.ini has not specified to RFC_INI environment value

sapnwrfc.ini file located in JP1/AJS3 for EAP working directory

System log

Run transaction SM21 via the SAP front-end software to collect the data matching the following criteria:

• User: Not specified

• Transaction code: Not specified

• SAP process: Not specified

• Error class: All messages

• Starting and ending dates and times: Period during which the target error occurred

For details about the system log, see the SAP BW documentation and the online help.

Release and patch information

• Start the SAP front-end software and choose System and then Status from the menu. Obtain a hard copy of the displayed window.

• Obtain hard copies of the following windows that can be opened from the above window:

  System: Status window

  System: Component Information window

  System: Kernel Information window

Execution result of InfoPackage (for InfoPackage control)

If an error occurs during the execution of a custom job for the SAP BW system or InfoPackage using the jbwipsta command:

Run transaction RSA1 via the SAP front-end software and display the monitor window. Obtain the execution result of the InfoPackage with the problem (header, status, contents of the Details page) from the window.

Execution result of a process chain (for process chain control)

If an error occurs during the execution of a custom job for the SAP BW system or a process chain using the jbwipsta command:

Run transaction RSPC via the SAP front-end software and display the log view. Obtain the execution result of the process chain and the execution logs of the process with the problem (process log (contents of the Process page) and the job log of the process (contents of the Backg page)).

Developer trace

If an error occurs during the execution of a custom job for the SAP BW system or a command provided by JP1/AJS3 for EAP:

Obtain the developer trace in the SAP BW system (dev_w*, dev_rfc*, and dev_rd files that are collected by running transaction ST11 via the SAP front-end software).

Job execution status (Result of Trcd:SM37)

Collect the detail information of job execution and failure jobs by using job list of SM37 transaction from SAP front end software.