OSF DCE Administration Guide--Core Components

OSF DCE Administration Guide—Core Components
Commands issued from scripts aren’t saved and can’t be recalled.
The history command takes various arguments depending on what you want to do.
Entering history with no arguments lists all the commands (called events) entered during
the current invocation of dcecp, as shown:
dcecp> history
1 principal create wardr -fullname {Ward Rosenberry} \
-quota unlimited
2 group add users -member wardr
3 organization add consultants -member wardr
4 account create wardr -mypwd mxyptlk -password qwerty \
-group users -organization consultants
dcecp>
Each history event is independent of previous events. This means that, if a recalled
command used a variable, its current value may not be the same as when it was first
entered. The history command itself generates a history event, too.
By default, the history list keeps the 20 most recent commands. You can use the history
keep command to lengthen or shorten the history list. For example, the following
command lengthens the history list to keep the 50 most recent events:
dcecp> history keep 50
dcecp>
You can specify events in various ways. Positive numbers specify events relative to the
earliest event in the list. Negative numbers specify events relative to the most recent
command. You can also specify an event by typing characters that match all or part of a
previous event.
The history facility lets you reuse previous events in many ways. The following
discussion covers just a few of the history commands you can use.
• You can execute a previous command without revision by using the history redo
command:
dcecp> history
1 directory show /.:/printers
2 object create /.:/printers/ascii_printer1
3 object create /.:/printers/ascii_printer2
4 object create /.:/printers/ascii_printer3
dcecp> history redo directory
directory show /.:/printers
.
. [output omitted]
.
dcecp>
1− 12 Tandem Computers Incorporated 124243