Conference lassie::ucx

5532.0. "PROBLEM PRINTING,STREAM FORMAT WITH TCP/IP " by LATINA::MAJOSE (MCS Madrid) Tue May 27 1997 07:16

	PRINTING PROBLEM "TCP/IP SERVICES",OVMS  6.2

	My customer has the problem reported on a STARS ARTICLE:

	"{Elev} printing problem byte record too large for users buffer"


---------------------------------------------------------------------------
{Elev} printing problem - byte record too large for users buffer

PRODUCT or COMPONENT:  DEC TCP/IP UCX

OP/SYS:  OPENVMSVAX

Submitter Name: Robin Norris                    DTN:  343-1140  Node: OASS::NORRIS_R
Immediate Manager's Name:  Valerie Moore        DTN:  343-1369  Node: SAHQ::MOORE


The severity levels set by MCS must reflect the total situation from
both the technical and political aspects.


VERSION INFORMATION:

Product: UCX V 3.3
Product/Component Version(s): 3.3
Operating System Version(s):  openvmsvax 5.5-2

SOURCE:   Digital Equipment Corporation


SYMPTOM:

PCNFS has problem passing serial stream file to RMS. Looking at problem on
casual basis for some time. See note 4560 in UCX conference

================================================================================
Note 4558.0                            ex                             No replies
OASS::NORRIS_R "Robinhood he bent his noble good bo" 36 lines  27-AUG-1996 12:06
--------------------------------------------------------------------------------
    a customer reports that using ucx 3.3 on VMS 5.5-2 PCNFS to point to a
    latsym que gets error.

    -RMS-W-RTB, 402050 byte record too large for user's buffer

     The file he tried to print was a Word For Windows document, 10 pages
    long with several grayscale screen images.

    Terminal queue LASER_VL, idle, on FALCON::LTA239:, mounted form
    HPLJ_PORTRAIT
      (stock=DEFAULT)

      Entry  Jobname         Username     Blocks  Status
      -----  -------         --------     ------  ------
         81  BBAIRD          bairdb         3970  Retained on error
            %PSM-E-READERR, error reading !AS
           -RMS-W-RTB, !UL byte record too large for user's buffer
           -RSX-E-SHACHASTA, Shadow set has changed state


    Questions:

    1. does NFS or PCNFS have *any* notion of RMS and munging a serial
    streaming file into a format that won't kill VMS buffers?
  2. Whose responsibility is it to bridge between the file systems in a
    way that works?


    any help appriciated!

    /Robin Norris CSC/AT



  [Include a description of the symptom and the processes/steps
that led to it.  What is broken which is supposed to work according to
the Hardware or Software Product Description?  Include complete error
messages.  If an application or file fails to execute, include the name
of the application or file, and provide an example.]


DIGITAL RESPONSE:

This problem has been reported to Engineering.


WORKAROUND:

haven't found any workaround yet...


ANALYSIS:

Julie Corenzwit replied to my mail as follows:

    #2           2-OCT-1996 17:27:50.33                                     MAIL
From:   LASSIE::CORENZWIT    "Julie Corenzwit, 8-226-5261, LKG2/2-Q5"
To:     OASS::NORRIS_R
CC:     CORENZWIT
Subj:   RE: file that causes buffers to blow in PCNFS not Pathworks.

Yes, I got the file some time ago.  There is a possibility of a
fix, but that file is neither ASCII nor Postscript, and I don't
have a printer to test it with, so I can't tell if the fix
actually allows the file to print correctly or merely gets rid of
the RMS error.  In any case, the fix presupposes one of the print
features that is missing from the current version.

I am currently working on IPMT cases.

Julie

---------------------------------------------------------------------------

	* When they want to print from the PC with "lpr"  using 
	TCP/IP to a queue on the AXP OVMS SERVER,it appears
	that error on the queue:

           -RMS-W-RTB, !UL byte record too large for user's buffer

	these files are sent to the server by lpd,and they appears 
	retained at the queue.These files are for example text
	of notes block.
	
	* If I send those files from VMS (stream format) to 
	this queue ,it fails.If I print with "PRINT/PASSALL"
	from VMS ,it also fails.

	* They had upgraded to TCP/IP SERVICES 4.1,but the
	problem hasn't solved.


	PLEASE ANY MORE INFORMATION ABOUT ??
	ANY PATCH ??
	WHO IS THE GUILTY ??



	Thanks and regards,
	M.Jos�
	MCSD Spain.

    
    Which database this Qar belongs ????
    I've tried to read 519 on TRIFID ,but I've not found this QAR.
    
    I don't know if there is a solution or workaround to this case ???
    
    Thanks and regards,
    M.Jos�.
    MCSD Spain.

    Our QAR databases were never on TRIFID, at least not in my memory. 
    They were recently transferred into the PTR system.  Once you get into
    that, you can look up cases by their former QAR numbers.  I believe
    some low numbered note in this conference says or soon will say how to
    get into the PTR system.
    
    The workaround is to manually copy the file to the NFS server system. 
    Then do a $ SET FILE name /ATTRIBUTE=RFM:UDF and print it using the VMS
    PRINT command.
    
    Julie