I suppose switching one of the machines to the other database is not an option?
>>> [EMAIL PROTECTED] 02/26/04 09:20AM >>> This file would be accessed by quite a number of programs, many times during a day. Thanks, everyone. You have given us some excellent options to consider. Randal -----Original Message----- From: Timothy Snyder <[EMAIL PROTECTED]> Sent: Feb 25, 2004 3:45 PM To: U2 Users Discussion List <[EMAIL PROTECTED]> Subject: Re: Common Universe/Unidata files Randal, With half a million records, I strongly agree that you don't want to put this in a directory file. Without knowing more about what you're doing, I'd be inclined to set up a hashed file stored in either UniVerse or UniData (flip a coin). Then you could put together a socket client/server setup to handle updates from the other side. That could be set up with the appropriate rules to handle locking and anything else that may be required to properly negotiate updates. You might need to pass around some other information, such the next key, etc., but it shouldn't be too bad. Is this something that would need to be accessed from many programs, or just a few? How frequently would the file be accessed and updated? Tim Snyder IBM Data Management Solutions Consulting I/T Specialist , U2 Professional Services Office (717) 545-6403 (rolls to cell phone) [EMAIL PROTECTED] Randal LeBlanc wrote on 02/25/2004 02:49:10 PM: > We have separate applications running on Universe and Unidata. The > apps run on separate > aix servers. > We would like to create a common file that can be accessed by both > applications > but are not sure of the best approach to take. > Any suggestions??-- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users Randal LeBlanc JCL Associates, Inc. [EMAIL PROTECTED] www.jclinc.com -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users
