IBM Support

Mustgather: Gathering data for hang or performance problem on z/OS

Troubleshooting


Problem

If your Java application experiences perceived hang or performance problem on a z/OS operating system, there are a number of diagnostic data files that are useful for diagnosing the problem. This mustgather document describes about the diagnostic data files to be collected and the procedure to collect the same.

Resolving The Problem

The following set of diagnostic data files need to be collected manually during the time of hang or performance problem perceive in your java application:

1. Transaction dumps (Tdumps)


2. Console logs (Application logs and Joblogs)
3. Verbose GC logs (native_stderr.log)
4. Netstat logs
5. Health Center logs (In case of performance problems)

For these diagnostic data files to be created, check that the system is configured correctly as per setup document.

Please collect the diagnostic data files manually during the time of hang or performance problem perceive in your java application as per the below steps:

1. Generate at least three transaction dumps using the following command:
kill -SIGQUIT [PID_of_problem_JVM]

There needs to be 2 or 3 minutes time interval in between each transaction dump generated. Otherwise spread the time interval across the issue time and generate the transaction dumps.

Please note that the transaction dumps will be generated as standard MVS™ Dump data sets and the names of them will follow the below format:

Transaction dump : %uid.JVM.TDUMP.%job.D%y%m%d.T%H%M%S



2. Collect all the console logs such as application logs and joblogs.

3. Collect Verbose Garbage Collector data. This data is in the location specified during setup. Alternatively, the data is sent to the stderr output.

4. Collect the netstat log containing the snapshot of network activities, by using the following command:
netstat -an > netstat1.out

Please collect multiple netstat logs during the time of hang or performance problems in your Java application.

5. In case of performance problem, run the Health Center tool along with the application and collect the health center dump file generated.

Please refer the IBM Health Center document for more information on installing, configuring and running the health center tool.

After collecting all the above diagnostic data files, you can submit them for help with diagnosing the problem.

Related Information

[{"Product":{"code":"SSNVBF","label":"Runtimes for Java Technology"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"Hangs\/Performance Degradation","Platform":[{"code":"PF035","label":"z\/OS"}],"Version":"8.0;7.1;7.0;6.1;6.0;5.0","Edition":"J2SE","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
15 June 2018

UID

swg21588546