Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.BERKELEY.EDU
Path: utzoo!decvax!ittatc!dcdwest!sdcsvax!ucbvax!PS2.CS.CMU.EDU!Dale.Moore
From: Dale.Moore@PS2.CS.CMU.EDU
Newsgroups: mod.computers.vax
Subject: sleep()
Message-ID: <8607021216.AA17402@ucbvax.Berkeley.EDU>
Date: Tue, 1-Jul-86 13:12:40 EDT
Article-I.D.: ucbvax.8607021216.AA17402
Posted: Tue Jul  1 13:12:40 1986
Date-Received: Thu, 3-Jul-86 00:36:17 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 21
Approved: info-vax@sri-kl.arpa


Bill Bogstad writes...
>	I actually had to program in FORTRAN (heaven forbid) on VMS and
> had to do the equivalent of a Unix sleep() call.  Sounds reasonable
>right?  Hah!  After spending 3-4 hours wading through the VMS manuals I
>discover that I have to do a "scheduled wakeup" for my process and then
>a "hibernate".  Of course there are optional arguments to both calls
>which I have to decipher.  In addition, I have to call a special routine
>to generate the correct arguement to the wakeup call.  Now, I realize
>that this is somewhat similiar to the internals of the Unix sleep()
>function, but isn't it nicely packaged?  You give it a number and your
>program pauses for the required number of seconds.  Obviously not
>everything is conceptually this easy, but when it is why make it so
>hard to do?

Why didn't you use LIB$WAIT (seconds)?  The VMS runtime library
routine LIB$WAIT places the current process into hibernation for the
number of seconds specified in its argument.  It is not really as
hard as you make it out to be.

	Dale.Moore@PS2.CS.CMU.EDU