In UniData (on Windows) this is pretty simple. First you create an
environment variable for the como file (e.g. MY_COMO) that points to the
directory under which you've created a _PH_ directory and a D__PH_
dictionary file. Then you create a VOC item as follows:
_PH_
001 DIR
002 @MY_COMO\_PH_
003 @MY_COMP\D__PH_
...to include in every account's VOC file. This will now act as a
centralized "como" repository. I do this with the _HOLD_ directory, as
everyone on our machines share the same spooler file, and each spooler
file name is a unique ".txt" file. I'm sure it would be even easier on
a "nix" machine. :-)
Bill
------------------------------------------------------------------------
----- Original Message -----
*From:* [email protected]
*To:* U2 Users List <[email protected]>
*Date:* 1/23/2013 6:31 PM
*Subject:* Re: [U2] Universal COMO
Hi Will,
I think the biggest *con* you might come up against will be concurrency issues
with multiple processes writing to the one central location.
If you had a solution where each session log is unique amongst all processes
then that would work very well.
You will still need to clean it out though whether it be one big centralised dir or one
for each account. As others have indicated, and if you run a unix box, then an
overnight cron job to find and clean out any &COMO& dirs older than a set
number of days would an option for you. I would suggest that you identify any logs that
were important historically to you and roll them first. Probably zipping them up and
moving them to an archive area would be viable. Google may even cough up a log rotate
script that you could adapt.
Regards,
Peter
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Wjhonson
Sent: Thursday, 24 January 2013 4:28
To: [email protected]
Subject: [U2] Universal COMO
By default, Universe will create several files in each account you create. Like &SAVEDLISTS&,
and &ED&... one of these default files is &COMO& which is where you can stick session
logs.
We use this constantly to monitor the output of phantoms, for review and
debugging the next day. The logs are emailed to myself and some other
programmers here.
By altering the VOC entries in the accounts, we could have a central, universal
COMO for all accounts, instead of one for each account.
I see a *pro* in this, for the ease of cleaning up old logs from years ago,
obviously no longer needed, which can be done from the O/S level. What might
be a *con* ?
Will Johnson
_______________________________________________
U2-Users mailing list
[email protected]
http://listserver.u2ug.org/mailman/listinfo/u2-users
-------------------------------------------------------------------------------
Note:
This email (inc all attachments) is for the use of the intended recipient(s)
only.
Privileged or confidential information may be contained in this communication.
If you have received this email in error, please notify the sender immediately
and then delete all copies of this message from your computer network. If you
are not the intended recipient, you must not keep, use, disclose, copy or
distribute this email without the author's prior permission. If you are the
intended recipient and you do not wish to receive similar electronic messages
from us in future, then please respond to the sender to this effect.
We have taken precautions to minimise the risk of transmitting software
viruses, but advise you to carry out your own virus checks on this email and
its attachments. We do not accept liability for any loss or damage caused by
software viruses and do not represent that this transmission is free from
viruses or other defects.
Firstmac Limited (ABN 59 094 145 963) (AFSL 290600)
-------------------------------------------------------------------------------
_______________________________________________
U2-Users mailing list
[email protected]
http://listserver.u2ug.org/mailman/listinfo/u2-users
_______________________________________________
U2-Users mailing list
[email protected]
http://listserver.u2ug.org/mailman/listinfo/u2-users
