A few years back I ran up an assembler program that used CELQPIPI(64-bit PIPI) to do this, but the assembler program called C routines via PIPI to do the real work; the C routines contained Java JNI code.
-----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Crawford Robert C (Contractor) Sent: Wednesday, July 12, 2023 1:40 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: [EXT] Re: Invoke Java from Assembler Thanks, Allan. Back in the 90's I used CEEPIPI to create a persistent C enclave I could call from Assembler because building the environment is expensive. Unfortunately, CEEPIPI documentation is kind of scarce. What we do find doesn't give us very many clues for how to get to Java. Robert Crawford Abstract Evolutions LLC (210) 913-3822 -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of allan winston Sent: Tuesday, July 11, 2023 5:22 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: [EXT] Re: Invoke Java from Assembler Robert, This reminds me of a situation I ran into 25 years ago involving assembler and COBOL. Granted, COBOL and Java are different environments, but there may be enough similarity in the issues to be relevant. We had an assembler main program that called a COBOL subroutine repeatedly. It was chugging along just fine until LE maintenance showed a large spike in CPU time within LE library routines, as shown by Strobe. It seemed as though the LE environment was constantly being created and torn down. I did look into solutions, such as using CEEPIPI, but this program was a major CPU consumer in this shop and we needed a quick solution. The solution I proposed and was implemented was to create a new main program, written in COBOL, that called the former assembler main program. That way the new main program established the LE environment that persisted until the program terminated. So, ALC calling COBOL changed to COBOL calling ALC calling COBOL. In your case: Java calling COBOL changed to COBOL calling Java calling COBOL. I have never used Java, so this is somewhat a shot in the dark. I should have created an ETR on IBMLINK about the increased CPU overhead, but did not bother since we had a circumvention. Allan On Tue, Jul 11, 2023 at 5:58 PM Crawford Robert C (Contractor) < 000004e08f385650-dmarc-requ...@listserv.ua.edu> wrote: > We're interested in invoking Java from assembler in batch. > Specifically, we'd like to create a persistent Java environment we can > call repeatedly and terminate when we're through. > > Has anyone done this? Is the LE pre-initialization module CEEPIPI > worth exploring? > > Thanks. > > Robert Crawford > Abstract Evolutions LLC > (210) 913-3822 > > > ---------------------------------------------------------------------- > 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 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- This e-mail message has been scanned and cleared by Google Message Security and the UNICOM Global security systems. This message is for the named person's use only. If you receive this message in error, please delete it and notify the sender. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
