> I recall reading > some blurb somewhere that although RQM is still supported by the > universe compiler it is in effect a NOP and doesn't actually do anything > on any platform.
Not true. On UniData, the documentation for RQM includes the following: " RQM is a synonym for the SLEEP function. For more information, see SLEEP." If you check TIME() or SYSTEM(12) before and after an RQM statement, you'll see that, without any parameters, RQM will generate a SLEEP 1. Although not documented as such for UniVerse, this will act the same way. Years back, I was working on Sequoia Pick O/A and was looking into a program that was suddenly taking a long time. I came across a bunch of RQM statements and talked to the programmer who was working on the program to see what they were all about. He said that they forced a screen flush so a record counter would be up to date. I slapped together a small test program and demonstrated that this was actually doing a one-second sleep, which was happening pretty frequently. (Well, yes, it did flush the screen, too.) I replaced all of the RQMs in the program with CRT CHAR(0):, which forced a screen flush on O/A, and the program sped up drastically. So anyway, this shouldn't be treated as a NOP. If you come across something like this in a program, get rid of it, unless the desired effect is actually to sleep for a second. I can't speak to other platforms, but for Pick O/A, UniData, and UniVerse, that's what you'll get. Tim Snyder Consulting I/T Specialist U2 Consulting North American Lab Services IBM Software Group ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
