Groups | Search | Server Info | Login | Register


Groups > alt.sys.pdp10 > #9922

Re: TOPS-20 and DQS printers

From jayjwa <jayjwa@atr2.ath.cx.invalid>
Newsgroups alt.sys.pdp10
Subject Re: TOPS-20 and DQS printers
Date 2026-02-07 00:16 -0500
Organization atr2net 2026
Message-ID <875x89yvyt.fsf@atr2.ath.cx> (permalink)
References <871pixmt2k.fsf@atr2.ath.cx> <mdd7bsps3wf.fsf@panix5.panix.com>

Show all headers | View raw


Rich Alderson <news@alderson.users.panix.com> writes:

> AA-J678A-TM_DECnet-20_System_Manager_and_Operators_Guide_Jun83
> AA-J679A-TM_DECnet-20_Users_Guide_Dec82
I read the docs. After about 10 hours (1.5 for a pizza break) I finally
got it. There's a few nasty GOTCHAs and a lack of examples in
MGR_GUIDE.MEM, though it does have some info in section 3.7.2 .

I don't recall if LPTSPL is enabled by default in Panda or if I took it
out (because there's no native printer device in KLH10) but I put it
back for this. Probably LPTSPR should be running on TOPS-20 (in
sysjb1.run). Before use, OPR must set the printer up. After this, the
user can use the "print" command with the "/remote-printer:" switch with
the node that matchs the node the OPR set in the OPR> interface.

Requires VMS DQS software, in AG-RX1XJ-BE.iso . Make sure NOT to select
"Defaults" when installing: it gives ONLY the client. If you want the
server too, which you do if you want to print from TOPS-20, don't take
the defaults. See files in sys$manager:dqs$* and hook startup file into
the system startup.

VMS directory where files land:
  TEOSTR$DUA0:[VMS$COMMON.DQS$SERVER]

@dqs$server_update_config.com   To recognize changes to server config
                                MUST RUN EVERY TIME YOU CHANGE things
                                
dqs$server_config.txt           Place server queue configs here
  QUEUE SYS$PRINT *  ! Lets everyone use it (see GOTCHA below)
  
sys$common:[dqs$server]         Server writes logs here

Starting DQS on TOPS-20 from OPR:
OPR>start printer (specify printer) dqs (VMS printer queue name) -
SYS$PRINT NODE teostr

Stopping (does not remove):
OPR>stop printER (specify printer) dqs SYS$PRINT node teostr

This removes a DQS printer from the list entirely. You MUST specify
every single piece of info (no leaving out node name or even the word
"node").
OPR>shutdown printer dqs SYS$PRINT node teostr

After the OPR sets up the DQS spooler, the user must set remote
printing as well. 
@set remote-PRINTING printer teostr SYS$PRINT teostr
                             ^-name  ^-queue  ^-node name
@print /REMOTE-PRINTER:teostr nft.init
[Printer job NFT queued, request #4, limit 3]
@
[From SYSTEM: Job NFT request #4 spooled to DQS printer SYS$PRINT on node TEOSTR
 at 22:39:27]

OPR>start printer dqs SYS$PRINT node teostr
OPR>
22:34:24        DQS Printer SYS$PRINT [TEOSTR]  -- Startup Scheduled --
OPR>show statUS printER (specify printer)
OPR>
22:34:33                -- System Device Status --

Printer Status:

DQS printers
           DQS queue name           Node        Status
  ------------------------------   ------  ---------------
                       SYS$PRINT   TEOSTR  Idle

OPR>
22:39:24        DQS Printer SYS$PRINT [TEOSTR]  -- Started --
SJ  0: OPR>
SJ  0: 22:39:24         DQS Printer SYS$PRINT [TEOSTR]  -- Started --

22:39:24        DQS Printer SYS$PRINT [TEOSTR]  -- Begin --
                Job NFT Req #4 for JAYJWA
OPR>
22:39:27        DQS Printer SYS$PRINT [TEOSTR]  -- End --
                Job NFT Req #4 for JAYJWA
OPR>

GOTCHA: TOPS-20 will not accept an "_" (underline) in the queue name,
which will probably be how VMS has it set up for a line printer.  For
example, "_LPA0". Running Wireshark, I could see TOPS-20 send the
request again and again, but something got lost in transit: the
"_". _LPA0 became LPA0, which VMS rejected. To work around this, you can
define a VMS logical such as "SYS$PRINT" to point to the "_LPA0"
device. TOPS-20 can use this.  Forthgoing, use the SYS$PRINT name for
the device else your attempts to print to VMS's DQS will result in "no
such queue" type errors over and over - even though the device is
techically correct on VMS - which look like this:

%DQS-I-REPORT, reporting the following message to the client.
-JBC-E-NOSUCHQUE, no such queue
  DQS$SERVER   job terminated at  6-FEB-2026 21:56:09.95

$ qshow
Batch queue SYS$BATCH, on TEOSTR::

Printer queue _LPA0, on TEOSTR::, mounted form DEFAULT

NOTE: PRINT JOB PROCESSED BY DQS V1.3-1 VAX
FILE _TEOSTR$DUA0:[VMS$COMMON.DQS$SERVER]NFT.INIT;1 (7168,19,0), LAST
REVISED ON  6-FEB-2026 22:39, IS A 1 BLOCK SEQUENTIAL FILE
... snip ASCII art banner
JOB NFT (3) QUEUED TO _LPA0 ON 6-FEB-2026 22:39 BY USER JAYJWA, UIC [DQS$SERVER], UNDER ACCOUNT AMATSU AT PRIORITY 5, STARTED ON
PRINTER _TEOSTR$LPA0: ON 6-FEB-2026 22:39 FROM QUEUE _LPA0.
... snip ASCII art banner
(actual file output)

-- 
PGP Key ID: 781C A3E2 C6ED 70A6 B356  7AF5 B510 542E D460 5CAE
       "The Internet should always be the Wild West!"

Back to alt.sys.pdp10 | Previous | NextPrevious in thread | Find similar


Thread

TOPS-20 and DQS printers jayjwa <jayjwa@atr2.ath.cx.invalid> - 2026-02-06 16:59 -0500
  Re: TOPS-20 and DQS printers Rich Alderson <news@alderson.users.panix.com> - 2026-02-06 21:06 -0500
    Re: TOPS-20 and DQS printers jayjwa <jayjwa@atr2.ath.cx.invalid> - 2026-02-07 00:16 -0500

csiph-web