Conference vaxuum::document_ft

    See note 39, especially reply 39.4.

    I did follow the instructions in 39.4 (although without benefit
    of having read them first), and still got the error.  Could this
    be the problem that Patti Anklam referred to as a TeX problem with
    tag arguments beginning with 0?  Is there a workaround?
    
    -pd

    
    sorry I missed this earlier (actually, I saw there was a reply with
    an answer and skipped over it).
    
    the error is because \declogo isn't defined. it is defined in the
    file CUP$LOCAL_ELEMENTS.TEX (in the DEC internal kit in
    DOC$LOCAL_FORMATS). You have to have the logical name
    DOC$LOCAL_ELEMENTS defined, pointing to that file in order for the
    \declogo to be processed.
    
    patti
    

    I'm having a similar problem. When I define DOC$LOCAL_FORMATS to
    CUP$LOCAL_ELEMENTS I get the following:
    
    $ show log DOC$LOCAL_FORMATS
   "DOC$LOCAL_FORMATS" = "DOC$ROOT:[LOCAL.FORMATS]CUP$LOCAL_ELEMENTS.TEX" (LNM$PROCESS_TABLE)
   "DOC$LOCAL_FORMATS" = "DOC$ROOT:[LOCAL.FORMATS]" (LNM$SYSTEM_TABLE)
                                
    $ DOC COUNT_SEEKS MEMO POSTSCRIPT
    %DOC-I-IDENT, VAX DOCUMENT T1.0-008
[ T a g   T r a n s l a t i o n ]...
%TAG-I-TAG_IDENT, T1.0-002
%TAG-I-DEFSLOADD, End of Loading of Tag Definitions
%TAG-I-ENDPASS_1, End of first pass over the input
%TAG-I-CPU_USAGE, Pass 1: 10.4  Pass 2: 1.7  Total: 12.1 seconds
[ T e x t   F o r m a t t i n g ]...
%TEX-I-IDENT, T1.0-005


%RMS-F-FNM, error in file name
-TEX-I-FILENAME, ''
%DOC-F-ERROR_FORMATTER, Errors found by the Text Formatter.
    
    
    I tried defining DOC$LOCAL_FORMATS to some other files like
    [DOC$TOOLS.LOCAL.FORMATS]DOC$DESIGN.DAT and
    [DOC$TOOLS.LOCAL.FORMATS]CUP$MEMO.GDX  to no avail. 

    Can someone please help me?
    
    					Sieg
    
        
    Here is the the original error message I was getting
    
%DOC-I-IDENT, VAX DOCUMENT T1.0-008
[ T a g   T r a n s l a t i o n ]...
%TAG-I-TAG_IDENT, T1.0-002
%TAG-I-DEFSLOADD, End of Loading of Tag Definitions
%TAG-I-ENDPASS_1, End of first pass over the input
%TAG-I-CPU_USAGE, Pass 1: 11.0  Pass 2: 1.8  Total: 12.8 seconds
[ T e x t   F o r m a t t i n g ]...
%TEX-I-IDENT, T1.0-005















%TEX-W-UNDEFINEDCS, Undefined control sequence
%TEX-I-SHOWCONTEXT, '...pt\hbox {\kern 4pt\sixpointcc '
%TEX-I-SHOWCONTEXT, '                                          {TM}} \fi '
%TEX-I-SHOWCONTEXT, '...hbox to \hsize {\declogo '
%TEX-I-SHOWCONTEXT, '                                          \hskip 48pt\raise 5.2pt\hbo...'
%TEX-I-LINE, Error occurred on or around line number: 6
%TEX-I-SHOWCONTEXT, '\individualto{Distribution}'
%TEX-I-SHOWCONTEXT, '                           '
%TEX-I-FILENAME, 'count_seeks'
-TEX-I-ONPAGE, on page [1]






%TEX-I-PAGESOUT, 2 pages written.
-TEX-I-OUTFILENAME, 'disk$csse_3:[heintze.rp]COUNT_SEEKS.DVI_POST'
%DOC-E-ERROR_FORMATTER, Errors found by the Text Formatter.
    
    
    

>   I'm having a similar problem. When I define DOC$LOCAL_FORMATS to
>   CUP$LOCAL_ELEMENTS I get the following:
    
    You need to define DOC$LOCAL_ELEMENTS to be 
                                 ^^^^^^^^
    DOC$LOCAL_FORMATS:CUP$LOCAL_ELEMENTS.TEX. Doc$Local_Elements is
    the file; Doc$Local_Formats is the directory.
    
    Anyone have any mnemonics to help with this? We lose lots of folks
    on these corners.

    
    You also need to get the corrected version of CUP$LOCAL_ELEMENTS.TEX
    from CLOSET::KITS_:[DOCUMENT]. The error message about \sixpointcc
    is caused by a bug in the version of this file in the kit.
    
    patti

    Thank you very much for the prompt reply.  However, now I have a
    new problem:  DOCUMENT produces no errors now, but here is what
    appears on the screen:       
    
    [ P r i n t i n g  F i l e ]...
    Job COUNT_SEEKS (queue POSTSCRIPT_LPSC2, entry 998) started on
    LPS40$LPSC2
    TINCUP $
    %LPS-E-PARSYNERR, Syntax error in the /PARAMETERS qualifier at or
    near DATA_TYPE :POSTSCRIPT
    
    Job COUNT_SEEKS (queue LPS40$LPSC2, entry 998) terminated with error
    status
    %SYSTEM-F-ABORT, abort

    Can anyone help me with this?

That's a bug which we've fixed for V1.0. To fix it on BL8 systems,
you must *carefully* edit DOC$STANDARD_FORMATS:DOC$DESTINATIONS.DAT.

Locate the line which contains the string "DATA_TYPE:POSTSCRIPT" and
change the colon to an equal sign: "DATA_TYPE=POSTSCRIPT".

Be sure that that's the only change you make, and that the new version
has the same protection and owner as the previous version.

--Brian

    Or, if you can't wait for the destinations file fix, use the /PRINT
    qualifier on the DOCUMENT command to say it the right way:
    
    $ DOCUMENT /PRINT=(QUEUE=yourqueue,PARAMETER=DATA_TYPE=POSTSCRIPT)...
    
    
    Of course, since this is VMS syntax, you can shorten it a lot:
    
    	$ DOC /PRIN=(QUE=yourqueue,PARAM=DATA=POST)...
    
    
    So, until somebody fixes your DOC$DESTINATIONS.DAT, you can still
    print to the LPS40 or LN03R with DOCUMENT.
    
    --Mark