APAR status
Closed as program error.
Error description
Error Message: When examining a system dump using the jdmpview tool, the 'info thread' command is used to obtain information about a thread, specifying a native thread ID as parameter. On zOS, a USS native thread ID is accepted by the command, but the more usual zOS TCB address is not. . Stack Trace: N/A .
Local fix
The issue can be worked around by using the 'info thread all' command to list all threads, then searching for the thread with the required TCB by looking at the properties of each thread.
Problem summary
The problem is caused when a zOS TCB address is supplied as parameter to the 'info thread' command rather than a USS native thread ID.
Problem conclusion
The jdmpview tool has been updated to accept the zOS TCB ID as a parameter to the 'info thread' command. . This APAR will be fixed in the following Java Releases: 8 SR2 FP10 (8.0.2.10) 7 R1 SR3 FP30 (7.1.3.30) . Contact your IBM Product's Service Team for these Service Refreshes and Fix Packs. For those running stand-alone, information about the available Service Refreshes and Fix Packs can be found at: https://www.ibm.com/developerworks/java/jdk/
Temporary fix
Comments
APAR Information
APAR number
IV79626
Reported component name
J9 COMMON CODE
Reported component ID
620700127
Reported release
270
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2015-12-09
Closed date
2015-12-09
Last modified date
2015-12-09
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
J9 COMMON CODE
Fixed component ID
620700127
Applicable component levels
R270 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSNVBF","label":"Runtimes for Java Technology"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]
Document Information
Modified date:
21 February 2022