Wirt writes
> rule: "Never use an asynchronous solution."

Agreed.  Now I know my linear example using e3k's on both sides was not
quite on target, and uses "legacy" tech, but doesn't it make the MOST sense
to avoid any and all tricks, too?

If the entire process is controlled a step at a time by one script /
jobstream / whatchacallit, how can there be any timing issues?  "Nothing can
go wrong!"

Is there some feature of the hp9000 which prevents it from, via a jobstream
or whatever they're called in 9000ese, logging onto the 3000, running
suprtool, creating the file, then transferring that file to the 9000, then
logging off the 3000, then proceeding merrily with processing the
transferred file?

this seems obvious, so I'm obviously missing something.

Tracy Pierce

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