Follow the general rules below when you enter commands.
The archive command archives a single file, selected files, or all files in a directory and its subdirectories on an ADSM server. Directories are archived.
Archive files that you want to keep in their present condition. To release storage space on your workstation, delete files as you archive them. Retrieve the archived files to your workstation whenever you need them again.
Syntax
.------------------.
V |
>>-Archive--+-----------+----+- filespec----+-+----------------><
'- options--' '- "filespec"--'
Parameters
You can use these common options with the archive command: changingretries, subdir. Go to Chapter 6. "Setting Common Options" for information about these common options.
Refer to Figure 28 for a list of common options you can use on all commands.
Examples
The table below provides examples of some tasks you might perform using the
archive command.
| Task | Command |
|---|---|
| Archive a single file named budget in the /home/proj1 directory. |
Archive /home/proj1/budget |
| Archive all files in the /home/proj1 directory that contain a file extension of .txt. |
Archive "/home/proj1/*.txt" |
| Archive a single file named budget and all files in the /home/proj1 directory that contain a file extension of .txt. |
Archive /home/proj1/budget "/home/proj1/*.txt" |
| Archive all files on the /home directory. |
Archive "/home/*" |
The cancel restore command displays a list of your restartable restore sessions in the ADSM server database. You can select zero or more restartable restore sessions that you want to cancel.
To cancel restartable restore sessions use the cancel restore command. To restart restartable restore sessions use the restart restore command. Use the cancel restore command when:
Syntax
>>-CANcel Restore--+-----------+-------------------------------><
'- options--'
Parameters
Refer to Figure 28 for a list of common options you can use on all commands.
Examples
To cancel a restore, you would enter:
cancel restore
The delete access command deletes authorization rules for files that are stored on the server. When you delete an authorization rule, you revoke the access a user has to any files specified by that rule.
Syntax
>>-Delete ACcess--+-----------+--------------------------------><
'- options--'
Parameters
Refer to Figure 28 for a list of common options you can use on all commands.
Examples
The table below provides an example of a task you might perform using the
delete access command.
| Task | Command |
|---|---|
| Display a list of current authorization rules and select the rules you want to delete. See the screen example below. |
Delete ACcess |
+--------------------------------------------------------------------------------+ | | |Index Type Node Owner Path | |_____ ____ ____________________________________ | |1 Backup NODE1 usera /home/dev/proja/list | |2 Archive NODE3 userb /home/fin/budg/depta | |3 Backup NODE4 userd /home/plan/exp/deptc | |4 Archive NODE5 usere /home/mfg/invn/parta | |Enter Index of rule(s) to delete, or quit to cancel: | +--------------------------------------------------------------------------------+
To delete the authorization rules that allow NODE3 and NODE5 to access your files, type 2 4 or (2,4) and press Enter.
The delete archive command deletes archived files from ADSM storage. Your ADSM administrator must give you authority to delete archived files.
Attention: When you delete archived files, you cannot retrieve them. Verify that the files are obsolete before you delete them.
Syntax
>>-Delete ARchive--+-----------+--+- filespec----+-------------><
'- options--' '- "filespec"--'
Parameters
You can use the subdir common option with the archive command. Go to Chapter 6. "Setting Common Options" for information about these common options.
Refer to Figure 28 for a list of common options you can use on all commands.
Examples
The table below provides examples of some tasks you might perform using the
delete archive command.
| Task | Command |
|---|---|
| Delete a single archived file named budget. |
Delete AR /user/home/proj1/budget |
| Delete all archived files in the /user/home/proj1 directory that end with the characters *.txt . | Delete ARchive "/user/home/proj1/*.txt" |
| Delete files archived from the /user/project directory using the pick option. | D AR "/user/project/*" -pick |
ADSM AUTHORIZED USER
The delete filespace command deletes file spaces from ADSM storage. A file space is a logical space on the ADSM server that contains files you backed up or archived. ADSM assigns a separate file space on the server for each file system at your workstation from which you back up or archive files. The file space name is the same as the file system name. When you enter the delete filespace command, ADSM displays a list of your file spaces . Select those files that you want to delete from this list.
Your ADSM administrator must give you authority to delete a file space. You need BACKDEL authority if the file space you want to delete contains backup versions, or ARCHDEL authority if the file space contains archive copies. If the file space contains both backup versions and archive copies, you need both types of authority.
Attention: When you delete a file space, you delete all backup versions and archive copies within that file space. When you delete a file space, you cannot retrieve the files. Verify that the files are obsolete before you delete them.
Syntax
>>-Delete Filespace--+-----------+-----------------------------><
'- options--'
Parameters
Refer to Figure 28 for a list of common options you can use on all commands.
Examples
The table below provides an example of some tasks you might perform using
the delete filespace command.
| Task | Command |
|---|---|
| Delete a file space. | Delete Filespace |
| Delete a file space. Use the dateformat and timeformat options to reformat the dates and times. | Delete Filespace -DATEformat=5 -TIMEformat=4 |
The help command displays help information for the command-line client. Enter the number of the topic that you want to view. If there is more than one screen of topics, scroll backward or forward through the Table of Contents. To exit, type q and press Enter.
Syntax
>>-Help--------------------------------------------------------><
Parameters
There are no parameters for this command.
Examples
To display a list of help choices, type Help and press Enter.
The incremental command backs up all changed or new files in the default client domain or from the file systems, directories, or files specified in the command, that are not excluded from backup services. To incrementally back up selected files, supply the file specification in the command. To incrementally back up files in the default domain, do not provide a file specification in the command.
The following attributes in the management class assigned to the file affect whether the file is actually backed up:
You can assign the default management class to a file or you can assign a specific management class to a file using the include option in an include-exclude list.
There are two types of incremental backup that you can select: "full incremental" or "incremental by date". The default is a full incremental backup. You must do a full incremental backup before you can perform an incremental by date backup. In a full incremental, the client queries the server so that it knows the exact state of your storage. During a full incremental, ADSM uses this information to:
All of this processing is required to maintain backups according to the policies defined in the management classes.
In an "incremental by date", the client only asks the server for the date and time of the last incremental backup of the entire file system. If the file's last changed date and time is after that of the last incremental backup of the entire file system, the file is backed up. Otherwise it is not, even if the file is new to the workstation. In an "incremental by date", files are not expired or rebound on the server, and the frequency attribute of the management classes is ignored. Because they do not change the last changed date and time, changes to access control lists (ACL) are not backed up during an "incremental by date". You can use the query filespace command to determine the date and time of the last incremental backup of the complete file system.
To do an "incremental by date" backup, specify -incrbydate as an option. Only use the "incremental by date" option if you must meet a limited backup time window, and a full incremental takes longer than the allotted time. Periodically perform full incremental backups to bring the ADSM server in line with your workstation's status. For example if you have only a limited time during the week to perform backups, but extra time on the weekend you can use "incremental by date" backups on the weekdays and then "full" incremental backups on the weekends.
Syntax
.-------------------.
V |
>>-Incremental--+-----------+-----+--------------+-+-----------><
'- options--' +- filespec----+
'- "filespec"--'
Parameters
You can use these common options with the incremental command: changingretries, domain, memoryefficientbackup, subdir. Go to Chapter 6. "Setting Common Options" for information about common options.
Refer to Figure 28 for a list of common options you can use on all commands.
If a file system is supplied for the filespec, all new and changed files in the entire file system are considered for backup and the "last incremental date" for the filespace is updated on the server. If a file or directory is supplied for the filespec, the "last incremental date" for the filespace is not updated, so the file or directory may be backed up again if a subsequent backup is done using the incrbydate option.
Examples
The table below provides examples of some tasks you might perform using the
incremental command.
| Task | Command |
|---|---|
| Run an incremental backup for your default client domain as indicated in the client options file. | Incremental |
| Run an incremental backup for the /home, /usr, and /proj file systems. | Incremental /home /usr /proj |
| Run an incremental backup for the /proj/test directory. | Incremental /proj/test/ |
| Run an incremental by date backup for the /home file system. | Incremental -incrbydate /home |
| Run an incremental backup of all files in the /fs/dir1 directory that begin with the string abc. | Incremental -subdir=yes "/fs/dir1/abc*" |
| Run an incremental backup of the abc file in the /fs/dir1 directory. | Incremental -subdir=yes /fs/dir1/abc |
| Run an incremental backup of the directory object /fs/dir1, but not any of the files in the /fs/dir1 directory. | Incremental -subdir=yes /fs/dir1 |
| Run an incremental backup of the directory object /fs/dir1 and all of the files in the /fs/dir1 directory. | Incremental -subdir=yes /fs/dir1/ |
The loop command starts an interactive command line session that is maintained until you enter quit. If you use an interactive command line session, it is not necessary to precede each command name with dsmc and your password, if one is required. Once you start an interactive session, most options you entered with other commands remain in effect throughout the session unless you enter them again using a different setting. The following options, however, must be entered on each command for which you want them to take effect:description, detail, dirsonly, filesonly, fromdate, fromnode, fromtime, ifnewer, inactive, latest, noprompt, pick, pitdate, pittime, preservepath, todate, totime, and volinformation.
You can enter all commands in interactive mode except the schedule and loop commands.
Syntax
>>-LOOP--+-----------+-----------------------------------------><
'- options--'
Parameters
Refer to Figure 28 for a list of common options you can use on all commands.
Examples
To start an ADSM interactive command line session, enter dsmc.
The macro command sends a series of ADSM commands that you specify in a macro file. By including the macro command within a macro file, you can nest as many as ten levels of commands.
Syntax
>>-MAcromacroname----------------------------------------------><
Parameters
Examples
The table below provides an example of how to use the macro
command.
| Task | Command |
|---|---|
| Selectively back up files in the following directories: /devel/project/proja, /devel/project/projb, and /devel/project/projc |
MACRO backabc.mac Where backabc.mac contains the following statements: Selective /devel/project/proja/ Selective /devel/project/projb/ Selective /devel/project/projc/ |
The query access command displays a list of users to whom you have given access to backup versions or archive copies of specific files. ADSM displays a list of authorization rules that you defined with the set access command, or with Set Authorization on the graphical user interface (GUI) Utilities menu. The information includes:
Syntax
>>-Query ACcess--+-----------+---------------------------------><
'- options--'
Parameters
Examples
To display a list of users who have access to your files, enter Query ACcess.
The query archive command displays a list of your archived files, the file size, archive date, file specification, expiration date, and file description.
Syntax
>>-Query ARchive--+-----------+--+- filespec----+--------------><
'- options--' '- "filespec"--'
Parameters
You can use the subdir common option with the query archive command. Go to Chapter 6. "Setting Common Options" for information about these common options.
Refer to Figure 28 for a list of common options you can use on all commands.
Examples
The table below provides examples of some tasks you might perform using the
query archive command.
| Task | Command |
|---|---|
| Display a list of all your archived files in the current directory. | Query ARchive "*" |
| Display a list of all your archived files in the /devel directory and all of its subdirectories. | Query ARchive "/devel/*" -SUBDIRectory=yes |
| Display a list of archived files in the current directory. Use the dateformat and timeformat options to reformat the dates and times. | Q AR -DATE=5 -TIME=1 "*" |
| Display the list of files that were archived from the /home/proj directory whose file names begin with the letters proj. Use the dateformat and timeformat options. | Q AR -DATE=1 -TIME=4 "/home/proj/proj*" |
The query backup command displays a list of backup versions of your files. For each backup version, ADSM displays the file size, backup date, and management class to which the file is assigned, whether the file is active or inactive, and the file specification. ADSM displays only the first ten characters of the management class name.
Syntax
>>-Query Backup--+-----------+--+- filespec----+---------------><
'- options--' '- "filespec"--'
Parameters
You can use the subdir common option with the query backup command. Go to Chapter 6. "Setting Common Options" for information about these common options.
Refer to Figure 28 for a list of common options you can use on all commands.
Examples
The table below provides examples of some tasks you might perform using the
query backup command.
| Task | Command |
|---|---|
| Display a list of all active and inactive backup versions of your files in the current directory. | Query Backup -INActive "*" |
| Display a list of active and inactive backup versions of your files in the /home filesystem. Use the dateformat and timeformat options to reformat the dates and times. | Q B -DATE=5 -TIME=1 -INA -SU=YES /home/ |
| Display the list of files that were backed up from the /home/proj directory with the names that begin with proj. Use the dateformat and timeformat options. | Q B -DATE=1 -TIME=4 "/home/proj/proj*" |
The query filespace command displays a list of file spaces for a node stored on the ADSM server. A file space is a logical space on the server that contains files you backed up or archived. ADSM assigns a separate file space on the server for each file system at your workstation from which you back up or archive files. The file space name is the same as the file system name.
Syntax
>>-Query Filespace--+-----------+------------------------------><
'- options--'
Parameters
Go to Chapter 6. "Setting Common Options" for information about common options.
Refer to Figure 28 for a list of common options you can use on all commands.
Examples
The table below provides examples of some tasks you might perform using the
query filespace command.
| Task | Commands |
|---|---|
| Display your file spaces. | Query Filespace |
| Display your file spaces. Use the dateformat and timeformat options to reformat the dates and times. | Query Filespace -DATEformat=5 -TIMEformat=4 |
The query mgmtclass command displays information about the management classes available in your active policy set.
Your ADSM administrator defines management classes that contain attributes controlling whether a file is eligible for backup or archive services. They also contain attributes that determine how ADSM manages the backups and archives after they reach the server.
Your active policy set contains a default management class; it can contain any number of additional management classes. You can assign specific management classes to files using include options. If you do not assign a management class to a file, ADSM uses the default management class.
Syntax
>>-Query Mgmtclass--+-----------+------------------------------><
'- options--'
Parameters
Go to Chapter 6. "Setting Common Options" for information about common options.
Refer to Figure 28 for a list of common options you can use on all commands.
Examples
To display available management classes, enter Query Mgmtclass.
The query restore command displays a list of your restartable restore sessions in the server database. The list contains the following fields: owner, replace, subdir, preservepath, source, and destination.
Certain restore operations, called restartable restore sessions, invoke a special protocol within ADSM. Some restore sessions can be restarted for these reasons:
Syntax
>>-Query RESTore--+-----------+--------------------------------><
'- options--'
Parameters
Refer to Figure 28 for a list of common options you can use on all commands.
Examples
To display your restartable restore session in the server database, enter Query Restore.
The query session command displays the information about your ADSM session. This information includes the current node name, when the session was established, server information, and server connection information. A sample query session display follows:
ADSTAR Distributed Storage Manager Command Line Backup Client Interface - Version 3, Release 1, Level 0.1 (C) Copyright IBM Corporation, 1990, 1997, All Rights Reserved. Node Name: EPSILON3 Session established with server FIJI_0918GA: AIX-RS/6000 Server Version 3, Release 1, Level 0.0 Server date/time: 11/04/1997 16:09:52 Last access: 11/04/1997 16:08:39 ADSM Server Connection Information Server Name.............: FIJI_0918GA Server Type.............: AIX-RS/6000 Server Version..........: Ver. 3, Rel. 1, Lev. 0.0 Last Access Date........: 11/04/1997 16:08:39 Delete Backup Files.....: Yes Delete Archive Files....: Yes Node Name...............: EPSILON3 User Name...............: amperez
Syntax
>>-Query SEssion--+-----------+--------------------------------><
'- options--'
Parameters
Refer to Figure 28 for a list of common options you can use on all commands.
Examples
To display your session information, enter Query SEssion.
The query schedule command displays the events scheduled for your node. Your ADSM administrator can set up schedules to perform automatic backups and archives for you. To plan your work, use this command to determine when the next of those scheduled events will occur.
Syntax
>>-Query SChedule--+-----------+-------------------------------><
'- options--'
Parameters
Refer to Figure 28 for a list of common options you can use on all commands.
Examples
To display your scheduled events, enter Query SChedule.
The restart restore command displays a list of your restartable restore sessions in the ADSM server database. You can select zero or more restartable restore sessions that you want to restart.
The restarted restore uses the same options you used in the failed restore. The restarted restore continues from the point at which the restore previously failed.
To restart restartable restore sessions use the restart restore command. To cancel restartable restore sessions use the cancel restore command. Use the restart restore command when:
Options from the failed session supersede new or changed options for the restarted session.
Syntax
>>-RESTArt Restore--+-----------+------------------------------><
'- options--'
Parameters
Refer to Figure 28 for a list of common options you can use on all commands.
Examples
To restart a restore, you would enter:
restart restore
The restore command obtains copies of backup versions of your files from an ADSM server. To restore files, specify the directories or selected files, or select the files from a list. Restore files to the directory from where you backed them up, or to a different directory.
When an entire directory or directory tree is restored, and the inactive, latest, pick, todate, and fromdate options are not specified on the restore command, ADSM keeps track of which objects have been restored. If the restore process is interrupted for any reason, you can restart the restore at the point of interruption by issuing the restart restore command. It is possible to create more than one restartable restore sessions. Use the query restore command to display a list of your restartable restore sessions in the server database. The existance of a restartable restore inhibits further backups of that file system until the restartable restore is completed using the restart restore command or the restartable restore is dropped using the cancel restore command.
Syntax
>>-REStore--+-----------+--+- sourcefilespec----+--------------->
'- options--' '- "sourcefilespec"--'
>----+----------------------+----------------------------------><
'- destinationfilespec-'
Parameters
You can use these common options with the restore command: replace, restoremigstate, subdir. Go to Chapter 6. "Setting Common Options" for information about common options.
Refer to Figure 28 for a list of common options you can use on all commands.
Examples
The table below provides examples of some tasks that you can perform using
the restore command.
| Task | Command |
|---|---|
| Restore a single file named budget. | REStore /home/devel/projecta/budget |
| Restore all files from the /home/devel/projecta directory that end with the characters .c. |
REStore "/home/devel/projecta/*.c" |
| Restore all files from the /home/devel/projecta directory that end with the characters .c to the /home/newdevel/projectn directory. If the projectn directory does not exist, it will be created. | REStore "/home/devel/projecta/*.c" /home/newdevel/projectn/ |
| Restore all files in the /user/project directory. Use the pick option and the inactive option. | REStore "/user/project/*" -PIck -INActive |
| Restore all files in the /home/mydir directory to their state as of 1:00 PM on August 17, 1997. | res -pitd=8/17/1997 -pitt=13:00:00 /home/mydir/ |
| Restore all objects in the /home/myid/ directory.
Since this restore is fully wildcarded, if the restore process is interrupted, a restartable restore session is created. Use the restart restore command to restart the restartable restore session. Use the cancel restore command to cancel the restartable restore session. | res /home/myid/* |
The retrieve command obtains copies of archived files from the server. Specify either selected files or whole directories to retrieve archived files. Use options such as description that allow you to search on the descriptions assigned to the files when they were archived.
Place the retrieved files in the same directory from which they were archived, or in a different directory.
Syntax
>>-RETrieve--+-----------+--+- sourcefilespec----+-------------->
'- options--' '- "sourcefilespec"--'
>----+----------------------+----------------------------------><
'- destinationfilespec-'
Parameters
You can use these common options with the retrieve command: replace, subdir. Go to Chapter 6. "Setting Common Options" for information about common options.
Refer to Figure 28 for a list of common options you can use on all commands.
Examples
The table below provides examples of some tasks that you can perform using
the retrieve command.
| Task | Command |
|---|---|
| Retrieve a single file named budget. | RETrieve /home/devel/projecta/budget |
| Retrieve all files with an extension of .c from the /home/devel/projecta directory. | RETrieve "/home/devel/projecta/*.c" |
| Retrieve all files in the /home directory. | RETrieve "/home/" |
| Retrieve all files in the /home/devel/projecta directory that end with the characters .c to the /home/newdevel/projectn directory. | RETrieve "/home/devel/projecta/*.c" /home/newdevel/projectn/ |
| Retrieve all files with a file extension of .c from the /home/devel/projecta directory to the /home/newdevel/projectn directory. If the /projectn directory does not exist, it will be created. | RETrieve "/home/devel/projecta/*.c" /home/newdevel/projectn/ |
| Retrieve files in the /user/project directory. Use the pick option. | RETrieve "/user/project/*" -PIck |
| Retrieve all files archived from the /proj directory with the description "1997 survey results". | RETrieve "/proj/*" -desc="1997 survey results" |
ADSM AUTHORIZED USER
The schedule command starts the client scheduler on your workstation. The client scheduler must be running before scheduled work can start.
When you start the client scheduler, it continuously polls the server for scheduled events based on the time you specified on the queryschedperiod option in your client options file. If your ADSM administrator sets this option for all nodes, that setting overrides your setting.
If you are using TCP/IP communications, the server can prompt your workstation when it is time to run a scheduled event. To do so, set the schedmode option to prompted in the client options file or on the schedule command.
Once you start the client scheduler, it continues to run and to start scheduled events until you press Ctrl+C, stop the scheduler process with the UNIX kill command, restart the machine, or turn off the machine to end it.
| Note: | You cannot enter this command in interactive mode. |
Syntax
>>-SCHedule--+-----------+-------------------------------------><
'- options--'
Parameters
Refer to Figure 28 for a list of common options you can use on all commands.
Examples
The table below provides an example of a task that you can perform using
the schedule command.
| Task | Command |
|---|---|
| For AIX: Start the scheduler at system bootup time by entering this command in the /etc/inittab file. Insure the passwordaccess option is set to generate. | adsm::once:/usr/lpp/adsm/bin/dsmc sched > /dev/null 2>&1 #ADSM Scheduler |
| For UNIX: Start the scheduler at system bootup time by entering this command in the /etc/inittab file. Insure the passwordaccess option is set to generate. | adsm::once:/usr/adsm/dsmc sched > /dev/null 2>&1 #ADSM Scheduler |
| Interactively start the scheduler and keep it running in the background. | nohup dsmc sched 2> /dev/null & |
The selective command selectively backs up files of your choice. If any of these files become damaged or lost, you can replace them with backup versions from the server. When you run a selective backup, ADSM backs up all the files that fit the filespec unless they are excluded from backup in your include-exclude list, or unless they do not meet management class requirements for serialization.
During a selective backup, ADSM sends copies of the files to the server even if they have not changed since the last backup. This might result in having more than one copy of the same file on the server. If that occurs, you might not have as many different down-level versions of the file on the server as you intended. Your version limit might consist of identical files. To avoid that, use the incremental command to back up only changed and new files.
You can selectively back up single files or directories. You can also use wildcards to back up groups of related files.
Syntax
.------------------.
V |
>>-Selective--+-----------+----+- filespec----+-+--------------><
'- options--' '- "filespec"--'
Parameters
You can use these common options with the selective command: changingretries, subdir. Go to Chapter 6. "Setting Common Options" for information about these common options.
Refer to Figure 28 for a list of common options you can use on all commands.
Examples
The table below provides examples of some tasks that you can perform using
the selective command.
| Task | Command |
|---|---|
| Back up the proja file in the /home/devel directory. | Selective /home/devel/proja |
| Back up all files in the /home/devel directory whose file names begin with proj. | Selective "/home/devel/proj*" |
| Back up all files in the /home/devel directory whose file names begin with proj. Back up the single file budget in the /user/home directory. | Selective "/home/devel/proj*" /user/home/budget |
The set access command gives users at other nodes access to your backup versions or archived copies. You can give another user access to a specific file, multiple files, or all files in a directory. When you give access to another user, that user can restore or retrieve your files. Define in the command whether you are giving access to archives or backups.
| Note: | You cannot give access to both types of files using a single command. |
Syntax
>>-SET Access--+- Archive--+--+- filespec----+-- node----------->
'- Backup---' '- "filespec"--'
>---+--------+--+-----------+----------------------------------><
'- user--' '- options--'
Parameters
Identifies the path and file name or directory name that was backed up or archived on the server to which you are giving access to another node or user.
Use wildcards to specify a group of files, all the files in a directory, all objects in a directory branch, or all objects in a file system. You can code a single asterisk "*" for the filespec to give access to all files owned by you and backed up on the server. When the command, set access backup "*" node user, is entered, no check is made with the server, it is assumed you have at least one object backed up.
If you give access to a branch of the current working directory, you only need to specify the branch. If you give access to objects that are not in a branch of the current working directory, you must specify file system and directory. The filespec to which you give access must have at least one backup version or archive copy object (file or directory) on the ADSM server.
Give access to all objects below a certain level by using asterisk, directory delimiter, and asterisk at the end of your filespec. For example, to give access to all objects below /home/test, enter filespec /home/test/*/*.
To specify all files in all directories off of the root directory, enter /*/* on the command line. Enter /* on one set access command and /*/* on another if you want another user to have complete access to your filespace. The first /* gives access to all subdirectories and all files off of the root directory.
Refer to Figure 28 for a list of common options you can use on all commands.
Examples
The table below provides examples of some tasks that you can perform using
the set access command.
| Task | Command |
|---|---|
| Give user user_c at node_3 authority to restore the budget file from the /home/user directory. | SET Access Backup /home/user/budget node_3 user_c |
| Give user user_c at node_3 authority to retrieve all files from the /home/devel/proja directory whose file names end with.c . | SET Access Archive "/home/devel/proja/*.c" node_3 user_c |
| Give any user at node_3 the authority to retrieve all files from the/home/devel/proja directory. | SET Access Archive /home/devel/proja/ node_3 |
| Give user_c at node_3 the authority to restore all of the backup versions of your files. | SET Access Backup "*" node_3 user_c |
| Give all users at node_3 whose user names start with depta authority to restore all the backup versions of your files. | SET Access Backup "*" node_3 "depta*" |
| Give all users at nodes whose node names end with bldgb authority to restore all the backup versions of your files. | SET Access Backup "*" "*bldgb" |
| Give all users at all nodes access to all objects in the /acct/paid directory and any subdirectories below it. | SET Access Backup "/acct/paid/*/*" "*" |
ADSM AUTHORIZED USER
The set password command changes the ADSM password for your workstation. If you do not specify the old and new password parameters, you are prompted once for your old password and twice for your new password.
A password is not case-sensitive, and it can be as many as 64 characters. Valid characters are:
Syntax
>>-SET Password--+--------------+--+-----------+---------------><
'- oldpw newpw-' '- options--'
Parameters
Refer to Figure 28 for a list of common options you can use on all commands.
Examples
The table below provides an example of using the set password
command.
| Task | Command |
|---|---|
| ADSM prompts you to change your password. | SET Password |