Re: [U2] TCL input and response logging such as COMO
The best options are probably: Security subroutines and named common switches (this was covered at U2U under Data Security and Best Practises Use wIntegrate thin client (more flexible and secure for this than the thick client) and log from the wIntegrate server using wIntegrate scripting. Are you sure you really want to do this ? If you implement this type of logging it is fairly easy to take down the service by filling your file system - a DOS attack. Ive seen different opinions from different compliance officers before. There has been some fairly inventive interpretation of guidelines and items that should be assessed as risks as being rules on what must be done. If you are going to log everything, then you should perform a risk assessment on how this exposes you. Remember that the logs themselves are a Data Protection time bomb and you will probably want to encrypt them securely and audit who can access and use the logs. Regards JayJay Sent from my iPad On 24 Apr 2013, at 21:34, Scott Zachary szach...@gardensalive.com wrote: For PCI compliance, we are tasked to log/capture all TCL entries and responses. I am familiar with COMO, which is one possible solution. 1) What other TCL logging methods are available in UniVerse besides COMO? 2) What AIX Unix tools are available to capture keyboard input and responses at TCL? -- View this message in context: http://u2-universe-unidata.1073795.n5.nabble.com/TCL-input-and-response-logging-such-as-COMO-tp40528.html Sent from the U2 - Users mailing list archive at Nabble.com. ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] TCL input and response logging such as COMO
On 24/04/13 22:54, Tom Whitmore wrote: Hi, Can you provide more information on what you are trying to capture? (edits, list commands, etc.) I suspect that you may be able to put security on the commands you are concerned with and address the problem with less pain. The problem with using the command stack or a COMO is that they are easily modifiable. You may want to consider using a Unix Tee to capture all output which isn't as easy to turn off. Having said that, I'm not a Unix expert so I can't offer the command string you should use but I'm sure someone will provide it. And if you're supposed to be logging power users, are they the sort of user who will know about the COMO command? It's not stackable, so if they have a genuine reason for wanting to use it (eg programming/debugging), they're going to innocently mess up your logging. Cheers, Wol ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] TCL input and response logging such as COMO
Hi. I'm with Tom on this - capturing EVERYTHING that EVERYONE types is a lot of data - much of it not interesting. May be smarter to identify the verbs that can actually cause 'change' and put them in a remote voc. That way you can put both preventive and detective controls on them as well. PRC can do this for you, too. (PRC is software configuration management / software life cycle management/ IT Governance for U2). This is crazy but .call me maybe! Susan Joslyn SJ+ Systems Associates, Inc. sjos...@sjplus.com (954-796-9868) Message: 6 Date: Wed, 24 Apr 2013 17:54:36 -0400 From: Tom Whitmore tewhitm...@ratex.com To: U2 Users List u2-users@listserver.u2ug.org Subject: Re: [U2] TCL input and response logging such as COMO Message-ID: BA2E471C9317804EB8470750F458BD9801EC7D8D3D38@public Content-Type: text/plain; charset=us-ascii Hi, Can you provide more information on what you are trying to capture? (edits, list commands, etc.) I suspect that you may be able to put security on the commands you are concerned with and address the problem with less pain. The problem with using the command stack or a COMO is that they are easily modifiable. You may want to consider using a Unix Tee to capture all output which isn't as easy to turn off. Having said that, I'm not a Unix expert so I can't offer the command string you should use but I'm sure someone will provide it. Tom Whitmore RATEX Business Solutions -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Scott Zachary Sent: Wednesday, April 24, 2013 4:35 PM To: u2-users@listserver.u2ug.org Subject: [U2] TCL input and response logging such as COMO For PCI compliance, we are tasked to log/capture all TCL entries and responses. I am familiar with COMO, which is one possible solution. 1) What other TCL logging methods are available in UniVerse besides COMO? 2) What AIX Unix tools are available to capture keyboard input and responses at TCL? ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] TCL input and response logging such as COMO
Hi maybe! -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Susan Joslyn Sent: Thursday, April 25, 2013 12:17 PM To: u2-users@listserver.u2ug.org Subject: Re: [U2] TCL input and response logging such as COMO Hi. I'm with Tom on this - capturing EVERYTHING that EVERYONE types is a lot of data - much of it not interesting. May be smarter to identify the verbs that can actually cause 'change' and put them in a remote voc. That way you can put both preventive and detective controls on them as well. PRC can do this for you, too. (PRC is software configuration management / software life cycle management/ IT Governance for U2). This is crazy but .call me maybe! Susan Joslyn SJ+ Systems Associates, Inc. sjos...@sjplus.com (954-796-9868) Message: 6 Date: Wed, 24 Apr 2013 17:54:36 -0400 From: Tom Whitmore tewhitm...@ratex.com To: U2 Users List u2-users@listserver.u2ug.org Subject: Re: [U2] TCL input and response logging such as COMO Message-ID: BA2E471C9317804EB8470750F458BD9801EC7D8D3D38@public Content-Type: text/plain; charset=us-ascii Hi, Can you provide more information on what you are trying to capture? (edits, list commands, etc.) I suspect that you may be able to put security on the commands you are concerned with and address the problem with less pain. The problem with using the command stack or a COMO is that they are easily modifiable. You may want to consider using a Unix Tee to capture all output which isn't as easy to turn off. Having said that, I'm not a Unix expert so I can't offer the command string you should use but I'm sure someone will provide it. Tom Whitmore RATEX Business Solutions -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Scott Zachary Sent: Wednesday, April 24, 2013 4:35 PM To: u2-users@listserver.u2ug.org Subject: [U2] TCL input and response logging such as COMO For PCI compliance, we are tasked to log/capture all TCL entries and responses. I am familiar with COMO, which is one possible solution. 1) What other TCL logging methods are available in UniVerse besides COMO? 2) What AIX Unix tools are available to capture keyboard input and responses at TCL? ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] TCL input and response logging such as COMO
Could also be a huge drag on your processors and storage. Lots of read/writes and at the unidata level, the block size,modulo and hash type. - Original Message - From: Susan Joslyn sjos...@sjplus.com To: u2-users@listserver.u2ug.org Sent: Thursday, April 25, 2013 1:17 PM Subject: Re: [U2] TCL input and response logging such as COMO Hi. I'm with Tom on this - capturing EVERYTHING that EVERYONE types is a lot of data - much of it not interesting. May be smarter to identify the verbs that can actually cause 'change' and put them in a remote voc. That way you can put both preventive and detective controls on them as well. PRC can do this for you, too. (PRC is software configuration management / software life cycle management/ IT Governance for U2). This is crazy but .call me maybe! Susan Joslyn SJ+ Systems Associates, Inc. sjos...@sjplus.com (954-796-9868) Message: 6 Date: Wed, 24 Apr 2013 17:54:36 -0400 From: Tom Whitmore tewhitm...@ratex.com To: U2 Users List u2-users@listserver.u2ug.org Subject: Re: [U2] TCL input and response logging such as COMO Message-ID: BA2E471C9317804EB8470750F458BD9801EC7D8D3D38@public Content-Type: text/plain; charset=us-ascii Hi, Can you provide more information on what you are trying to capture? (edits, list commands, etc.) I suspect that you may be able to put security on the commands you are concerned with and address the problem with less pain. The problem with using the command stack or a COMO is that they are easily modifiable. You may want to consider using a Unix Tee to capture all output which isn't as easy to turn off. Having said that, I'm not a Unix expert so I can't offer the command string you should use but I'm sure someone will provide it. Tom Whitmore RATEX Business Solutions -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Scott Zachary Sent: Wednesday, April 24, 2013 4:35 PM To: u2-users@listserver.u2ug.org Subject: [U2] TCL input and response logging such as COMO For PCI compliance, we are tasked to log/capture all TCL entries and responses. I am familiar with COMO, which is one possible solution. 1) What other TCL logging methods are available in UniVerse besides COMO? 2) What AIX Unix tools are available to capture keyboard input and responses at TCL? ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] TCL input and response logging such as COMO
Look at Centrify DirectControl and DirectAudit, we use them and they work pretty well. www.centrify.com -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of bradley.sch...@usbank.com Sent: Thursday, 25 April 2013 9:06 a.m. To: U2 Users List Subject: Re: [U2] TCL input and response logging such as COMO I can't speak for UV, but we've been required to log all sessions for specific powerful users. It becomes a little simpler if you do it for all users. Make sure you have some type of automated purge of whatever log files you create or you'll probably start filling up your file system. This is what we're doing under UD7.1. Nothing fancy. We added this to our LOGIN: PQ HRUN DIR COMO.PROG P And here's what's in COMO.PROG USERS = 'user1, user2, user3' IF INDEX(USERS,@LOGNAME,1) 0 THEN FN = @LOGNAME:'_':@USERNO:'_':DATE():'_':TIME() DATA FN EXECUTE 'COMO ON' END U.S. BANCORP made the following annotations - Electronic Privacy Notice. This e-mail, and any attachments, contains information that is, or may be, covered by electronic communications privacy laws, and is also confidential and proprietary in nature. If you are not the intended recipient, please be advised that you are legally prohibited from retaining, using, copying, distributing, or otherwise disclosing this information in any manner. Instead, please reply to the sender that you have received this communication in error, and then immediately delete it. Thank you in advance for your cooperation. - ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] TCL input and response logging such as COMO
I guess it depends on what legislation you must comply with for auditing purposes and what you can get away with. If you have to log everything then I'd agree that the unix tee command as others suggest would be best. The following works OK on our AIX dev box but there are a few strange terminal characters in the log file that might make parsing difficult and require some quality time with sed and/or awk. A log roll utility should also be employed to regularly compress and archive the resulting logs once they reach a certain size/age. $ `cat /.uvhome`/bin/uv | tee -a /var/uvlogs/user1.log If you just need to lock down and/or log the relevant UV verbs then remote VOC pointers will do the job. This might include a false TCL program invoked at login or when exiting from the menu (e.g. loop, input, log, execute, repeat) that just logs everything at TCL. Doctoring the TCL verbs for logging/security would require to disable break and possibly make exceptions for any phantoms and other background/batch jobs though which may be more effort to implement thoroughly. HTH Peter -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Scott Zachary Sent: Thursday, 25 April 2013 6:35 To: u2-users@listserver.u2ug.org Subject: [U2] TCL input and response logging such as COMO For PCI compliance, we are tasked to log/capture all TCL entries and responses. I am familiar with COMO, which is one possible solution. 1) What other TCL logging methods are available in UniVerse besides COMO? 2) What AIX Unix tools are available to capture keyboard input and responses at TCL? -- View this message in context: http://u2-universe-unidata.1073795.n5.nabble.com/TCL-input-and-response-logging-such-as-COMO-tp40528.html Sent from the U2 - Users mailing list archive at Nabble.com. ___ U2-Users mailing list U2-Users@listserver.u2ug.org 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 U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] TCL input and response logging such as COMO
If you have a COMO running, and you run some *other* process that itself starts a COMO, it will stomp on the first one :) -Original Message- From: Wols Lists antli...@youngman.org.uk To: u2-users u2-users@listserver.u2ug.org Sent: Thu, Apr 25, 2013 1:57 am Subject: Re: [U2] TCL input and response logging such as COMO On 24/04/13 22:54, Tom Whitmore wrote: Hi, Can you provide more information on what you are trying to capture? (edits, list commands, etc.) I suspect that you may be able to put security on the commands you are concerned with and address the problem with less pain. The problem with using the command stack or a COMO is that they are easily modifiable. You may want to consider using a Unix Tee to capture all output which isn't as easy to turn off. Having said that, I'm not a Unix expert so I can't offer the command string you should use but I'm sure someone will provide it. And if you're supposed to be logging power users, are they the sort of user who will know about the COMO command? It's not stackable, so if they have a genuine reason for wanting to use it (eg programming/debugging), they're going to innocently mess up your logging. Cheers, Wol ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] TCL input and response logging such as COMO
In UniVerse in the SAVEDLIST directory a user's TCL statements are saved as $$userid:user# Dan Goble | Senior Systems Engineer Interline Brands, Inc. 804 East Gate Drive Suite 100, Mount Laurel, NJ 08054 Office: 856.533.3110 | Mobile: 609.792.6855 E-mail: dan.go...@interlinebrands.com | Website: www.interlinebrands.com This e-mail and any files transmitted with it are confidential and intended solely for the individual or entity to whom they are addressed. Please notify the sender immediately by e-mail if you have received this e-mail in error and delete all copies of this message. -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Scott Zachary Sent: Wednesday, April 24, 2013 4:35 PM To: u2-users@listserver.u2ug.org Subject: [U2] TCL input and response logging such as COMO For PCI compliance, we are tasked to log/capture all TCL entries and responses. I am familiar with COMO, which is one possible solution. 1) What other TCL logging methods are available in UniVerse besides COMO? 2) What AIX Unix tools are available to capture keyboard input and responses at TCL? -- View this message in context: http://u2-universe-unidata.1073795.n5.nabble.com/TCL-input-and-response-logging-such-as-COMO-tp40528.html Sent from the U2 - Users mailing list archive at Nabble.com. ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] TCL input and response logging such as COMO
Capturing TCL entries and responses is not related to PCI compliance, which is only related to payment card uses. -Original Message- From: Scott Zachary szach...@gardensalive.com To: u2-users u2-users@listserver.u2ug.org Sent: Wed, Apr 24, 2013 1:45 pm Subject: [U2] TCL input and response logging such as COMO For PCI compliance, we are tasked to log/capture all TCL entries and responses. I am familiar with COMO, which is one possible solution. 1) What other TCL logging methods are available in UniVerse besides COMO? 2) What AIX Unix tools are available to capture keyboard input and responses at TCL? -- View this message in context: http://u2-universe-unidata.1073795.n5.nabble.com/TCL-input-and-response-logging-such-as-COMO-tp40528.html Sent from the U2 - Users mailing list archive at Nabble.com. ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] TCL input and response logging such as COMO
This is an automated response. Allen Bell will be out of town and unavailable until Monday, April 29th, 2013. On 4/24/2013 3:34 PM, Scott Zachary wrote: For PCI compliance, we are tasked to log/capture all TCL entries and responses. I am familiar with COMO, which is one possible solution. 1) What other TCL logging methods are available in UniVerse besides COMO? 2) What AIX Unix tools are available to capture keyboard input and responses at TCL? -- View this message in context: http://u2-universe-unidata.1073795.n5.nabble.com/TCL-input-and-response-logging-such-as-COMO-tp40528.html Sent from the U2 - Users mailing list archive at Nabble.com. ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] TCL input and response logging such as COMO
I can't speak for UV, but we've been required to log all sessions for specific powerful users. It becomes a little simpler if you do it for all users. Make sure you have some type of automated purge of whatever log files you create or you'll probably start filling up your file system. This is what we're doing under UD7.1. Nothing fancy. We added this to our LOGIN: PQ HRUN DIR COMO.PROG P And here's what's in COMO.PROG USERS = 'user1, user2, user3' IF INDEX(USERS,@LOGNAME,1) 0 THEN FN = @LOGNAME:'_':@USERNO:'_':DATE():'_':TIME() DATA FN EXECUTE 'COMO ON' END U.S. BANCORP made the following annotations - Electronic Privacy Notice. This e-mail, and any attachments, contains information that is, or may be, covered by electronic communications privacy laws, and is also confidential and proprietary in nature. If you are not the intended recipient, please be advised that you are legally prohibited from retaining, using, copying, distributing, or otherwise disclosing this information in any manner. Instead, please reply to the sender that you have received this communication in error, and then immediately delete it. Thank you in advance for your cooperation. - ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] TCL input and response logging such as COMO
Hi, Can you provide more information on what you are trying to capture? (edits, list commands, etc.) I suspect that you may be able to put security on the commands you are concerned with and address the problem with less pain. The problem with using the command stack or a COMO is that they are easily modifiable. You may want to consider using a Unix Tee to capture all output which isn't as easy to turn off. Having said that, I'm not a Unix expert so I can't offer the command string you should use but I'm sure someone will provide it. Tom Whitmore RATEX Business Solutions -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of bradley.sch...@usbank.com Sent: Wednesday, April 24, 2013 5:06 PM To: U2 Users List Subject: Re: [U2] TCL input and response logging such as COMO I can't speak for UV, but we've been required to log all sessions for specific powerful users. It becomes a little simpler if you do it for all users. Make sure you have some type of automated purge of whatever log files you create or you'll probably start filling up your file system. This is what we're doing under UD7.1. Nothing fancy. We added this to our LOGIN: PQ HRUN DIR COMO.PROG P And here's what's in COMO.PROG USERS = 'user1, user2, user3' IF INDEX(USERS,@LOGNAME,1) 0 THEN FN = @LOGNAME:'_':@USERNO:'_':DATE():'_':TIME() DATA FN EXECUTE 'COMO ON' END U.S. BANCORP made the following annotations - Electronic Privacy Notice. This e-mail, and any attachments, contains information that is, or may be, covered by electronic communications privacy laws, and is also confidential and proprietary in nature. If you are not the intended recipient, please be advised that you are legally prohibited from retaining, using, copying, distributing, or otherwise disclosing this information in any manner. Instead, please reply to the sender that you have received this communication in error, and then immediately delete it. Thank you in advance for your cooperation. - ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] TCL input and response logging such as COMO
Scott,
One thing that I've seen in use on unix systems is the script command. You
would put it in the user's .profile, or whatever startup script is executing
UV/UD. The syntax of the command would be script -c uv/ud command
logfile. Replace uv/ud command with the command that you use to start the
database of your choice and replace logfile with a unique log file name.
I've seen the unique filename generated with the date command, such as: date
+%F_%H-%M-%S.%N.
A simple example would be the following:
Contents of .profile:
Any OS setup goes here
logfile=/usr/local/audit.logs/${USER}-`date +%F_%H-%M-%S.%N`.log
cd /path/to/account
exec script -c /path/to/uv ${logfile}
-Mike
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Scott Zachary
Sent: Wednesday, April 24, 2013 4:35 PM
To: u2-users@listserver.u2ug.org
Subject: [U2] TCL input and response logging such as COMO
For PCI compliance, we are tasked to log/capture all TCL entries and responses.
I am familiar with COMO, which is one possible solution.
1) What other TCL logging methods are available in UniVerse besides COMO?
2) What AIX Unix tools are available to capture keyboard input and responses at
TCL?
--
View this message in context:
http://u2-universe-unidata.1073795.n5.nabble.com/TCL-input-and-response-logging-such-as-COMO-tp40528.html
Sent from the U2 - Users mailing list archive at Nabble.com.
___
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users
___
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] TCL input and response logging such as COMO
I've used unix/linux tee before, but not with UV. I think this might work, though: `cat /.uvhome`/bin/uv tee /dirname/filename 21 -John -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Tom Whitmore Sent: Wednesday, April 24, 2013 2:55 PM To: U2 Users List Subject: Re: [U2] TCL input and response logging such as COMO Hi, Can you provide more information on what you are trying to capture? (edits, list commands, etc.) I suspect that you may be able to put security on the commands you are concerned with and address the problem with less pain. The problem with using the command stack or a COMO is that they are easily modifiable. You may want to consider using a Unix Tee to capture all output which isn't as easy to turn off. Having said that, I'm not a Unix expert so I can't offer the command string you should use but I'm sure someone will provide it. Tom Whitmore RATEX Business Solutions -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of bradley.sch...@usbank.com Sent: Wednesday, April 24, 2013 5:06 PM To: U2 Users List Subject: Re: [U2] TCL input and response logging such as COMO I can't speak for UV, but we've been required to log all sessions for specific powerful users. It becomes a little simpler if you do it for all users. Make sure you have some type of automated purge of whatever log files you create or you'll probably start filling up your file system. This is what we're doing under UD7.1. Nothing fancy. We added this to our LOGIN: PQ HRUN DIR COMO.PROG P And here's what's in COMO.PROG USERS = 'user1, user2, user3' IF INDEX(USERS,@LOGNAME,1) 0 THEN FN = @LOGNAME:'_':@USERNO:'_':DATE():'_':TIME() DATA FN EXECUTE 'COMO ON' END U.S. BANCORP made the following annotations - Electronic Privacy Notice. This e-mail, and any attachments, contains information that is, or may be, covered by electronic communications privacy laws, and is also confidential and proprietary in nature. If you are not the intended recipient, please be advised that you are legally prohibited from retaining, using, copying, distributing, or otherwise disclosing this information in any manner. Instead, please reply to the sender that you have received this communication in error, and then immediately delete it. Thank you in advance for your cooperation. - ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
