Subject: | |
From: | |
Reply To: | |
Date: | Thu, 29 Feb 1996 08:15:34 -0800 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
Don't laugh, I know of a system that has more (quite a few more actually)
than that number of printers, and they are spooled! They don't use device
classes heavily :)
Michael L Gueterman
Easy Does It Technologies
[log in to unmask]
"The opinions expressed DO reflect those of the company,
since I OWN the company"
----------
From: [log in to unmask][SMTP:[log in to unmask]]
Sent: Thursday, February 29, 1996 5:06 AM
To: Editcorp
Subject: Re: Pseudo Devices/MPE limits
Return-Path: [log in to unmask]
Received: from UTCVM.UTC.EDU by fred.nwinfo.net with smtp
id AIAGALGB ; Thu, 29 Feb 1996 08:06:12 -0500
Date: Thu, 29 Feb 1996 10:57:00 +0000
From:
Subject: Re: Pseudo Devices/MPE limits
To: Multiple recipients of list HP3000-L <[log in to unmask]>
Doug Werth answered...
>You can configure cards that do not exist in the DTC and even
>DTC's that aren't there. However, since NBSpool can move
>reports from device classes as well as ldev numbers, my
>personal preference is to create a single dummy device in
>NMMGR and simply add as many device classes to the profile
>in as needed. One psuedo device, one profile, less hassle.
I concur. We use Unispool here with the same technique and with
no problems. Nice and tidy, works well.
There is a limit of somewhere around 450 device classes per
system which we did come close to hitting at one time. But who
needs 450 printers!
John Pickering
JWP Systems Inc
Toronto
|
|
|