From:	SMTP%"Leonard@Craw.TGV.COM"  9-JAN-1995 10:35:39.74
To:	EVERHART
CC:	
Subj:	Re: async notification of file arriving wanted.

From: leonard@telcom.arizona.edu (Aaron Leonard)
X-Newsgroups: comp.os.vms
Subject: Re: async notification of file arriving wanted.
Date: 8 Jan 1995 05:23:12 GMT
Organization: TGV, Inc., or just me at home
Lines: 27
Sender: leonard@Maggie.Telcom.Arizona.EDU (Aaron Leonard)
Distribution: world
Message-ID: <3enss0$j47@news.CCIT.Arizona.EDU>
Reply-To: Leonard@Craw.TGV.COM
NNTP-Posting-Host: maggie.telcom.arizona.edu
X-Newsreader: mxrn 6.18-18
To: Info-VAX@Mvb.Saic.Com
X-Gateway-Source-Info: USENET


In article <5W07QxU.cslewis@delphi.com>, Cary Lewis <cslewis@delphi.com> writes:
|I have the following problem:
| 
|An UNIX machine (SCO or DG/UX) connected via a TCP/IP link to a VAX
|running VMX. These two machines will be transferring work files to each other.

[ ... ]

|I would like to devise a notification scheme whereby the arrival of a new
|work file causes the machine to kick into action.
 
[ ... ]

|Can anyone suggest a notification scheme that consists of two processes
|being blocked (one on each machine) that unblock when a file is transferred,
|or deleted, or permissions are changed.

There's a little old program called WFILE (on Arizona.EDU, in 
ua_source:[wfile], that) basically just waits till a file becomes
existent + accessible, then exits so that a DCL stream can do
its thing.  This might be helpful.

Aaron

Aaron Leonard           MultiNet-VMS@Support.TGV.COM [ work ]
                        Leonard@Leonard.Tucson.AZ.US [ home ]