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 (Watson log file) |
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):
|
(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 and patchlog.txt files: installation-folder\system\version installation-folder\system\patchlog.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 |
(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). |
(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 UNIX is used
Collect the following data as maintenance information.
(a) OS log information
Type of information to be collected |
Procedure |
---|---|
syslog file |
Obtain the syslog files whose facility includes user in the /etc/syslog.conf file. You only need the part of the system log that covers the period of time during which the problem occurred. |
Version information |
Collect the execution result of the uname -a command. |
Information about installed Hitachi products |
Collect the /etc/.hitachi/pplistd/pplistd file. |
(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 |
(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). |
(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