Conference azur::mcc

I belive that version 1 is directly from the distribution kit, and
it seems a bit dangerous to give world write access.
Version two was generated by the DECnet FDA field test installation procecure,
and is better.
Version three was generated by a manual rebuild, for the TCPIP_AM
installation, and is not usable without modifying for at least W:R

MCC$PTB_PARSER.DAT;3
                      3-APR-1990 11:58:48.46  [SYSTEM]    (RWD,RWD,R,)
MCC$PTB_PARSER.DAT;2
                      2-APR-1990 16:14:17.71  [SYSTEM]    (RWD,RWD,RWD,R)
MCC$PTB_PARSER.DAT;1
                      1-MAR-1990 17:53:33.47  [SYSTEM]    (RWED,RWED,RWED,RW)

Hi,

I copied my mcc$common files from my system disk to a user disk.
And since then I am having mcc problems due to the required protections 
 on the files.
Luckily I found note re -.1 to reset the parse table but other file protections
are still cause failure (see end) 
So  would someone post an mcc file listing with the permissions.
This stuff should be in an MCC administration GUIDE --Is there such a thing??


--I know: I  deleted  the system disk files TOO quickly. 
Thanks,  ===STEVE

........below startup errors :

MCC ALARMS RULE __DUMMY_TEST
AT  4-APR-1990 10:23:27


Database error occurred while storing rule information.
                             MIR Status = %RMS-E-CRE, ACP file create failed
MCC ALARMS RULE __DUMMY_TEST
AT  4-APR-1990 10:23:30


Software logic error detected
                      MCC Routine Error = %RMS-E-CRE, ACP file create failed

RE: .2

  The startup errors you are seeing:

> ........below startup errors :
> 
> MCC ALARMS RULE __DUMMY_TEST
> AT  4-APR-1990 10:23:27
> 
> 
> Database error occurred while storing rule information.
>                              MIR Status = %RMS-E-CRE, ACP file create failed
> MCC ALARMS RULE __DUMMY_TEST
> AT  4-APR-1990 10:23:30
> 
> 
> Software logic error detected
>                       MCC Routine Error = %RMS-E-CRE, ACP file create failed

  are being caused by the protection settings on the following two files:

  MCC$ALARMS_ATTRIBUTE_MIR.DAT;1            1782  (RWED,RWED,RWED,RWE)
  MCC$ALARMS_INSTANCE_MIR.DAT;1             2301  (RWED,RWED,RWED,RWE)

  The protections shown above are (currently) the default protections that have
  been set on these files in the EFT kit.

  Please understand that these file protections will be changed in the EFT 
  update release.  SQM doesn't appreciate world writable files being 
  distributed on kits!  

  I'm not sure about an "Administrative guide", but I know that the Alarms 
  Use manual will be updated to discuss setting appropriate protections.

                                                                - Jerry Plouffe

                                                          Alarms Project Leader

    To add to Jerry's note. We are currently reviewing all of the default
    file protections so that an accurate list can be generated. At this
    time I do not know who other than SQM is slated to get it, but when
    it is done I will make sure it gets at least posted here and included
    in the developers kit.
    
    About the PTB file protections, all you need is READ. Depending
    upon who you want to be able to get at the MCC command set, you
    can decide if you want to to be a World, Group, System or Owner priv.
    
    The reason you got the parse tables in the specific directory is
    because PTB simply wirtes the file to MCC$SYSTEM. That means if
    you have it defined to include a specific, then that is where it
    goes. The write uses a logical so that it can be used by a development
    tool. The point was to allow multiple users to point to differing
    specifics so that private copies of certain files could be maintained
    during development. This is explained in the Guide to Writing an
    Access Module.
    
    
    jill
    

One more followup  question:  does the TRM use the same logical to read
the parse tables as PTB uses to write them?  We have a non-clustered
system, so I would have thought that even if PTB wrote to sys$specific,
the TRM should have picked up the latest tables anyway.

    
    The TRM uses MCC$SYSTEM as well. Just remember on a cluster each
    cluster member has it's own sys$specific directory. This means an
    update on one node doesn't effect any of the others.
    
    

    Jill,
    
    A question : does the Iconic Map use the parse table, or is it just the
    FCL PM ?
    
    Philippe.

    
    A bunch of modules use the Parse Tables:
    
    FCL, IMPM, ALARMS, NOTIFICATION
    
    aud...