I agree with both of you. Where we use this is to grant the AM (normally
a lead developer) of an account that uses a specific printer the
association to manage that printer. So far, it has worked well for us.

On another note, I look forward to figuring out how to configure the
software and the account so that a given user can print a given document
to one of a bank of printer (either specifically to one printer, or to
one of a class) based on their configuration, but at a level of
abstraction so that a smaller office can rotate among any one of three
side by side printers for any given document. I know that this is just
an algorithm; I just haven't thought it completely thru yet. I have gone
to putting printers in classes, but individually giving them Borg
designations. :-) In fact, when I refer to printer third of twelve,
other developers look at me funny, until I explain my naming convention.
It's usually good for a laugh.

> -----Original Message-----
> From: John Burke [SMTP:[log in to unmask]]
> Sent: Wednesday, May 06, 1998 11:04 AM
> To:   [log in to unmask]
> Subject:      Re: [HP3000-L] OP and HIPRI
>
> Actually, it can be very easy depending upon account structure. For
> example, we use @.payroll and @.AP to associate all payroll users and
> all AP users respectively to specific printers. Of course the
> interface
> for setting up the table is at best "user hostile", not to mention
> poorly documented.
>
> -----Original Message-----
> From: Leonard S. Berkowitz
> [mailto:[log in to unmask]]
> Sent: Wednesday, May 06, 1998 5:19 AM
> To: [log in to unmask]
> Subject: OP and HIPRI
>
> Lars,
>
> That's an interesting idea but it requires a lot of maintenance.
>
> Leonard