[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

7187.0. "DCPS 1.3 AppleTalk jobs stop and requeue" by COPCLU::PETHOMSEN () Thu May 01 1997 11:55

    Hello
    
    Sorry for the 3rd question today.
    
    A customer is using DCPS 1.3 on a AXP running VMS 6.1 and printing to
    apple printers through appletalk.
    
    He claims that after upgrading of DCPS from 1.2 to 1.3 big printjobs 
    (more than 100 pages plain text) prints fine app. 100 pages and then
    stops and are requeued in the printerqueue and starts again.
    However it keeps stopping before everything is printed so until now the
    only workaround he has found is to split his output in smaller jobs.
    
    Any hints what this is caused by?
    
    
    Regards
    
    Poul Erik Thomsen
T.RTitleUserPersonal
Name
DateLines
7187.1REGENT::LASKOTim - Printing Systems BusinessThu May 01 1997 12:483
    Do any messages come back from the printer or are generated by DCPS?
    (/PAR=MESSAGES=...) Are the printers explicitly on the DCPS v1.2 and
    v1.3 support list? (Which ones, just for the record?)
7187.2job aborted during executionCOPCLU::PETHOMSENTue May 13 1997 10:0931
    Hello            
    
    The printer is a LASER WRITER 16/600, which I don't think is supported.
    However it worked before.
    
    The reason I say before and not on DCPS 1.2 is that the customer has
    made a lot of upgrades apparently.
    
    He has upgraded a VAX 6410 to a cluster of VAX 4705/4505
    
    He has upgraded VMS from 5.5.2 to 6.1
    
    He has upgraded MSA from 1.2 to 1.3
    
    He has upgraded DCPS from 1.2 to 1.3
    
    He has among other patches applied the required VAXQMAN patch described
    in the release notes.
    
    When he prints using the messages=(keep,print) he gets when it does not
    work.   job aborted during execution.
    
    It has turned out now that sometimes the print works and sometimes not,
    so maybe he has got networks problems or maybe some parameters to set
    up properly.
    
    If anybody has got a hint what to look for I would be pleased.
    
    
    Poul Erik Thomsen