|
>
> I hope all of that makes sense, it's really hard to put into words.
>
It all makes sense, thanks por pointing me out how to handle the char(*) api
parms, but im still having problems. In the prototype i've changed:
d qzruclsp pr extpgm('QZRUCLSP')
d QualSrvPgm...
d 20a const
d ExportName...
d 4096A const options(*varsize)
d ReturnValueFormat...
d 10i 0 const
d ParametersFormat...
d 10i 0 const dim(3)
d NumberOfParameters...
d 10i 0 const
d ErrorCode...
d 256a
d ReturnValue...
d 10i 0 options(*nopass)
d Parameter1...
d 10i 0 options(*nopass)
d Parameter2...
d 10i 0 options(*nopass)
d Parameter3...
d 10i 0 options(*nopass)
d p1 s 10i 0 inz(4)
d p2 s 10i 0 inz(3)
d p3 s 10i 0 inz(10)
d Rtn s 10i 0
c callp qzruclsp('TEST BABIB': 'MAX' + x'00':
c 1: array: 3: p_error:
c Rtn: p1: p2: p3)
Parameter1, Parameter2 and Parameter3 are now passed as integers (so the api
will get the address of that integer values), but know i get the MCH3601
error saying that the pointer has no valid address.
Is the api converting the address i send to a char(*) correctly ?
I'm kinda lost...
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.