RE: Fw: [U2] Unidata logging of BASIC Runtime errors {Unclassified}

2006-05-14 Thread HENDERSON MIKE, MR 
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 can do this, you just tweak the DOS verb to include an H in
 attribute 4 or 5. 

Changed Attribute 4 from TICERGM to TICERGMH

And it _does_ work, even stays there when the UV transaction is rolled
back.

Now, I wonder if I can get the SysAdmins to make that change in
Production ...
;-)

Mike

 
 Cheers
 
 Phil
 
 -Original Message-
 From: [EMAIL PROTECTED] On Behalf Of HENDERSON MIKE,
MR
 Sent: Friday, 12 May 2006 1:30 p.m.
 To: u2-users@listserver.u2ug.org
 Subject: 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.  Darn, it would have been really 
 useful otherwise.
 That's why we need a UV-supported method.
 
 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! :-) 
 
 
 Mike
 
  -Original Message-
  From: [EMAIL PROTECTED] 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 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 
  (any text, but most likely it's the offending program name) 
  /d = Description
  
  There are many other options (you can even specify a different 
  computer to send the event information to).
  
  Regards,
  
  Jim
  
The information contained in this Internet Email message is intended
for the addressee only and may contain privileged information, but not
necessarily the official views or opinions of the New Zealand Defence Force.
If you are not the intended recipient you must not use, disclose, copy or 
distribute this message or the information in it.

If you have received this message in error, please Email or telephone
the sender immediately.
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/

RE: Fw: [U2] Unidata logging of BASIC Runtime errors {Unclassified}

2006-05-12 Thread phil walker 
Mike,

You can do this, you just tweek the DOS verb to include and H in
attribute 4 or 5. 

Cheers

Phil

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of HENDERSON MIKE,
MR
Sent: Friday, 12 May 2006 1:30 p.m.
To: u2-users@listserver.u2ug.org
Subject: 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.  Darn, it would have been really useful
otherwise.
That's why we need a UV-supported method.

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! :-) 


Mike

 -Original Message-
 From: [EMAIL PROTECTED] 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 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 (any text, 
 but most likely it's the offending program name) /d = Description
 
 There are many other options (you can even specify a different 
 computer to send the event information to).
 
 Regards,
 
 Jim
 
 
 [snip]
 
 Yes, Yes, YES!
 CALL OSEventLog(Category, Type, EventID, DescriptionText)
 ---
 u2-users mailing list
 u2-users@listserver.u2ug.org
 To unsubscribe please visit http://listserver.u2ug.org/
 
The information contained in this Internet Email message is intended for
the addressee only and may contain privileged information, but not
necessarily the official views or opinions of the New Zealand Defence
Force.
If you are not the intended recipient you must not use, disclose, copy
or distribute this message or the information in it.

If you have received this message in error, please Email or telephone
the sender immediately.
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/

RE: Fw: [U2] Unidata logging of BASIC Runtime errors {Unclassified}

2006-05-11 Thread James Canale, Jr. 
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 (any text, but most likely it's the offending program name)
/d = Description

There are many other options (you can even specify a different computer to
send the event information to).

Regards,

Jim


[snip]

Yes, Yes, YES!
CALL OSEventLog(Category, Type, EventID, DescriptionText)
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/

RE: Fw: [U2] Unidata logging of BASIC Runtime errors {Unclassified}

2006-05-11 Thread HENDERSON MIKE, MR 
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.  Darn, it would have been really useful
otherwise.
That's why we need a UV-supported method.

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! :-) 


Mike

 -Original Message-
 From: [EMAIL PROTECTED] 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 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 
 (any text, but most likely it's the offending program name) 
 /d = Description
 
 There are many other options (you can even specify a 
 different computer to send the event information to).
 
 Regards,
 
 Jim
 
 
 [snip]
 
 Yes, Yes, YES!
 CALL OSEventLog(Category, Type, EventID, DescriptionText)
 ---
 u2-users mailing list
 u2-users@listserver.u2ug.org
 To unsubscribe please visit http://listserver.u2ug.org/
 
The information contained in this Internet Email message is intended
for the addressee only and may contain privileged information, but not
necessarily the official views or opinions of the New Zealand Defence Force.
If you are not the intended recipient you must not use, disclose, copy or 
distribute this message or the information in it.

If you have received this message in error, please Email or telephone
the sender immediately.
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/

Re: Fw: [U2] Unidata logging of BASIC Runtime errors {Unclassified}

2006-05-11 Thread Craig Bennett 

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'Reilly but my Safari tokens for the 
month are all used up.


Either way if its trivial using GCI it can't be that hard to build into 
U2 itself.


Craig
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/

RE: Fw: [U2] Unidata logging of BASIC Runtime errors {Unclassified}

2006-05-10 Thread HENDERSON MIKE, MR 
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 logged to syslog (every platform
except 
 windows) or the windows error logs?
  windows application event logs
Yes, please, we'll have some of that 

[snip]

 For bonus points expose the system logging functionality into U2
itself 
 so that application writers can also write to the system logs where
this 
 is appropriate.

Yes, Yes, YES!
CALL OSEventLog(Category, Type, EventID, DescriptionText)

 
 
 
 Craig
The information contained in this Internet Email message is intended
for the addressee only and may contain privileged information, but not
necessarily the official views or opinions of the New Zealand Defence Force.
If you are not the intended recipient you must not use, disclose, copy or 
distribute this message or the information in it.

If you have received this message in error, please Email or telephone
the sender immediately.
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/

Re: Fw: [U2] Unidata logging of BASIC Runtime errors {Unclassified}

2006-05-10 Thread Craig Bennett 

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 syslog.h

void OSEventLog(int priority, char* message){
syslog(priority, message);
}

If you wanted to get fancy you could even use openlog to specify an 
identifier, logging facility etc.


Come to think of it, I might suggest this one to the boss.

Craig
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/