× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: RE: external *PRTF (was: RE: 'ILE RPG' or 'RPG IV' . What's the difference!!!)
  • From: "Bale, Dan" <DBale@xxxxxxxx>
  • Date: Tue, 11 Apr 2000 11:25:45 -0400

I strongly disagree.  _Can_ you define screens internally?  Other than DSPLY
opcode?  Subfiles?

Totally different ballgame

> -----Original Message-----
> From: Nelson C. Smith [SMTP:ncsmith@gate.net]
> Sent: Monday, April 10, 2000 10:16 PM
> To:   RPG400-L@midrange.com
> Subject:      Re: external *PRTF (was: RE: 'ILE RPG' or 'RPG IV' . What's
> the difference!!!)
> 
> Every argument made for internal print files fits equally well for
> internal
> screen files.  Do you define your screens internally?
> 
> 
> ----- Original Message -----
> From: "Bale, Dan" <DBale@lear.com>
> To: <RPG400-L@midrange.com>
> Sent: Monday, April 10, 2000 10:35 AM
> Subject: external *PRTF (was: RE: 'ILE RPG' or 'RPG IV' . What's the
> difference!!!)
> 
> 
> > Really don't mean to start a holy war here <g>, but...  IMNSHO:
> >
> > External printer files - BLEAAHHH!  If it's used in only one program,
> which
> > is the case for 99.95% of all printer files I've ever come across, then
> keep
> > it in the RPG source!
> >
> > Granted, had IBM's braindead RLU been something closer to what RDA (by
> > BugBusters???) is, then I might have formed a different opinion ten
> years
> > ago.  Then again, since RDA allows you to choose between creating
> printer
> > DDS specs or RPG O-specs, who knows?  There's really not a whole lot you
> can
> > do in DDS that can't be done in RPG O-specs for _most_ printer output.
> >
> > Honestly, though, it really isn't an "ease of design / development"
> issue
> > with me.  For me, it's an "ease of maintenance" issue, since I do much
> more
> > maintenance than new development.
> > Internal: One source member. External: Two source members.
> > Internal: No confusing where the printer file source is; it's right
> there.
> > External: Ever been in a JBA shop? 'nuf said.
> > Internal: One edit session, one compile.  External: Two edit sessions,
> two
> > compiles.
> > Internal: When RPG compile error occurs, you just need to look for
> errors
> in
> > the RPG source.  External:  When RPG compile error occurs, you need to
> check
> > the RPG compile listing, oops - not there, now go check the printer file
> > DDS, make corrections, recompile DDS, recompile RPG.
> >
> > All that said, I always follow the shop standards.  I can do printer
> specs
> > either way.
> >
> > Jon, please indicate why you think "it is just better and safer to
> describe
> > these things externally."
> >
> > - Dan Bale
> >
> > > -----Original Message-----
> > > From: Jon.Paris@halinfo.it [SMTP:Jon.Paris@halinfo.it]
> > > Sent: Saturday, April 08, 2000 9:08 AM
> > > To: RPG400-L@midrange.com
> > > Subject: Re: 'ILE RPG' or 'RPG IV' . What's the difference!!!
> > >
> > > PS. I don't think printer files have _anything_ to do with using them
> in
> > > multiple places any more that display files do - it is just better and
> > > safer to
> > > describe these things externally.
+---
| 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
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.