• Subject: RE: Overiding Screen Output in a CL Program
  • From: "Chapman, Colin" <Colin.Chapman@xxxxxxxxxxxxxxx>
  • Date: Tue, 30 Nov 1999 09:18:54 -0000

Cheers Dan, I was wondering about a way to "get inside" the command - thanks
for the answer.

Colin

-----Original Message-----
From: Dan Bale [mailto:dbale@genfast.com]
Sent: Monday, November 29, 1999 9:24 PM
To: MIDRANGE-L@midrange.com
Subject: Re: Overiding Screen Output in a CL Program




Colin,

Actually, DSPPFM was probably a bad example to use ;-)  You wouldn't really
want
to "capture" the output of a DSPPFM, would you?  In most cases, where IBM
doesn't give you an option for output, there's usually a pretty good reason
for
it.  After all, if you didn't want to just view the DSPPFM output on the
screen,
then RUNQRY *n FILENAME to print it, or CPYF to copy it.

If you're asking if there's a way to "get inside" of a command like DSPPFM
and
change the output device or otherwise intercept the output, I don't believe
you've got a prayer.  There are probably some commands out there that don't
give
you options for output but IBM has supplied an API that supplies the same
info.

Don't know if you were really leaning towards this, but there are a lot of
IBM
commands that do give you the output option of display, print, or outfile.
But
I've had requirements for RTV-type commands because of the one-file limit in
CL.
For example, I've created a RTVFA (ReTrieVe File Attributes) that basically
is a
DSPFD TYPE(*BASATR).

HTH,
- Dan Bale


"Chapman, Colin" <Colin.Chapman@lloydsudt.co.uk> wrote:

Boris, the reason I gave the example DSPPFM FILE(QGPL/QCLSRC) was that it
doesn't have any output options. I have used CMD's before which create
prints or create output files and can incorporate this no problem in CL
pgm's.
I was just wondering whether it was possible to get info that normally went
to the screen but doesn't have any output options and incorporate that into
a CL pgm.

I don't want to do anything specific - it was just a general query.

Thanks,

Colin





+---
| 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
+---
**********************************************************************
This email is intended for the exclusive use of the addressee only.
If you are not the intended recipient, you should not use the contents
nor disclose them to any other person and you should immediately
notify the sender and delete the email.
**********************************************************************
+---
| 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
+---

This thread ...


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

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