Conference 7.286::postscript_printing

7207.0. "DEClaser 3250 does not print" by STKHLM::HORNBLAD () Thu May 22 1997 12:03

Hi,

We are having  problems with 3 DEClaser 3250 where the printjob get into status
starting but nothing is printed on the printer and the job just hangs.

We use DCPS v1.2 and the printer is connected to a DECserver 90L+.

There is one way to get the printer to print and that is to disconnect from the
DECserver (unplug the cable) and restart the printer. Then ONE job is printed,
the next job hags. This happens to 3 printer queues on two different DECservers
but with the same configuration.

To test the connection I did the following:

BCFI01>stop/queue/reset JAR2211$LN08R
BCFI01>set device/nospool LTA114:
BCFI01>set host/dte lta114:

%REM-I-TOQUIT, connection established

Press Ctrl/\ to quit, Ctrl/@ for command mode
 
<Ctrl>t

Nothing is returned. The printer sometimes switches from "ready" to "waiting"
but nothing is printed or returned.

All 3 printers used to work and the customer says "nothing" has been done to
their printers or system setup.  The printer and cable has been replaced with a
another printer so I assume the problem is not printer HW or cable.

I'm enclosing some information from the system. The port logs "frame err" but
I'm not sure what this means.
                                            
I'm stuck on this one... looking for help!


Regards,
Maria


-> sh 1

Name      92211A
Speed     19200
In Flow   ENA/on
Out Flow  ENA/on
Type      PRINTER
Break     LOCAL
Rem Mod   ENA
Test      NO
AutoConf  DIS
ODL       DIS
Status    CONN
Service   *
Node      BCFI01
Port      LTA114
Fram Err  40510
Queued    SWETDS




BCFI01>show queue/full JAR2211$LN08R/all
Printer queue JAR2211$LN08R, busy, on BCFI01::LTA114:, mounted form CPS$DEFAULT
(stock=DEFAULT)
  /AUTOSTART_ON=(BCFI01::LTA114:,BCFI02::LTA114:,BCFI03::LTA114:)
  /BASE_PRIORITY=4 /DEFAULT=(FLAG=ONE,FORM=CPS$DEFAULT (stock=DEFAULT))
  /NOENABLE_GENERIC /LIBRARY=DCPS_LIB Lowercase /OWNER=[SYSTEM]
  /PROCESSOR=DCPS$SMB /PROTECTION=(S:E,O:D,G:R,W:W) /SCHEDULE=(NOSIZE)

  Entry  Jobname         Username     Blocks  Status
  -----  -------         --------     ------  ------
     24  OFR             ORDERDESK        11  Starting
         Submitted 20-MAY-1997 08:25 /FORM=CPS$DEFAULT (stock=DEFAULT)
         /PARAM=("PAGE_O=LANDSCAPE","SIDES=2","DATA=ANSI") /PRIORITY=100
         File: _DSA1:[ORDERDESK.ALLIN1]OFR.TXT;10 (printing)



BCFI01>show terminal lta114:
Terminal: _LTA114:    Device_Type: Unknown       Owner: SYMBIONT_396
                                              Username: SYSTEM

   Input:  19200      LFfill:  0      Width:  80      Parity: None
   Output: 19200      CRfill:  0      Page:   24

Terminal Characteristics:
   Interactive        No Echo            Type_ahead         No Escape
   Hostsync           TTsync             Lowercase          Tab
   No Wrap            Hardcopy           No Remote          Eightbit
   No Broadcast       No Readsync        Form               Fulldup
   No Modem           No Local_echo      No Autobaud        Hangup
   No Brdcstmbx       No DMA             Altypeahd          Set_speed
   No Commsync        No Line Editing    Overstrike editing No Fallback
   No Dialup          Secure server      No Disconnect      Pasthru
   No Syspassword     No SIXEL Graphics  No Soft Characters No Printer Port
   Numeric Keypad     No ANSI_CRT        No Regis           No Block_mode
   No Advanced_video  No Edit_mode       No DEC_CRT         No DEC_CRT2
   No DEC_CRT3        No DEC_CRT4        VMS Style Input

Being stuck in the "starting" state is indicative of the printer
not responding to the ctrl-T codes the symbiont sends to synchronize
at the start of the job.
This is consistent with your test of sending a manual ctrl-T via /dte
and the lack of a response.
Disconnecting the printer from the DECserver and restarting (you mean power
cycling?) would clear an outstanding flowcontrol state (an XOFF unmatched
by a following XON).

Thus I suspect bad handling of flow control somehow, but I don't read VMS
terminal settings well enough to recognize whether there is a settings
problem.

A test:  Set EITHER the printer or the DECserver to hardware flow control
(DTR high or low on the printer, I don't know the setting on the DECserver).
This has the effect of disabling communication line flow control,
so this is NOT a valid operational mode.
Send several successive SHORT jobs to the printer to see if this
clears the problem.  If it does, you'll have to investigate why flow control
is unbalanced.

- tom]