From: hye_ok_park@CSUFRESNO.EDU
Newsgroups: bit.listserv.advanc-l
Subject: Re: Terminal servers and printers
Date: 17 Nov 92 22:33:53 GMT
              <ADVANC-L@IDBSU.BITNET>
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
X-Mailer: ELM [version 2.3 PL5]
              at Nov 13, 92 9:43 pm

Tim LaBorie asked:
> >  Does Advance have a way of knowing that the terminal (which is atta  ched
> >  through a terminal server) has a printer? The student wants to sign   on
> >  with their own campus account so they could either use the printer   or
> >  save their search results to their personal "network drive".

Minh-Thu answered:>
> If the students sign on with to their own individual account, then this
> terminal would have to be attached to a physical port, either directly
> by an RS-232 wire or a serial cluster controller. We will then be able
> to configur that physical port as having a printer and it would not
> matter who is signing on at that terminal: it still has a printer.
>
> We also have terminals in the library which are attached to a TCP/IP
> terminal server. I don't think we can configur a physical port for
> these terminals. We can still define a logical port which has a printer,
> then attached a login used specifically at this terminal to this
> logical port.
>
> You wouldn't want to attach students' individual logins to this logical
> port, because if they use their logins at other terminals outside
> the library, then ADVANCE still thinks it has a printer.
>
> That's about all I know at the present. As it happens, I am presently
> struggling to make our printers work as we want them to. So don't
> quote me please...
>
> Besides, it is important to know that I am talking about ADVANCE
> logins, not Unix logins. I don't know how to do the same with Unix.
>

If I may offer my comments on how ours are set up:

   Most of our terminals and dial-in remote ports come thru terminal
servers with the exception of several direct nail-down connections
which are used for Circ. checkout/in, OCLC downloading, one Ref. Desk
terminal, and system printers.

   We have Unix logins that are linked automatically to ADVANCE logins
by using LOGIN.CONTROL and OPAC users do not have to go thru two sets
of logins.  In other words, when OPAC users log in thru Unix login,
they get linked to PUBLIC ID within ADVANCE, which opens up the OPAC
only menu screen.  Within ADVANCE utility logical ports are defined
for each of the logins with the indication of whether a printer is
attached or not.  And this is how we control Circ. terminals to print
receipts and inserts automatically.

   There is a little (BIG) problem with printing receipts and inserts,
however, due to handshaking problem between terminals and printers.
Among several corrective measures that were finally put on, it has
been determined that the EPSON printers which GEAC supplies with
non-standard serial cards do cause the communication hangups.

I don't know if this helps but maybe someone else will comment on it.
And by the way, we do not let OPAC users log in with their own IDs.
We use a couple of wholesale logins for OPAC users, one within the
building and another for remote users.

Hye Ok Park
hye_ok_park@csufresno.edu
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU