So - we are starting our planning cycle for the next release of UniData
now.
Is this something that there is a ground-swell of support for?
If so - what would it look like?
All or nothing switch? UDT.OPTIONS? udtconfig setting? environment
variable? All users? Just selected users?
New log name - eg unibasic.errlog vs udt.errlog?
Some limit to the number logged before shutting it off? (concern about log
size and filling disk?)
ALL UniBasic run-time errors or warnings logged - regardless of fatality?
Just some class of errors? Is so - how would you define the ones you want
logged?
Collect your thoughts and funnel them thru the U2UG Better and Better
committee...
That is likely a better way than flooding this list. Just my
recommendation.
Wally Terhune
U2 Support Architect
IBM Information Management
4700 South Syracuse Street, Denver, CO 80237
Tel: 303.773.7969
Fax: 303.773.5915
[EMAIL PROTECTED]
----- Forwarded by Wally Terhune/Denver/IBM on 05/10/2006 05:27 PM -----
"Bill Haskett"
<[EMAIL PROTECTED]
os.net> To
Sent by: <[email protected]>
[EMAIL PROTECTED] cc
stserver.u2ug.org
Subject
[U2] Unidata logging of BASIC
05/10/2006 04:07 Runtime errors
PM
Please respond to
[EMAIL PROTECTED]
er.u2ug.org
Dave:
UniData does not have logging for BASIC runtime errors (IBM got back with
me
on this). There aren't enough requests for this feature to include it in
UniData. :-(
Bill Haskett
-------
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
pic00485.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/