Maintain it against the part files (mind you, I'd just declare them DYNAMIC and let UV sort it out).
In a distributed file, each individual part file is just an ordinary file, with a little bit of extra logic that hashes the ID to say "is this record permitted in this file". You can treat the partfile exactly as if it were a normal file, except that any record that doesn't pass this test will suffer a write failure if you try to save it. If you open the "header file", as you call it, then another extra bit of logic gets invoked that works out which partfile to write it to. Cheers, Wol -----Original Message----- From: Moderator [mailto:[EMAIL PROTECTED] Sent: 19 June 2007 13:50 To: u2-users@listserver.u2ug.org Cc: Dominion Subject: [U2] [UV] - Distributed Files REPOSTED FOR NON-MEMBER ADDRESS: Dominion <[EMAIL PROTECTED]> Hi, I'm looking at implementing Universe distributed files. We are moving a UV app from TRU64 to LINUX on Intel, and unfortunately that means we will lose the luxury of 64bit files. I've got the files converted to distributed files no problem, but I'm trying to get my head round file sizing. Do I need to maintain the file sizing against the DF header file, or against each of the part files defined within the DEFINE.DF ommand? Thanks BOUNCE NOTICE: Your recent post to our lists bounced because either you are not a member or because you are not signed up using the e-mail address which you used to post. To subscribe or resubscribe please visit http://listserver.u2ug.org/. - Charles Barouch, Moderator U2-Users, U2-Community, SBSolutions, RBSolutions ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
