Perhaps it is a problem, perhaps not. Have you corrected the blink error?
If you are finding you have blink issues on a somewhat frequent basis,
perhaps the focus is not in the right place? I might be trying to ascertain
why my files are becoming damaged and worry about how BASIC deals with it
after the corruption is taken care of. That takes the pressure of you and
allows you to reproduce the BASIC concern in a controlled environment for
support.

I am not convinced hiding behind ON ERROR when file corruption is detected
is the right thing to do. But, someday putting a toggle in uvconfig might
make everyone happy. Perhaps someday.


Regards,

LeRoy F. Dreyfuss
Advanced Technical Services - U2 Technology Analyst
IBM U2 Data Management Solutions
Tel: 303-672-1254          Fax: 303-294-4832
Mobile: 720-341-4317
External email:  [EMAIL PROTECTED]
WWW:  http://www.ibm.com/software/data/u2/support

www.ibm.com/software/data/u2/support - Open, Query, Update, Search -
Online!

Don't miss out on the IBM DB2 Information Management Technical Conference
September 19-24, 2004 - Las Vegas, NV



             Craig Bennett
             <[EMAIL PROTECTED]
             au>                                                        To
             Sent by:                  [EMAIL PROTECTED]
             [EMAIL PROTECTED]                                          cc
             stserver.u2ug.org
                                                                   Subject
                                       Re: [U2] [UV] File corruption
             07/26/2004 05:05          error, but ON ERROR branch not
             PM                        taken


             Please respond to
                 u2-users






Leroy,

>>But Leroy, the program neither aborts nor takes the ON ERROR branch, it
>>takes the ELSE branch and continues.
>
> That might be a problem. I guess you see something in the errlog file,
but
> does anything display on the screen? If so, then perhaps that is a
problem.
> The code is a bit tricky and blink errors are tested a bit deep in it,
but
> it should probably be a non-recoverable fatal error that drops to TCL
> regardless of the clause used.
>
> On the other hand, it is coded such that it takes the ELSE clause,
probably
> not being set as fatal. it has also been that way since blink checking
was
> added to UV, and that has been for quite a few years. I am not sure why
> this behavior is a problem now.

The user sees a message, there is an entry in errlog and then it takes
the ELSE branch -- as you say, a problem. I have a case open with
techsupport in Australia and hope to supply them with more information
today.


regards,


Craig
-------
u2-users mailing list
[EMAIL PROTECTED]
To unsubscribe please visit http://listserver.u2ug.org/

[demime 1.01d removed an attachment of type image/gif which had a name of graycol.gif]

[demime 1.01d removed an attachment of type image/gif which had a name of pic08619.gif]

[demime 1.01d removed an attachment of type image/gif which had a name of ecblank.gif]
-------
u2-users mailing list
[EMAIL PROTECTED]
To unsubscribe please visit http://listserver.u2ug.org/

Reply via email to