8.2.1 Data to be collected about the job control function
If a problem occurs while you are using the job 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 |
If an application error occurs during execution of a custom job for the R/3 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
|
Host name |
Execution result of hostname command. |
Communication status |
Execution result of following commands
|
List of environment variable |
Execution result of following command
|
Process information |
Execution result of following commands
|
(b) Information to be collected from JP1/AJS3 for EAP (job 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\conf\conf |
RFC trace file |
If an error occurs during the execution of a custom job for the R/3 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 R/3 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 file, List of access permissions |
Execution result of following commands:
|
Configuration file of RFC library |
Following files:
|
Install log |
Following files: Files located under
All files located under
|
(c) Information to be collected from the R/3 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 R/3 documentation and the online help. |
XMI log |
Run transaction RZ15 via the SAP front-end software and collect the data matching the following criteria:
Legend: *: Asterisk For details about the XMI log, see the R/3 documentation and the online help. |
Release and patch information |
|
Developer trace |
If an error occurs during the execution of a custom job for the R/3 system or a command provided by JP1/AJS3 for EAP: Obtain the developer trace in the R/3 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. |
(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)
-
Machine configuration (version of each OS, host name, and the configuration of JP1/AJS and the R/3 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 |
Collect the execution result of the uname -a command. |
Information about installed Hitachi products |
Collect the /etc/.hitachi/pplistd/pplistd file. |
Kernel version information |
Execution result of following command.
|
Linux distribution name |
Execution result of following command.
|
Time zone information |
Execution result of following commands.
|
Hosts file, Services file |
Following files.
|
Host name |
Execution result of following commands.
|
Communication Status |
Execution result of following commands.
|
List of installed PP |
Execution result of following command.
|
Kernel parameter |
Execution result of following command.
|
User resource restriction |
Execution result of following command.
|
Kernel message |
Execution result of following command.
|
Disk capacity |
Execution result of following command.
|
Disk mount information |
The following file.
|
Network interface information |
Execution result of following commands.
|
Firewall information |
Execution result of following commands.
|
Environment variable |
Execution result of following command.
|
Process information |
Execution result of following command.
|
User list |
The following file.
|
Core information |
Collect the following files.
|
(b) Information to be collected from JP1/AJS3 for EAP (job 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: Collect 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/conf/conf |
RFC trace file |
If an error occurs during the execution of a custom job for the R/3 system or a command of JP1/AJS3 for EAP: Collect the file named dev_rfc containing the trace information about the communication with the R/3 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 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 results of following commands:
|
Configuration file of RFC library |
Following files:
|
(c) Information to be collected from the R/3 system
Type of information to be collected |
Procedure |
---|---|
System log |
Run transaction SM21 via the SAP front-end software and collect the data matching the following criteria:
For details about the system log, see the R/3 documentation and the online help. |
XMI log |
Run transaction RZ15 via the SAP front-end software and collect the data matching the following criteria:
Legend: *: Asterisk For details about the XMI log, see the R/3 documentation and the online help. |
Release and patch information |
|
Developer trace |
If an error occurs during the execution of a custom job for the R/3 system or a command provided by JP1/AJS3 for EAP: Obtain the developer trace in the R/3 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. |
(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)
-
Machine configuration (version of each OS, host name, and the configuration of JP1/AJS and the R/3 system)
-
Whether the problem is reproducible, how often the problem occurs