Doug Werth writes:

-----Original Message-----
From: Doug Werth [mailto:[log in to unmask]]
Sent: Thursday, February 22, 2001 9:15 AM
To: [log in to unmask]
Subject: Re: DBUTIL and SM capability


Leonard,

To clarify this statement, I believe it should say that you may fully
qualify the database name in DBUTIL using the SHOW command. AFAIK none of
the other commands will allow you to fully qualify the database, nor file
equate it, as you can see below.

>>show opsdb.pred.sys flags
  For database OPSDB.PRED.SYS

  Access is enabled.
  Autodefer is disabled.
  Dumping is disabled.
  Rollback recovery is disabled.
  Recovery is disabled.
  ILR is disabled.
  Mustrecover is disabled.
  Logging is disabled.
  Prefetch is disabled.
  Indexing is disabled.
  HWMPUT is disabled.
  Add entry into lock table for deadlock detect is enabled.
  Restart is disabled.
  Database last stored on TUE, FEB 20, 2001, 11:49 PM.
  Database has not been modified since last store date.
  Shadowing is disabled.
  Using Dependency SEMaphore(DSEM) is disabled.
  Subsystem access is READ/WRITE.
>>activate opsdb.pred.sys
                ^
  Database-access file name may not be qualified.
  Activation FAILED!!
>>addindex opsdb.pred.sys
                ^
  Database name may not be qualified.
>>create opsdb.pred.sys
              ^
  Database name may not be qualified.
>>
----------------------------------------------
On the Image SIB is #4 DBUTIL: Non-destructive creator access across groups:
This will allow a DB creator to specify a group name to do most any activity
except purge and erase.  Vote plenty and often for it.

Mike Berkowitz
Guess? Inc.