RE: [U2] UV - Tracking file writes Unclassified}
Mike, > -Original Message- > From: [EMAIL PROTECTED] On Behalf Of Mike Randall > Sent: Thursday, 13 July 2006 05:46 > To: u2-users@listserver.u2ug.org > Subject: RE: [U2] UV - Tracking file writes > > A trigger would be an ideal method as it's non-intrusive to > your existing code. [snip] > Since your goal is to identify processes, the caveat would be > how to identify the process. The trigger is based strictly > on the file and doesn't really care what process initiated > it. Depending on your platform and how your system is put > together, @VERB or @SENTENCE might give you what you need or > you might have to come up with something different. I wonder what would be in the SYSTEM(9001) CALL Stack in a trigger program? It might be able to tell you exactly where you came from. Mike > > HTH > > Mike Randall 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] ODBC to Open Office
We are running UniData 6.0.12. We currently have ODBC and use it to import data into Excel. We are thinking of migrating to Open Office's Calc. What ODBC driver do I need to do this with? Anybody have any instructions? Thanks Albert L. DeWitt Jr. Senior Programmer Analyst Stylmark, Inc. (V) 763-574-8705 (F) 763-574-1052 [EMAIL PROTECTED] --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] UV - Tracking file writes
The UV SQL Reference manual gives a pretty good description. The odd part is cataloging the trigger program; if you're "pick" flavor, you'll need to create an "information" flavor CATALOG verb (although I don't remember if I was working on a Windows or Unix box?). Also, before the Trigger subroutine can Write to a file, it must first READU the record. And I think you need to be on UV 10.x to use triggers with "files". HTH, Mark -Original Message- I need to track all processes that write to a specific file. At one time I remember that you could set some type of trigger to do this. If someone could provided me the information on how to do this, or direct me to the documentation that covers this I would appreciate it. --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] UV - Tracking file writes
I use file triggers quite frequently to trace down problems with processes. You can find the documentation for this in the Universe SQL Reference manual. Jim Koca wrote: I need to track all processes that write to a specific file. At one time I remember that you could set some type of trigger to do this. If someone could provided me the information on how to do this, or direct me to the documentation that covers this I would appreciate it. Jim Koca --- 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: [U2] UV - Tracking file writes
A trigger would be an ideal method as it's non-intrusive to your existing code. There are some caveats though. Basically you'd create a UNIBASIC program that could have any logic you want. In your case, probably something that writes to an audit file. You then attach this program to your file via a CREATE.TRIGGER command most likely defining it as an UPDATE trigger (there are some rules and parameters that you can get from the docs). Since your goal is to identify processes, the caveat would be how to identify the process. The trigger is based strictly on the file and doesn't really care what process initiated it. Depending on your platform and how your system is put together, @VERB or @SENTENCE might give you what you need or you might have to come up with something different. HTH Mike Randall -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jim Koca Sent: Wednesday, July 12, 2006 1:15 PM To: u2-users@listserver.u2ug.org Subject: [U2] UV - Tracking file writes I need to track all processes that write to a specific file. At one time I remember that you could set some type of trigger to do this. If someone could provided me the information on how to do this, or direct me to the documentation that covers this I would appreciate it. Jim Koca --- 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/
[U2] UV - Tracking file writes
I need to track all processes that write to a specific file. At one time I remember that you could set some type of trigger to do this. If someone could provided me the information on how to do this, or direct me to the documentation that covers this I would appreciate it. Jim Koca --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] UODOTNET.DLL
Thank you all for your responses. I was hoping to avoid downloading the entire "Clients" package just for this DLL, which as I recall was something over 100MB, but it's time for me to get updated anyway. :) For me this is OK but I'm always hesitent to recommend that an end-user upgrade the clients package because it contains other non-.NET components (.NOT Dawn?). Since some MV vendors build around the older components and not the newer ones this is where someone is subject to DLL Hell if they upgrade the entire package just to get one file. Kendrew and Peter, my note about UO.NET as a wrapper stems from an experience I had where UO.NET threw an exception from a P/Invoke to UO. I trust it's different now and look forward to taking another look. Regards, Tony Nebula R&D --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] UODOTNET.DLL
Tony, As far as the two versions co-existing goes, it is possible, even in the same application (not simply however). If this is for different applications, then just make sure the correct assembly is in the bin directory. And finally, UO.NET is not a wrapper around the COM components; it is 100% managed code. Cheers KP > -Original Message- > From: [EMAIL PROTECTED] [mailto:owner-u2- > [EMAIL PROTECTED] On Behalf Of Tony Gravagno > Sent: Tuesday, July 11, 2006 6:57 PM > To: u2-users@listserver.u2ug.org > Subject: [U2] UODOTNET.DLL > > Please forgive a quick post being made without appropriate prior > investigation. I'm hoping someone will have a quick answer for what might > otherwise take several hours of research. > > I'm told there are two versions of UODOTNET.dll: > 2.1.0.7137 and 2.1.0.7149 > > Where can we get the new build? We may need this file for use with > another > project that was built with it. > > If UO.NET is managed code, can the two versions co-exist? I would assume > so since this is one of the big benefits of .NET. > > If UO.NET is a big wrapper around COM (which I believe it is), then might > there be a registration issue (DLL Hell) if the two cuts are > loaded/running > on the same system? > > Thanks! > Tony, TG@ remove.thisNebula-RnD.com > http:// we.really.dislike.spamNebula-RnD.com > New blog postings: http:// remove.this.partNebula-RnD.com/blog > --- > 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: [U2] UODOTNET.DLL
>If UO.NET is a big wrapper around COM (which I believe it is), then might >there be a registration issue (DLL Hell) if the two cuts are loaded/running >on the same system? I was under the impression that the UO.NET dll is a native .net dll, not a wrapper. There is no registration or COM components required when using the UO.NET dll. I've run projects on a system that has nothing but the UO.NET dll just sitting in the application directory without problems. "DLL Hell" is nowhere to be found. :) --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] Universe file size limits {Unclassified}
> Ok, since this is at least the 2nd time this has been brought up, can some give some examples > of "standard unix utilities that do not support files > > 2GB" ? Hasn't Linux had 2GB file support for, like 10 years? > Hasn't Windows had 2GB file support since W2K (assuming you are not using FAT16 partitions)? > I accept that if you are running a 5 year old version of your O/S you may encounter some problems. > But if you are reasonably current and patched, where are the land mines? AIX 5.1 (yes, it is a couple of years old) If one mans the following commands, you will see the message below: Tar/cpio: Note: 1. The [command above] command is not enabled for files greater than 2 Gig in size due to limitations imposed by XPG/4 and POSIX.2 standards. We used cpio all the time, now we use 'pax' on IBM's recommendation. Also, if you are using a third party backup solution confirm that whatever disk utility they use to backup the files supports >2G. We used Veritas NetBackup at the time and they said it was fine. We now use Tivoli Storage Manager. Steve Ferries --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] UODOTNET.DLL
>"You just need to add UODOTNET.dll into the > GAC on each >workstation/system that uses UniObjects.NET. I'm not > sure why IBM >don't do this as part of their SDK install..." I guess because using GAC is a pain in the backside if you want to use one-click publishing and automatic updates: yes I know you can fiddle about with the prerequisites. But requiring a separate install into the GAC rather pushes against the whole 'publish-and-forget' update model, which is one of the most useful things in .net. You should be able to quite happily distribute the uodotnet.dll as a copy local file: that works for me. I've spent too many hours trying to fix one-click references that have gone wrong. Regards Brian --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/