|
midrange.com
I don't think RLU is all that unfriendly, it's not just the same as SDA. It
would have been nice if SDA and RLU used some if not most of the same
conventions.
-----Original Message-----
From: Rob Berendt [SMTP:rob@dekko.com]
Sent: Tuesday, April 11, 2000 9:47 AM
To: RPG400-L@midrange.com
Subject: Re: external *PRTF (was: RE: 'ILE RPG' or 'RPG IV' . What's the
diffe rence!!!)
I've heard that they've redone that. I haven't tried the
redone. In the past it earned the name Really Lousy Utility.
dbryant@banpharm.com on 04/11/2000 08:33:55 AM
Please respond to RPG400-L@midrange.com@Internet
To: RPG400-L@midrange.com@Internet
cc:
Fax to:
Subject: Re: external *PRTF (was: RE: 'ILE RPG' or 'RPG IV' . What's the
diffe rence!!!)
Have you used RLU lately? It is absolutely GREAT!! O specs (ugly), might
as
well be an RPG-II program.
With RLU, no worries about end positions, page overflow, line spacing or
even
knowing the field lengths. With RLU, you can quickly center a field. You
can use
the REFER option for RLU to get the field attributes for you. You can copy,
move
and delete fields with a quick function key sequence. Even highlight fields
and
underline (you can even use indicators to control the different functions
available). But most of all I love the fact that RLU will output your
TODAYS
date and time, and the page number with NO RPG coding at all. Also you
can
print a "Sample" prototype report to see how your report looks on paper.
RLU is cool!!!
IMHO.....
|--------+----------------------->
| | "Jim" |
| | <jcannon@anti|
| | gua.com> |
| | |
| | 04/10/2000 |
| | 01:36 PM |
| | Please |
| | respond to |
| | RPG400-L |
| | |
|--------+----------------------->
>--------------------------------------------------------|
| |
| To: RPG400-L@midrange.com |
| cc: (bcc: Darlene H Bryant/Banpharm) |
| Subject: Re: external *PRTF (was: RE: 'ILE |
| RPG' or 'RPG IV' . What's the diffe rence!!!) |
>--------------------------------------------------------|
very well said! I agree!
From: "Bale, Dan" <DBale@lear.com>
To: "'RPG400-L@midrange.com'" <RPG400-L@midrange.com>
Subject: external *PRTF (was: RE: 'ILE RPG' or 'RPG IV' . What's
the
diffe
rence!!!)
Date sent: Mon, 10 Apr 2000 10:35:02 -0400
Send reply to: RPG400-L@midrange.com
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
+---
+---
| 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
+---
+---
| 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
+---
+---
| 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
+---
+---
| 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 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.
