× 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: Program standards (was Named indicators (was DOW vs DOU))
  • From: "James W. Kilgore" <qappdsn@xxxxxxx>
  • Date: Wed, 28 May 1997 08:49:54 -0700
  • Organization: Progressive Data Systems, Inc.

John Carr wrote:

> 

> James;

> 

> I'd  be willing to bet that even "CUSThit,  ITEMhit"  doesn't always mean the

> same thing in all programs.  What if you're using three ODP's to the same

> file(PF, & a couple of LF's over the same PF).?  Do you resort to " CUSThit, 
>or

> CUSThit01, CUSThitLF1,   etc, etc"



When using multiple ODP's to the same file, you are correct, we number

the variables and that number just happens to be the same number that's

at the end of the file name. ie: CUSTKEY = CUSThit, CUSTALT1 = CUSThit1



> 

> Does EVERY programmer use the same label (CUSThit) for the same file?  Or are

> they a "Variations on a Theme"  kind of thing?  The reason I'm asking is I've

> seen that sometimes even named variables do not automatically produce clear

> understanding( See the ramblings in one of my recent posts about Russian 
>General

> names as variables).



In EVERY program a given field will have the same meaning, and  we also

do the function key indicator standard.



We started this habit years ago on the S/36 with heavy use of /COPY. 

For each file we would create members for record format I/O, CHAIN,

SETLL, READ, initialize record, etc.  Within these routines we would set

fields xxHIT, xxANY, xxDONE, etc.



Routine names are standardized and we also have a pretty good library of

template programs which are used as a start point.  When file B is to be

chained based upon the contents of file A we even have a standard

routine for that, even if it's only done in one program.  (BTW primed

DOW loops is our standard)



> 

> I agree that indicators are not "self evident"  in their meanings,  But on the

> other hand,  I have been in shops that had STRICT standards concerning

> indicators  and in EVERY program indicators 1-29 were function keys (F1-F24,

> Home, etc.)  and so on.  And in those cases I'd rather have consistent obtuse

> indicators than have named variables that change their meanings from routine 
>to

> routine or program to program, or be named after russian generals or parts of

> boats (EXSR ANCHOR?).

> 

We are one of those STRICT shops. 



The STRICT enforcement of standards also eased our transition to full

native applications, made it easier to hunt down Y2K issues and is

making life easier for writing our RPG to C conversion aid.



Without meaning to offend anyone, we have two classes of technical

staff: designers and coders.  Coders do not have the liberty of choice. 

Designers do their choosing for them.



Then there's me: the keeper of the standards, keys and check book. :-)

-- 

===================================================

James W. Kilgore   | Progressive Data Systems, Inc.

President          | 311 31st Ave SE

(206) 848-2567     | Puyallup, Washington 98374 USA

qappdsn@ibm.net    | http://www.ultimate.org/PDS

===================================================
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the Midrange System Mailing List!  To submit a new message,   *
* send your mail to "MIDRANGE-L@midrange.com".  To unsubscribe from     *
* this list send email to MAJORDOMO@midrange.com and specify            *
* 'unsubscribe MIDRANGE-L' in the body of your message.  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:
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.