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 any files that you want to keep in their present condition. To release storage space on your workstation, delete the files as you archive them. Retrieve the archived files to your workstation whenever you need them again.
Syntax
.---------------.
V |
>>-Archive--+---------+----+-filespec--+-+---------------------><
'-options-' +-BINdery---+
'-DIRectory-'
Parameters
Go to Chapter 6. "Setting Common Options" for information about the common options you can use with the archive command.
Examples
The table below provides examples of some tasks you might perform using the
archive command.
| Task | Command |
|---|---|
| Archive a single file named budget. |
load dsmc Archive T9\SYS:/user/proj1/budget |
| Archive all files in the T9\SYS:/user/proj1 directory that end with the characters .txt. |
load dsmc Archive T9\SYS:/usr/proj1/*.txt |
| Archive a single file named budget and files with names that end with the characters .txt from the server T9 and the volume SYS:. |
load dsmc A T9\SYS:/user/prj/budget T9\SYS:/user/prj/*.txt |
| Archive all files in the T9\SYS:/home directory. |
load dsmc Archive T9\SYS:/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.
You may want to cancel restartable restore sessions with the cancel restore command or restart restartable restore sessions with the restart restore command for the following reasons:
Syntax
>>-CANcel Restore-+---------+----------------------------------><
'-options-'
Parameters
Examples
To cancel a restore, you would enter:
load dsmc 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
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 User Path | |_____ ____ ____________________________________ | |1 Backup NODE1 * M0\SYS:/u/dev/proja/list | |2 Archive NODE3 * M0\SYS:/u/fin/budg/depta | |3 Backup NODE4 * M0\SYS:/u/plan/exp/deptc | |4 Archive NODE5 * M0\SYS:/u/mfg/inv/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) (your selections can be separated by commas or spaces) and press Enter. Quit without making a selection by entering quit.
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
.---------------.
V |
>>-Delete ARchive--+---------+----+-filespec--+-+--------------><
'-options-' +-BINdery---+
'-DIRectory-'
Parameters
Go to Chapter 6. "Setting Common Options" for information about the common options you can use with the delete archive command.
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. | load dsmc Delete ARchive SYS:/user/home/proj1/budget |
| Delete all archived files in the SYS:/user/home/proj1 directory that end with the characters .txt. |
load dsmc Delete ARchive
SYS:/user/home/proj1/*.txt
|
| Delete archived files in the SYS:/user/project directory using the pick option. | load dsmc Delete ARchive SYS:/user/project/* -pick |
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 drive at your workstation from which you back up or archive files. The file space name is the same as the drive label 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
Examples
The table below provides an example of some tasks you might perform using
the delete filespace command.
| Task | Command |
|---|---|
| Delete a file space. | load dsmc Delete Filespace |
| Delete a file space. Use the dateformat and timeformat options to reformat the dates and times. These formats remain in effect for the rest of the interactive session unless you enter them again on a later command. | load dsmc 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 new or changed files in your default client domain, or on the NetWare volumes you specify that are not excluded from backup services, and that meet management class requirements for frequency, mode, and serialization. The following attributes in the management class assigned to a file affect whether the file is actually backed up.
You can incrementally back up an entire filespace (domain) or just a single file. If you specify only the filespace name, the entire directory tree is traversed. If you specify a directory, only that directory is backed up, unless you use subdir=y.
There are two types of incremental backups: full and partial. You must perform a full incremental backup before you can perform a partial.
For more information about partial incremental backups, see "Understanding Partial Incrementals".
Normally, use incremental backup to back up all files created or changed since the last time you ran a backup. However, you can exclude specific files or groups of files from backup services by using the exclude option in your client option file's include-exclude list.
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.
If you are running NetWare Btrieve on your NetWare server (or any other server-based database), stop the database application before backing up the files associated with the database. Many database applications place locks on files that can prevent ADSM from backing them up. Because ADSM is a Storage Management Services (SMS) backup application, it supports database Target Service Agents (TSA's) as soon as they are available. This allows ADSM to maintain database integrity without manual interaction.
If you are running your communication with SNA LU6.2 (NetWare for SAA), you cannot stop the Btrieve database application because NetWare for SAA requires Btrieve to be running. Therefore, you cannot back up the file named btrieve.trn in the system subdirectory. As a result, you might be unable to maintain true data integrity here.
If ADSM refuses to back up a file, check to see if it is marked for execute only or it is opened and locked by another user.
If your system fails during an incremental backup, ADSM checks all files again when you start the next incremental backup. Only files that have changed are backed up.
Syntax
.--------------------.
V |
>>-Incremental--+---------+-----+---------------+-+------------><
'-options-' +-filespec------+
'-filespacename-'
Parameters
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. | load dsmc Incremental |
| Run an incremental backup for the SYS: volume, the DATA: volume and the bindery on server B9. | load dsmc Incremental B9\SYS: B9\DATA: B9\BINDERY |
| Run an incremental backup by date using the incrbydate option. | load dsmc Incremental -incrbydate |
| Incrementally back up the NDS. | load dsmc I- SYS:/system |
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:
You can enter all commands in interactive mode except the schedule and loop commands.
Syntax
.-LOOP-.
>>-+------+--+---------+---------------------------------------><
'-options-'
Parameters
Go to Chapter 6. "Setting Common Options" for information about the common options you can use with the loop command.
Examples
To start an ADSM interactive command-line session, enter load dsmc LOOP
At the dsmc> prompt, enter an ADSM command.
There are three methods for ending an interactive session. Select one of the following:
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
>>-MAcro macroname---------------------------------------------><
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:SYS:/project/proja, SYS:/project/projb, and SYS:/project/projc |
MACRO SYS:/adsm/backabc.macwhere backabc.mac contains the following statements: Selective SYS:/devel/project/proja/*.* Selective SYS:/devel/project/projb/*.* Selective SYS:/devel/project/projc/*.* |
The query access command displays a list of nodes 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 nodes that have access to your files, enter load dsmc 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
.---------------.
V |
>>-Query ARchive--+---------+----+-filespec--+-+---------------><
'-options-' +-BINdery---+
'-DIRectory-'
Parameters
You can use the following command-line options:
Go to Chapter 7. "Using Options With Commands" for information about command-line options.
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 serverA's SYS: volume. | load dsmc Query ARchive -SUBdir=Yes serverA\SYS:* |
| Display a list of all your archived files on serverA\SYS:. Use the dateformat and timeformat options to reformat the dates and times. | load dsmc Q AR -SUBdir=Yes -DATE=5 -TIME=4 serverA\SYS:* |
| Display a list of archived files in the serverA\SYS:/u/proj directory whose first four characters of the file name begin with proj. Use the dateformat and timeformat options. | load dsmc Q AR -DATE=1 -TIME=4 serverA\SYS:\u/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
.---------------.
V |
>>-Query Backup--+---------+----+-filespec--+-+----------------><
'-options-' +-BINdery---+
'-DIRectory-'
Parameters
You can use the following command-line options:
Go to Chapter 7. "Using Options With Commands" for information about command-line options.
Examples
The table below provides examples of some tasks you might perform using the
query backup command.
| Task | Command |
|---|---|
| Display a list of all your backed up files on the SYS: volume. |
load dsmc Query Backup \SUbdir=Yes servA\SYS:* |
| Display a list of all your backed up files. Use the dateformat and timeformat options to reformat the dates and times. | load dsmc Q B -DATE=1 -TIME=4 -SUbdir=Yes servA\SYS:* |
| Display a list of files that were backed up from the servA\SYS:/proj directory that have file names that begin with the four characters proj. Use the dateformat and timeformat options. | load dsmc Q B -DATE=1 -TIME=4 servA\SYS:/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 node from which you back up or archive files.
Syntax
>>-Query Filespace--+---------+--------------------------------><
'-options-'
Parameters
You can use the following command-line option:
Go to Chapter 7. "Using Options With Commands" for information about command-line options.
Examples
The table below provides examples of some tasks you might perform using the
query filespace command.
| Task | Commands |
|---|---|
| Display your file spaces. | load dsmc Query Filespace |
| Display your file spaces. Use the dateformat and timeformat options to reformat the dates and times. | Query Filespace -DATEformat=1 -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 that are located in the client options file. If you do not assign a management class to a file, ADSM uses the default management class.
When you archive files, you can override the assigned management class by using the archmc option.
Syntax
>>-Query Mgmtclass--+---------+--------------------------------><
'-options-'
Parameters
You can use the following command-line options:
Go to Chapter 7. "Using Options With Commands" for information about command-line options.
Examples
To display default and available management classes, enter load dsmc Query Mgmtclass -DETail.
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-----------------------------------------------><
Parameters
There are no parameters for this command.
Examples
The following is an example of the output when you use query restore:
owner Rep Sub Pre Source
----- --- --- --- -------
1. nshaw P N L /home/nshaw/testdir/*
2. nshaw P N L /home/nshaw/*
dest = /tmp/
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
Go to Chapter 6. "Setting Common Options" for information about common options.
Examples
To display your scheduled events, enter
load dsmc Query SChedule
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.
Syntax
>>-Query SEssion--+-----------+--------------------------------><
'- options--'
Parameters
Examples
To display your session information, enter
load dsmc Query SEssion
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
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.
You may want to restart restartable restore sessions by using the restart restore command or cancel restartable restore sessions by using the cancel restore command for the following reasons:
Options from the failed session supersede new or changed options for the restarted session.
Syntax
>>-RESTArt restore-+---------+---------------------------------><
'-options-'
Parameters
Go to Chapter 6. "Setting Common Options" for information about common options.
Examples
To restart a restore, you would enter:
load dsmc 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.
Syntax
.--------------------.
V |
>>-REStore---+---------+----+-sourcefilespec-+-+---------------->
'-options-' +-BINdery--------+
'-DIRectory------'
>----+---------------------+-----------------------------------><
'-destinationfilespec-'
Parameters
Go to Chapter 6. "Setting Common Options" for information about common options.
You can use the following command-line options:
Go to Chapter 7. "Using Options With Commands" for information about command-line options.
The following selections are also available for this command:
Always restore the bindery first to ensure the trustee data (permissions) are restored correctly.
It is also a good idea to ensure that the bindery restore reconciled with the current NetWare system configuration, especially if the bindery is restored using a version that is back level.
To restore each volume on the server, enter load dsmc REStore SYS:* -su=yes -rep=yes
| Note: | Any changes made after the backup version was made are lost. |
To restore one container, specify dir/.o=container_name
It is also a good idea to ensure that the directory restore reconciled with the current NetWare system configuration, especially if the directory is restored using a version that is back level.
| Note: | Objects added after the backup version was made are not deleted. |
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 | load dsmc REStore SYS:/u/projecta/budget |
| Restore files from the SYS:/projecta directory that end with the characters.BAK. | load dsmc res SYS:/u/projecta/*.BAK |
| Restore all files from the SYS:/projecta directory that
end with the characters .BAK to the
SYS:/projectndirectory.
Attention: If the destination is a directory, you must specify the delimiter (/) as the last character of the destination. If you omit the delimiter and your specified source is a directory or a filespec with a wildcard, you will receive an error. | load dsmc res SYS:/projecta/*.BAK SYS:/projectn/ |
| Restore all files from the SYS:/projecta directory that end with the characters.BAK to another directory on a different NetWare server, serverb\SYS:/projectn. Projectn need not exist on serverb. | load dsmc REStore SYS:/projecta/*.BAK serverb\SYS:/projectn/ |
| Restore the NDS | load dsmc REStore T9\directory |
| Restore the .o=ibm organization in the NDS | load dsmc res adsm40\directory/.o=ibm |
| Restore files in the SYS:/user/project directory. Use the pick option and the inactive option. | load dsmc res servB\SYS:/user/project/* -PIck -INActive |
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.
| Note: | If you are retrieving files to a different directory than the original directory, file names become the names you specify with the destinationfilespec option. Because only DOS names are valid within the ADSM client, the file name becomes a DOS name. |
Syntax
.--------------------.
V |
>>-RETrieve--+---------+----+-sourcefilespec-+-+---------------->
'-options-' +-BINdery--------+
'-DIRectory------'
>----+---------------------+-----------------------------------><
'-destinationfilespec-'
Parameters
Go to Chapter 6. "Setting Common Options" for information about common options.
You can use the following command-line options:
Go to Chapter 7. "Using Options With Commands" for information about command-line options.
The following selections are also available for this command:
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. | load dsmc RETrieve SYS:/projecta/budget | ||
| Retrieve all files from the SYS:/projecta directory that end with the characters .BAK. | load dsmc RETrieve SYS:/projecta/*.BAK | ||
Retrieve all files from the \SYS:/projecta directory
that end with the characters .BAK to the
SYS:/projectn directory.
| load dsmc ret/projecta\*.BAK servB\SYS:/projectn/ | ||
Retrieve all files in the SYS:/home directory.
| RETrieve SYS:/home/* | ||
| Retrieve files in the SYS:/project directory. Use the pick option. | RETrieve SYS:/project/* -PIck |
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 +Break, restart the machine, or turn off the machine to end it.
| Note: | You cannot enter this command in interactive mode. |
Syntax
>>-SCHedule--+---------+---------------------------------------><
'-options-'
Parameters
Examples
The table below provides an example of a task that you can perform using
the schedule command.
| Task | Command |
|---|---|
| Start the client scheduler. | load dsmc SCHedule -password=notell |
When you run the schedule command, all messages regarding scheduled work are sent to a file called dsmsched.log or to an alternate file specified in the schedlogname option in your client options file. If you do not specify a directory path with the file name in the schedlogname option, ADSM stores the file in the default installation directory.
The selective command backs up files that you specify selectively, for example, when you don't want to wait for the next incremental backup.
You can selectively back up single files and directories from the NetWare server. You can also selectively back up the NDS and the bindery. Use wildcard characters to back up groups of related files.
When you run a selective backup, ADSM backs up all the files 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.
If ADSM refuses to back up a file, check to see if it is marked for execute only or if it is opened and locked by another user.
Syntax
.---------------.
V |
>>-Selective--+---------+----+-filespec--+-+-------------------><
'-options-' +-BINdery---+
'-DIRectory-'
Parameters
You can use the following command-line options:
Go to Chapter 7. "Using Options With Commands" for information about command-line options.
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 SYS:/u/devel directory. | load dsmc Selective SYS:/u/devel\proja |
| Back up all files in the SYS:/u/devel directory whose file names begin with proj. | load dsmc Selective SYS:/u/devel/proj* |
| Back up all files in the SYS:/u/devel directory whose file names begin with proj. Back up the single file budget in the SYS:/user directory. | load dsmc Selective SYS:/u/devel/proj* SYS:/user/budget |
| Back up the NDS. | load dsmc S T9\directoryl |
| Back up the bindery on serverc. | load dsmc S serverC\BINDERY |
| Back up the tfr organization container of the NDS. | load dsmc S T9\dir/.o=tfr |
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. Access is enabled only between like platforms. You can grant access only to another NetWare client node. |
Syntax
>>-SET Access--+-archive-+--filespec--node--+---------+--------->
'-backup--' '-options-'
.-*----.
>---+------+---------------------------------------------------><
'-user-'
Parameters
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 volume. 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 you enter the command SET Access backup * node user, 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 volume 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 an asterisk, the directory delimiter, and another asterisk at the end of your filespec. For example, to give access to all objects below SYS:/ANN/, use filespec SYS:/ann/*/*.
To specify all files in all directories off the root directory, enter SYS:/*/* on the command line. Enter SYS:/* on one set access command and SYS:/*/* on another if you want another user to have complete access to your filespace. The first SYS:/* gives access to all subdirectories and all files off the root directory.
Examples
The table below provides examples of some tasks that you can perform using
the set access command.
| Task | Command |
|---|---|
| Give the user at node_2 authority to restore the budget file from the directory of SYS:/user directory. | load dsmc SET Access Backup SYS:/budget node_2 |
| Give node_3 authority to retrieve all files in the SYS:/devel/proja whose file names end with .SYS. | load dsmc SET Access Archive SYS:/devel/proja/*.SYS node_3 |
| Give node3 the authority to retrieve all file from the directory SYS:/u/devel/proja. | load dsmc SET A Archive SYS:/u/devel/proja node3 |
| Give node3 authority to restore all your backed up files. | load dsmc SET Access B * node3 |
| Give all nodes whose names end with bldgb the authority to restore all your backed up files. | load dsmc SET A B *bldgb |
The set password command changes the ADSM password for your workstation. You are prompted 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
Examples
The table below provides an example of using the set password
command.
| Task | Command |
|---|---|
| Change your current password from osecret to nsecret. | load dsmc SET Password osecret nsecret |