× 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: System 36 internal display file
  • From: "Peter Dow" <pcdow@xxxxxxxxxxxxxxx>
  • Date: Sun, 8 Oct 2000 14:54:20 -0700

Hi Mark,

As long as there are comments identifying the output specs that go with
which input specs, I agree with you.  However, you _could_ define the record
ID as a protected, non-display I/O field. For debugging, remove the
non-display attribute to be sure you're getting what you think you are.
Although I suppose if you want to conserve screen real-estate a hidden field
is better.

Actually, I like to put the name of the format visibly on the screen
somewhere so that when users ask for a modification, they have a reference
name. At least with RPG III and RPG IV we don't need to worry so much about
the input specs!

Regards,
Peter Dow
Dow Software Services, Inc.
909 425-0194 voice
909 425-0196 fax


From: "M. Lazarus" <mlazarus@ttec.com>

>>As you say, the record ID field does not need to be output, but it makes
it
>>clearer (to me at least) which output specs are related to which input
specs
>>and I doubt that it has any performance impact. The screen field can be
>>hidden and protected, or displayable protected in case it helps in
debugging.

> For input, maybe.  But why for output?  Since it's a hidden / protected
> field, and its only use is for the *program* to ID which format was read,
> making this field an output field is a waste and can be confusing (since
it
> never shows up on the screen).  Actually, thinking about it, since it's a
> constant in the S & D specs, you CAN'T output it via your program.
There's
> no buffer position defined.

> +---
> | 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 thread ...

Replies:

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.