Thanks Phil,
> -Original Message-
> From: [EMAIL PROTECTED] On Behalf Of phil walker
> Sent: Friday, 12 May 2006 19:37
> To: u2-users@listserver.u2ug.org
> Subject: RE: Fw: [U2] UniData logging of BASIC Runtime errors
> {Unclassified}
>
> Mike,
>
> You c
: RE: Fw: [U2] Unidata logging of BASIC Runtime errors
{Unclassified}
Thanks, Jim
That's brilliant ... Except it doesn't work in Transaction State because
you can't do a "DOS /c ...", you get a 'Verb "DOS" illegal when a
transaction is active' error. Dar
Mike,
But actually, if you're on UV 10.1 you can use the new GCI function
"UVRunCommand" [see Issue Number 5616 in the Release Notes] even in
transaction State.
Gee, another reason to upgrade! :-)
Or you could call the windows api functions directly from GCI.
I'd find you the reference in O'
ED] On Behalf Of
> James Canale, Jr.
> Sent: Friday, 12 May 2006 05:28
> To: u2-users@listserver.u2ug.org
> Subject: RE: Fw: [U2] Unidata logging of BASIC Runtime errors
{Unclassified}
>
> Well, for Windows platforms, you can do something like this
> (this is from ECL, but wi
gt;>>>>>>>>>>>>>>>
18 0 0
19 10812 19>>>>>>>>>>>>>>>>>>>
I have experimented with blocksize, KEYONLY, HASHTYPE of 1 and this was the
best I could do. I am sure that if I brought this fil
Well, for Windows platforms, you can do something like this (this is from
ECL, but with a tiny bit of code...):
:! eventcreate /t information /id 999 /l System /so MyModule /d "Error Test"
/t = ERROR | WARNING | INFORMATION
/id = Event ID
/l (lowercase L) = APPLICATION OR SYSTEM
/so = SourceName
Craig Bennett wrote:
Wally,
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.
As a UV user I don't mind what happens to UniData; but wouldn't it be
great if UV and UD logged to sys
Mike,
Yes, Yes, YES!
CALL OSEventLog(Category, Type, EventID, DescriptionText)
surely that one is easy using GCI? If you really want it
(excuse the unix version, can error logging from C be that much harder
in windows?)
#include
void OSEventLog(int priority, char* message){
syslog(prior
Craig,
> -Original Message-
> From: [EMAIL PROTECTED] On Behalf Of Craig Bennett
> Sent: Thursday, 11 May 2006 16:03
> To: u2-users@listserver.u2ug.org
> Subject: Re: Fw: [U2] UniData logging of BASIC Runtime errors
[snip]
> wouldn't it be great if UV and UD
log of it!
Ross Ferris
Stamina Software
Visage > Better by Design!
>-Original Message-
>From: [EMAIL PROTECTED] [mailto:owner-u2-
>[EMAIL PROTECTED] On Behalf Of Craig Bennett
>Sent: Thursday, 11 May 2006 2:03 PM
>To: u2-users@listserver.u2ug.org
>Subject: Re: Fw: [U2] U
Wally,
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.
As a UV user I don't mind what happens to UniData; but wouldn't it be
great if UV and UD logged to syslog (every platform ex
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 -
Well, we added file open error logging at one point and upset a lot of
folks - until we made it optional (which was the right thing to do...) :-(
Wally Terhune
U2 Support Architect
IBM Information Management
4700 South Syracuse Street, Denver, CO 80237
Tel: 303.773.7969
Fax: 303.773.5915
[EMAI
13 matches
Mail list logo
