JMS/3000 also has networking capability, but we don't use it (all our
copies are standalone), so I can't vouch for its functionality.

Lee Gunter
Regence BlueCross BlueShield of Oregon / Regence HMO Oregon
==========================================================
The opinions expressed, here, are mine and mine alone.



From: "Stigers, Greg [And]" <[log in to unmask]> on 05/05/99 09:17
      AM

Please respond to "Stigers, Greg [And]" <[log in to unmask]>


To:   [log in to unmask]
cc:    (bcc: Lee Gunter/BCBSO/TBG)
Subject:  Re: Job Scheduler for HP3000




X-no-Archive:yes
The 'same functionality' is the problem. Presumably, you want BETTER
functionality in some ways, whereas Maestro almost certainly has features
that you don't use at all. It becomes a question of which functions you
want.

One of the things that Maestro lets you do is control multiple,
heterogeneous systems from a Master system, talking to client software on
each controlled system. The current 6.1 version of Nobix JobPak lets you
control a schedule on another HP 3000 running another copy of JobPak,
across
NS. They have a character-based menuing system (which does not get along
well with QCTerm for reasons unknown) or a command line interface, but no
GUI. Since we are a customer, running JobPak on our production system only,
the Nobix folks were kind enough to send us a time-limited demo of their
product for our development system, so we could test and develop something
that they currently do not recommend, leaving the scheduler job up during
backup.

Carl, any chance of adding network support to MasterOp?