Command Line Interface

The command line interface allows you to create and maintain Edit Definitions, as well as browse and edit data, without opening the graphical user interface for Edit. The command line interface can be run from the command line, or automatically — in a batch file, or from another program.

Command Line Tasks

Use the command line interface to:

  • Browse and edit database tables.
  • Apply overrides to Edit Definitions and Access Definitions.

The following sections explain and describe how to perform each type of task.

Guidelines

The typical command begins with PR0CMND followed by command line keywords and associated arguments. The following guidelines apply:
  • The first operation argument must be prefixed with a forward slash (/) or dash (‑). To start the Table Editor, for example, use /E or -E.
  • A command line keyword may be prefixed by a forward slash (/) or dash (‑), but it is not required. Example: PST, /PST, and -PST are equal and valid keywords.
  • Generally, command line keywords can be specified in any order, separated by one or more spaces without commas. When overrides are specified for a process defined in a parameter file, the OV keyword must follow other command line keywords and precede the override parameters. The first override keyword and associated argument must begin on the following line, and each additional override must be on a separate line. The END keyword must follow the last override, and must also be on a separate line.
  • A command line keyword and associated argument are separated by an equals sign (=) or a colon (:), with no intervening spaces.
  • An override keyword and associated argument are separated by a blank space.
  • Keywords are recognized without regard to case. (Most keywords are shown in this chapter using bold and uppercase for emphasis.)
  • An argument associated with a keyword that includes spaces must be enclosed in single or double quotes.
  • Use double quotes to enclose a command line keyword argument that includes a macro.
  • You can include all keywords and arguments in a parameter file and reference the parameter file on the command line.
  • In a parameter file, command line keywords corresponding to an Edit Definition can be entered on one or multiple lines. You can include several Edit Definitions in the file; each must begin with the REQUEST parameter.
  • Use override keywords and arguments to override specifications in an Edit Definition.
  • A keyword that is inappropriate for the type of processing requested may cause a fatal conflicting-parameter error.
  • The following relational operator symbols and mnemonics are acceptable for use in selection criteria overrides:
    =, <, >, <=, >=, !=, !<, !>, <>, ^=, ^<, ^>, EQ, NE, LT, GT, LE, GE, BETWEEN, LIKE, IN, IS, NOT, NULL.
  • Comments in a parameter or override file must begin on a separate line and start with two forward slashes (//). Blank lines may also be included in the parameter stream.

Syntax Conventions

The syntax conventions used to describe these statements are:

KEYWORD
Keywords are shown in uppercase for emphasis, but can be specified in lower or mixed case.
text
Variable text is shown in lowercase italics.
( )
Statement delimiter to group a series of qualifiers for a parameter.
[ ]
Indicates an optional parameter.
{ }
Indicates a choice of two or more settings from which one (and only one) must be selected.
|
Separates options.