Conference vaxuum::document_ft

    
    have you modified DOC$DESTINATIONS.DAT ? you may have extra text
    or blank lines in there or in DOC$DESIGNS.DAT...
    

    No, I have not modified DOC$DESTINATIONS.DAT.
    Yes, I have modified DOC$LOCAL_FORMATS:DOC$DESIGNS.DAT - it is a
    copy of CUP$DESIGNS.DAT (I think the installation guide requested
    that), and I have removed two or three blank lines from it.
    
    And there comes another message with the CLI-W-BUFOVF - here is
    a window into my log file (comes out the same interactively):
    
    %DOC-I-IDENT, VAX DOCUMENT T1.0-008
    %CLI-W-BUFOVF, command buffer overflow - shorten expression or command line
    %CLI-E-INVROUT, invalid routine specified in command tables - check
           .CLD file
    
    However, SHOW COMMAND shows 'image DOC$ROOT:[TOOLS]DOCUMENT', all
    logicals seem to be set up correctly, and - believe it or not -
    it works fine !  So what about the messages ?
    
    Sorry that I did not quote the complete set of messages in my original
    note.
    
    Hans.

    What command line are you using, and what local and global symbols have
    you set up?  Also, where did you get "SHOW COMMAND"?  I'd love a
    tool like that.
    
    -tl

    > What command line are you using, and what local and global symbols have
    > you set up?
    
    I can use the document command with any qualifiers / parameters
    to get the BUFOVF message - to be honest, I did *not* try all possible
    combinations ;-)
    
    For example, I typed
    
    $ docu /noprint docgen s.spec ln03
    
    to get the message.
    
    During the tests done before this reply I found out another strange
    behaviour:
    Our system manager installed LN01-support and apparently got into
    the 'trap' already noted elsewhere (do you want to add another
    queue/printer .. for this destionation or so), he entered NL:
    
    When I removed this entry with the editor, the 'invalid routine
    specified...' message appeared on subsequent DOCUMENT invocations.
    When I switched back to the original version of DOC$DESTINATIONS.DAT,
    the INVROUT message disappeared.
    
    I also noticed, that document does not recognize all destinations
    defined in DOC$DESTINATIONS.DAT (e.g. gives a message like 'unknown
    destination - check your spelling' for LN01, LINE_PRINTER, but works
    with VIDEOTEX).
    I also tried to use AUTODEST (defined as a foreign command following
    the release notes instructions), but didn't get any result. AUTODEST
    typed the first destination within brackets (which was [NL:]), then
    also came up with the BUFOVF message, which was overtyped by the
    rest of destinations from DOC$DESTINATIONS.DAT. AUTODEST did not
    accept any commands, but echoed them on the terminal (no matter
    if uppercase or lowercase) and prompted for the next command.
    
    Any guru having any idea ?
    All this happened on a 8550 with VMS 4.5.
    
    > Also, where did you get "SHOW COMMAND"?  I'd love a tool like that.
    
    Unfortunately, I don't know, and our system manager went on vacation
    just yesterday. The tool already was on the machine when I started
    here four months ago.
    
    Hans.

    Addition to .4:
    
    I forgot to mention that there is
    - no symbol 'docu' defined
    - no logical name 'docgen' or 'ln03'
    
    (all used in the sample command line).
    Hans.

    Re show command command:
    
    See Note 390 in METOO::SW_TOOLS_CATALOG regarding SHCOMMA.
    

         
         I can not reproduce this error, from your description
         I don't know what's wrong, but I have some suspicions.
         
         First of all, send me the versions of DOC$DESTINATIONS.DAT
         and DOC$DESIGNS.DAT that are in DOC$STANDARD_FORMATS:
         
         From what account was DOCUMENT installed?
         
         Now, could you run document with a /LIST qualifier, and
         send to me the resulting(if any) .LIS file?
         
         I know this sounds like a real pain, but could you do
         one other thing for me?  Could you DEFINE SYS$OUTPUT BUG.DOC, 
         then do these from the command line.
         
         	$ SHOW COMMAND DOCUMENT
         	$ SHOW PROCESS/ALL
         	
         
         Then could you DEASSIGN SYS$OUTPUT, and then send me BUG.DOC
         
         
         Thanks,
         Chris
	

         Hans,
         	I have recieved the information, thank you.  The
         problem was there was a destination defined in your
         DOC$DESTINATIONS.DAT data file which had a destination
         keyword NL: -- I assume this is because you have a
         destination which prints to the null que.  Take off the
         colon from the NL: and only use NL as the keyword to your
         destination.  - The problem will then go away.
         
         Did you use AUTODEST to modify your, DOC$DESTINATIONS.DAT
         file?  You probably should, because the syntax of that
         particular data file is stringent, and little errors like
         this one will appear when you make a mistake in the data
         file.
         
         Chris

         
         One more thing,  I became curious that you specified the
         print que to be nl: -- well this is equivalent to processing
         the command
         
         	$ print/queue=NL: foo.foo
         
         Well out of curiosity I tested this, well the print command
         will not accept queue = NL: as a valid queue name.  So
         even when this destination works it won't because you
         will get error when it comes time for document to print.
         
         I think what you really want to do is to have your
         destination NL not supply a /print qualifier, and supply
         an /exclude_action=(print) qualifier.  (Look at the MAIL
         destination).
         
         But you should do this using AUTODEST.  Now there are
         a few bad versions of AUTODEST flying around, and you
         may have a bad version, (it is semi-documented in the release
         notes to BL08) to get a good version you can copy it from
         VAXUUM::KITS_:[DOCUMENT]AUTODEST.EXE
         
         
         Chris
         	

    Chris,
    
    your tips have brought me to the right way. As mentioned in .4 (or
    .5 ?), the NL: destination slipped into the destination file because
    of 1) the behaviour of the installation procedure - taking additional
    destinations for a printer type as default (has already been discussed
    in another note) and, of course, 2) our system manager not having
    read the installation guide carefully enough to be aware of this
    'feature'. So he entered NL which was never intended to be used.
    
    When removing the NL: destination with the new (thank you !) AUTODEST
    utility, the second LN01 destination was also removed !  So I went
    back to the original version and removed the NL stuff with the editor.
    Well, and finally I found that both the BUFOVF and INVROUT messages
    (now I had both of them back again, as reported in .4) were caused
    by a (too ?) long destination name LN01_LASER_PRINTER. When I modified
    that name to LN01, both DOCUMENT and AUTODEST were happy again.
    
    Chris, many thanks to your really fast support !
    Hans.

    Hmmm. I copied the DOCUMENT V1.0 files last night and just finished
    installing the stuff (DOC010, DOCLN03010, DOCINT010). Trying to
    build a one page memo as a test I get the same errors discussed
    here: %CLI-W-BUFOVF (command buffer overflow) and %CLI-E-INVROUT
    (invalid routine specified in command tables).
    
    I did a "RENAME DOC$LOCAL_FORMATS:CUP$DESIGNS.DAT DOC$DESIGNS.DAT"
    like section 1.3.1 of the Internal Install Notes say to do. I even
    check the .DAT file for "NL:" stuff but there isn't any.
    
    I haven't done any fancy stuff or anything, just vanilla installation.
    
    Anybody know what's up?
    
    -Glenn-

         Did you check your DOC$STANDARD_FORMATS:DOC$DESTINATIONS.DAT
         file?  Possibly an extraneous character was accepted into
         that data file during installation.  If you don't see
         anything, please send me your doc$destinations.dat file
         and your doc$local_formats:doc$designs.dat.
         
         Chris

