Hello.
Unidata 6.0.8
AIX 5.1
One of our programmers asked this question:
If I have this:
COMMAND = 'PROGRAM.A'
EXECUTE COMMAND CAPTRURING OUTPUT
Is there any way for 'PROGRAM.A' to sense that it is in capturing output
and stop the capture?
What we have is a case where an open file error may
I am kind of enjoying it.
Glenn W. Paschal [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
04/05/2004 10:53 PM
Please respond to U2 Users Discussion List
To: 'U2 Users Discussion List' [EMAIL PROTECTED]
cc:
Subject:RE: Modern Universe (TESTING)
Why is
Marco,
We just had this happen on Monday on Unidata 6.0.8 on AIX 5.1, we were
told to run udtdiag to colloect data about the state of Unidata and stop
and restart Unidata. There is no other way. Here is what Unidata support
told us:
This is very difficult to chase down. Usually associated with
Marco,
Also, you say you are on sb+ 5.4 and sbclient 5.3, we were told to always
have sb+ equal or below sbclient, not at a higher level. This would not
cause your current issue, but could cause you to have unpredictable
results in other applications. Just an FYI.
Thanks!
Marco Antonio
Yimi,
The first place I'd look would be file
performance. I am unfamiliar with Unidata on windows, but we use Unidata
on AIX-unix. I'd run guide on the file and see what it recommends as far
as sizing. You may have alot of overflow1 or even overflow2. Also, you
may want to utilize indexing as
