UniVerse already does that. The file name is capturexxxxxnn, where xxxxx is
the PID and nn is aa, ab, etc.

I do see one possible problem, though. I noticed the PID is masked to 5
digits, and today's systems can have 6 or more digits. Our engineering
staff would have to determine if that is a real problem or not.

This message occurs when it tries to reopen the capture file in UVTEMP.
Because we haven't seen this in-house, it is difficult to say, but perhaps
the file hasn't been flushed to disk yet at the time the attempt to reopen
it occurs. The reopen attempt is immediately after the close.

If the capture file is not needed, we recommend using HUSH ON and HUSH OFF
around the EXECUTE statement, which prevents the capture file from being
created, reducing I/O. This is helpful when many such CAPTURING clauses are
used in succession, but their output is not really needed by the
application.

Regards,

LeRoy F. Dreyfuss
Advanced Technical Services - U2 Technology Analyst
IBM U2 Data Management Solutions
Tel: 303-672-1254          Fax: 303-294-4832
Mobile: 720-341-4317
External email:  [EMAIL PROTECTED]
WWW:  http://www.ibm.com/software/data/u2/support

www.ibm.com/software/data/u2/support - Open, Query, Update, Search -
Online!

Don't miss out on the IBM DB2 Information Management Technical Conference
September 19-24, 2004 - Las Vegas, NV



             "Ray Wurlod"
             <[EMAIL PROTECTED]
             m>                                                         To
             Sent by:                  [EMAIL PROTECTED]
             [EMAIL PROTECTED]                                          cc
             stserver.u2ug.org
                                                                   Subject
                                       Re: [U2] capturing problem
             07/12/2004 07:37
             PM


             Please respond to
                 u2-users






Is your new machine too fast?  :)
Each process trying to create the same capture file?
Maybe you need to single thread this, perhaps using LOCK.
Definitely report it as a bug, though; multiple capture files with the same
date/time should get a different sequencer (the "aa" or "ab" on the end).

----- Original Message -----
From: Sara Burns <[EMAIL PROTECTED]>
Date: Mon, 12 Jul 2004 13:29:14 +1200
To: "U2 List ([EMAIL PROTECTED])" <[EMAIL PROTECTED]>
Subject: [U2] capturing problem

> What platform?
>
> We see this on AIX 4.3.3 and 5.2 when the machine is very lightly loaded
-
> early morning.  We create 3 phantoms in succession to start our
> communications from Oracle.  Usually one of these will not create the
> capture file.  It is not consistent.  We had not noticed it prior to
> changing to AIX (previously dynix on Sequent) using same process.
>
> Sara Burns
>
> Sara Burns (SEB)
> Development Team Leader
>
> Public Trust
> Phone: +64 (04) 474-3841 (DDI)
>
> Mobile: 027 457 5974
> < <mailto:[EMAIL PROTECTED]>
mailto:[EMAIL PROTECTED]>
>
> Information contained in this communication is confidential. If you are
not
> the intended recipient the information should not be used, disclosed,
copied
> or commercialised. The information is not necessarily the views nor the
> official communication of Public Trust. No guarantee or representation is
> made that the communication is free of errors, virus or interference.
> -------
> u2-users mailing list
> [EMAIL PROTECTED]
> To unsubscribe please visit http://listserver.u2ug.org/
-------
u2-users mailing list
[EMAIL PROTECTED]
To unsubscribe please visit http://listserver.u2ug.org/

[demime 1.01d removed an attachment of type image/gif which had a name of graycol.gif]

[demime 1.01d removed an attachment of type image/gif which had a name of pic16091.gif]

[demime 1.01d removed an attachment of type image/gif which had a name of ecblank.gif]
-------
u2-users mailing list
[EMAIL PROTECTED]
To unsubscribe please visit http://listserver.u2ug.org/

Reply via email to