Re: Add a unique key field to view without redefining table

I'm away from my computer but you may want to consider not selecting all columns in your logical files. This should keep your format id the same.

Sent from Lotus Traveler


Charles Wilt --- Re: Add a unique key field to view without redefining table ---
From:"Charles Wilt" <charles.wilt@xxxxxxxxx>To:"Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>Date:Tue, Dec 13, 2016 11:18 AMSubject:Re: Add a unique key field to view without redefining table
On Tue, Dec 13, 2016 at 8:54 AM, Dan wrote: > Doable, but a maintenance > nightmare. > ​Not really, no. The idea is that the LFs will never change. And once you build the first field list, it's a simple matter to copy and past to the other logicals. If at some point you add a new field that a program needs, then you create a new logical, with an explicit field list that includes that new field and change the program to use the new logical. As long as the​ new logical has the same key as an existing, there's no extra overhead beyond a few bytes of DASD for the object definition. The concept's been around a while, programs only access data via logical file with an explicit and unchanging format. But the DB2 modernization whitepaper/redbook outlines the technique as a method to move from DDS -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. Please contact support@xxxxxxxxxxxx for any subscription related questions. Help support midrange.com by shopping at amazon.com with our affiliate link: http://amzn.to/2dEadiD