Record too large for user's buffer
This problem is most likely due to sending a binary file as text. If the file is sent, or received, as binary (file type v
), the server will read and store the data as fixed length binary records.
When printing to MultiNet's LPD server record is too large for user's buffer
messages are generated.
There are several ways to correct this problem:
-v
option in the lpr
command.
multinet_lpd_*_V_passall
(in the MultiNet printer table) like this:
$ define/system/exec/tabl=multinet_printer_table multinet_lpd_*_V_passall "YES" $ define/system/exec/tabl=multinet_printer_table multinet_lpd_*_V_filetype "FIXED512"
When I send a job to print the job is not accepted and the following error message appears:
%%%%%%%%%%% OPCOM 24-JUN-2017 15:14:50.13 %%%%%%%%%%% Message from user SYSTEM on HOSTA MultiNet Printer Symbiont: Entry 83, queue SUPPORT1 Couldn't open temporary file [192.169.1.1/printer]: %RMS-E-DNR, device not ready, not mounted, or unavailable, ABORTING PRINT JOB.
What is causing this and how can I correct it?
The cause of the error is that the MultiNet spool directory is set to an invalid or unavailable directory. You can correct this by using the MultiNet configuration utility as follows:
$ MU CONFIG NET-CONFIG> SET SPOOL-DIRECTORY valid-directory NET-CONFIG> EXIT [Writing configuration to MULTINET:NETWORK_DEVICES.CONFIGURATION] [Writing Startup file MULTINET:START_MULTINET.COM] [Changes take effect after the next MultiNet reload]
You can define the logical MultiNet_Spool to have the change take effect immediately; for example:
$ DEFINE/SYSTEM/EXEC MULTINET_SPOOL valid-directory
Yes, issue this command:
$ DEFINE/SYSTEM/EXEC MULTINET_PRINTER_NO_OPCOM "true"
This works for both stream and lpd symbionts. Add this command to MULTINET:LOCAL_ROUTES.COM
so it executes every time MultiNet starts.