|
This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. -- [ Picked text/plain from multipart/alternative ] Andy, I am very concerned about how the corruption had occurred also. But it seems that the majority of the corruption and probably all of it occured during a conversion since the data goes up to 1999. This was a S36 package and still uses mostly S36 Cobol. Recently though we have been implementing the reporting process in Sequel which is SQL based and when we encounter one of these situations it generates huge joblogs. I was able to fix the particular field that I had problems with using SQL for an update. statement follows: UPDATE NCTPFT16/"T16.COAD" SET ODAAMT = 0 WHERE hex(odaamt) = '0000000000' As I indicated prior the field contains all hex 0's and should have the F as the low position. So as I staed I have been able to find a solution to my problem. Thanks again. Ron -----Original Message----- From: Andy Nolen-Parkhouse [mailto:aparkhouse@attbi.com] Sent: Tuesday, August 27, 2002 10:28 AM To: midrange-l@midrange.com Subject: RE: Fixing bad data in a numeric field Ron, Perhaps the easiest method would be to write a simple program which would examine the hex data within the field (redefine the field to character data) and then update the last byte to x'0F'. I assume that you are referring only to the last byte of a packed field. Having a value of x'00' in the middle of a packed field is normal. Can you give an example of the hex value of a bad field? What is it? What should it be? I would be concerned about how such corruption could occur. Regards, Andy Nolen-Parkhouse > On Behalf Of Klein, Ron > Subject: Fixing bad data in a numeric field > > Hi All, > I have encountered a lot of numeric fields that contain bad data. In > specific these are packed fields that have a value of Hex'00' in them. So > I > need to change them to Hex'0F'. Any suggestions on how I can accomplish > this. TIA > Ron _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.