Options for Managing a DTC Remotely

3. Options
3.1. Option 1: Status Quo
In this option, the user decides to continue using the OVDTCMGR
platform at their remote sites.
3.1.1. Advantages
In this scenario, no changes are required at all by the
customer. Current configurations remain the same and the
customer continues using the same tasks and processes
that have already been established in order to manage the
use of their DTCs. The customer’s users who connect via
the DTC see no difference in their connection mechanism or
ability.
3.1.2. Disadvantages
The greatest issue with this option is that the customer will
now be using a product that has a component that is no
supportable. While it is true that this component has been
stable and has not been a central cause of a problem in
several years, there is an inherent risk in using an
unsupported product that will be unacceptable to many
MPE/iX customers. It is also possible that given the decision
to not support part of the OPENVIEW platform, may impact
the ability of the CSY team to deliver any OVDTCMGR
changes in a timely manner. While it is true that an end-of-
life date has been established for the HP3000 and the DTC,
there is still functionality that could possibly be added to the
DTC family, albeit being minor.
3.2. Option 2: HP-UX Management
In this option, the customer moves management of the DTC from
the OPENVIEW platform to the HP-UX platform running the
DTCMGR/UX utilities.
3.2.1. Advantages
If the customer has an existing HP-UX system on its network, than
this system can be used to manage the DTCs, avoiding the need to
buy any extra hardware to replace the OVDTCMGR PC. Also,
since the HP-UX utilities are based on ARPA standard protocols,
the DTCs can be managed from any system on the network and no
special networking configuration is needed to allow access to the
DTCs.