Conference vaxuum::document_ft

 The messages are stored in SYS$MESSAGE:DOC$MSG.EXE and respectively mean:

   DOC-I-IDENT VAX Document !AS   (=V1.0)
   DOC-F-OPEN_DEST Error opening DOC$DESTINATIONS data file

 Are you sure the installation did go right (full/partial)? Check for the
 presence of the DOC$MSG file in SYS$MESSAGE and 
 DOC$STANDARD_FORMATS:DOC$DESTINATIONS.DAT

Theo

    If both files Theo mentioned are in there proper places, check
    that their protection permits W:RE.
    
    Lee

< Note 874.2 by VAXUUM::SEGAL >
                                   -< hmmm >-

    If both files Theo mentioned are in there proper places, check
    that their protection permits W:RE.
    
    Lee


Many thanks for the quick reply Theo and Lee. I have DOC$MSG.EXE and it is W:RE
but I do not have a DOC$STANDARD_FORMATS: defined. I see in the
installation for Document (the first one I did) it is defined. Below is my 
DOC$STARTUP.COM and if this is where it is supposed to be I am in trouble.

$ defi/syst/exec/tran=concealed DOC$ROOT $1$DJA6:[DOC$TOOLS.]
$ defi/syst/exec DOC$LOCAL DOC$ROOT:[LOCAL]
$ defi/syst/exec DOC$LOCAL_TOOLS DOC$ROOT:[LOCAL.TOOLS]
$ defi/syst/exec DOC$LOCAL_FORMATS DOC$ROOT:[LOCAL.FORMATS]
$ defi/syst/exec DOC$LN01_FONTS DOC$ROOT:[TEX.LN01.FONTS]
$ defi/syst/exec DOC$LN01_TOOLS DOC$ROOT:[TEX.LN01.TOOLS]
$ defi/syst/exec DOC$LOCAL DOC$ROOT:[LOCAL]
$ defi/syst/exec DOC$LOCAL_TOOLS DOC$ROOT:[LOCAL.TOOLS]
$ defi/syst/exec DOC$LOCAL_FORMATS DOC$ROOT:[LOCAL.FORMATS]
$ defi/syst/exec DOC$LN01_FONTS DOC$ROOT:[TEX.LN01.FONTS]
$ defi/syst/exec DOC$LN01_TOOLS DOC$ROOT:[TEX.LN01.TOOLS]

As I mentioned the IVP ran after the installation. I then rebooted the
cluster for other unrelated reasons and lost the logicals? The installation
completed successfully for sure, but not the first time for any of the
modules. I saw nothing about "go all the way back to go if this fails"
messages. Maybe that is what is wrong? Anyway, I have no file
DOC$DESTINATIONS.DAT. Where do I go from here?

Jack Keefe

    The installation procedure executes the DOC$STARTUP.COM file,
    which defines all the logicals needed to run the IVP, so it
    ran succesfully because those names were defined.
    
    After the IVP has run, you must edit the sys$startup file 
    to include execution of DOC$STARTUP.COM.
    
    The directions for doing that are in the printed installation
    guide and they also appear on the screen.  Once you have booted
    the system, the old logical names go away, and if your
    system start up does not execute DOC$STARTUP.COM, you will not have
    any of the DOCUMENT logicals defined and you will not be able to
    run DOCUMENT.                                                   
    
    bill

Thanks for your interest Bill. Please see my reply note 874.3. I do indeed run
DOC$STARTUP.COM . The problem seems to be that the logicals are somehow not
in DOC$STARTUP.COM . Please read note 874.3 for all the details. I do
not know if it is an installation bug or what. Seems like that is what
it is since I got no messages that DOC$STARTUP.COM had been corrupted by
a failed but subsequently succeeded installation.

Thanks agin for your interest. Any further help would be greatly apreciated.

Jack Keefe

    Sorry, Jack.  You are right, I did not read the contents of 
    DOC$STARTUP.COM that you supplied in 874.3.  It had the right
    length, but I did not see that the logical names were wrong.
    
    It looks to me like you installed the DOCINT010 kit twice,
    which is how you got two sets of definitions for the "local"
    logical names and the "ln01" logical names.  And somehow you
    lost all the "external" logical names, including DOC$STANDARD_FORMATS.
    
    I'll try to figure out how that can happen.
    
    You will have to reinstall DOC010 and then DOCINT010 in order to
    get the DOC$STARTUP.COM corrected, unless you want to simply try
    using a DOC$STARTUP.COM that I can send you.  
    
    bill
    

    Because there is no doc$destinations.dat (as noted in .3), I'd say
    that it would be better to take from the top. If doc$destinations
    is not present or gets scrambled, one can spend quite a bit of time
    in the trenches with it.

    Well, Jack may be looking for DOC$DESTINATIONS.DAT in the
    DOC$STANDARD_FORMATS: directory (DOC$ROOT:[TEX.FORMATS]),
    but if DOC$STANDARD_FORMATS is not defined, then he can't
    see the files that are located there.  My point is that the
    DOCUMENT tree may be correct and the only thing that may
    be missing is the "defi/syst ..." lines in DOC$STARTUP.COM
    that define the logicals.  Can't figure out how that can
    happen, but...

    Please send file DOC$STARTUP.COM and I will try it.
    Regards how DOC$STARTUP.COM got corrupted, I have no idea. I
    have the hardcopy console listing from the installation if
    you are interested. I did indeed have to do the installations
    several times to get the responses correct, etc.. I saw nothing
    anywhere to the effect "if this installation dies go back to
    the beginning .... ". Did I miss something?
    Many thanks for your time.
    Jack Keefe    

    Karl:
    	I just answered your mail to TSG::SYSTEM. Sorry I failed to
    get back right away yesterday.
    
    Anyway, the file doc$destinations.dat is there. There is no logical
    pointing to it. Bill suggested sending down a doc$startup.com and
    see if that will work which I think should fix it.
    
    If I have to do it all over, what should I delete before I start.
    while doing this past installation, one pass of docln03 failed 
    because I had not deassigned the logical doc$root and had not deleted
    the directory [doctools...]. Any thoughts would be extremely
    helpful.
    
    Thanks
    JEK

 You have to delete the entire directory tree that is now pointed at
 by doc$root: logical name. Including that rootdirectory itself.
 Then VMSINSTALL as described and hope your luck doesn't run out...

Theo