Thank you David, but my problem is not on the read and write operatios , is in the fact that I can't continue debugging the program after the read and write operations did over the distributed file.
Jose Luis > Add the on error option to your read & write statement. First you can > use the STATUS() to identify the fatal error and second, this allows a > graceful exit from the program when you have a fatal. It sounds like > you are unable to resolve the key for the part file at the time of the > read or write, so print the Key as well in the On Error clause > > Hyope that helps > > Regards > David Jordan > Managing Consultant > [EMAIL PROTECTED] > > Dacono Holdings Pty Ltd > Business & Technology Consulting > PO Box 909 > Lane Cove > NSW 2066 > Australia > Ph 61 2 9418 8329 > Fax 61 2 9427 2371 > www.dacono.com.au > > > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > On Behalf Of José Luis Gutiérrez de la Peza > Sent: Saturday, 7 February 2004 10:12 AM > To: [EMAIL PROTECTED] > Subject: Debug problem with Distributed files > > > Hi, Could anyone help me with this : > > We have an installation with uniVerse 10 and when we try to debug a > program that use a distributed file, the debugging stops every time the > program has a Read or Write instruction. > > We are using an external subroutine as a partition algorithm. > > Thanks in advance for your help > > > José Luis Gutiérrez De la Peza > > -- > 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 -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users
