Re: [U2] UD - Error Logging
Wally, I guess I'm the taker. There is this nice open source product called log4c. It can log to files, syslog or any other destinations. It is modeled after an open source product we use called log4j. It runs on HP, RedHat, Solaris, AIX, and Windows. But since it is open source, you can port it any other platform as well. Perhaps the best part is the logging levels (TRACE, DEBUG, INFO, WARN, ERROR, and FATAL). That adds standard granularity to the logging. Additionally you can reformat the logging into any format you want. You can control the size and the number of logs you want to keep. I pulled this from our log4j configuration on our U2WebLink middleware product: # Loggers log4j.logger.com.u2logic.XLr8U2Interface.U2WebLinkLogger=INFO,U2WebLinkFileA ppender log4j.logger.com.u2logic.XLr8U2Interface.XLr8ReplicatorLogger=INFO,XLr8Repli catorFileAppender log4j.logger.org.quartz=INFO,QuartzSchedulerFileAppender log4j.logger.org.directwebremoting=INFO,DirectWebRemotingFileAppender # # U2WebLink Log File Appender log4j.appender.U2WebLinkFileAppender=org.apache.log4j.RollingFileAppender log4j.appender.U2WebLinkFileAppender.File=logs/U2WebLink.log log4j.appender.U2WebLinkFileAppender.Append=true log4j.appender.U2WebLinkFileAppender.ImmediateFlush=true log4j.appender.U2WebLinkFileAppender.layout=org.apache.log4j.SimpleLayout log4j.appender.U2WebLinkFileAppender.MaxFileSize=1000KB log4j.appender.U2WebLinkFileAppender.MaxBackupIndex=10 What this means is your entire code must be changed to accommodate this new logging structure. Additionally, you could use standard tools for you log analysis instead of writing your own. We use an open source tool in Eclipse to analyze our logs that even allows us to see them live over the internet. Regards, Doug -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Wally Terhune Sent: Monday, March 15, 2010 8:06 PM To: U2 Users List Subject: Re: [U2] UD - Error Logging I would be happy to entertain (and formally register) a detailed, coherent proposal for logs, error logs, diagnostic logs - location and management. Do you still want the saved_logs directory concept? (20 or configurable? Iterations saved) What happens at 'startud'? Anything happen at 'stopud'? Is the trunclog command useful? Should the detailed UniBasic run-time error message logging provided by 7.2.0 /usr/ud72/include/msglevelconfig be placed separate from udt.errlog? Should RFS have a separate log for error messages? Should RFS Archiving - have a separate log for offload messages? Client/server debug logs are inconsistent in configuration and activation. What would you propose in this area? Locations must be discoverable by tools that collect information for diagnostics (such as udtdiag). What else am I missing? Whereas I am constantly requesting more usable content of the messages, can we just focus on the overall architecture for this specific proposal? This would be something to be considered by PM for UniData.NEXT and prioritized with the rest of the enhancements. Other venues for proposals such as this are u2-users better and better forum and the UniData CAB (just recently formed by PM). Any takers? Regards, Wally Terhune U2 Support Architect Rocket Software 4700 S. Syracuse Street, Suite 400 **Denver, CO 80237 **USA Tel: +1.720.475.8055 Email: wterh...@rs.com Web: www.rocketsoftware.com/u2 ___ 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] UD - Error Logging
Far be it from me to suggest how they actually implement the logging in the code base, but it is hard to go past the log4* libraries. -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Doug Sent: Tuesday, 23 March 2010 7:53 AM To: 'U2 Users List' Subject: Re: [U2] UD - Error Logging Wally, I guess I'm the taker. There is this nice open source product called log4c. It can log to files, syslog or any other destinations. It is modeled after an open source product we use called log4j. It runs on HP, RedHat, Solaris, AIX, and Windows. But since it is open source, you can port it any other platform as well. Perhaps the best part is the logging levels (TRACE, DEBUG, INFO, WARN, ERROR, and FATAL). That adds standard granularity to the logging. Additionally you can reformat the logging into any format you want. You can control the size and the number of logs you want to keep. I pulled this from our log4j configuration on our U2WebLink middleware product: # Loggers log4j.logger.com.u2logic.XLr8U2Interface.U2WebLinkLogger=INFO,U2WebLinkF ileA ppender log4j.logger.com.u2logic.XLr8U2Interface.XLr8ReplicatorLogger=INFO,XLr8R epli catorFileAppender log4j.logger.org.quartz=INFO,QuartzSchedulerFileAppender log4j.logger.org.directwebremoting=INFO,DirectWebRemotingFileAppender # # U2WebLink Log File Appender log4j.appender.U2WebLinkFileAppender=org.apache.log4j.RollingFileAppende r log4j.appender.U2WebLinkFileAppender.File=logs/U2WebLink.log log4j.appender.U2WebLinkFileAppender.Append=true log4j.appender.U2WebLinkFileAppender.ImmediateFlush=true log4j.appender.U2WebLinkFileAppender.layout=org.apache.log4j.SimpleLayou t log4j.appender.U2WebLinkFileAppender.MaxFileSize=1000KB log4j.appender.U2WebLinkFileAppender.MaxBackupIndex=10 What this means is your entire code must be changed to accommodate this new logging structure. Additionally, you could use standard tools for you log analysis instead of writing your own. We use an open source tool in Eclipse to analyze our logs that even allows us to see them live over the internet. Regards, Doug -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Wally Terhune Sent: Monday, March 15, 2010 8:06 PM To: U2 Users List Subject: Re: [U2] UD - Error Logging I would be happy to entertain (and formally register) a detailed, coherent proposal for logs, error logs, diagnostic logs - location and management. Do you still want the saved_logs directory concept? (20 or configurable? Iterations saved) What happens at 'startud'? Anything happen at 'stopud'? Is the trunclog command useful? Should the detailed UniBasic run-time error message logging provided by 7.2.0 /usr/ud72/include/msglevelconfig be placed separate from udt.errlog? Should RFS have a separate log for error messages? Should RFS Archiving - have a separate log for offload messages? Client/server debug logs are inconsistent in configuration and activation. What would you propose in this area? Locations must be discoverable by tools that collect information for diagnostics (such as udtdiag). What else am I missing? Whereas I am constantly requesting more usable content of the messages, can we just focus on the overall architecture for this specific proposal? This would be something to be considered by PM for UniData.NEXT and prioritized with the rest of the enhancements. Other venues for proposals such as this are u2-users better and better forum and the UniData CAB (just recently formed by PM). Any takers? Regards, Wally Terhune U2 Support Architect Rocket Software 4700 S. Syracuse Street, Suite 400 **Denver, CO 80237 **USA Tel: +1.720.475.8055 Email: wterh...@rs.com Web: www.rocketsoftware.com/u2 ___ 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 __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ ### The information transmitted in this message and attachments (if any) is intended only for the person or entity to which it is addressed. The message may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer
Re: [U2] UD - Error Logging
Nothing prevents us from using syslog right? Ive been thinking about logging a lot lately. Specifically, syslog-ng or rsyslog. Any unix db should log to syslog. ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] UD - Error Logging
We use syslog in UniData and UniVerse to log all kinds of application events. Best regards, Henry Henry P. Unger Hitech Systems, Inc. http://www.hitech.com -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Steve Romanow Sent: Tuesday, March 16, 2010 12:06 PM To: u2-users@listserver.u2ug.org Subject: Re: [U2] UD - Error Logging Nothing prevents us from using syslog right? Ive been thinking about logging a lot lately. Specifically, syslog-ng or rsyslog. Any unix db should log to syslog. ___ 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] UD - Error Logging
Wally, Just because I have not noticed anyone else responding to your question about the saved_logs, yes, please keep that concept - I, for one, end up checking the saved_logs quite a bit when I get calls after the client has already rebooted in order to get their users working again. I would hate to see all that good data go away! I would think that a configurable number of iterations would be optimal, given that your team would be going in and doing a lot of work here anyway. Just my 2 cents! Susan Lynch F. W. Davison Company, Inc. - Original Message - From: Wally Terhune wterh...@rocketsoftware.com To: U2 Users List u2-users@listserver.u2ug.org Sent: 03/15/2010 10:06 PM Subject: Re: [U2] UD - Error Logging I would be happy to entertain (and formally register) a detailed, coherent proposal for logs, error logs, diagnostic logs - location and management. Do you still want the saved_logs directory concept? (20 or configurable? Iterations saved) What happens at 'startud'? Anything happen at 'stopud'? Is the trunclog command useful? Should the detailed UniBasic run-time error message logging provided by 7.2.0 /usr/ud72/include/msglevelconfig be placed separate from udt.errlog? Should RFS have a separate log for error messages? Should RFS Archiving - have a separate log for offload messages? Client/server debug logs are inconsistent in configuration and activation. What would you propose in this area? Locations must be discoverable by tools that collect information for diagnostics (such as udtdiag). What else am I missing? Whereas I am constantly requesting more usable content of the messages, can we just focus on the overall architecture for this specific proposal? This would be something to be considered by PM for UniData.NEXT and prioritized with the rest of the enhancements. Other venues for proposals such as this are u2-users better and better forum and the UniData CAB (just recently formed by PM). Any takers? Regards, Wally Terhune U2 Support Architect Rocket Software 4700 S. Syracuse Street, Suite 400 **Denver, CO 80237 **USA Tel: +1.720.475.8055 Email: wterh...@rs.com Web: www.rocketsoftware.com/u2 ___ 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] UD - Error Logging
Steve: What's wrong with syslog? We use Windows. I don't have a problem with UD logging to the event log, but many applications log to their own standard area. UD logging needs to be configured, so having that in the same area would be nice too. cross-platform? I suspect, all U2 logging should configure in one location/directory and write to one location/directory. Every logging needs archiving and I understand @UDTHOME/bin/saved_logs does that, although @UDTHOME/logs/saved_logs would be a better location. It could be nice to have a structure like: @UDTHOME + config + logs + saved_logs ...and one could have an environment variable names @UDTCONF and @UDTLOGS where one could offload these directories somewhere else. Bill Steve Romanow said the following on 3/16/2010 12:05 PM: Nothing prevents us from using syslog right? Ive been thinking about logging a lot lately. Specifically, syslog-ng or rsyslog. Any unix db should log to syslog. ___ 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] UD - Error Logging
Does anyone know why most of the various UniData logs are in the @UDTHOME/bin directory? Why aren't they in the @UDTHOME/log directory? Maybe there's a @UDTLOG environment variable? Thanks, Bill ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] UD - Error Logging
Bill, That is where in Engineers put them originally. Makes no sense today nor did it years ago when I worked there. Also, you have many ways to turn on the severity of each log as well as getting logs for non-daemons. I put in a request last year to fix this. No business case, so it was rejected. Regards, Doug -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Bill Haskett Sent: Monday, March 15, 2010 4:37 PM To: U2 Mail List Subject: [U2] UD - Error Logging Does anyone know why most of the various UniData logs are in the @UDTHOME/bin directory? Why aren't they in the @UDTHOME/log directory? Maybe there's a @UDTLOG environment variable? Thanks, Bill ___ 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] UD - Error Logging
A business case, eh? How about any world-class dbms must have consistent, comprehensive, and easily configurable error logging. If U2 doesn't have this then it needs to get it...period! Every one of us in the applications market know we have to incorporate basic industry functionality (plus logging) into our application, otherwise we eventually lose business. Why doesn't this rule apply to UD? Because they can blow us off and tell us to migrate to UniVerse? (Perhaps I'm being a little unfair.) Just IMHO, of course. :-) Bill Doug Averch said the following on 3/15/2010 5:16 PM: Bill, That is where in Engineers put them originally. Makes no sense today nor did it years ago when I worked there. Also, you have many ways to turn on the severity of each log as well as getting logs for non-daemons. I put in a request last year to fix this. No business case, so it was rejected. Regards, Doug -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Bill Haskett Sent: Monday, March 15, 2010 4:37 PM To: U2 Mail List Subject: [U2] UD - Error Logging Does anyone know why most of the various UniData logs are in the @UDTHOME/bin directory? Why aren't they in the @UDTHOME/log directory? Maybe there's a @UDTLOG environment variable? Thanks, Bill ___ 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
Re: [U2] UD - Error Logging
I've made the same complaint and pretty much feel like I received an 'eye roll' of 'who would be that stupid...' My argument was how easy it would be to have someone shut down their systems by deleting required files while trying to clean up log files that are stored in bin... That would SEEM to be a rational business case. But I got the impression we're likely to never see that fixed... David W. -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Bill Haskett Sent: Monday, March 15, 2010 8:05 PM To: U2 Mail List Subject: Re: [U2] UD - Error Logging A business case, eh? How about any world-class dbms must have consistent, comprehensive, and easily configurable error logging. If U2 doesn't have this then it needs to get it...period! Every one of us in the applications market know we have to incorporate basic industry functionality (plus logging) into our application, otherwise we eventually lose business. Why doesn't this rule apply to UD? Because they can blow us off and tell us to migrate to UniVerse? (Perhaps I'm being a little unfair.) Just IMHO, of course. :-) Bill Doug Averch said the following on 3/15/2010 5:16 PM: Bill, That is where in Engineers put them originally. Makes no sense today nor did it years ago when I worked there. Also, you have many ways to turn on the severity of each log as well as getting logs for non-daemons. I put in a request last year to fix this. No business case, so it was rejected. Regards, Doug -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Bill Haskett Sent: Monday, March 15, 2010 4:37 PM To: U2 Mail List Subject: [U2] UD - Error Logging Does anyone know why most of the various UniData logs are in the @UDTHOME/bin directory? Why aren't they in the @UDTHOME/log directory? Maybe there's a @UDTLOG environment variable? Thanks, Bill ___ 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 ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] UD - Error Logging
Of course log files belong in the bin directory! I get tripped up every second time I got hunting for them... -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of David Wolverton Sent: Tuesday, 16 March 2010 12:12 PM To: 'U2 Users List' Subject: Re: [U2] UD - Error Logging I've made the same complaint and pretty much feel like I received an 'eye roll' of 'who would be that stupid...' My argument was how easy it would be to have someone shut down their systems by deleting required files while trying to clean up log files that are stored in bin... That would SEEM to be a rational business case. But I got the impression we're likely to never see that fixed... David W. -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Bill Haskett Sent: Monday, March 15, 2010 8:05 PM To: U2 Mail List Subject: Re: [U2] UD - Error Logging A business case, eh? How about any world-class dbms must have consistent, comprehensive, and easily configurable error logging. If U2 doesn't have this then it needs to get it...period! Every one of us in the applications market know we have to incorporate basic industry functionality (plus logging) into our application, otherwise we eventually lose business. Why doesn't this rule apply to UD? Because they can blow us off and tell us to migrate to UniVerse? (Perhaps I'm being a little unfair.) Just IMHO, of course. :-) Bill Doug Averch said the following on 3/15/2010 5:16 PM: Bill, That is where in Engineers put them originally. Makes no sense today nor did it years ago when I worked there. Also, you have many ways to turn on the severity of each log as well as getting logs for non-daemons. I put in a request last year to fix this. No business case, so it was rejected. Regards, Doug -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Bill Haskett Sent: Monday, March 15, 2010 4:37 PM To: U2 Mail List Subject: [U2] UD - Error Logging Does anyone know why most of the various UniData logs are in the @UDTHOME/bin directory? Why aren't they in the @UDTHOME/log directory? Maybe there's a @UDTLOG environment variable? Thanks, Bill ___ 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 ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ ### The information transmitted in this message and attachments (if any) is intended only for the person or entity to which it is addressed. The message may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer. The intended recipient of this e-mail may only use, reproduce, disclose or distribute the information contained in this e-mail and any attached files with the permission of IMB. ### ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] UD - Error Logging
I would be happy to entertain (and formally register) a detailed, coherent proposal for logs, error logs, diagnostic logs - location and management. Do you still want the saved_logs directory concept? (20 or configurable? Iterations saved) What happens at 'startud'? Anything happen at 'stopud'? Is the trunclog command useful? Should the detailed UniBasic run-time error message logging provided by 7.2.0 /usr/ud72/include/msglevelconfig be placed separate from udt.errlog? Should RFS have a separate log for error messages? Should RFS Archiving - have a separate log for offload messages? Client/server debug logs are inconsistent in configuration and activation. What would you propose in this area? Locations must be discoverable by tools that collect information for diagnostics (such as udtdiag). What else am I missing? Whereas I am constantly requesting more usable content of the messages, can we just focus on the overall architecture for this specific proposal? This would be something to be considered by PM for UniData.NEXT and prioritized with the rest of the enhancements. Other venues for proposals such as this are u2-users better and better forum and the UniData CAB (just recently formed by PM). Any takers? Regards, Wally Terhune U2 Support Architect Rocket Software 4700 S. Syracuse Street, Suite 400 **Denver, CO 80237 **USA Tel: +1.720.475.8055 Email: wterh...@rs.com Web: www.rocketsoftware.com/u2 ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] UD - Error Logging
Location, if fixed: $UDTHOME/log[s]/server/ $UDTHOME/log[s]/client/ This allows client and server logging to be on separate mount points if the admin desires, without needing the configuration options If configurable, just make the parameter a path relative to $UDTHOME Saved_logs: Yes. Saved_logs is the right concept. Having it either in the log[s] directory or configurable relative to $UDTHOME would be an acceptable option. Trunclog: I do believe it is useful. We have at least 1 application here that would have benefitted from this command. One caveat, however. Having the possibility of log data being lost is not acceptable in a production environment. Maybe instead of 'trunclog' a 'SwitchOutLog' would be better. This would instead to processes that are logging to close there current log file, move it out to the saved_logs directory and open a new one. A slightly more complex solution of writing to a temporary log file while the trunclog/switchoutlog was in process would prevent data loss without causing a system to pause while the logs are processed. RFS: Having RFS logging separate would make any automation of monitoring them easier to tune. If something is considered a separate sub-system, it should either have its own log file, or the log file contents should be structured in a manner where the particular sub-system in question can be found in a consistent manner/location. I cannot really speak about RFS logging however, as we are not running it so I have no idea of the volume of logging data being generated. This isn't a detailed proposal (or perhaps even coherent), as I'm not sure work would be happy with me doing it on the clock, but it is some general ideas on the architecture. Regards, Dan -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Wally Terhune Sent: Tuesday, 16 March 2010 1:06 PM To: U2 Users List Subject: Re: [U2] UD - Error Logging I would be happy to entertain (and formally register) a detailed, coherent proposal for logs, error logs, diagnostic logs - location and management. Do you still want the saved_logs directory concept? (20 or configurable? Iterations saved) What happens at 'startud'? Anything happen at 'stopud'? Is the trunclog command useful? Should the detailed UniBasic run-time error message logging provided by 7.2.0 /usr/ud72/include/msglevelconfig be placed separate from udt.errlog? Should RFS have a separate log for error messages? Should RFS Archiving - have a separate log for offload messages? Client/server debug logs are inconsistent in configuration and activation. What would you propose in this area? Locations must be discoverable by tools that collect information for diagnostics (such as udtdiag). What else am I missing? Whereas I am constantly requesting more usable content of the messages, can we just focus on the overall architecture for this specific proposal? This would be something to be considered by PM for UniData.NEXT and prioritized with the rest of the enhancements. Other venues for proposals such as this are u2-users better and better forum and the UniData CAB (just recently formed by PM). Any takers? Regards, Wally Terhune U2 Support Architect Rocket Software 4700 S. Syracuse Street, Suite 400 **Denver, CO 80237 **USA Tel: +1.720.475.8055 Email: wterh...@rs.com Web: www.rocketsoftware.com/u2 ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ ### The information transmitted in this message and attachments (if any) is intended only for the person or entity to which it is addressed. The message may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer. The intended recipient of this e-mail may only use, reproduce, disclose or distribute the information contained in this e-mail and any attached files with the permission of IMB. ### ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
