I'm having a bit of trouble following this, so let me restate what I think
you mean, to see if I've understood or misunderstood.

You have a application whose menus build and submit job streams. Instead of
streaming the jobs this way, you want to have an existing job stream, which
you can stream, that are exactly the same as the application builds. Is that
about right?

Now, do you still need help with this? While I know MPE, I am just learning
Linux and still a newbie. But I can still provide some analogies between the
two that might help. We have nothing native to MPE that is like cron, that
will always automatically stream jobs at certain times. We have a robust
scheduling facility, and you can easily write job streams or command files
which will automatically stream jobs. You can even have your system
automatically stream such a job at startup, or schedule such a job to run
daily or weekly or whatever you need. But there's no cron or crontab.

Our [log in to unmask] is where the outputs normally go, our "stdlists", rather
like the mail program for croned jobs. [log in to unmask] is, very much unlike
cron, where the text of a job stream lives, between the time that it is
streamed, and when it finishes run. We can stream a job to run at any date
and time (although 'now' is the default), and the existing job stream file
is essentially copied there, at that time.

Yes, you can, in various ways, raise priorities, or even just stop the
spooler, so that a streamed job will sit, not running, and you can examine
the [log in to unmask] I  imagine that you have been given several ways to do
this.

Others probably explained much of this. I hope that you will keep this
thread going on the 3000-L. We could do with just such a discussion.

Greg Stigers
http://www.cgiusa.com

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