This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
--
[ Picked text/plain from multipart/alternative ]
Thanks Simon,

That's exactly what I found about return, too big! But I did find a solution
that will work in this situation, 'SNDDTAQ DTAQ(HGR0093/RAND) ENTLEN(6)
ENTRY(&RNBR)' and then RCVDTAQ DTAQ(HGR0093/RAND) ENTLEN(&L) ENTRY(&MAXD) on
the outside. Odd about that RTNVAL(*YES), tried that as well to no avail!

In reality, that was mostly an exercise to reacquaint myself with Rexx and
getting my mind set to convert the VB program, I choose Rexx because I
figured there would be a better corollary with the VB program (which does
some very unusual things! and because here there is no other choice, the C
compiler while here is only used when all else fails!). Also there was the
added bonus of being able to see the results *now* vs. after a compile. I
think in the end I will make this a command since I can fake out returning
data to the outside world but I want to look into the QREXXQ API, I was sort
of taken back when I pushed data onto the Q and when the Rexx program ended
NADA! I expected to see a flood of useless error messages saying like *No
such command you idiot!* but nothing, guess the Queue data just goes off
into the bit bucket.

"
2/ Put the return value on the Rexx queue (using PUSH) and retrieve it
using the QREXQ API.

Since Rexx can be the CPP for a CL command it would be nice if we could
use RTNVAL(*YES) for the parameter and code something like:

CMD        PROMPT('Test Rexx Command')

PARM       KWD(RANDOM) TYPE(*CHAR) LEN(6) RTNVAL(*YES)

however RTNVAL(*YES) is not supported when Rexx is used as the CPP.
"


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 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.