DAG%SBPHY@LBL.ARPA (02/02/86)
I have a number of VAXen on a DECnet. One of these is VERY crowded (we
only had 3 minutes of NULL time last week) another one is hardly used at
all. Noticing this problem I decided to try and unload some of the jobs
on the loaded VAX. Because of the type of work done on the VAX the best
way to do this would be to have a queue that automatically executed jobs
on the second system, unfortunately three problems arise. I can think of
a few ways to implement this but none of them seem very good. I'm not sure
what to do if the batch job opens and closes files (the files will be on
another system). Finally, the two machines are in different buildings and
the only resonable way to DECnet them is via a 9600 asynchronous line so
I would like to limit the I/O.
It sounds like a fun problem doesn't it. If anyone has any suggestions
on the best way to move jobs from one VAX to another I would really appreciate
hearing from you. I would like to give people accounts on the second machine
but the type of work done won't really allow that. It is important that
the extra machine is as transparent to the users as possible.
Thanx in advance,
== Dag ==