[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference 7.286::postscript_printing

Title:Digital PostScript printers and their associated software
Moderator:REGENT::LASKOHER
Created:Wed Jan 24 1990
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:7230
Total number of notes:31971

7109.0. "Deleting a printserver, how." by STKHLM::BARBRO () Wed Mar 05 1997 05:10

When adding a printserver there is a procedure (LPS$ADD_PRINTSERVER.COM)
to do this. Is there a similar one to do the opposite, ie to delete
a printeserver off a node ? That is something like LPS$DELETE_PRINTSERVER.COM)
I know it is very simple to prevent a printservernode from booting by just
changing the hardware Ethernet adress to a non existing one (using NCP), but
that's not what our customer wants, he wants to get rid of ALL files
that are tied to just this one printserver node, without removing
the files that are common to all other printservers on this node.
At least this is an input for product improvement (next release fix ?)

Improvement 2: Big users of LPSes have a need for centralized
surveilance of toner refill without being on the site (next town).
Is there any way to get hold of the sheet counter from the boot node ?
best rgds
GB


T.RTitleUserPersonal
Name
DateLines
7109.1Here are the stepsNECSC::HARVEYPrintserver Support- America's ZoneWed Mar 05 1997 12:2221
    Hi,
    
    	There is not any utility to remove a LPS printer from a VMS server.
    However it is quite simple:
    
    1. Phase IV Decnet, use NCP purge and clear commands with the printers
       nodename to remove it from the network databases. 
    
       Phase V use NCL commands to remove the  MOP client for the  printer
       nodename. Then using the sys$system:decnet_register.exe utility
       remove the nodename from registry database.
    
    2. Using the sys$manager:lps$stop_daemon.com utility stop the
       management daemon process for the printer.
    
    3. Then in the lps$support directory delete all files with the
       extension of the nodename of the printer. Then edit the file in the
       same lps$support directory, lpsnetsetup.dat and remove the entry for
       the printer nodename with all its associated data.
    
    Renis
7109.2sheet counterREGENT::GALLAGHERWed Mar 05 1997 12:4617
 
    To answer the other question on sheet counters....
    
    2)The short answer is no. What is available remotely is the PostScript
    page count via the pagecount operator. This number shows up on the
    startpage, for example. So, you could send a PostScript job to the
    printer that will send this pagecount back to the user as 
    PostScript "userdata". You can have the userdata stored in a logfile
    by /PARAM=MESSAGES=KEEP, as well as seeing it on the screen via
    /NOTIFY.
    
    Hope that helps your customer...
    
    -cg
    
    
    
7109.3The toner is measured by volume, not pagesSHRMSG::HOWARDWhoever it takesFri Mar 07 1997 16:1514
    You can get a sheet count if you turn on Accounting for the printer. 
    What you get is raw data, but it is a fairly easy job to write
    something to produce totals.  I imagine this is fairly accurate.  Of
    course, toner runs out when it runs out.  A page with a lot of black
    uses a lot more toner than a blank page.  You can't refill before it is
    time, so I don't know what you are going to do with the page count.
    
    I wonder if you could use LPS$CONCONSOLE or some variation to poll the
    printer if it needs toner.  The information is when you run the
    program, but nobody wants to check each printer.  You could run
    LPS$PRISM in a Windows environment, then have someone visually check
    for "Add Toner".  
    
    Ben