Below is an excerpt from the README.SRV file.
ADSM has been updated to provide additional control related to the
administrative authority required to issue selected commands that cause the
ADSM server to write information to an external file. A new server option
REQSYSAUTHOUTFILE has been added to control this processing.

REQSYSAUTHOUTFILE YES:  Specifies that system authority is required for
administrative commands that cause the server to write to an external file.
The commands and associated parameters that are controlled by this option are:

      - MOVE and QUERY DRMEDIA when the CMD parameter has been specified
      - MOVE and QUERY MEDIA when the CMD parameter has been specified
      - BACKUP VOLHISTORY  when the FILENAMES parameter has been specified
      - BACKUP DEVCONFIG  when the FILENAMES parameter has been specified
      - TRACE BEGIN  when a file name has been specified
      - QUERY SCRIPT when the OUTPUTFILE parameter has been specified

REQSYSAUTHOUTFILE NO:  Specifies that system authority is not required for
administrative commands that cause the server to write to an external file
(i.e. there is no change to the privilege class required to execute the
command).

    The default is REQSYSAUTHOUTFILE YES.

In addition, when REQSYSAUTHOUTFILE NO has been specified, authorization
changes have been been made to select QUERY commands that cause the ADSM
server to write information to an external file. The commands and their
associated authorization changes are:

     Jim Sporer


     ______________________________ Reply Separator
     _________________________________
     Subject: Administrator not Authorized?
     Author:  "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>  at IPNET
     Date:    8/9/99 4:43 PM


     (Embedded image moved to file: pic17119.pcx)

     From: Doug Crossan@PERDUE on 08/09/99 04:43 PM


     To:   ADSM-l AT vm.marist DOT edu
     cc:
     Subject:  Administrator not Authorized?

     I am running ADSM 3.1.2.20 on AIX 4.3.2. I have set up an
     administrator called operator with, appropriately enough, operator
     privilege. This administrator can run the following command:

     mov drm \* wherest=notmo tost=va w=y

     But that same administrator can NOT run the following command:

     mov drm \* wherest=courierr cm=\"checkin libvol 3494lib \&vol
     status=scratch\" w=y

     Anyone out there know why?

     Thank you.

     doug.crossan AT perdue DOT com