RE: external *PRTF (was: RE: 'ILE RPG' or 'RPG IV' . What's the d iffe rence!!!)

["Bale, Dan" <DBale@xxxxxxxx>]

Dave,

I beg to differ.  QPRINT & QSYSPRT are indeed printer file objects, but they
are not externally described.  

Still, no one has answered the question.  Is it possible to do meaningful
screen I/O with a display file created with SRCFILE(*NONE) using only RPG
I-specs and O-specs?  If there is, I can't see how it could be as simple to
code as internal printer file O-specs; you and someone else mentioned UDDS -
enough said?

Ah yes, workstation files using the primary cycle!  I think there was a
point where the only choice you had for workstation files on a S/34 was to
define it as primary.  Only later did we have the option to define it as a
"D"emand file.  (Or was that just the way it was introduced to me? <g>)

- Dan Bale

> -----Original Message-----
> From: Shaw, David [SMTP:dshaw@spartan.com]
> Sent: Wednesday, April 12, 2000 4:21 PM
> To:   'RPG400-L@midrange.com'
> Subject:      RE: external *PRTF (was: RE: 'ILE RPG' or 'RPG IV' . What's
> the d iffe    rence!!!)
> 
> Dan,
> 
> When you use O-specs, you still have a print file, probably QSYSPRT or
> something similar.  You're just program-describing it.  The same thing can
> be done with display files, in several different ways.  REAL programmers
> use
> user-defined data streams and control everything directly - well, at least
> one time in their careers. <grin>  Or there's the wimp way - define one
> 1919-character field in your display file, and program-describe the thing
> in
> O and I specs.  It's not hard, just tedious.  Heck, at my first job we had
> a
> program like that which actually handled the screen with the RPG cycle -
> that was a dinosaur in 1986 when I saw it on the /38.  The program used
> arrays to simulate a subfile, just like the S/34 program that it had been
> derived from.
> 
> Dave Shaw
> Spartan International, Inc.
> Spartanburg, SC
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---