|
David Gibbs wrote: >I'm looking for opinions... what's the best way to pass binary data to a CL? >I've got a CL wrapper around an IBM API that requires binary parameters. >I've tried passing standard numeric parms, but I'm looking for alternatives. Write a command and use *INT4 on the command def. Use *CHAR 4 in the CL program and you're good to go. CMD 'TEST' PARM KWD(BIN1) TYPE(*INT4) PGM (&parmbin) DCL &parmbin *CHAR 4 Buck +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.