Re: Alias

[BillsVilla@xxxxxxx]

In a message dated 5/11/00 8:15:53 AM Eastern Daylight Time, 
Colin@IBS-PUBLIC-SERVICES.CO.UK writes:

<< I've created a PF using the alias keyword...ie FIELD1
 ALIAS(CUSTOMER_NUM).
 This compiles OK
 
 Then I created a small RPGLE pgm to access this field,
 in the RPGLE pgm I`ve attempted to access the field CUSTOMER_NUM.
 
 The program fails to compile with an error saying undefined field
 CUSTOMER_NUM.
 I thought the whole point of ALIAS was to enable you to redefine fields with
 useful names...
 obviously I`ve misunderstood the usage of ALIAS.
 
 Any help will be greatly appreciated,
 
 Thanks in advance
 
 
 Colin Thorpe.  >>

I find something like CUSTOMER_NUM tends to clutter a program rather than 
make it look good. For the most part I still keep field names short to help 
keep programs clean looking. A name can still be useful and short. I think 
what helps programs look best is variable clarity and reasonable 
documentation.

Personally I would prefer to use CUST#, or for local data areas LD_CUST#, or 
for work station variables WS_CUST#.

If something has a long name I try to break it down in the same way IBM does 
within CL commands. Anyone familiar with IBM would be able to read the code 
especially with descent documentation.

Bill Francis
Director Of MIS
Abacus Corporation
Baltimore, MD
+---
| 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
+---