I to am getting the messages %CLI-W-BUFOVF and %CLI-E-INVROUT. After
reading this note I have concluded that my DOC$DESTINATIONS.DAT may have
something wrong with it. Knowing how touchy this file is, I thaught I'd
ask the resident guru before monkeying around with it. I think my problem
lies on the line that says:

	DESTINATION TLTL LN03 -

TLTL is the name of the LN03 printer que. I'm not sure the next DESTINATION
line is correct either. The information following the Form Feed is my 
DOC$DESTINATIONS.DAT.

Thanks ALOT for any help,

chris

DESTINATION LN01_LASER_PRINTER LN01 -
 /command_procedure=DOC$LN01_TOOLS:DVC$LN01.COM -
 /dvi_filetype=.DVI_LN01 -
 /fonts_filetype=.LN01_FONTS -
 /format_file=SDMLLPR -
 /output_filetype=.LN01 -
 /print=(queue=SYS$LASER,nofeed,passall) -
 /special_characters=TEX$LN01CHARS
 parameter number HORIZONTAL_OFFSET/default=72
 parameter number VERTICAL_OFFSET/default=72
 parameter string STARTING_PAGE
 parameter string ENDING_PAGE
 parameter string NUMBER_OF_PAGES

! DOC$DESTINATIONS.DAT
!
! COPYRIGHT (c) 1987 BY
! DIGITAL EQUIPMENT CORPORATION, MAYNARD, MASSACHUSETTS.
! ALL RIGHTS RESERVED.
!
! THIS SOFTWARE IS FURNISHED UNDER A LICENSE AND MAY BE USED AND COPIED
! ONLY  IN  ACCORDANCE  OF  THE  TERMS  OF  SUCH  LICENSE  AND WITH THE
! INCLUSION OF THE ABOVE COPYRIGHT NOTICE. THIS SOFTWARE OR  ANY  OTHER
! COPIES THEREOF MAY NOT BE PROVIDED OR OTHERWISE MADE AVAILABLE TO ANY
! OTHER PERSON.  NO TITLE TO AND  OWNERSHIP OF THE  SOFTWARE IS  HEREBY
! TRANSFERRED.
!
! THE INFORMATION IN THIS SOFTWARE IS  SUBJECT TO CHANGE WITHOUT NOTICE
! AND  SHOULD  NOT  BE  CONSTRUED  AS A COMMITMENT BY DIGITAL EQUIPMENT
! CORPORATION.
!
! DIGITAL ASSUMES NO RESPONSIBILITY FOR THE USE  OR  RELIABILITY OF ITS
! SOFTWARE ON EQUIPMENT WHICH IS NOT SUPPLIED BY DIGITAL.
!
! Facility:
!   VAX DOCUMENT
!
! ***DO NOT EDIT THIS FILE***


