RE: [U2] [UD] Possible causes of corrupt data on a UniData static file
Kathleene, I wish it were that easy. READNEXT and READ can't get it's hands on these records. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Kathleeni M Hunter Sent: Thursday, November 01, 2007 6:34 PM To: u2-users@listserver.u2ug.org Subject: RE: [U2] [UD] Possible causes of corrupt data on a UniData static file Basic program read record, check id for char (o), if there get new id, write record with new id and delete old record. -Original Message- From: Wally Terhune [mailto:[EMAIL PROTECTED] Sent: Thursday, November 01, 2007 2:14 PM To: u2-users@listserver.u2ug.org Subject: Re: [U2] [UD] Possible causes of corrupt data on a UniData static file I wrote previously: UniBasic does not prevent you from writing out a record or ID with char(0) imbedded. It is a legal character. No guesses as to the cause of your particular issue. To assist in diagnosis, you can search your problem file for all occurances of char(0) in data records or keys using an option on 'guide'. For instance: guide -U0 PROBLEM.FILE.NAME option is -U followed by the ascii charcter number you want to search for. I should add that the information about characters found is in GUIDE_ERRORS.LIS. For instance: guide -U65 VOC (looking for 'A') pg GUIDE_ERRORS.LIS VOC File Integrity: Group 0, block 1, record number 0 = COL.SPACES has char(65) in key. Group 0, block 1, record number 1 = LIST.LABEL has char(65) in key. Group 0, block 1, record number 7 = STATS has char(65) in key. Group 0, block 1, record number 0 = COL.SPACES record has char(65) in data. Group 0, block 1, record number 1 = LIST.LABEL record has char(65) in data. ... (many more entries) Wally Terhune SWG Client Support - Information Management Software U2 Support Architect b IBM U2 Client Support Team 4700 S. Syracuse St., Denver, CO 80237 Tel: (303) 773-7969 T/L 656-7969 Mobile: (303) 807-6222 [EMAIL PROTECTED] Register today for the premier U2 technical event! [demime 1.01d removed an attachment of type image/jpeg which had a name of 08633156.jpg] [demime 1.01d removed an attachment of type image/jpeg which had a name of 08907059.jpg] --- 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/ __ This e-mail has been scanned by MCI Managed Email Content Service, using Skeptic(tm) technology powered by MessageLabs. For more information on MCI's Managed Email Content Service, visit http://www.mci.com. __ __ This e-mail has been scanned by MCI Managed Email Content Service, using Skeptic(tm) technology powered by MessageLabs. For more information on MCI's Managed Email Content Service, visit http://www.mci.com. __ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] [UD] Possible causes of corrupt data on a UniData static file
UD 7.1 They are not SELECT statements. They are things like: sort FILENAME THIS THAT TOXML -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Dave Davis Sent: Thursday, November 01, 2007 3:06 PM To: u2-users@listserver.u2ug.org Subject: RE: [U2] [UD] Possible causes of corrupt data on a UniData static file What unidata version? What SELECT .. BY statement were you using. Are the BY fields actually stored in the file, or are they I-types that tran to another file? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Burwell, Ed Sent: Thursday, November 01, 2007 2:36 PM To: u2-users@listserver.u2ug.org Subject: [U2] [UD] Possible causes of corrupt data on a UniData static file Hello, I have been getting corrupt data lately. Stuff like this: sort: warning: first character of the record is '\0' discard it! sort: warning: the record contain '\0' character, discard it! sort: warning: the record contain '\0' character, discard it! sort: warning: the record contain '\0' character, discard it! sort: warning: the record contain '\0' character, discard it! sort: warning: the record contain '\0' character, discard it! sort: warning: the record contain '\0' character, discard it! Are there any programming no-no's that could cause stuff like this, for instance: 1. Putting logic in an UPDATE trigger that calls a UniData function that run a UniQuery statement that creates XML, then writes that XML to a file (to be HTTP transmitted later by a separate background task). 2. Putting logic in an UPDATE trigger that compares the prior record to the one about to be written, then updates a log file if the records are different. 3. Four separate indexes on a file. I'm getting desperate. Any help would be GREATLY appreciated! Thanks. Ed __ This e-mail has been scanned by MCI Managed Email Content Service, using Skeptic(tm) technology powered by MessageLabs. For more information on MCI's Managed Email Content Service, visit http://www.mci.com. __ --- 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/ __ This e-mail has been scanned by MCI Managed Email Content Service, using Skeptic(tm) technology powered by MessageLabs. For more information on MCI's Managed Email Content Service, visit http://www.mci.com. __ __ This e-mail has been scanned by MCI Managed Email Content Service, using Skeptic(tm) technology powered by MessageLabs. For more information on MCI's Managed Email Content Service, visit http://www.mci.com. __ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] [UD] Possible causes of corrupt data on a UniData static file
more issues: guide -U0 filename is now giving me this: GUIDE_ERRORS.LIS: WORK.ORDER File Integrity: Group 11338, block 11339, record number 12 = 970941 is in wrong group, key length 6, hash value 2413 Group 11340, block 11341, record number 12 = 970943 is in wrong group, key length 6, hash value 2415 Group 11343, block 11344, record number 12 = 970946 is in wrong group, key length 6, hash value 2418 Group 11346, block 11347, record number 12 = 970949 is in wrong group, key length 6, hash value 2421 Group 11350, block 11351, record number 12 = 970953 is in wrong group, key length 6, hash value 2425 The weird part, is that I can edit these items (with AE) and they are there and they SEEM to be fine! Ed -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Wally Terhune Sent: Thursday, November 01, 2007 5:14 PM To: u2-users@listserver.u2ug.org Subject: Re: [U2] [UD] Possible causes of corrupt data on a UniData static file I wrote previously: UniBasic does not prevent you from writing out a record or ID with char(0) imbedded. It is a legal character. No guesses as to the cause of your particular issue. To assist in diagnosis, you can search your problem file for all occurances of char(0) in data records or keys using an option on 'guide'. For instance: guide -U0 PROBLEM.FILE.NAME option is -U followed by the ascii charcter number you want to search for. I should add that the information about characters found is in GUIDE_ERRORS.LIS. For instance: guide -U65 VOC (looking for 'A') pg GUIDE_ERRORS.LIS VOC File Integrity: Group 0, block 1, record number 0 = COL.SPACES has char(65) in key. Group 0, block 1, record number 1 = LIST.LABEL has char(65) in key. Group 0, block 1, record number 7 = STATS has char(65) in key. Group 0, block 1, record number 0 = COL.SPACES record has char(65) in data. Group 0, block 1, record number 1 = LIST.LABEL record has char(65) in data. ... (many more entries) Wally Terhune SWG Client Support - Information Management Software U2 Support Architect b IBM U2 Client Support Team 4700 S. Syracuse St., Denver, CO 80237 Tel: (303) 773-7969 T/L 656-7969 Mobile: (303) 807-6222 [EMAIL PROTECTED] Register today for the premier U2 technical event! [demime 1.01d removed an attachment of type image/jpeg which had a name of 08633156.jpg] [demime 1.01d removed an attachment of type image/jpeg which had a name of 08907059.jpg] --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ __ This e-mail has been scanned by MCI Managed Email Content Service, using Skeptic(tm) technology powered by MessageLabs. For more information on MCI's Managed Email Content Service, visit http://www.mci.com. __ __ This e-mail has been scanned by MCI Managed Email Content Service, using Skeptic(tm) technology powered by MessageLabs. For more information on MCI's Managed Email Content Service, visit http://www.mci.com. __ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] [UD] Possible causes of corrupt data on a UniData static file
quote who='Burwell, Ed' date='Friday 02 November 2007' Are there any known issues with UPDATE triggers that write to records that have UPDATE triggers? As long as you don't get into a cycle where trigger A invokes B, B invokes C and then C invokes A. That turns into a nasty infinite loop fast. -- Jeff Butera, Ph.D. Administrative Systems Hampshire College [EMAIL PROTECTED] 413-559-5556 That's why you have two ears and one mouth - use them accordingly. Mike Golic --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] [UD] Possible causes of corrupt data on a UniData static file
Ed, I have dealt with UniData file corruption in the past and it can be quite difficult to get a handle on it. I have seen files get corrupted by memory failures, processor failures, and disk failures. If this is not due to a hardware issue a file can be corrupted,(or at least used to be corrupted depend on your release) by performing a unix copy (cp -rp) on a file that is being updated, and running guide against a file that me be in use. There could be more issues that haven't been listed. I have also found that running guide against a corrupt file does not always fix the file. In some cases a second check against a file by guide has turned up more errors. There are times when a file has been corrupted, guide can't fix it. I usually make a copy of the file, clear it, and copy the records into it, and run guide against this file. The fact that AE will let you access a record only means the editor can read the record. If you try to change something in the record and file it, you will see errors. We don't use triggers, so I can't comment on that. Rich Richard Sammartino Systems Analyst School District of Philadelphia 440 N Broad Street Philadelphia, Pa 19130 Phone: (215) 400-5086 Fax: (215) 400-4411 --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] [UD] Possible causes of corrupt data on a UniData static file
[demime could not interpret encoding quoted-printable - treating as plain text] My guess is that you have real records with real Ids that you can access. Then you have other records that appear to have the same Ids but really don't. It sounds like these other records are hashed into the wrong groups - hence your inability to access them. I would try creating another file with a different modulo then copy the records from the current file to this new one. They should re-hash, and then maybe you can get to them. Dick Kryka | Director of Applications CCCS of Greater Denver | Paragon Financial Services a Division of Money Management International 10065 East Harvard Avenue | Suite 210 Denver, CO 80231 D: 303-632-2226 | F: 303-632-2101 | M: 303-907-1907 [EMAIL PROTECTED] -Original Message- I wish it were that easy. READNEXT and READ can't get it's hands on these records. The information in this email is intended only for the personal and confiden= tial use of the designated recipient above. If the reader of this message i= s not the intended recipient or an agent responsible for delivering it to th= e intended recipient, you are hereby notified that you have received this do= cument in error, and that any review, dissemination, distribution or copying= of the message is strictly prohibited. If you are not the intended recipie= nt, please contact the sender immediately by reply e-mail and destroy all co= pies of the original message. --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] [UD] Possible causes of corrupt data on a UniData static file
Ed, Copy the file and then resize it. That way you can confirm that you have the same information. I had this problem a long time ago and was able to read the records. Kathleeni -Original Message- From: Burwell, Ed [mailto:[EMAIL PROTECTED] Sent: Friday, November 02, 2007 8:11 AM To: u2-users@listserver.u2ug.org Subject: RE: [U2] [UD] Possible causes of corrupt data on a UniData static file Kathleene, I wish it were that easy. READNEXT and READ can't get it's hands on these records. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Kathleeni M Hunter Sent: Thursday, November 01, 2007 6:34 PM To: u2-users@listserver.u2ug.org Subject: RE: [U2] [UD] Possible causes of corrupt data on a UniData static file Basic program read record, check id for char (o), if there get new id, write record with new id and delete old record. -Original Message- From: Wally Terhune [mailto:[EMAIL PROTECTED] Sent: Thursday, November 01, 2007 2:14 PM To: u2-users@listserver.u2ug.org Subject: Re: [U2] [UD] Possible causes of corrupt data on a UniData static file I wrote previously: UniBasic does not prevent you from writing out a record or ID with char(0) imbedded. It is a legal character. No guesses as to the cause of your particular issue. To assist in diagnosis, you can search your problem file for all occurances of char(0) in data records or keys using an option on 'guide'. For instance: guide -U0 PROBLEM.FILE.NAME option is -U followed by the ascii charcter number you want to search for. I should add that the information about characters found is in GUIDE_ERRORS.LIS. For instance: guide -U65 VOC (looking for 'A') pg GUIDE_ERRORS.LIS VOC File Integrity: Group 0, block 1, record number 0 = COL.SPACES has char(65) in key. Group 0, block 1, record number 1 = LIST.LABEL has char(65) in key. Group 0, block 1, record number 7 = STATS has char(65) in key. Group 0, block 1, record number 0 = COL.SPACES record has char(65) in data. Group 0, block 1, record number 1 = LIST.LABEL record has char(65) in data. ... (many more entries) Wally Terhune SWG Client Support - Information Management Software U2 Support Architect b IBM U2 Client Support Team 4700 S. Syracuse St., Denver, CO 80237 Tel: (303) 773-7969 T/L 656-7969 Mobile: (303) 807-6222 [EMAIL PROTECTED] Register today for the premier U2 technical event! [demime 1.01d removed an attachment of type image/jpeg which had a name of 08633156.jpg] [demime 1.01d removed an attachment of type image/jpeg which had a name of 08907059.jpg] --- 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/ __ This e-mail has been scanned by MCI Managed Email Content Service, using Skeptic(tm) technology powered by MessageLabs. For more information on MCI's Managed Email Content Service, visit http://www.mci.com. __ __ This e-mail has been scanned by MCI Managed Email Content Service, using Skeptic(tm) technology powered by MessageLabs. For more information on MCI's Managed Email Content Service, visit http://www.mci.com. __ --- 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/
RE: [U2] [UD] Possible causes of corrupt data on a UniData static file
Can UniData TRIGGERS be problematic? In the past, I wrote a trigger that would launch a UniData function that would (eventually) generate XML with a UniQuery statement, then POST the XML using submitRequest to a secure site, take the XML that was returned in the RESPONSE.DATA parameter and write it somewhere - all before finishing the original trigger that called this stuff. That never caused corruption. Am I near any limits or anything that you are aware of? Are there any known issues with UPDATE triggers that write to records that have UPDATE triggers? Thanks. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Wally Terhune Sent: Thursday, November 01, 2007 5:14 PM To: u2-users@listserver.u2ug.org Subject: Re: [U2] [UD] Possible causes of corrupt data on a UniData static file I wrote previously: UniBasic does not prevent you from writing out a record or ID with char(0) imbedded. It is a legal character. No guesses as to the cause of your particular issue. To assist in diagnosis, you can search your problem file for all occurances of char(0) in data records or keys using an option on 'guide'. For instance: guide -U0 PROBLEM.FILE.NAME option is -U followed by the ascii charcter number you want to search for. I should add that the information about characters found is in GUIDE_ERRORS.LIS. For instance: guide -U65 VOC (looking for 'A') pg GUIDE_ERRORS.LIS VOC File Integrity: Group 0, block 1, record number 0 = COL.SPACES has char(65) in key. Group 0, block 1, record number 1 = LIST.LABEL has char(65) in key. Group 0, block 1, record number 7 = STATS has char(65) in key. Group 0, block 1, record number 0 = COL.SPACES record has char(65) in data. Group 0, block 1, record number 1 = LIST.LABEL record has char(65) in data. ... (many more entries) Wally Terhune SWG Client Support - Information Management Software U2 Support Architect b IBM U2 Client Support Team 4700 S. Syracuse St., Denver, CO 80237 Tel: (303) 773-7969 T/L 656-7969 Mobile: (303) 807-6222 [EMAIL PROTECTED] Register today for the premier U2 technical event! [demime 1.01d removed an attachment of type image/jpeg which had a name of 08633156.jpg] [demime 1.01d removed an attachment of type image/jpeg which had a name of 08907059.jpg] --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ __ This e-mail has been scanned by MCI Managed Email Content Service, using Skeptic(tm) technology powered by MessageLabs. For more information on MCI's Managed Email Content Service, visit http://www.mci.com. __ __ This e-mail has been scanned by MCI Managed Email Content Service, using Skeptic(tm) technology powered by MessageLabs. For more information on MCI's Managed Email Content Service, visit http://www.mci.com. __ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] [UD] Possible causes of corrupt data on a UniData static file
UV doesn't have guide, but it has uvfixfile and fixtool. Regards, LeRoy -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Arnold Bosch Sent: Friday, November 02, 2007 3:53 PM To: u2-users@listserver.u2ug.org Subject: Re: [U2] [UD] Possible causes of corrupt data on a UniData static file Is guide only available on UD ? It does not work with UV (10.0). Is there a similar command available in UV? Thanks! Arnold Bosch IT Administrator -- --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
[U2] [UD] Possible causes of corrupt data on a UniData static file
Hello, I have been getting corrupt data lately. Stuff like this: sort: warning: first character of the record is '\0' discard it! sort: warning: the record contain '\0' character, discard it! sort: warning: the record contain '\0' character, discard it! sort: warning: the record contain '\0' character, discard it! sort: warning: the record contain '\0' character, discard it! sort: warning: the record contain '\0' character, discard it! sort: warning: the record contain '\0' character, discard it! Are there any programming no-no's that could cause stuff like this, for instance: 1. Putting logic in an UPDATE trigger that calls a UniData function that run a UniQuery statement that creates XML, then writes that XML to a file (to be HTTP transmitted later by a separate background task). 2. Putting logic in an UPDATE trigger that compares the prior record to the one about to be written, then updates a log file if the records are different. 3. Four separate indexes on a file. I'm getting desperate. Any help would be GREATLY appreciated! Thanks. Ed __ This e-mail has been scanned by MCI Managed Email Content Service, using Skeptic(tm) technology powered by MessageLabs. For more information on MCI's Managed Email Content Service, visit http://www.mci.com. __ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] [UD] Possible causes of corrupt data on a UniData static file
What unidata version? What SELECT .. BY statement were you using. Are the BY fields actually stored in the file, or are they I-types that tran to another file? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Burwell, Ed Sent: Thursday, November 01, 2007 2:36 PM To: u2-users@listserver.u2ug.org Subject: [U2] [UD] Possible causes of corrupt data on a UniData static file Hello, I have been getting corrupt data lately. Stuff like this: sort: warning: first character of the record is '\0' discard it! sort: warning: the record contain '\0' character, discard it! sort: warning: the record contain '\0' character, discard it! sort: warning: the record contain '\0' character, discard it! sort: warning: the record contain '\0' character, discard it! sort: warning: the record contain '\0' character, discard it! sort: warning: the record contain '\0' character, discard it! Are there any programming no-no's that could cause stuff like this, for instance: 1. Putting logic in an UPDATE trigger that calls a UniData function that run a UniQuery statement that creates XML, then writes that XML to a file (to be HTTP transmitted later by a separate background task). 2. Putting logic in an UPDATE trigger that compares the prior record to the one about to be written, then updates a log file if the records are different. 3. Four separate indexes on a file. I'm getting desperate. Any help would be GREATLY appreciated! Thanks. Ed __ This e-mail has been scanned by MCI Managed Email Content Service, using Skeptic(tm) technology powered by MessageLabs. For more information on MCI's Managed Email Content Service, visit http://www.mci.com. __ --- 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/
Re: [U2] [UD] Possible causes of corrupt data on a UniData static file
UniBasic does not prevent you from writing out a record or ID with char(0) imbedded. It is a legal character. No guesses as to the cause of your particular issue. To assist in diagnosis, you can search your problem file for all occurances of char(0) in data records or keys using an option on 'guide'. For instance: guide -U0 PROBLEM.FILE.NAME option is -U followed by the ascii charcter number you want to search for. Wally Terhune SWG Client Support - Information Management Software U2 Support Architect b IBM U2 Client Support Team 4700 S. Syracuse St., Denver, CO 80237 Tel: (303) 773-7969 T/L 656-7969 Mobile: (303) 807-6222 [EMAIL PROTECTED] Register today for the premier U2 technical event! Burwell, Ed [EMAIL PROTECTED] omTo Sent by: u2-users@listserver.u2ug.org [EMAIL PROTECTED] cc stserver.u2ug.org Subject [U2] [UD] Possible causes of 11/01/2007 12:35 corrupt data on a UniData static PMfile Please respond to [EMAIL PROTECTED] er.u2ug.org Hello, I have been getting corrupt data lately. Stuff like this: sort: warning: first character of the record is '\0' discard it! sort: warning: the record contain '\0' character, discard it! sort: warning: the record contain '\0' character, discard it! sort: warning: the record contain '\0' character, discard it! sort: warning: the record contain '\0' character, discard it! sort: warning: the record contain '\0' character, discard it! sort: warning: the record contain '\0' character, discard it! Are there any programming no-no's that could cause stuff like this, for instance: 1. Putting logic in an UPDATE trigger that calls a UniData function that run a UniQuery statement that creates XML, then writes that XML to a file (to be HTTP transmitted later by a separate background task). 2. Putting logic in an UPDATE trigger that compares the prior record to the one about to be written, then updates a log file if the records are different. 3. Four separate indexes on a file. I'm getting desperate. Any help would be GREATLY appreciated! Thanks. Ed __ This e-mail has been scanned by MCI Managed Email Content Service, using Skeptic(tm) technology powered by MessageLabs. For more information on MCI's Managed Email Content Service, visit http://www.mci.com. __ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ [demime 1.01d removed an attachment of type image/jpeg which had a name of 25739582.jpg] [demime 1.01d removed an attachment of type image/jpeg which had a name of 25465054.jpg] [demime 1.01d removed an attachment of
Re: [U2] [UD] Possible causes of corrupt data on a UniData static file
I wrote previously: UniBasic does not prevent you from writing out a record or ID with char(0) imbedded. It is a legal character. No guesses as to the cause of your particular issue. To assist in diagnosis, you can search your problem file for all occurances of char(0) in data records or keys using an option on 'guide'. For instance: guide -U0 PROBLEM.FILE.NAME option is -U followed by the ascii charcter number you want to search for. I should add that the information about characters found is in GUIDE_ERRORS.LIS. For instance: guide -U65 VOC (looking for 'A') pg GUIDE_ERRORS.LIS VOC File Integrity: Group 0, block 1, record number 0 = COL.SPACES has char(65) in key. Group 0, block 1, record number 1 = LIST.LABEL has char(65) in key. Group 0, block 1, record number 7 = STATS has char(65) in key. Group 0, block 1, record number 0 = COL.SPACES record has char(65) in data. Group 0, block 1, record number 1 = LIST.LABEL record has char(65) in data. ... (many more entries) Wally Terhune SWG Client Support - Information Management Software U2 Support Architect b IBM U2 Client Support Team 4700 S. Syracuse St., Denver, CO 80237 Tel: (303) 773-7969 T/L 656-7969 Mobile: (303) 807-6222 [EMAIL PROTECTED] Register today for the premier U2 technical event! [demime 1.01d removed an attachment of type image/jpeg which had a name of 08633156.jpg] [demime 1.01d removed an attachment of type image/jpeg which had a name of 08907059.jpg] --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] [UD] Possible causes of corrupt data on a UniData static file
Basic program read record, check id for char (o), if there get new id, write record with new id and delete old record. -Original Message- From: Wally Terhune [mailto:[EMAIL PROTECTED] Sent: Thursday, November 01, 2007 2:14 PM To: u2-users@listserver.u2ug.org Subject: Re: [U2] [UD] Possible causes of corrupt data on a UniData static file I wrote previously: UniBasic does not prevent you from writing out a record or ID with char(0) imbedded. It is a legal character. No guesses as to the cause of your particular issue. To assist in diagnosis, you can search your problem file for all occurances of char(0) in data records or keys using an option on 'guide'. For instance: guide -U0 PROBLEM.FILE.NAME option is -U followed by the ascii charcter number you want to search for. I should add that the information about characters found is in GUIDE_ERRORS.LIS. For instance: guide -U65 VOC (looking for 'A') pg GUIDE_ERRORS.LIS VOC File Integrity: Group 0, block 1, record number 0 = COL.SPACES has char(65) in key. Group 0, block 1, record number 1 = LIST.LABEL has char(65) in key. Group 0, block 1, record number 7 = STATS has char(65) in key. Group 0, block 1, record number 0 = COL.SPACES record has char(65) in data. Group 0, block 1, record number 1 = LIST.LABEL record has char(65) in data. ... (many more entries) Wally Terhune SWG Client Support - Information Management Software U2 Support Architect b IBM U2 Client Support Team 4700 S. Syracuse St., Denver, CO 80237 Tel: (303) 773-7969 T/L 656-7969 Mobile: (303) 807-6222 [EMAIL PROTECTED] Register today for the premier U2 technical event! [demime 1.01d removed an attachment of type image/jpeg which had a name of 08633156.jpg] [demime 1.01d removed an attachment of type image/jpeg which had a name of 08907059.jpg] --- 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/
Re: [U2] [UD] Possible causes of corrupt data on a UniData static file
Is guide only available on UD ? It does not work with UV (10.0). Is there a similar command available in UV? Thanks! Arnold Bosch IT Administrator Taeuber Corssen SWA (Pty) Ltd Tel +264 (0)61 293 2106 Cell +264 (0)81 124 8625 Fax +264 (0)61 293 2104 Email: [EMAIL PROTECTED] -- [EMAIL PROTECTED] wrote on 01/11/2007 23:14:16: I wrote previously: UniBasic does not prevent you from writing out a record or ID with char(0) imbedded. It is a legal character. No guesses as to the cause of your particular issue. To assist in diagnosis, you can search your problem file for all occurances of char(0) in data records or keys using an option on 'guide'. For instance: guide -U0 PROBLEM.FILE.NAME --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
