enoft Manual

Introduction to eNOFT and ar
eNOFT Manual—527507-005
1-3
Common Formats of Command Arguments
infile is a text file containing one or more eNOFT commands. Commands listed in
this file must follow the same rules for the command-line processing. If infile does not
exist, a syntax error will be generated and the program terminates normally.
If both an infile and commands are given, eNOFT ignores the infile.
outfile specifies a file name to which eNOFT writes its output. If the specified file
does not exist, eNOFT creates a text file with that name. If the specified file exists,
eNOFT appends to the file. eNOFT writes its output to the display terminal if no output
file is specified.
Common Formats of Command Arguments
The following lists common rules associated with eNOFT commands. Exceptions, if
any, are listed with individual commands.
Argument Groupings
[ ] denote grouping of optional arguments. The first argument in the options list is the
default.
{ } also denote groupings of arguments except at least one argument is mandatory.
Input Format
All commands are limited to 256 characters.
For commands that have the asterisk symbol "*" as an option, NOFT displays syntax
errors when these commands are typed without an option.
New to eNOFT, all available or applicable items will be shown when these commands
are entered with or without an asterisk.
The (default) NOFT options "BRIEF" and "B" are not supported.
Output Display Format
Most outputs of eNOFT will be left justified instead of center-justified in NOFT.
All displays are limited to 79 characters per line. If an output file is specified,
information in excess of this limit will wrap around the following line to maximum
number of characters per line allowed by that output file type; for example, 239
characters for the EDIT file type in Guardian. In such a case, information may be
truncated.
Unless otherwise specified, dumps are presented in multiples of 32-bit values; for
example, 10 decimal digits for decimal and 8 hexadecimal digits for the hexadecimal
format.
All virtual addresses are represented as 32-bit hexadecimal numbers (that is, 8
hexadecimal digits) whereby the top halves of the 64-bit addresses are ignored . If the