As a test, a co-worker suggested I see if the time increased with multiple sessions.
Again, udt'd into demo account, issued quit command: 1 session = 3 seconds 2 sessions = 5-6 seconds 4 sessions = 14 seconds 8 sessions = 1st ended at 21 seconds, 2nd at 35, 3rd at 40, then last couple cleaned up by 50 seconds. I don't necessarily think it matters that they were all logged in as me, but they were, in case that sparks anything for anyone. I DO think it matters that they were all trying to logout at the same time. I currently have 16 record locks, none of them are mine. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Bill Haskett Sent: Thursday, June 24, 2010 9:14 AM To: U2 Users List Subject: Re: [U2] UniData 'QUIT' Kevin: Quit may be in UV but it's the "off" command in UniData. I've had to remove it from our application and replaced it with "off", which cleans up our application, then quits. I suspect SB+ doing something similar with "quit" by replacing the default verb with their version. Bill ------------------------------------------------------------------------ Kevin King said the following on 6/24/2010 8:56 AM: > John has an interesting point. I thought QUIT was UV but looking into the > system in front of me right now it appears to be an SB+ thing running SH.OFF > out of DMSH. So that makes me wonder if the file size of DMSECURITY or > DMCONT or one of those DM files might be having an impact? > _______________________________________________ > 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 _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users