DESTINATION TLTL LN03 -
 /dvi_filetype=.DVI_LN03 -
 /fonts_filetype=.LN03_FONTS -
 /format_file=SDMLLN03 -
 /output_filetype=.LN03 -
 /print=(queue=TLTL,nofeed,passall) -
 /special_characters=TEX$LN03CHARS
 parameter number HORIZONTAL_OFFSET/default=72
 parameter number VERTICAL_OFFSET/default=72
 parameter string STARTING_PAGE
 parameter string ENDING_PAGE
 parameter number NUMBER_OF_PAGES

DESTINATION LN03_LASER_PRINTER LN03 -
 /dvi_filetype=.DVI_LN03 -
 /fonts_filetype=.LN03_FONTS -
 /format_file=SDMLLN03 -
 /output_filetype=.LN03 -
 /print=(queue=SYS$LN03,nofeed,passall) -
 /special_characters=TEX$LN03CHARS
 parameter number HORIZONTAL_OFFSET/default=72
 parameter number VERTICAL_OFFSET/default=72
 parameter string STARTING_PAGE
 parameter string ENDING_PAGE
 parameter number NUMBER_OF_PAGES

DESTINATION LINE_PRINTER LPR -
 /dvi_filetype=.DVI_LINE -
 /fonts_filetype=.LINE_FONTS -
 /format_file=SDMLLPR -
 /output_filetype=.LINE -
 /print=(queue=MAGI_LIA0,nofeed) -
 /special_characters=TEX$LPCHARS
 parameter number HORIZONTAL_OFFSET
 parameter number VERTICAL_OFFSET
 parameter string STARTING_PAGE
 parameter string ENDING_PAGE
 parameter number NUMBER_OF_PAGES
 parameter number /value=0

