Conference acadmy::tpas_notes

67.0. "Load and Import RMU problem - A Fix?" by AYRMIS::LSS055::Charles (If you can't knit bring a book!) Thu Feb 09 1995 08:24

                  I N T E R O F F I C E   M E M O R A N D U M

                                        Date:     09-Feb-1995 11:42am GMT
                                        From:     Charles Flach @AYO
                                                  FLACH.CHARLES
                                        Dept:     Services UISG
                                        Tel No:   (7) 823-4011

TO:  LOIS MAGNI                           ( MAGNI @AWARD @VMSMAIL )


Subject: I: Load/Import fixes for rmu privs

        Lois,

        As you know we are using RDB V6.0 and have had problems with the
        RMU commands in the Load/Import com files.  This is because the
        mechanism for controlling which RMU functions an account can use
        on a particular database has changed.  This is now defined using
        Access control Lists/Entries on the RDB root file.

        Even though you have total access to an RDB (read, write,
        execute, delete and control) you will not be able to perform any
        RMU functions unless the appropriate RMU privileges exist for
        your account or for a rights identifier that you have been
        granted.

        One way to fix the TPAS Load/Import is as follows:

        o  Set up the tpas$xcldd_db database with the desired ACLs
           including RMU privileges:

�IS> dir/sec tpas$xcldd_db

Directory TPAS$ROOT:[DATA]

TPAS_XCLDD.RDB;1     TPAS$DB_OWNER         (RWED,R,,)
          (IDENTIFIER=TPAS$SUPPORT,ACCESS=READ+WRITE+EXECUTE+DELETE+CONTROL+
          BIT_5+BIT_6+BIT_7+BIT_8+BIT_9+BIT_10+BIT_11+BIT_12+BIT_13+BIT_14+
          BIT_15+BIT_16+BIT_17+BIT_18)
          (IDENTIFIER=TPAS$DB_OWNER,ACCESS=READ+WRITE+EXECUTE+DELETE+CONTROL+
          BIT_5+BIT_6+BIT_7+BIT_8+BIT_9+BIT_10+BIT_11+BIT_12+BIT_13+BIT_14+
          BIT_15+BIT_16+BIT_17+BIT_18)
          (IDENTIFIER=TPAS$DB_READ,ACCESS=READ+WRITE+EXECUTE)
          (IDENTIFIER=TPAS_XCLDD$DB_WRITE,ACCESS=READ+WRITE+EXECUTE)
          (IDENTIFIER=[*,*],ACCESS=NONE)

Total of 1 file.


�IS> rmu/show priv tpas$xcldd_db
Object type: file,  Object name: TPAS$ROOT:[DATA]TPAS_XCLDD.RDB;1,  on  9-FEB-19
95 12:56:18.27

          (IDENTIFIER=TPAS$SUPPORT,ACCESS=READ+WRITE+EXECUTE+DELETE+CONTROL+
          RMU$ALTER+RMU$ANALYZE+RMU$BACKUP+RMU$CONVERT+RMU$COPY+RMU$DUMP+
          RMU$LOAD+RMU$MOVE+RMU$OPEN+RMU$RESTORE+RMU$SECURITY+RMU$SHOW+
          RMU$UNLOAD+RMU$VERIFY)
          (IDENTIFIER=TPAS$DB_OWNER,ACCESS=READ+WRITE+EXECUTE+DELETE+CONTROL+
          RMU$ALTER+RMU$ANALYZE+RMU$BACKUP+RMU$CONVERT+RMU$COPY+RMU$DUMP+
          RMU$LOAD+RMU$MOVE+RMU$OPEN+RMU$RESTORE+RMU$SECURITY+RMU$SHOW+
          RMU$UNLOAD+RMU$VERIFY)
          (IDENTIFIER=TPAS$DB_READ,ACCESS=READ+WRITE+EXECUTE)
          (IDENTIFIER=TPAS_XCLDD$DB_WRITE,ACCESS=READ+WRITE+EXECUTE)
          (IDENTIFIER=[*,*],ACCESS=NONE)
�IS>


        You can do this with edit/acl or a set acl like this:

$set acl -
/acl=(IDENTIFIER=TPAS$SUPPORT,ACCESS=READ+WRITE+EXECUTE+DELETE+CONTROL) -
/replace=(IDENTIFIER=TPAS$SUPPORT,ACCESS=R+W+E+D+C+BIT_5+BIT_6+BIT_7+BIT_8+BIT_9
+BIT_10+BIT_11+BIT_12+BIT_13+BIT_14+BIT_15+BIT_16+BIT_17+BIT_18) -
tpas$xcldd_db

$set acl -
/acl=(IDENTIFIER=TPAS$DB_OWNER,ACCESS=READ+WRITE+EXECUTE+DELETE) -
/replace=(IDENTIFIER=TPAS$DB_OWNER,ACCESS=R+W+E+D+C+BIT_5+BIT_6+BIT_7+BIT_8+BIT_
9+BIT_10+BIT_11+BIT_12+BIT_13+BIT_14+BIT_15+BIT_16+BIT_17+BIT_18) -
tpas$xcldd_db

           The assumption being that the exclude database is not going to
           be removed and recreated on a regular basis.  Is this true
           Lois?

           Note: The 'proper' way to add/change these is by

             rmu/set priv

           but I couldn't do that because I didn't have the rmu priv to
           allow me to do it in the first place!

        o  Edit the command files for importing/loading to include the
           line:

             set acl/like=(object_name=tpas$xcldd_db) <db file name>

           e.g.

             set acl/like=(object_name=tpas$xcldd_db) tpas$nor$db

           At the point just after the creation of the new database.

           I.e. use the ACL for the exclude database as the basis for the
           other databases.

        I'll post the above in the conference as well.


        Regards

        Charley


  Charley,

  Thanks for posting this. As the TPAS Development site is only running on
  RDB 4, I will not be making any changes to the RDB ACLs as I cannot test.


  If you are running RDB 6 and are having problems with the RMU/VERIFY in:
	TPAS_SITE_IMPORT_DB.COM
	TPAS_SITE_IMPORT_STKRM_DB.COM
	TPAS_SITE_LOAD_NOR_DB.COM

  Then either add the ACLs as described by Charley in .0
     or edit these command streams and remove the RMU/VERIFY.


  I will post this as an SPR and incorporate a fix in the next release.

  Lois

Lois,

Don't forget there is an rmu/load in TPAS_SITE_LOAD_NOR_DB.COM

$ DEFINE SYS$OUTPUT TPAS_NOR_DB_LOAD.LOG
$ ON ERROR THEN DEASSIGN SYS$OUTPUT
$ RMU/LOAD/RMS_RECORD_DEF=FILE=TPAS_NOR_DB$RRD -
  /TRANSACTION_TYPE=BATCH_UPDATE TPAS$NOR$DB -
         NOR_TABLE      TPAS_NOR_DB$UNL
$ DEASSIGN SYS$OUTPUT

If running RDB 5 or 6 you need rmu privs or system privs.


Regards

Charley