RE: [U2] [UV] - Getting the call stack trace within a program

2007-09-05 Thread Bernard Lubin
: [U2] [UV] - Getting the call stack trace within a program I posted the following when SYSTEM(9001) was invented. It's gotta be in the archives somewhere. I recently added it to the newly developing U2UG Wiki, along with a table of other un- or poorly documented uses of SYSTEM(n), sorted by said n

RE: [U2] [UV] - Getting the call stack trace within a program

2007-09-04 Thread Bernard Lubin
Thanks to every one who answered so promptly to my query. It is just what I was looking for. Rgds Bernard Lubin Development Department Reynolds and Reynolds --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/

RE: [U2] [UV] - Getting the call stack trace within a program

2007-09-04 Thread Stevenson, Charles
I posted the following when SYSTEM(9001) was invented. It's gotta be in the archives somewhere. I recently added it to the newly developing U2UG Wiki, along with a table of other un- or poorly documented uses of SYSTEM(n), sorted by said n. Most info I gleaned from u2-users list archives. Some

[U2] [UV] - Getting the call stack trace within a program

2007-09-03 Thread Bernard Lubin
I would like to write a program that will enable me to identify which program has modified our master file. I have a generic program that issues the write command, but would like to know what program/subroutine called this generic program. Alternatively, I am also looking at putting a trigger on

RE: [U2] [UV] - Getting the call stack trace within a program

2007-09-03 Thread Symeon Breen
] [UV] - Getting the call stack trace within a program I would like to write a program that will enable me to identify which program has modified our master file. I have a generic program that issues the write command, but would like to know what program/subroutine called this generic program

RE: [U2] [UV] - Getting the call stack trace within a program

2007-09-03 Thread Womack, Adrian
Checkout SYSTEM(9001) - this should return what you're after. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bernard Lubin Sent: Monday, 3 September 2007 3:47 PM To: u2-users@listserver.u2ug.org Subject: [U2] [UV] - Getting the call stack trace within

RE: [U2] [UV] - Getting the call stack trace within a program

2007-09-03 Thread phil walker
: Monday, 3 September 2007 9:45 p.m. To: u2-users@listserver.u2ug.org Subject: RE: [U2] [UV] - Getting the call stack trace within a program In Unidata it is system(49) Not sure what number it is in uv but it is a system function call. Rgds Symeon. -Original Message- From: [EMAIL

Re: [U2] [UV] - Getting the call stack trace within a program

2007-09-03 Thread Brett Callacher
:[EMAIL PROTECTED] On Behalf Of Bernard Lubin Sent: 03 September 2007 08:47 To: u2-users@listserver.u2ug.org Subject: [U2] [UV] - Getting the call stack trace within a program I would like to write a program that will enable me to identify which program has modified our master file. I have

RE: [U2] [UV] - Getting the call stack trace within a program

2007-09-03 Thread Perry Taylor
:[EMAIL PROTECTED] On Behalf Of phil walker Sent: Monday, September 03, 2007 6:00 AM To: u2-users@listserver.u2ug.org Subject: RE: [U2] [UV] - Getting the call stack trace within a program SYSTEM(9001) from memory. A multvalued array with the stack level, program and address in multivalues if my memory