[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference lassie::ucx

Title:	DEC TCP/IP Services for OpenVMS
Notice:	Note 2-SSB Kits, 3-FT Kits, 4-Patch Info, 7-QAR System
Moderator:	ucxaxp.ucx.lkg.dec.com::TIBBERT

Created:	Thu Nov 17 1994
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	5568
Total number of notes:	21492

5447.0. "Printing VFC files with LPD question." by UTRTSC::VWEE () Thu Apr 17 1997 05:17

Hello,

A customer got some problems with printing of VFC format files.

File information.
    
Record format:      VFC, 2 byte header, maximum 200 bytes, longest 0 bytes
Record attributes:  Print file carriage control
 
He is using LPD for printing.
When they print a file, on the server site there is filled in a <LF> before
every line.


Is there someone who can explain this to me?


Thanks in advance.
gerard.

T.R	Title	User	Personal Name	Date	Lines
5447.1	probably LF filling is expected (hardwired in VFC's)	COL01::VSEMUSCHIN	Duck and Recover !	`Thu Apr 17 1997 07:27`	28
	>>Record format: VFC, 2 byte header, maximum 200 bytes, longest 0 bytes >>Record attributes: Print file carriage control >> >>He is using LPD for printing. >>When they print a file, on the server site there is filled in a <LF> before >>every line. It depends on the information in those 2 byte line headers. You can read VFC's with DUMP utility. Then decrypt the information stored there using FAB$V_PRN description from chapter 4.27 of RMS Reference Manual. It is enough if you do it for first 2-3 records. Then copare your results with output you can get when define UCX$LPD_DEBUG and UCX$LPD_RECEIVE logical names as specified in 13.7.1 of UCX Management Manual. By example, if you see in dump 8D8A0016 just before the printed text it means 22 byte record prefixecd with LF and postfixed with CR. Probably LF filling is exactly that, what expected. =Seva PS Did you got FF after the last page of your file ? I try to solve that problem already 3rd day... =Seva
5447.2	File (dump) info.	UTRTSC::VWEE		`Tue Apr 22 1997 10:01`	52
	Thanks for your reply; Part of the file (dump) Dump of file USER:[VWEE]TEST.VFC;1 on 22-APR-1997 15:48:26.69 File ID (7132,5,0) End of file block 6 / Allocated 9 Virtual block number 1 (00000001), 512 (0200) bytes 20612073 69685420 20313030 8D010036 6...001 This a 000000 6F662065 68742068 74697720 656C6966 file with the fo 000010 72657461 72616863 20676E69 776F6C6C llowing charater 000020 20323030 8D010008 3A207363 69747369 istics :....002 000030 45542020 20202033 30308D01 00452020 E...003 TE 000040 etc. > By example, if you see in dump 8D8A0016 just before the printed text > it means 22 byte record prefixecd with LF and postfixed with CR. I see 8D010036, explains this the 0A at the beginning of print job. Dump of data (UCX$LPD_QUEUE): Dump of file $20$DUA0:[SYS0.UCX_LPD.TESTLAT]DFA035AUSSIE_UTO_DEC_COM.DAT;1 on 22 -APR-1997 15:55:15.19 File ID (2138,5,0) End of file block 5 / Allocated 6 Virtual block number 1 (00000001), 512 (0200) bytes 6C696620 61207369 68542020 3130300A .001 This a fil 000000 6F6C6C6F 66206568 74206874 69772065 e with the follo 000010 74736972 65746172 61686320 676E6977 wing charaterist 000020 300A0D20 20203230 300A0D3A 20736369 ics :..002 ..0 000030 3B434656 2E545345 54202020 20203330 03 TEST.VFC; 000040 20202020 20202020 20202020 20202031 1 000050 2820203A 44492065 6C694620 20202020 File ID: ( 000060 20202020 2029302C 38322C35 36373033 30765,28,0) 000070 657A6953 20202020 20343030 0A0D2020 ..004 Size 000080 > PS > Did you got FF after the last page of your file ? > I try to solve that problem already 3rd day... I didn't got a FF after the lastpage. I will ask my customer if he got some problems with it. regards Gerard
5447.3	Workaround, used "relay queue".	UTRTSC::VWEE		`Fri Apr 25 1997 05:16`	6
	I spoke with the customer, I suggested that he used a "relay queue". This solved his problem. Printing is working fine now. The customer is happy with this workaround. Regards Gerard.