The PCOMM DLL location is already in my PATH (double checked, "which dllname.dll" finds it in the PCOMM install location).
As I said in my other reply, also checking whether HACL can be an alternative implementation. Peter -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Tom Brennan Sent: Friday, June 30, 2023 12:35 AM To: [email protected] Subject: Re: Using EHLLAPI from ooRexx Windows also looks for DLL's in the same directory as the running program. So you could copy the PCOMM DLL to your working directory as a test to see what happens. And if no more DLL's are needed, it might even work. Or like Seymour said, try putting the PCOMM DLL directory in your PATH. Windows doesn't make that easy. Control Panel, System, Advanced System Settings, Environment Variables, find Path in the list and run through the goofy editor. On 6/29/2023 8:20 AM, Farley, Peter wrote: > That's what I thought too, but what variable? And where is that documented? > > Peter > > -----Original Message----- > From: IBM Mainframe Discussion List <[email protected]> On > Behalf Of Seymour J Metz > Sent: Thursday, June 29, 2023 11:17 AM > To: [email protected] > Subject: Re: Using EHLLAPI from ooRexx > > I suspect that you need to add the DLL to an environment variable. > > ________________________________________ > From: IBM Mainframe Discussion List <[email protected]> on > behalf of Farley, Peter > <[email protected]> > Sent: Thursday, June 29, 2023 10:56 AM > To: [email protected] > Subject: Using EHLLAPI from ooRexx > > Hi All, > > I have sent this question to the ooRexx help list but have not yet seen an > answer. Hoping someone here has been down this path and can help cure my > ignorance. > > I have an automation task before me that needs some complex 3270 screen > interactions, so I was hoping to use ooRexx from the company laptop (Windows > 10) using the EHLLAPI interface to PCOMM. > > I started with a simple logon script to learn the connection/setup > requirements, and after (I thought) successfully executing rxfuncadd for the > EHLLAPI interface, the first actual call to EHLLAPI (for the Connect > function) gets oorexx error 43.1, cannot find routine EHLLAPI, indicating to > me that the rxfuncadd did not really work. > > Then it occurred to me to ask how does rxfuncadd know where to find the > EHLLAPI DLL? Is there some environment variable that needs to be set > pointing to the PCOMM directory where the DLL is stored? > > There is some old Rexx EHLLAPI interface material in the PCOMM V6 > documentation available on the web, but I now have PCOMM V14 on my machine > and it seems that the Rexx examples have disappeared from the V14 > documentation (at least I didn't find any). > > I am a little "lost at sea" here, so I would appreciate any help or RTFM you > can provide. Or better yet a publicly available set of example scripts for > EHLLAPI interactions with PCOMM. > > Peter -- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
