It truly is a well-thought out, clean approach. If I'd endeavored, the result would have likely been a 300-line program that called 17 APIs and pulled information from three continents. :) If I may borrow from Middleman, Chuck's solution is sheer elegance in its simplicity.

The one thing to watch for (and I don't wish to pick nits) is presence of double quote within the data to be written. For that, one would need special code, or to remember to escape ( \" ) the character before the CALL.
++
Dennis
++
"Peace: In international affairs, a period of cheating between two periods of fighting."
-- Ambrose Bierce


Sent from my Galaxy tablet phone. Please excuse my brevity.
For any grammatic/spelling errors, there is no excuse.
++


"James Lampert" <jamesl@xxxxxxxxxxxxxxxxx> wrote:

CRPence wrote:
pgm parm(&inpstr)
dcl &inpstr *char 30
dcl &qshrqs *char 2000
dcl &outnam *char 30 'output.txt'
chgvar &qshrqs 'touch -C 819 '
chgvar &qshrqs (&qshrqs *bcat &outnam *tcat ';')
chgvar &qshrqs (&qshrqs *tcat 'echo "')
chgvar &qshrqs (&qshrqs *tcat &inpstr )
chgvar &qshrqs (&qshrqs *tcat '" > ' *bcat &outnam)
sndpgmmsg msg(&qshrqs) topgmq(*ext) tomsgq(*topgmq)
qsh cmd(&qshrqs)
endpgm

Thanks, Chuck: that's slicker than frog scat. Not that Vern's answer
wouldn't have also worked, but this was quite remarkable, and it runs
fast on the customer box.

--
JHHL
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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

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.