HP3000-L Archives

April 2005, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Greg Stigers <[log in to unmask]>
Reply To:
Greg Stigers <[log in to unmask]>
Date:
Fri, 22 Apr 2005 17:16:55 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (22 lines)
We have a few jobs that stream other subordinate jobs, waiting for and
validating each job before streaming the next subordinate. Currently, we
rely on LIMIT and STREAM ;AT= to manage these jobstreaming jobs, streaming
the second such job five minutes after the first. Inevitably, the first job
will take more than five minutes, and the second job will begin streaming
its jobs, before the first is finished, with less than desirable results.
Remarkably, the larger design is not so ham-handed, such that simply
combining two such jobs is not an effective solution. Creating yet another
layer, an uber-stream to stream both jobstreaming jobs could work. The
objection to that is that it complicates this further than two levels, and
perhaps merely perpetuates a poor idea.

So, is there some clever solution that only requires MPE? We do not have
MPEX. We do not have a budget for solving this, and that does not mean that
we can spend as much as we want. I can only spend time, within reason. We
are evaluating MasterOp, and that may become our solution.

Greg Stigers

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2