8.2.2 Data to be collected about the InfoPackage control function or the process chain control function
If a problem occurs while you are using the InfoPackage control function or the process chain control function, collect the data described below.
- Organization of this subsection
(1) When Windows is used
Collect the following data as maintenance information.
(a) OS log information
Type of information to be collected |
Procedure |
---|---|
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 (Watson log file) |
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):
|
(b) Information to be collected from JP1/AJS3 for EAP (InfoPackage control or process chain control)
Type of information to be collected |
Procedure |
---|---|
Trace information |
Collect the following files:
|
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, 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 |
(c) Information to be collected from the SAP BW system
Type of information to be collected |
Procedure |
---|---|
System log |
Run transaction SM21 via the SAP front-end software to collect the data matching the following criteria:
For details about the system log, see the SAP BW documentation and the online help. |
Release and patch information |
|
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). |
(d) Operational details
Check the following information about the operation that was being performed when the problem occurred:
-
Detailed contents of the operation
-
Time when the problem occurred
-
Job in which the problem occurred (jobnet name and job name in JP1/AJS, InfoPackage ID, process chain ID)
-
Machine configuration (version of each OS, host name, and the configuration of JP1/AJS and the SAP BW system)
-
Whether the problem is reproducible, how often the problem occurs
(2) When Linux is used
Collect the following data as maintenance information.
(a) OS log information
Type of information to be collected |
Procedure |
---|---|
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. |
(b) Information to be collected from JP1/AJS3 for EAP (InfoPackage control or process chain control)
Type of information to be collected |
Procedure |
---|---|
Trace information |
Collect the following files:
|
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 |
(c) Information to be collected from the SAP BW system
Type of information to be collected |
Procedure |
---|---|
System log |
Run transaction SM21 via the SAP front-end software to collect the data matching the following criteria:
For details about the system log, see the SAP BW documentation and the online help. |
Release and patch information |
|
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). |
(d) Operational details
Check the following information about the operation that was being performed when the problem occurred:
-
Detailed description of the operation
-
Time when the problem occurred
-
Job in which the problem occurred (jobnet name and job name in JP1/AJS, InfoPackage ID, process chain ID)
-
Machine configuration (version of each OS, host name, and the configuration of JP1/AJS and the SAP BW system)
-
Whether the problem is reproducible, how often the problem occurs