A fix is available
APAR status
Closed as program error.
Error description
64bit Java SPs in 64bit environment may encounter ** ASSERTION FAILED ** on methodID can't be found. The message looks like: j9vm.224 * ** ASSERTION FAILED ** at ./callin.cpp:1135: ((0 != methodID)) Processing IN and INOUT parameters of the Java method JVMDUMP039I Processing dump event "traceassert", detail "" at 2024/01/08 00:31:58 - please wait. . parmlen: 10 . parmlen: 10 . parmlen: 255 . parm 13 is var String: '4516' CCSID: 37 . parm 13 is var String: '1918' CCSID: 37 . parmnum: 15 parmIsNullFlg=1 . parmlen: 30 . parmlen: 30 . parm 15 is null var String, CCSID: 37 . parm 14 is var String: 'DITTMAR RD N' CCSID: 37 . parm 14 is var String: 'MASSACHUETTS AVE' CCSID: 37 . parmlen: 4608 . parmlen: 255 . parmlen: 255 . parm 16 is BigDecimal (DECIMAL(18,0)): 6 . parmnum: 15 parmIsNullFlg=1 . parmnum: 15 parmIsNullFlg=1 . invoking class: com/citigroup/gcif/messages/db/triggers/ADDAUD1, parm 15 is null var String, CCSID: 37 . parm 15 is null var String, CCSID: 37 . method: entry . parmlen: 4608 . parmlen: 4608 . parm 16 is BigDecimal (DECIMAL(18,0)): 4 . parm 16 is BigDecimal (DECIMAL(18,0)): 6 . invoking class: com/citigroup/gcif/messages/db/triggers/ADDAUD1,invoking class: com/citigroup/gcif/messages/db/triggers/ADDAUD1, met . hod: entry . method: entry . JVMDUMP032I JVM requested System dump using 'NYBTX.JVM.D2TRWLMJ.D240108.T003158.X&DS' in response to an event . IEATDUMP in progress with options SDATA=(LPA,GRSQ,LSQA,NUC,PSA,RGN,SQA,SUM,SWA,TRT) . Back from Call: Processing time was 0.013500 . Processing OUT and INOUT parameters of the Java method . Number of result sets is 0 . Back from Call: Processing time was 0.003000 . Processing OUT and INOUT parameters of the Java method . Number of result sets is 0 . Return Status: Execution=0, Debug=0 . JVMDUMP040I System dump written to dataset(s) using name template NYBTX.JVM.D2TRWLMJ.D240108.T003158.X&DS ---------------------------------------------------- invoking class: com/citigroup/gcif/messages/db/triggers/JFPL2P4, method: entry JVMDUMP030W Cannot write dump to file //javacore.20240108.003158.16845015.0002.txt: EDC5141I Read-only file system. JVMDUMP032I JVM requested Java dump using '/tmp/javacore.20240108.003158.16845015.0002.txt' in response to an event Number of result sets is 0 JVMDUMP010I Java dump written to /tmp/javacore.20240108.003158.16845015.0002.txt JVMDUMP032I JVM requested Snap dump using '//Snap.20240108.003158.16845015.0003.trc' in response to an event JVMDUMP030W Cannot write dump to file //Snap.20240108.003158.16845015.0003.trc: EDC5141I Read-only file system. JVMDUMP010I Snap dump written to /tmp/Snap.20240108.003158.16845015.0003.trc JVMDUMP013I Processed dump event "traceassert", detail "".
Local fix
NA
Problem summary
**************************************************************** * USERS AFFECTED: Db2 for z/OS users of Java stored * * procedures and User Defined Functions(UDFs) * * that are running in 64-bit multi-threaded * * JVM environment. * **************************************************************** * PROBLEM DESCRIPTION: When Java stored procedures or UDFs * * are running concurrently, the routine * * may terminate unexpectedly during * * execution. The following error * * messages may be found in the WLM job * * log: * * * * j9vm.224 * ** ASSERTION FAILED ** * * at ./callin.cpp:1135:((0 != methodID)) * * * * JVMDUMP032I JVM requested System dump * * using... * * * * The stored procedure and UDF might be * * put into a stopped state after the * * failure. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available * **************************************************************** When Java stored procedures or UDFs are running concurrently, there might be a rare timing window where the method ID for one of the stored procedure or UDF parameters is not obtained, but the execution continues. The NULL method ID is incorrectly passed to a JNI function, resulting in an abend in the JVM. The Java routine then terminates abnormally.
Problem conclusion
Db2 code has been modified to ensure the method ID for all stored procedure or UDF parameters is obtained during the parameter processing.
Temporary fix
Comments
×**** PE24/07/23 FIX IN ERROR. SEE APAR PH62422 FOR DESCRIPTION
APAR Information
APAR number
PH60180
Reported component name
DB2 OS/390 & Z/
Reported component ID
5740XYR00
Reported release
C10
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2024-03-05
Closed date
2024-06-05
Last modified date
2024-08-14
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI97180 UI97181
Modules/Macros
DSNX9JA6
Fix information
Fixed component name
DB2 OS/390 & Z/
Fixed component ID
5740XYR00
Applicable component levels
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSEPEK","label":"DB2 for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"12.0","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
14 August 2024