My application is creating some bogus records in a file, somewhere...we
are unable to pinpoint when where what the user is doing to create
these records, but they're popping up every couple of weeks.
I'd like to create a trigger to tell me when these records appear so
that someone gets
I've had similar problems. I put together a program to track changes.
This is for UniData.
SUBROUTINE TRIGGER.CHANGES(EXECSTAT,DICTFLAG,FILENAME,RECID,RECORD)
* program: TRIGGER.CHANGES
* programmer : Bruce M. Neylon
* Date : 07/17/06
*
* Description: Track TRANS changes
*
*
We have successfully used this approach several times to find out what
program was causing the problem. We used the call stack and also some
info in our named commons to write to a debug file that we created for
this process. We used to use dummy indexes to debug this type of
problem. But
OPOS works on a pc, I have not seen it work through Unix. There is a jpos
(java opos), I don't know anything about jpos.
Feel free to contact me off-line.
Tom
RATEX Business Solution
www.ratex.com
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
Been spending a bit of time with Unidata 7.1 and XDOM support and I have to
say that I'm disappointed, frustrated, and really quite concerned.
With a simple hand-constructed XML document, everything seems to work pretty
well. Throw any xmlns namespaces into the mix and, well, things get
It's looking like Windoze is gonna have to be the way to gothis is for
offsite anyway
so, that actually isn't too bad.
Since OPOS seems to be an active-x componant, I'm wondering if I can use
javascript and
design a few local pages to process the scanning (which can be tied to the
I have never used the XDOM stuff in anger - i tend to define extraction
files and whiz through the xml using READXMLDATA etc. We have had problems
with namespaces in the past - it does ring a bell, i will take a look at
what our problem was.
-Original Message-
From:
Hi All,
I am trying to capture the output from an EXECUTE statement on a command
line program but nothing is being captured, even though I know there is some
output.
Here is the command
CMD = 'C:\usr\lib\sendmail -t ':EMAIL.TEMPFILE:''
EXECUTE DOS /c:CMD CAPTURING TRASH
