APAR status
Closed as duplicate of another APAR.
Error description
userSignalHandler() sees signal 29 SIGPWR 29 (+) power-fail restart ================================== This shows at the beginning of the JAVADUMP. This is not a valid signal for z/OS.
Local fix
This APAR was created to fix this problem. The JNI function JVM_FindSignal() now returns the correct signal numbers and names for USS. ===================================================== userSignalHandler() sees signal 29 SIGXCPU 29 (@) CPU time limit exceeded, see setrlimit() and/or JCL TIME= parameter
Problem summary
Problem conclusion
Temporary fix
Comments
Customer reported JAVADUMP/CEEDUMP taken when running various XML parsing classes in batch. Dump was taken due to catching signal 29 (which is SIGXCPU or CPU excession problem) in USS. The error message printed (seen at the top of the JAVADUMP) reports SIGPWR 29 (+) power-fail restart which is not meaningful on 390. This defect taken to bring the signal description array in src/jvm/pfm/xm/signals_md.c in line with the signals documented in the USS signal handling module, BPXSNDLV. OS/390 Bring signal descriptions in line with USS (BPXNSDLV) Intergrated into code = 20010203 This APAR is a duplicate of PQ47697
APAR Information
APAR number
PQ46643
Reported component name
JAVA2(1.3) OS/3
Reported component ID
5648C9801
Reported release
130
Status
CLOSED DUB
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2001-03-02
Closed date
2001-05-04
Last modified date
2001-05-04
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSNVBF","label":"Runtimes for Java Technology"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"1.3.1","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]
Document Information
Modified date:
04 May 2001