jr3ras

Format 1

jr3ras -outdir analysis-data-stored-folder or directory
       [specify the trace file stored folder]
       [-bw_trace_file The trace file name of the InfoPackage or process-chain control function]
       [-rfctrace destination of the RFC trace file stored directory]

Note

For following cases, the strings should be surrounded by double quotation (") mark, to avoid mistaken analysis on shell or command prompt.

• One or more spaces in the argument

• Symbols describes below

  ( )

To Page Top

Format 2

jr3ras -help

To Page Top

Description

This is a tool to collect the information of JP1/AJS3 for EAP when failures occurred.

The collected information contains maintenance information, system information of OS, integrated trace log of JP1/AJS3 for EAP.

This command needs to be executed by Administrator privileged user in Windows, or super user privileged in Linux.

After executing this command, the designated information is stored under the specified folder or directory. Refer the table 4-4 and table 4-5 for detailed collected information.

Additionally, further information which is manually generated can be required depending on the failure. Refer to 8.2 Data to be collected if a problem occurs to retrieve the failure analysis information.

When you execute this command, change the current directory to the directory where jr3ras command exists.

The following table shows the folder structure in where the analysis data stored.

Table 4‒4: The folder structure of the collected information (Windows)

Folder/File name	Description
information-stored-folder\jr3ras.log	Log messages of the collection tool (jr3ras.bat)
information-stored-folder\date.log	Date and time of the collection
information-stored-folder\os\System.evt information-stored-folder\os\Application.evt	Windows event log
information-stored-folder\os\os_system.txt	Windows system information
information-stored-folder\os\hosts	Hosts file
information-stored-folder\os\services	Services file
information-stored-folder\os\hostname.txt	Host name
information-stored-folder\os\netstat.txt information-stored-folder\os\ipconfig.txt information-stored-folder\os\firewall.txt	Communication information
information-stored-folder\os\getenv.log	Environment variable
information-stored-folder\os\proc_svc.list	Executing services/process information
information-stored-folder\product\Version.txt	JP1/AJS3 for EAP version information
information-stored-folder\product\jp1amr3.dat	JP1/AJS3 for EAP product information registry file
information-stored-folder\product\ProductInfo.txt	JP1/AJS3 for EAP product information
information-stored-folder\product\regist.txt	JP1/AJS3 for EAP registry file
information-stored-folder\product\filelist.txt	JP1/AJS3 for EAP file list
information-stored-folder\product\cacls.txt	JP1/AJS3 for EAP access control file list
information-stored-folder\product\system\version	JP1/AJS3 for EAP model name, version information
information-stored-folder\product\system\patchlog.txt	Patch information for JP1/AJS3 for EAP
information-stored-folder\product\system\jr3chrfc	RFC library status management file
information-stored-folder\product\rfctrace\dev_rfc.trc information-stored-folder\product\rfctrace\dev_rfc.trc.log	RFC trace
information-stored-folder\product\HCDINST\*	Installation log for JP1/AJS3 for EAP
information-stored-folder\product\jp1common\jp1amr3\* information-stored-folder\product\r3command\* information-stored-folder\product\Log\*	Trace information (job control)
information-stored-folder\product\conf\conf	Job control environment configuration file
information-stored-folder\product\Bwsta\bwcommand\* information-stored-folder\product\Bwsta\Log\*	Trace information (InfoPackage or process chain control)
information-stored-folder\product\Bwsta\conf\conf	Environment configuration file (InfoPackage or process chain control)

Table 4‒5: The directory structure of the collected information (Linux)

Directory/File name	Description
information-stored-directory/jr3ras.log	Log messages of the collection tool (jr3ras.bat)
information-stored-directory/date.log	Date and time of the collection
information-stored-directory/os/messages*	System log
information-stored-directory/os/uname.txt	OS version information
information-stored-directory/os/boot.txt	Kernel version information
information-stored-directory/os/dist.txt	OS system information (Distribution information)
information-stored-directory/os/clock.txt information-stored-directory/os/timedatectl.txt	Timezonne information
information-stored-directory/os/hosts	Hosts file
information-stored-directory/os/services	Services file
information-stored-directory/os/hostname.txt	Host name
information-stored-directory/os/netstat.txt	Communication information
information-stored-directory/os/os_inst_pp.list	Installed product package list
information-stored-directory/os/kernel_param.list	Kernel parameter
information-stored-directory/os/ulimit.txt	User resource limitation
information-stored-directory/os/dmesg.txt	Kernel message
information-stored-directory/os/df.txt	Disk space usage
information-stored-directory/os/fstab	Disk mount information
information-stored-directory/os/ifconfig.txt information-stored-directory/os/ip_addr_show.txt information-stored-directory/os/firewall.txt	Network information
information-stored-directory/os/getenv.log	Environment variable
information-stored-directory/os/proc.list	Executing process information
information-stored-directory/os/user.txt	List of users
information-stored-directory/product/.version	JP1/AJS3 for EAP version information
information-stored-directory/product/.patch_hist	JP1/AJS3 for EAP patch information
information-stored-directory/product/jr3chrfc	RFC library status management file
information-stored-directory/product/116C.dat	JP1/AJS3 for EAP product registry information
information-stored-directory/product/ProductInfo.txt	JP1/AJS3 for EAP product list
information-stored-directory/product/pplistd	Installed Hitachi products
information-stored-directory/product/filelist.txt	JP1/AJS3 for EAP file list
information-stored-directory/product/rfctrace/dev_rfc.trc information-stored-directory/product/rfctrace/dev_rfc.trc.log	RFC trace file
information-stored-directory/product/inst/.hitachi.log* information-stored-directory/product/inst/.install.log* information-stored-directory/product/inst/.uninstall.log* information-stored-directory/product/inst/.hliclog/*	Install/Uninstall log
information-stored-directory/product/r3command/* information-stored-directory/product/Log/*	Trace information (Job control)
information-stored-directory/product/conf/conf	Job control environment configuration file
information-stored-directory/product/Bwsta/bwcommand/* information-stored-directory/product/Bwsta/Log/*	Trace information (InfoPackage or process chain control)
information-stored-directory/product/Bwsta/conf/conf	Environment Configuration file (InfoPackage or process chain control)

To Page Top

Arguments

To Page Top

Return values

0

Ended normally.

1

Specified variables are incorrect.

2

Information collection destination directory is already exists.

3

jr3ras command is not found in current directory.

4

Cannot access to the information collection directory.

5

Disk space is not enough.

6

Cannot access to the installation directory.

To Page Top

Notes

• When the tool fails to collect the information, the remediation message is printed in the standard out. If the problem is not resolved, refer to the manual 8.2 Data to be collected if a problem occurs, and collect the information manually. If you can not collect maintenance information because there are no commands or files, contact the system administrator that maintenance information could not be collected.

• When the information collection tool finishes without KAJM0651-I or KAJM0652-E, check whether the script syntax error is logged in jr3ras.log which is generated in the stored folder (Windows) or directory (Linux).

  See below for an example of syntax error (When Linux is used).

  • syntax error: unexpected end of file

    In that case, check whether special characters such as "(double quote) or `(back quote) are contained in the specified path as an argument of the information collection tool.

    If the special character is in the argument, refer to table 4-6 and table 4-7 and take appropriate action(s).

    Table 4‒6: Troubleshoot for syntax error (Windows)

    Argument	Troubleshoot
    -outdir	Change the path which does not have a special character and run the information collection tool again.
    -r3_trace_dir	Remove this argument and run the information collection tool again. See the description under When a directory name is specified for the TargetDir key in the trace section in the conf file: in the Trace information row of Table 8-2: Information to be collected from JP1/AJS3 for EAP (job control) (for Windows) and collect the materials manually.
    -r3_trace_file	Remove this argument and run the information collection tool again. See the description under When a file name is specified for the TargetFile key in the trace section in the conf file: in the Trace information row of Table 8-2: Information to be collected from JP1/AJS3 for EAP (job control) (for Windows) and collect the materials manually.
    -bw_trace_file	Remove this argument and run the information collection tool again. See the description under When a file name is specified for the TargetFile key in the trace section in the conf file: in the Trace information row of Table 8-8: Information to be collected from JP1/AJS3 for EAP (InfoPackage control or process chain control) (for Windows) and collect the materials manually.
    -rfctrace	Remove this argument and run the information collection tool again. See the RFC trace file row of Table 8-2: Information to be collected from JP1/AJS3 for EAP (job control) (for Windows) or Table 8-8: Information to be collected from JP1/AJS3 for EAP (InfoPackage control or process chain control) (for Windows) and collect the materials manually.

    Table 4‒7: Troubleshoot for syntax error (Linux)

    Argument	Troubleshoot
    -outdir	Change the path which does not have a special character and run the information collection tool again.
    -r3_trace_dir	Remove this argument and run the information collection tool again. See the description under When a directory name is specified for the TargetDir key in the trace section in the conf file: in the Trace information row of Table 8-5: Information to be collected from JP1/AJS3 for EAP (job control) (for Linux) and collect the materials manually.
    -r3_trace_file	Remove this argument and run the information collection tool again. See the description under When a file name is specified for the TargetFile key in the trace section in the conf file: in the Trace information row of Table 8-5: Information to be collected from JP1/AJS3 for EAP (job control) (for Linux) and collect the materials manually.
    -bw_trace_file	Remove this argument and run the information collection tool again. See the description under When a file name is specified for the TargetFile key in the trace section in the conf file: in the Trace information row of Table 8-11: Information to be collected from JP1/AJS3 for EAP (InfoPackage control or process chain control) (for Linux) and collect the materials manually.
    -rfctrace	Remove this argument and run the information collection tool again. See the RFC trace file row of Table 8-5: Information to be collected from JP1/AJS3 for EAP (job control) (for Linux) or Table 8-11: Information to be collected from JP1/AJS3 for EAP (InfoPackage control or process chain control) (for Linux) and collect the materials manually.

• Do not edit the information collection tool.

To Page Top

Usage examples

• When you collect the information with the following conditions in Windows

  • Collect the information stored in or under C:\temp\jr3rasout

  • The folder which the trace file is stored in is not changed in the environment configuration file (conf file)

  Example

  jr3ras -out C:\temp\jr3rasout

• When you collect the information with the following conditions in Linux

  • Collect the information stored in or under /tmp/jr3rasout

  • The /tmp/r3log is set to the TargetIDir in the trace (trace section) of the environment configuration file (conf file) for job control function.

  • The /tmp/bwlog/bwsta.log is set to the TargetFile in the trace (trace section) of the environment configuration file for InfoPackage or Process Chain control function.

  Example

  jr3ras -out /tmp/jr3rasout -r3_trace_dir /tmp/r3log -bw_trace_file /tmp/bwlog/bwsta.log

To Page Top