Administrator's Guide
Workstation users can request ADSM services by using an application that
uses the ADSM application programming interface (API). An administrator
uses the REGISTER NODE command to register the workstation as an ADSM
client.
For applications that use the ADSM API, compression can be
determined by:
- An administrator during registration who can:
- Require that files are compressed
- Restrict files from being compressed by the client
- Allow the application or client user to determine the compression status
- The client options file. If an administrator does not set
compression on or off, ADSM checks the compression status set in the client
options file. The client options file is required, but the API user
configuration file is optional.
- One of the object attributes. When an application sends an object
to the server, some object attributes can be specified. One of the
object attributes is a flag that indicates whether or not the data has already
been compressed. If the application turns this flag on during either a
backup or an archive operation, then ADSM does not compress the data a second
time. This process overrides what the administrator sets during
registration.
For more information on setting options for the API and on controlling
compression, see ADSM V3 Using the Application Program Interface.
For applications using the ADSM API, the file deletion option can be
set by:
- An administrator during registration
If an administrator does not allow the file deletion, then an ADSM
administrator must delete any objects or file spaces associated with the
workstation from server storage.
If an administrator allows file deletion, then ADSM checks the client
options file.
- An application using the ADSM API deletion program calls
If the application uses the dsmDeleteObj or
dsmDeleteFS program call, then objects or files are marked for
deletion when the application is executed.
[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]