SV: [U2] Newest UV UniDebugger

2006-04-06 Thread bjorn.eklund
I have a similar problem. I have a support case with IBM on this right now. I'll get back when I have a solution Bjvrn Eklund -Ursprungligt meddelande- Fren: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] leslie chamberlin Skickat: den 5 april 2006 21:48 Till: Nick Cipollina; [EMAIL

Re: [U2] Newest UV UniDebugger

2006-04-06 Thread Symeon Breen
I do use it all the time and have encountered numerous problems, with breakpoints, also in using run to cursor. If you do get into a muddle and reset does not work you can do Session-show duel session. This is the actual session in debug, so you can then do E or whatever command you need + you can

RE: [U2][UD] Logout/Logoff/? Udtno/Pid

2006-04-06 Thread David Wolverton
If you started the process, type !stopudt {pidno} At an ECL prompt. Not a 'pretty' way to stop it, but it is a sure kill. David W. UD Ver 7.1.0 PE on Win 2000 Server: I have been unable to find a way to logoff/logout/otherwise disconnect a

RE: [U2][UD] Logout/Logoff/? Udtno/Pid

2006-04-06 Thread colin.alfke
I received this from IBM a while back on the differences between stopudt and deleteuser: stopudt pid will log ANY user out of unidata by allowing any current write to complete and prevent any subsequent operations for that pid deleteuser will attempt a graceful kill equivalent to the unix kill

[U2] TIME

2006-04-06 Thread Nancy Fisher
Windows 2003 / UniVerse 10+ We recently expanded into a different time zone! Our server time is syncronized to pacific time (daylight savings or not). Now we have electronic timecards as well as many other entry processes being performed in a Mountain Time Zone. Of course all of the processes

Re: [U2] [UD] phantom processing

2006-04-06 Thread John Hester
Adrian Merrall wrote: On Unix/Linux I have modded the startud/stopud script in $UDTBIN but of course I will have to redo after each upgrade. It would be nice if the startud/stopud scripts provided an options for us to specify any scripts we wanted to run after startup/before shutdown (e.g.

RE: [U2] TIME

2006-04-06 Thread Bob Woodward
My suggestion would be, since everything is currently written for a single time zone, is to store everything in GMT then for reports/displays/whatever, you can prompt for a timezone to convert to. This way you're only updating programs instead of converting database structure to add a timezone

RE: [U2][UD] Ctrl-Break Key(s)?

2006-04-06 Thread Eric Armstrong
Dave, Have you tried MASTER BREAK user.no ? -Original Message- From: Dave Taylor [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 05, 2006 6:21 PM To: u2-users@listserver.u2ug.org Subject: [U2][UD] Ctrl-Break Key(s)? UD 7.1.0 PE on Win 2000 Server The Env_Var INIT_BREAKOFF is not set

Re: [U2] TIME

2006-04-06 Thread Gordon J Glorfield
Nancy, The best practice on this is to standardize on a single time zone. In your circumstance, due to your legacy systems, perhaps standardizing on PT may be the best course. However, if there are future expansions into other time zones in the works a change to GMT as a standard may work

RE: [U2] [UV]write failure question

2006-04-06 Thread Donnie Jacobs
What was the value of ID (include any non-printing characters)? That was my first thought. In the else clause, we wrote the key and record using an OPENSEQ/WRITEBLK combination and verified the resulting unix file using the od -cx command in Unix. Everything was exactly as expected. ---

RE: [U2] TIME

2006-04-06 Thread results
Nancy, I would keep the time stored as-is. I can't stress enough that you don't want to store it based on local time. Just tweak it on output. That solves your interstate trucker issues. 12:01 PM to 4:01 PM is four hours 100% of the time if you store based in a single time zone. There

RE: [U2] TIME

2006-04-06 Thread Stewart Leicester
Good advice. I've been through this several times, the last required entry and reporting to time zones around the world, a task for which -- unfortunately -- the original system was not designed. A possible transition approach: shut down external entry, convert all date/times in the DB to

Re: [U2] TIME

2006-04-06 Thread Nancy Fisher
Thanks for all the help and suggestions. I believe we are going to standardize on Pacific Time... Nancy Fisher Peninsula Truck Lines, Inc Auburn, Washington 253/929-2040 [EMAIL PROTECTED] - Original Message - From: Gordon J Glorfield [EMAIL PROTECTED] To: u2-users@listserver.u2ug.org

RE: [U2] TIME

2006-04-06 Thread Don Verhagen
I have to agree. We are in 4 times zones in the US and 2 Daylight Savings Time (Arizona and parts of Indiana do not observe DST). We store all our DATES and times in EST. You have to always include the DATE when dealing with time because 04/04/2006 12:30AM PST is 04/03/2006 11:30PM MST (notice

RE: [U2] Newest UV UniDebugger

2006-04-06 Thread David Jordan
Hi Symeom To increase the timeout of uniobjects, modify the unirpcservices files Locate the unirpcservices file in the account that UniVerse is installed \ibm\unishared\unirpc Create a backup copy of the file unirpcservices It should look something like this. uvnet /usr/ibm/uv/bin/uvnetd

RE: [U2] TIME

2006-04-06 Thread John Cassidy
For a good time, as if you have time to waste, visit /usr/share/lib/zoneinfo/src. So what time is it at the South Pole? John Cassidy Unix Sys Admin DCCCD Don Verhagen [EMAIL PROTECTED] 04/06/06 2:50 PM I have to agree. We are in 4 times zones in the US and 2 Daylight Savings Time (Arizona

Re: [U2][UD] Logout/Logoff/? Udtno/Pid

2006-04-06 Thread Dave Taylor
Bill and Others, !stopudt works like a champ! Thanks very much, Dave Dave Taylor President Sysmark Information Systems, Inc. 49 Aspen Way Rolling Hills Estates, CA 90274 800-SYSMARK (800-797-6275) (O) 310-544-1974 (C) 310-561-5200 (P) 800-339-1497 (F) 310-377-3550 Your Source for Integrated