OP stated that it is not reusable. Regrettable, but he's stuck with it. Your guess of a DS that the code assumes is initialized seems plausible.
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Peter Relson [rel...@us.ibm.com] Sent: Tuesday, February 14, 2023 8:13 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Are JNI required to be re-entrant and/or re-usable? Steve Austin wrote >as the 1st call works and subsequent calls fail in the assembler routine. That's a bit surprising to me. It's usually concurrent calls that fail due to reentrancy issues of a non-reentrant module, not "subsequent calls". So while the concurrency case is quite possibly still a big problem, there might be something else going on, such as not initializing something that you are assuming is initialized. And if that was the case, your module is not only not reentrant but is not reusable. And that is unlikely to be what you intend. Peter Relson z/OS Core Technology Design ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
