On Wed, 24 May 1995, Jeff Vance wrote:
 
> But ,I think that most shops that run both 3000s and, say, 9000s aren't using
> OpC. Do you just maintain completely separate views of the two platforms?  Do
> you have 2 staff teams -- one for hp-ux and one for MPE?  Or, one team that
> know the quirks of both platforms?  Have you written your own tools to better
> integrate the management of the two platforms?  Are there other 3rd party
> solutions that help you manage both platforms?
>
 
   IMHO, I would think that it would be more cost effective to have a
team that is fluent in both MPE and UNIX semantics.  In my personal
experience, it doesn't take that long to pick up UNIX once you know MPE.
I've known it to be more difficult for UNIX'ers to learn MPE than for
MPE'ers to learn UNIX.  I run my own UNIX box, and will be picking up a
few more very soon (a Sun SPARC 20, and another Linux box, or perhaps
FreeBSD box), and I'll hopefully soon have a MPE box or 2 which I'll be
administrating at the local high school.  I will say that I feel more
comfortable programming for the MPE systems, why, I don't know... I guess
I like the old SPL/Pascal/BASIC approach on the MPE/V platforms (I never
used C/iX on the MPE/iX platform, when I had the iX platform to work
with...)  C scares me...  shell programming is more my taste in UNIX.
 
    Also, if you have a single team for both divisions, then a possible
networking or transition for your employees from one platform to another
wouldn't be so bad.  I am now writing a C Shell type interface for MPE
(it's operable, but very primitive at this point... command line history
though), which could mean that your team could develop shells and similar
interfaces for the UNIX and MPE systems, making transition and ease of
use more attainable for your users.
 
    Just my $0.02 worth...
 
Daniel Kosack