Thanks Sri, that second URL you posted was what I started with, but testing the
results of rxfuncquery('ehllapi') using the rexxtry script shows that I get
RC=0 for the query instead of the expected RC=1. Directly executing the call
to rxfuncadd as coded in that example gets RC=X and RESULT=1 and trying a call
to EHLLAPI after rxfuncadd gets the same "routine not found" error.
That's why I am asking questions here. I can't seem to make it work and I do
not know why not.
Peter
-----Original Message-----
From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Sri
h Kolusu
Sent: Thursday, June 29, 2023 11:05 AM
To: [email protected]
Subject: Re: Using EHLLAPI from ooRexx
>> 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?
Peter,
EHLLAPI is provided as an external feature and is loaded into memory only when
used. To ensure that REXX EHLLAPI functions are available, REXX application
programs must contain the following statement:
if rxfuncquery('hllapi') then call rxfuncadd 'hllapi','saahlapi','hllapisrv'
REXX EHLLAPI provides a single function name, which is used with a set of
parameters. The function name is the first parameter of the rxfuncadd call
above; the default is HLLAPI.
https://urldefense.com/v3/__https://www.ibm.com/docs/en/personal-communications/6.0?topic=programming-rexx-ehllapi-functions__;!!Ebr-cpPeAnfNniQ8HSAI-g_K5b7VKg!NXT-gEyLA1veUbT40qeI3qKGZ7PWwsJQmImOIojCYTColpdmBQbv9VGBY8TUU5umM1Vu1_6u51gPB2f8ZIkU6A$
Also here is an example
https://urldefense.com/v3/__https://www.mcpressonline.com/programming-other/general/rexx-ehllapi-programming-by-example__;!!Ebr-cpPeAnfNniQ8HSAI-g_K5b7VKg!NXT-gEyLA1veUbT40qeI3qKGZ7PWwsJQmImOIojCYTColpdmBQbv9VGBY8TUU5umM1Vu1_6u51gPB2c66Zs29Q$
Thanks,
Kolusu
--
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
