Hum...

Be careful with original DTC48 (HP2345A)...  I think they needed an upgrade
(possibly 2348A ???) to support switching...  Not sure that upgrade is still
available though...

Hope it will help !
--
==================================================
Denis St-Amand (Remove "removeit." from email address)
==================================================
"Dennis Walker" <[log in to unmask]> wrote in message
news:3c62fbf9$1_3@athena.netset.com...
> Its pretty easy if you not using dtc16ix's.  In NMMGR DTC.PROFILE  use the
> GOTO SWITCH function key.  Add the dtc's to all the systems, and use the
> switched profiles on each.   This will allows multiple systems to print to
> the dtc's printers, and allows terminals to connect to the systems that
name
> that port with a switched profile.
>
> On terminals you get a little connection dialog to tell what host to
connect
> to and you can have multiple connections open on one terminal.
>
> the printer switch profile looks like this
>
> PATH:  DTS.PROFILE.LP.SWITCH
>
> Printer name           [                 ] (optional)
> Number of hosts sharing printer        [2] (1..5)
>
> Enable port?                 [Y]  (Y/N)
> Dedicated printer?           [Y]  (Y/N)
> Automatic connection?        [N]  (Y/N)
> Enable keep alive?           [Y]  (Y/N)
> Save port config in binary?  [N]  (Y/N)
>
> Default destination
                          ]
> Initialization string  [                ] (optional)
>
>
> the terminal switch profile looks like this
>
> PATH:  DTS.PROFILE.TR10D96S.SWITCH
>
> Terminal name         [                 ]  (optional)
>
> Data transfer                         [1]  (1 - ASCII, 2 - Binary)
> Escape from data transfer character  [^T]  (Y/N) (optional)
> Maximum  number of sessions           [5]  (1 to 5)
>
> Enable port?           [Y] (Y/N)     DTC user interface timeout?  [Y]
(Y/N)
> Enable switching?      [Y] (Y/N)     Enable keep alive?           [Y]
(Y/N)
> Automatic connection?  [N] (Y/N)     Save port config in binary?  [N]
(Y/N)
>
> Default destination
 ]
> Initialization string  [                ]  (optional)
>
> The only complication I had was making sure all the systems had the same
> setup, if one was different the dtc will end up being set up the way the
> first system the dtc downloads its configuration from.
>
> "Bullock, James O." <[log in to unmask]> wrote in message
> news:a3uqs702m6j@enews3.newsguy.com...
> > We have an HP3000 957 that is being replaced by an HP9000.  We have four
> > DTC48s and one DTC72 on their own card in the 957.  We also have two
> > additional nics in the HP3000, one for the public network and one for
> > the private network.  We use host-based DTC management and do not own OV
> > DTC Manager.
> >
> > The object is to continue to use our vast collection of serial printers
> > with the HP9000.  We will have to run concurrent systems for a while, so
> > the 3000 and 9000 will have to share the serial printers.
> >
> > Any ideas on the best way to do this?
> >
> > I have been told that the DTC 72 will work but not the DTC48's.  I am
> > assuming that the DTCs will have to join the private network.  We tried
> > mixing AFCP and IP before and had some problems.
> >
> > Our conversion to all network printing has not happened.  I would just
> > as soon eliminate the DTCs altogether, but I can't right now.
> >
> > Regards,
> >
> > James O. Bullock
> > Computer Operations Manager
> > Department of Information Technology
> > Wharton County Junior College
> > 911 Boling Hwy
> > Wharton, TX 77488
> > (979) 532-6330 voice
> > (979) 532-6484 fax
> > (979) 282-1983 cell
> > [log in to unmask]
> >
> > * To join/leave the list, search archives, change list settings, *
> > * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
> >
>
>

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