RE: Another V5R1 query... Qualified DSs

["Stone, Brad V (TC)" <bvstone@xxxxxxxxxxxxxx>]

Let me try and explain a little more.

I know we've all hated the fact that you can't have the same field in two
different Data Structures.  So, when I saw this, I thought "cool!  This will
be great."

But then I realized.  Using the QUALIFIED keyword means I have to qualify it
when i use it.

The reason I wanted to use the same field in two different data structures
is I wanted them to have the same value as well.  So when I said:

eval   Date = *DATE

Each and every data structure with a field of Date inside of it would have
the same value.  

But, with this new feature, you have to say:

eval   DS1.Date = *DATE
eval   DS2.Date = *DATE

It may be just me, but this is why I wanted to have the same field names in
data structures.  What you describe in your #3 is just a small piece that
may be helpful.  It could be quite possible the only reason I'm saying this
is because I thought it meant something it did not and am looking for
something that makes this change worth the $15 we had to pay (I don't know
what it was, I'm just guessing.)

Brad

> -----Original Message-----
> From: Gary Guthrie [mailto:GaryGuthrie@home.com]
> Sent: Wednesday, May 09, 2001 6:00 PM
> To: RPG400-L@midrange.com
> Subject: Re: Another V5R1 query... Qualified DSs
> 
> 
> Brad,
> 
> I can make a few comments with respect to using QUALIFIED vs. PREFIX.
> 
> 1) Qualified is more standard
> 2) Qualified helps prevent the possibility of collisions. For 
> example, a
> subfield with field name Address prefixed with Cust would result in a
> field named CustAddress. It's possible you could try to create a
> standalone field named CustAddress. I realize this is no 
> biggie, but...
> 3) Qualified hopefully opens the door to such operations as 
> COBOL's Move
> Corresponding in which all fields of the same name within two 
> structures
> are candidates for copy from the source structure to the target
> structure- that would be great.
> 
> Gary Guthrie
> NEWS/400 Technical Editor
> +---
> | 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
+---