Checking Command-Line Errors; Using Command History; Accessing History Commands - HP A-F1000-E Getting Started Manual

NOTE:
With this feature enabled:
If you have no input at the command line prompt and the system outputs system information such as
•
logs, the system will not display the command line prompt after the output.
If the system outputs system information when you are typing interactive information (not YES/NO for
•
confirmation), the system will not redisplay the prompt information but a line break after the output and
then display what you have typed.

Checking command-line errors

If a command contains syntax errors, the CLI reports error information.
command line errors.
Table 15 Common command line errors
Error information
% Unrecognized command found at '^' position.
% Incomplete command found at '^' position.
% Ambiguous command found at '^' position.
Too many parameters
% Wrong parameter found at '^' position.

Using command history

The CLI automatically saves the commands recently used in the history command buffer. You can access
and execute them again.

Accessing history commands

Follow a step below to access history commands:
To do...
Display history commands
Display the previous history
command
Display the next history
command
NOTE:
You can use arrow keys to access history commands in Windows 200X and XP Terminal or Telnet.
However, the up and down arrow keys are invalid in Windows 9X HyperTerminal, because they are
defined differently. You can use Ctrl+P or Ctrl+N instead.
Cause
The command was not found.
Incomplete command
Ambiguous command
Too many parameters
Wrong parameters
Use the key/command...
display history-command
Up arrow key or Ctrl+P
Down arrow key or Ctrl+N
125
Table 15 lists some common
Result
Displays valid history commands you
used
Displays the previous history command, if
any
Displays the next history command, if any