Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!lll-winken!uunet!cbmvax!grr
From: grr@cbmvax.UUCP (George Robbins)
Newsgroups: comp.unix.wizards
Subject: Re: uucp delivery order?
Message-ID: <7258@cbmvax.UUCP>
Date: 10 Jul 89 20:32:18 GMT
References: <454@amanue.UUCP>
Reply-To: grr@cbmvax.UUCP (George Robbins)
Organization: Commodore Technology, West Chester, PA
Lines: 26

In article <454@amanue.UUCP> jr@amanue.UUCP (Jim Rosenberg) writes:
> I asked this question once before & got a thundering silence -- sorry if I
> missed any replies, but I *still need to know*.  How can I guarantee that uucp
> will deliver jobs to a remote system in the order in which they were queued?
> More specifically, how can I issue a series of uux requests and be sure that
> the uuxqt at the remote end will execute them in the same order?  I have HDB
> at one end, and by the time the system is in production will have HDB at the
> other end too.  The system will be Sytem V.3 in production, if that makes any
> difference.

I'm not sure you can do what you want directly.  The traditional forms of
uucp had a "sequence file" what was somehow intended to allow uucp to
detect when a transfer got "lost".  This feature is almost entirely
unused.  I don't know that it would do quite what you want, or whether
is has survived in any usable form in HDB.

Most likely you will have to implement some kind of queueing system, where
the uux requrests simply drop that data into some kind of spool queue and
then some task has to analyze the queue and see which tasks have enough
input to run or which might need to request a resend or some nature of
manual intervention.

-- 
George Robbins - now working for,	uucp: {uunet|pyramid|rutgers}!cbmvax!grr
but no way officially representing	arpa: cbmvax!grr@uunet.uu.net
Commodore, Engineering Department	fone: 215-431-9255 (only by moonlite)