In the 911 business a call taker must have the ability to enter something at any given time without having to wait. So we use a standard routine that we have used for over 20 years very successfully. This is our copyrighted routi
Nicholas M Gettino, Director of Professional Services & Support, EnRoute Emergency Systems an Infor Company, Concourse Center 1, 3501 East Frontage Rd, Suite 350, Tampa, FL 33607 -(813) 207-6998 direct, (813) 334-3507 cell, FAX (678) 393-5389 nick.gett...@enroute911.com or nick.gett...@infor.com -----Original Message----- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of u2-users-requ...@listserver.u2ug.org Sent: Wednesday, March 28, 2012 3:00 PM To: u2-users@listserver.u2ug.org Subject: U2-Users Digest, Vol 35, Issue 26 Send U2-Users mailing list submissions to u2-users@listserver.u2ug.org To subscribe or unsubscribe via the World Wide Web, visit http://listserver.u2ug.org/mailman/listinfo/u2-users or, via email, send a message with subject or body 'help' to u2-users-requ...@listserver.u2ug.org You can reach the person managing the list at u2-users-ow...@listserver.u2ug.org When replying, please edit your Subject line so it is more specific than "Re: Contents of U2-Users digest..." Today's Topics: 1. Re: Detecting idle time in INPUT statement. (Rex Gozar) 2. Re: Detecting idle time in INPUT statement. (Wjhonson) 3. Re: Detecting idle time in INPUT statement. (Rex Gozar) 4. Re: Detecting idle time in INPUT statement. (Wjhonson) 5. Re: Detecting idle time in INPUT statement. (George Gallen) 6. Re: Detecting idle time in INPUT statement. (Rex Gozar) 7. Re: Detecting idle time in INPUT statement. (Don Robinson) 8. Re: Detecting idle time in INPUT statement. (Don Robinson) 9. Re: Detecting idle time in INPUT statement. (Keith Johnson [DATACOM]) 10. Re: Detecting idle time in INPUT statement. (Wjhonson) 11. Re: Record lock (Charles Stevenson) 12. Job at Rocket in Denver (Wjhonson) 13. Re: Job at Rocket in Denver (Allen E. Elwood) 14. Re: Job at Rocket in Denver (George Gallen) 15. Re: Job at Rocket in Denver (George Gallen) 16. Re: Job at Rocket in Denver (Wjhonson) 17. Re: Job at Rocket in Denver (Brian Leach) 18. Re: Job at Rocket in Denver (Allen E. Elwood) 19. Re: Job at Rocket in Denver (Drew William Henderson) 20. Re: Job at Rocket in Denver (Symeon Breen) 21. Re: Job at Rocket in Denver (Wally Terhune) 22. AUTO: Asvin DATTANI is out of the office (returning 01/05/2012) (asvin.datt...@hsbcib.com) 23. Re: Job at Rocket in Denver (Bob Wyatt) 24. Re: Job at Rocket in Denver (Wally Terhune) 25. Re: Job at Rocket in Denver (Drew William Henderson) 26. Re: Job at Rocket in Denver (Bob Wyatt) 27. Re: Job at Rocket in Denver (Doug Averch) ---------------------------------------------------------------------- Message: 1 Date: Tue, 27 Mar 2012 15:30:09 -0400 From: Rex Gozar <rgo...@gmail.com> To: dgr...@dagconsulting.com, U2 Users List <u2-users@listserver.u2ug.org> Subject: Re: [U2] Detecting idle time in INPUT statement. Message-ID: <CA+zh1UxaK7=khfnnzuxuv14jn-vfr8xyr2mueawwo5mpcxc...@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 It does not matter if a system is old or not, you gotta keep it up to date. "Maintenance programming" means adding LOCKED clauses that should have been there in the first place. I doubt it would take more than a few hours; probably less time than writing and debugging some off-the-wall input timer routine. There probably aren't that many critical READU's. On my system, for the number of programs I have in the system, I only have a third as many READU's. rex ------------------------------ Message: 2 Date: Tue, 27 Mar 2012 15:37:48 -0400 (EDT) From: Wjhonson <wjhon...@aol.com> To: u2-users@listserver.u2ug.org, dgr...@dagconsulting.com Subject: Re: [U2] Detecting idle time in INPUT statement. Message-ID: <8ceda6839b9ef2e-b3c-4...@webmail-m138.sysops.aol.com> Content-Type: text/plain; charset="us-ascii" "On your system", as you said, versus in the rest of the programming world, where a programmer works for a manager, who works for another manager, who reports to a committee, who reports to the CEO, who gets funded by sometimes not so understanding money guys. Rex we don't have the luxury of being in the decision chair to make such changes :) That's the world. In addition to the non-hot-dog approach of actually testing your changes... on three hundred programs, or three thousand. -----Original Message----- From: Rex Gozar <rgo...@gmail.com> To: dgreen <dgr...@dagconsulting.com>; U2 Users List <u2-users@listserver.u2ug.org> Sent: Tue, Mar 27, 2012 12:30 pm Subject: Re: [U2] Detecting idle time in INPUT statement. It does not matter if a system is old or not, you gotta keep it up to ate. "Maintenance programming" means adding LOCKED clauses that hould have been there in the first place. I doubt it would take more han a few hours; probably less time than writing and debugging some ff-the-wall input timer routine. There probably aren't that many ritical READU's. On my system, for the number of programs I have in he system, I only have a third as many READU's. ex ______________________________________________ 2-Users mailing list 2-us...@listserver.u2ug.org ttp://listserver.u2ug.org/mailman/listinfo/u2-users ------------------------------ Message: 3 Date: Tue, 27 Mar 2012 15:46:24 -0400 From: Rex Gozar <rgo...@gmail.com> To: U2 Users List <u2-users@listserver.u2ug.org> Subject: Re: [U2] Detecting idle time in INPUT statement. Message-ID: <CA+zh1UwkTGg9+_GPhDkbiG=1xeyxw0jjxphsn1bmpd9jy+c...@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 The OP's system probably doesn't have three thousand READU statements; I'm willing to guess a few hundred. And out of that few hundred, maybe a dozen of those READU's block user access during normal day-to-day operation. And yet a CEO, manager, whatever wouldn't have a problem implementing some input-timing thingy? rex ------------------------------ Message: 4 Date: Tue, 27 Mar 2012 15:51:43 -0400 (EDT) From: Wjhonson <wjhon...@aol.com> To: u2-users@listserver.u2ug.org Subject: Re: [U2] Detecting idle time in INPUT statement. Message-ID: <8ceda6a2ba2dcda-b3c-4...@webmail-m138.sysops.aol.com> Content-Type: text/plain; charset="us-ascii" I believe he was discussing putting that on a *single* program, not every program. I would strongly advise against putting a creature like that on every program. That's the sort of change that can bring a fast machine to its knees. -----Original Message----- From: Rex Gozar <rgo...@gmail.com> To: U2 Users List <u2-users@listserver.u2ug.org> Sent: Tue, Mar 27, 2012 12:46 pm Subject: Re: [U2] Detecting idle time in INPUT statement. The OP's system probably doesn't have three thousand READU statements; 'm willing to guess a few hundred. And out of that few hundred, aybe a dozen of those READU's block user access during normal ay-to-day operation. And yet a CEO, manager, whatever wouldn't have problem implementing some input-timing thingy? rex ______________________________________________ 2-Users mailing list 2-us...@listserver.u2ug.org ttp://listserver.u2ug.org/mailman/listinfo/u2-users ------------------------------ Message: 5 Date: Tue, 27 Mar 2012 14:54:42 -0500 From: George Gallen <ggal...@wyanokegroup.com> To: U2 Users List <u2-users@listserver.u2ug.org> Subject: Re: [U2] Detecting idle time in INPUT statement. Message-ID: <be8d41dcf5c32d4c982de29a5d8838f705c4737...@dfw1mbx02.mex07a.mlsrvr.com> Content-Type: text/plain; charset="us-ascii" The tough part isn't so much the qty of but knowing which ones are the important Ones that will most likely be affected. Depending on the turnover of staff, the Current staff might not know the code that well, and pinpointing the top programs That should be converted first could be a shot in the dark. -----Original Message----- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Rex Gozar Sent: Tuesday, March 27, 2012 3:46 PM To: U2 Users List Subject: Re: [U2] Detecting idle time in INPUT statement. The OP's system probably doesn't have three thousand READU statements; I'm willing to guess a few hundred. And out of that few hundred, maybe a dozen of those READU's block user access during normal day-to-day operation. And yet a CEO, manager, whatever wouldn't have a problem implementing some input-timing thingy? rex _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ------------------------------ Message: 6 Date: Tue, 27 Mar 2012 15:57:12 -0400 From: Rex Gozar <rgo...@gmail.com> To: U2 Users List <u2-users@listserver.u2ug.org> Subject: Re: [U2] Detecting idle time in INPUT statement. Message-ID: <CA+zh1UzuD80usqu7s-dYGN=jtz+onbohgxxnmec_bcb-sk4...@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 He already has the use-case; someone in some specific screen/program is getting locked out. That's where you start. On Tue, Mar 27, 2012 at 3:54 PM, George Gallen <ggal...@wyanokegroup.com> wrote: > The tough part isn't so much the qty of but knowing which ones are the > important > Ones that will most likely be affected. Depending on the turnover of staff, > the > Current staff might not know the code that well, and pinpointing the top > programs > That should be converted first could be a shot in the dark. ------------------------------ Message: 7 Date: Tue, 27 Mar 2012 13:11:16 -0700 (PDT) From: Don Robinson <donr_w...@yahoo.com> To: U2 listserver <u2-users@listserver.u2ug.org> Subject: Re: [U2] Detecting idle time in INPUT statement. Message-ID: <1332879076.51999.yahoomail...@web39303.mail.mud.yahoo.com> Content-Type: text/plain; charset=iso-8859-1 David, ? Good idea. ? Revised code. ? * Don Robinson * Testing the INPUTIF statement. * PROMPT '' * ZZ = '' FOR X = 1 TO 100? ;* Loop for 10 seconds. ?? INPUTIF ZZ THEN EXIT ?? NAP 100 NEXT X * IF ZZ = '' THEN ?? CRT 'The user is sleeping....' ?? STOP? ;* Do whatever you want here. END ELSE * * User entered something, proceed as usual. * ?? CRT ?? CRT 'User entered: ': ZZ END * STOP END Thanks, Don Robinson From: David A. Green <dgr...@dagconsulting.com> To: 'Don Robinson' <donr_w...@yahoo.com>; 'U2 Users List' <u2-users@listserver.u2ug.org> Sent: Tuesday, March 27, 2012 2:31 PM Subject: RE: [U2] Detecting idle time in INPUT statement. Don, You should at least optimize the code by just checking a counter and not messing with TIME().? Your NAP command automatically takes care of the amount of time spent in each loop.? You just need to count how many NAPs it takes to equal the amount of wait time you wish to have. David A. Green (480) 813-1725 DAG Consulting _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
