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

Conference vaxuum::document_ft

Title:DOCUMENT T1.0
Notice:**New notesfile (DOCUMENT.NOTE) now available (see note 897)**
Moderator:CLOSET::ADLER
Created:Mon Feb 09 1987
Last Modified:Thu Oct 31 1991
Last Successful Update:Fri Jun 06 1997
Number of topics:897
Total number of notes:4397

253.0. "Building STT files" by CYCLPS::CARRIG () Wed Apr 15 1987 10:09

We have both versions of DOCUMENT on the system, and invoke the version
we want by either the DOCNEW.COM or DOCOLD.COM file. However, with the
two versions on the system, DOCTYPE_STT does not work; (TAG_TABLE is
not defined as a destination.)

We have checked the steps listed in the Section "Building STT Files"
in the Release Notes.  Can anyone see what we need to do?

Thanks.  


$  
$ This is DOCNEW.COM
$
$set message/nofacility/notext/noidentification/noseverity
$on warn then goto end_if1
$write sys$output ""
$write sys$output "                           Activating DOCUMENT V1.0"
$write sys$output ""
$ defi DOC$ROOT DRB4:[DOCTOOLS.]
$ defi DOC$TOOLS DRB4:[DOCTOOLS.TOOLS]
$ defi DOC$GUTENTAGSHR DOC$ROOT:[TOOLS]GUTENTAGSHR.EXE
$ defi DOC$INDEXSHR DOC$ROOT:[TOOLS]DOC$INDEXSHR.EXE
$ defi DOC$TEXSHR DOC$ROOT:[TOOLS]DOC$TEXSHR.EXE
$ defi DOC$LPR_FONTS DOC$ROOT:[TEX.LPR.FONTS]
$ defi DVC$LPRSHR DOC$ROOT:[TEX.LPR.TOOLS]DVC$LPRSHR.EXE
$ defi DOC$STANDARD_FORMATS DOC$ROOT:[TEX.FORMATS]
$ defi DOC$LOCAL_ELEMENTS NL:
$ defi DOC$LOCAL DOC$ROOT:[LOCAL]
$ defi DOC$LOCAL_TOOLS DOC$ROOT:[LOCAL.TOOLS]
$ defi DOC$LOCAL_FORMATS DOC$ROOT:[LOCAL.FORMATS]
$ defi DOC$LN03_FONTS DOC$ROOT:[TEX.LN03.FONTS]
$ defi DVC$LN03SHR DOC$ROOT:[TEX.LN03.TOOLS]DVC$LN03SHR.EXE
$ SDMLLSE == "LSEDIT/ENVIRONMENT=DRB4:[DOCTOOLS.LSE]SDMLLSE.ENV"
$ @DOC$ROOT:[SETUP]DOC$SETUP
$ @DOC$ROOT:[LOCAL]DOC$LOCAL_SETUP
$end_if1:
$set message/facility/text/identification/severity
$exit
$
$ This is DOCOLD.COM
$
$set message/nofacility/notext/noidentification/noseverity
$on warn then goto end_if1
$ set noon
$ deas DOC$ROOT 
$ deas DOC$GUTENTAGSHR 
$ DEAS DOC$TOOLS
$ deas DOC$INDEXSHR 
$ deas DOC$TEXSHR 
$ deas DOC$LPR_FONTS 
$ deas DVC$LPRSHR 
$ deas DOC$STANDARD_FORMATS 
$ deas DOC$LOCAL_ELEMENTS
$ deas DOC$LOCAL 
$ deas DOC$LOCAL_TOOLS
$ deas DOC$LOCAL_FORMATS
$ deas DOC$LN03_FONTS
$ deas DVC$LN03SHR 
$ ASSIGN CYCU:[DOCTOOLS.] DOC$ROOT
$ @DOC$ROOT:[LOCAL]DOC$LOCAL_SETUP.COM
$ @DOC$ROOT:[SETUP]DOC$SETUP.COM
$end_if1:
$set message/facility/text/identification/severity
$exit
T.RTitleUserPersonal
Name
DateLines
253.1need a bit more infoCLOSET::ANKLAMFri Apr 17 1987 13:048
    
    Does building STT files work on either DOCNEW or DOCOLD? If
    you installed the DEC internal kit or T1.0, the DOC$DESTINATIONS.DAT
    file in DOC$ROOT:[TOOLS] should contain an entry for TAG_TABLE.
    You also need the entries in DOC$DESIGNS.DAT for the DOCTYPE_STT
    'doctype'. This was in the stub file CUP$DESIGNS.DAT.
    
    -patti
253.2CYCLPS::CARRIGTue Apr 21 1987 13:4424
Thanks for getting back to me.

We installed T1.0, and everything worked OK until we restored 
BL06. When we execute DOCOLD.COM, BL06 works fine, including BUILD_STT.

When we execute DOCNEW.COM, however, not everything works OK. In particular,
DOCTYPE_STT is broken.  Since writing the first note I stumbled upon
the BASELEVELS.COM, and am now comparing how the logicals are setup in
that command, and how we have set up the logicals in DOCNEW.COM. So far,
I do not see what we have missed. Since DOCTYPE_STT worked OK before we
had both versions of DOCUMENT on the system, my plan of attack is to
try to see whether some logical has not been reassigned. The two versions
are on separate disks, so there should not be a problem with keeping
them separate.

As stated in my first note, we followed the procedures outlined in
the Release Notes, and pointed out in your reply. (As far as I can tell,
we have set up everything as suggested.) After all, DOCTYPE_STT once
worked.

If I can supply any further information, please indicate exactly what you
would look at. So far, this problem is not critical, but we would like to
resolve it.  Thanks very much.