|
Hi, The recent flurry of activity in the thread relating to QzshSystem etc leads me to wonder if any of the respondents with more experience than I at low level programming can provide an answer to a question that has eluded me for some years. If an existing AS400 program has processed a request which has been written to stdout, can I create a "simple wrapper" for that process that will allow me to read the contents of stdout and then rewrite stdout? While it may be possible by using the OVRDBF command where the existing program has been written in C/400, this does not appear to be the case where the output has been generated by a call to a system API that populates stdout, for example QtmhWrStout in an RPGLE program or a call to DB2WWW. This is essentially a piping exercise. I have recently seen some unsupported code from IBM that attempts to emulate the popen() and pclose() functions that are available in some languages. These appear to provide for spawning a child process to run a request where the input/output can be piped, but I am not game to use them. This is one of those things that one would think to be so simple, but alas. Cheers, Peter This communication is confidential and may be legally privileged. If it is not addressed to you, you are on notice of its status. Please immediately contact us at our cost and destroy it. Please do not use, disclose, copy, distribute or retain any of it without our authority - to do so could be a breach of confidence. Thank you for your co-operation. If you need assistance, please contact Baycorp Advantage on either :- Australia 133124 or New Zealand +64 9 356 5800 *** Please be advised that all Baycorp Advantage email addresses *** *** must be in the format 'firstname.lastname@baycorpadvantage.com' *** *** ALL OLD BAYCORP ADDRESSES WILL CEASE TO EXIST FROM THE 1ST OF JUNE ***
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.