A blink error occurs when the internal linkage between records becomes inconsistent. Specifically, the backward link of a record no longer references the location from which you just came in the file. For instance, recordA forward links(flinks) to recordB which forward links to recordC. In this scenerio, recordC also backward links (blinks) to recordB, which backward links to recordA. This is considered to have link consistency.
I believe when I coded this all up (back in the dark ages it seems!) and made blink verification mandatory (flink verification was already of this state), I added the "internal data error" tag to indicate that this wasn't a message that should be ignored (though for years prior we had blink values in record headers and never verified them without issue - but that's a whole other story). The blink verification simply takes the last location (in our above example that would be the location of recordA) and XOR's that value with the size of the current record (which would be recordB). That computed value should match the blink value stored in the header of recordB. If it doesn't match you get that nifty message showing computed and actual blink values along with the "internal data error" message and you are aborted out to fix the file (using uvfixfile, filepeek or whatever handy tool you choose - assuming you know how to fix it). Disregarding hardware problems, one cause of blink loss is due to group splitting. This happens in both static and dynamic files, but since dynamic files have more internal movement of data during balancing they tend to exhibit blink loss more often. Usually this occurs when records are rebalanced from one group into another - this is generally just a copy of the data from one place to another, but sometimes I've seen occurence where the flink's are updated, yet the first blink in the new group is incorrect. I believe there are quite a number of people who are pretty adept at repairing these things - just understanding what the message means can help you determine what to do next. Good luck! =+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+= "I reject your reality and substitute my own" - Adam Savage Glenn M. Herbert - Connectivity Development Engineer Information Integration Solutions, IBM Software Group 50 Washington Street Westboro, MA 01581 508-599-7281 direct "Debster" <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 02/23/2006 08:37 AM Please respond to [email protected] To <[email protected]> cc Subject RE: [U2] Access IBM Knowledge base/Blink Error Yeah but yesterday I was seeking information on an "Blink error" with the ominous "internal data error" clause added in both the U2 and AIX areas and was unable to find anything. Anyone have a clue as to what this might be? ~ Debbie ~~~~~~~~~~~~ "Anyone can hold the helm when the sea is calm" -Syrus Publilius www.infinite-systems.net -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Ross Ferris Sent: Thursday, February 23, 2006 3:53 AM To: [email protected] Subject: RE: [U2] Access IBM Knowledge base I have a case in point at the moment - trying to access an article to remind myself on how to use "fnuxi" on ALL files in a directory .... the information is there, but ... (reminders gratefully accepted :) Ross Ferris Stamina Software Visage > Better by Design! >-----Original Message----- >From: [EMAIL PROTECTED] [mailto:owner-u2- >[EMAIL PROTECTED] On Behalf Of Vance, Kathy >Sent: Thursday, 23 February 2006 8:23 AM >To: [email protected] >Subject: [U2] Access IBM Knowledge base > >All, > >I remember we had a discussion on the accessibility to the IBM knowledge >base several weeks ago. Yesterday, I received my IBM user ID from our >vendor (tech support), which allows me to view the locked articles in >IBM KB. I believe this user list has very positive impact on this move >made by IBM. IBM KB should be opened to everybody, I think. > >I would like to thank the people for their hard working in order to >maintain this user mail list. The list is a wonderful place for us to >share our knowledge. Meanwhile, it provides a communication channel so >that IBM could hear our voices. I have learnt a lot from the others via >the list. > >Kathy >------- >u2-users mailing list >[email protected] >To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