DESTINATION TERMINAL LPR -
 /dvi_filetype=.DVI_LINE -
 /exclude_action=(print) -
 /fonts_filetype=.LINE_FONTS -
 /format_file=SDMLLPR -
 /output_filetype=.TERM -
 /special_characters=TEX$LPCHARS
 parameter number HORIZONTAL_OFFSET
 parameter number VERTICAL_OFFSET
 parameter string STARTING_PAGE
 parameter string ENDING_PAGE
 parameter number NUMBER_OF_PAGES
 parameter number /value=2

DESTINATION MAIL LPR -
 /dvi_filetype=.DVI_LINE -
 /exclude_action=(print) -
 /fonts_filetype=.LINE_FONTS -
 /format_file=SDMLLPR -
 /output_filetype=.TXT -
 /special_characters=TEX$LPCHARS
 parameter number HORIZONTAL_OFFSET
 parameter number VERTICAL_OFFSET
 parameter string STARTING_PAGE
 parameter string ENDING_PAGE
 parameter number NUMBER_OF_PAGES
 parameter number /value=1


DESTINATION TAG_TABLE TAG -
 /exclude_action=(text_formatter,device_converter,print) -
 /output_filetype=.STT

DESTINATION VIDEOTEX LPR -
 /dvi_filetype=.DVI_LINE -
 /exclude_action=(print) -
 /fonts_filetype=.LINE_FONTS -
 /format_file=SDMLLPR -
 /output_filetype=.VTX -
 /special_characters=TEX$LPCHARS
 parameter number HORIZONTAL_OFFSET
 parameter number VERTICAL_OFFSET
 parameter string STARTING_PAGE
 parameter string ENDING_PAGE
 parameter string NUMBER_OF_PAGES
 parameter number /value=3
 parameter presence MULTINATIONAL_CHARACTER_SET

         I'm sorry, I forgot to reply to the cause of these CLI buffer
         overflows.  The destination and design data files are parsed
         using CLI$ VMS system services.  Unfortuately the CLI$
         routines have an arbitrary limit on the size of any given
         command, this limit is 256 characters, spaces included. 
         
         Many of the people who have been adding LN01 support run
         into this limit because of the length of the command
         procedure file spec.  I already complained to the source
         of the problem.
         
         You will get the error no matter what destination
         you are using since the entire data file is parsed on
         each run of DOCUMENT.  Probably the LN01 destination on
         your system doesn't work, since that is where the error
         occured.
         
         To fix it merely abrieviate the command qualifiers in the
         destination data file just as you would on a DCL command
         line.  Therefore, your LN01 destination would change to:
         
         
DESTINATION LN01_LASER_PRINTER LN01 -
/command_proc=DOC$LN01_TOOLS:DVC$LN01.COM -
/dvi=.DVI_LN01 -
/fonts=.LN01_FONTS -
/format_file=SDMLLPR -
/output=.LN01 -
/print=(queue=SYS$LASER,nofeed,passall) -
/special=TEX$LN01CHAR
         
 parameter number HORIZONTAL_OFFSET/default=72
 parameter number VERTICAL_OFFSET/default=72
 parameter string STARTING_PAGE
 parameter string ENDING_PAGE
 parameter string NUMBER_OF_PAGES

         Or whatever, just as long as the DESTINATION command is
         less than 256 characters.  Note that the parameters are
         actually different commands called PARAMETER, these are
         each parsed individually so you do not need to include
         these when you count the length of the destination command.
    
         
         Hope this helps.
         
         Chris              

    I changed
    		LN01_LASER_PRINTER to LN01
    	    and LN03_LASER_PRINTER to LN03 and everything works great.
    
    Thank you very much for the information,
    
    chris