Conference azur::mcc

    Did you startup DNS before invoking the MCC command file?  I believe
    there should be a DNS startup file DNS$CLIENT_STARTUP.COM.  Also, you
    need to have a DNS server to communicate with, this can be defined by
    running DNS$CHANGE_DEF_FILE.COM.  Try doing a show system and
    see if there are any DNS programs running.
    
    By the way, the mcc help builder has nothing whatsoever to do with
    DNS.  It is a simple stand-alone program which just merges the .HELP
    text files and builds a single .HLB help library file.
    
    -Matt.

    to see what went wrong on the help you would have to look at the
    log file created, and see if any .HLB files were created.
    
    

    Oh by the way to run the help builder you must have write access
    to the dicectory you are in, and at least read access to all of
    the .help files as well as the directory itself.
    

    HI,
    just clarifying some things,
    
    DNS runs OK, the server is my node (VS3100-38). DNS start correctly
    with the DNS$STARTUP file.
    
    The problem is: When i start mcc, manage/enter fails to search DNS$RTL
    and DNS$SHARE shareable installed files.
    
    If i install shareables images DNS will crash. (I.E DNS>SH DIR .)
    
    The second (little) problem is around logicals ??, when i log into
    MCC_SYSTEM directory (SYS$COMMON:[MCC]), yes the logicals are defined,
    and invoking MCC_build_help, the command file failed with an error like
    "The current directory must be MCC_SYSTEM" argggh...
    
    Thanks
    Thierry
    

The two problems you are having may be related.

Are your sys$common and sys$specific logicals defined correctly?  Does 
everything that needs access to them have access to them?

Informed sources tell me that your DNS images should be installed if you
are running the DNS startup scripts.  You can check your DNS startup procedures
to be sure.  SYS$MANAGER:DNS$STARTUP calls SYS$MANAGER:DNS$CLIENT_STARTUP which
in turn calls SYS$MANAGER:DNS$CLERK_STARTUP, which installs the DNS images.

But, if your sys$common and sys$specific logicals get incorrectly re-defined
in between the time DNS started up and when you're trying to run MCC,
or get defined in such a way that you can't get access to them, then nothing
is going to work very well.  

Try doing a show logical/full sys$common,sys$specific at various points between
the steps you've described in your earlier notes.

I'll bet something is redefining sys$common and sys$specific when it should
be redefining mcc_common and mcc_system.

regards,

Pete

    Pete,
    
    Seems to be a version problem... or...
    
    DNS$CLIENT_STARTUP DONT'T call DNS$CLERCK_STARTUP, if i do it manually,
    SOLICIT will fail with "Mailbox message badly fragmented"  after the
    SOLICIT DEF_PARSE command.... i've lost my latin (joke).
    
    If i install manually the DNS$SHARE and DNS$RTL, system will crash.
    There's an incompatibility between server 1.1 and clerk of VMS 5.3-1
    ??, i wrote a note to BOEHM::DNS notesfile.
    
    For the second problem, 
    
        "MCC_SYSTEM" = "MCC_SPECIFIC" (LNM$SYSTEM_TABLE)
    	     = "MCC_COMMON"
    1   "MCC_SPECIFIC" = "SYS$SPECIFIC:[MCC]" (LNM$SYSTEM_TABLE)
    1   "MCC_COMMON" = "SYS$COMMON:[MCC]"  (LNM$SYSTEM_TABLE)
    
    are the logicals for MCC_SYSTEM and common defined in my VMS...
    
    I think that's a compatibility problem between DNS server 1.1 and clerk
    ??
    
    
    Thanks
    Thierry
    

Re: DNS shareable image problems

Oh well, my guess was wrong, but it sounds like you're on the right track
with the DNS problem, or at least you've got the DNS folks' attention, and
they'll help you solve it -- I'll be watching your note in the DNS conference.
There is at least one other person experiencing the same problem as you.

Re: little problem with mcc_build_help.com

That command procedure hasn't been updated since we've relaxed the restrictions
on where you could put your mcc_system directories.  My suggestion (which
you've probably already done) is to just edit mcc_build_help.com and comment
out the following lines:

$   Location = F$DIRECTORY()
$   if ''Location' .NES. "[MCC]" THEN GOTO PrintError

and then try running the help file builder again.

regards,

Pete

    Pete,
    
    Thanks for solving .com problem.
    
    Effectively i'm not alone with the DNS problem, quite obscure.
    I hope that DNS folks may resolve it.
    
    Thanks and bises de Paris
    
    Thierry
    
    

I don't know where or why people have been told to delete all DNS files
before (re-)installing a DNS V1.1 Server, but it is incorrect.
Starting with VMS V5.3, the DNS clerk comes with the operating system.
If you delete the DNS clerk files and then install a DNS V1.1 Server, you've
got an unsupported and unworkable configuration, as some have discovered.

See note 378.* for the same problem and further exposition.

--Roger