Conference azur::mcc

Hi

Maybe the file protection is not right.

The protection must be:
	S:RWED,
	O:RWED,
	G:RWED,
	W:R
On the following file:
	MCC_PTB_PARSER.BPT


See also page 9-11 in the DECmcc Use manual.


Regards	
	Henk.

  The new (default) file name for the parse table file is: mcc_fdictionary.bpt.

  The name: mcc_ptb_parser.bpt is quite old.

  Look for this file in the MCC_SYSTEM directory to check its protection.

                                                                       - Jerry

Following is the description of the file mcc_fdictionary.bpt.  The owner [1,4] 
is SYSTEM MANAGER.  It seems that the protection is right, but since I installed
DECmcc using SYSTEM account, all the files are owned by [1,4].  What can I do?


HGSW70> dir mcc_fdictionary.bpt/ful

Directory HGSW70$DKB0:[MCC]

MCC_FDICTIONARY.BPT;1                     File ID:  (148,2,0)
Size:         2640/2640       Owner:    [1,4]
Created:   7-FEB-1992 08:13:05.82
Revised:  13-MAR-1992 12:06:44.00 (5)
Expires:   <None specified>
Backup:    <No backup recorded>
File organization:  Sequential
File attributes:    Allocation: 2640, Extend: 0, Global buffer count: 0
                    No version limit
Record format:      Stream_LF
Record attributes:  Carriage return carriage control
RMS attributes:     None
Journaling enabled: None
File protection:    System:RWED, Owner:RWED, Group:RWED, World:R
Access Cntrl List:  None

Susan:

  Are you saying that you still get the "Can't read parse tables" message
  when you run the IMPM from your account?

  The protections look fine to me and it shouldn't matter if the owner is
  SYSTEM as long as world read is allowed -- which it apparantly is.

                                                                    - Jerry

    Have you installed ANY other optional modules?
    
    s/rob

DECmcc BMS V1.2 Baselevel 15 is the only software I have installed.  No other
optional modules are installed.  It is VMS V5.4-3 and DNS V1.1 that DECmcc
is running on.

The DECmcc BMS IVP and the DNS IVP are successfully passed.

But I am still getting error when run IMPM or FCL from any user account other 
than the SYSTEM account.

$ MANAGE/ENTERPRISE/INTERFACE=DECW

 software error: unable to read in parse table.
%MCC-F-PM_READPARERR, software error: unable to read in parse table.

or 

$ MANAGE/ENTERPRISE 

%MCC-F-PTBINACC, parse tables inaccessible, unable to initialize FCL PM
%MCC-F-TRM_FAILURE, PM unable to continue



Please help!!!!!!

Susan:

  What are the values of the logical mcc_system and mcc_common before you
  run the FCL or IMPM?

                                                                    - Jerry

Also, make sure you don't have copies of the parse tables in any 
"specific" directories.  Make sure the only parse table files are in 
MCC_COMMON and not in MCC_SPECIFIC.  Jerry's suggestion of checking your 
MCC_SYSTEM logicals is also very good. 

I got the error you are seeing and after changing the protections so 
to be PROT=(W:RE) everything worked.  It seems that changing the file 
protections did not help you, so make sure you don't have any rougue 
files hanging around.  

Also, if you do run the DAP tool (manage/tool/dict) and change the 
dictionary in any way, you will get a new parse table file with the wrong 
protections, so make sure you haven't created a new parse table file 
since you changed the protections on the parse table file that got 
installed with the kit.

...kjn

Afterall, I reinstalled the DECmcc BMS V1.2 BL15 again, but having the same 
problem. 

First of all, on this machine I haven't installed any version before V1.2 BL15.
Does it matter?

The mcc logicals loogs fine to me, they are :  

  "MCC_COMMON" = "HGSW70$DKB0:[MCC]"
  "MCC_DNS_SELECTION" = "DNS"
  "MCC_ICONS" = "MCC_COMMON"
  "MCC_MAPS" = "SYS$DISK:[]"
        = "MCC_COMMON"
  "MCC_NODE_IDP" = "49::"
  "MCC_REPORTS_FILES" = "HGSW70$DKB0:[MCC.MCC_REPORTS_FILES]"
  "MCC_SPECIFIC" = "SYS$SPECIFIC:[MCC]"
  "MCC_SYSTEM" = "MCC_SPECIFIC"
        = "MCC_COMMON"
  "MCC_TDF" = "+8:00"
  "MCC_UIL" = "MCC_COMMON"


I have set these three files with W:RE

MCC_FDICTIONARY.BPT      [1,4]                 (RWED,RWED,RWED,RE)
MCC_FDICTIONARY.DAT      [1,4]                 (RWED,RWED,RWED,RE)
MCC_META_DICTIONARY.DAT  [1,4]                 (RWED,RWED,RWED,RE)

What else can be wrong?  I believe I will have to install the BL4 if no clues.

Thanks for any help,
Susan

    Hi,
    
    I have the same problem on our VS4000-60 where I've installed mcc
    X1.2-15.
    The system account works fine, but from any other account with all
    privileges I can't startup mcc.
    Message received:
    
    $ manage/enterprise
    DECmcc (X1.2.15)
    
    %MCC-F-PTBINACC, parse tables inaccessible, unable to initialize FCL PM
    %MCC-F-TRM_FAILURE, PM unable to continue
    
    See also note 2321...
    Already any solutions for this?
                         
    	-Geert-        
    

    
    Thanks to a colleague from Switserland I found a solution for the
    problem I mentioned in .10.
    Increasing the working set quota's (wsdef,wsquota,wsextent) solved it.
    
    -Geert-
    
                         

    This was qared as qar 2522: the response is:
    
    
    I will retest these conditions. For the t1.2.4 build the parser file read
    error messages were surpressed. This was done so as to speed up the
    moving of the read into an independent shareable image (the messages
    were in the code using routines for printing that were not supported
    in the new shareable image).  This has since (x1.2.17) been rectified
    and the error messages replaced. The latest version should be able
    to provide more informative data. Note, that not all instances allow
    us to provide nice neat error messages, but we will try our best.
    
    jill
    
    
    -----------------
    
    retest:
    
    GOSTE::GOSTE> set proc/priv=all
    GOSTE::GOSTE> manage/enter
    DECmcc (X1.2.18 - cma BL9)
    
    %MCC-F-PARTABREAD, error reading parse tables into memory
    %SYSTEM-F-INSFWSL, insufficient working set limit
    %MCC-F-PTBINACC, parse tables inaccessible, unable to initialize
    FCL PM
    %MCC-F-TRM_FAILURE, PM unable to continue
    GOSTE::GOSTE>
    
                   

After all I get it work now. 

Is x1.2.17 available yet?  What's the difference between x1.2.15 and x1.2.17?
Where is x1.2.16?

Thanks again,
Susan

>Is x1.2.17 available yet?  What's the difference between x1.2.15 and x1.2.17?
>Where is x1.2.16?

X1.2.16, X1.2.17, and X1.2.18 are internal development group baselevels.
Unfortunately, we don't have the resources to support general distribution
of these baselevels.  X1.2.19 will (probably) be releases internally
shortly before the EFT update is released.

-- Erik

    Please run the MCC_AUDIT procedure if you are having problems with
    a new instalation. It will discover quota and parameter problems.
    It can be found at
    	NETS::USER$NETS:[MCC011.S-KIT]MCC_AUDIT.COM
    and it has updates made as we learn more so if you need it, grab a
    current copy.
    
    As always, comments and suggestions are welcome.
    
    s/rob