HP 3000 Manuals HP 3000 Manuals
The HP System Dictionary Command Language
The HP System Dictionary Command Language is a free formatted language
that allows you to create, maintain, and report on entries in HP System
Dictionary. The general format of the language is:
COMMAND SUBCOMMAND OBJECT-CLAUSE;
KEYWORD-CLAUSE1; KEYWORD-CLAUSE2; ... KEYWORD-CLAUSEn.
Free formatting means that the command, subcommand, object-clause, and
keyword-clause may appear on the same line or on different lines.
However, the order of these language elements is important. They are,
therefore, positional. In other words, a subcommand must follow a
command, an object-clause must follow a subcommand, and a keyword-clause
must follow an object-clause. However, among themselves, keyword clauses
are non-positional. That is, you may enter them in any order, as long
as they follow the object-clause. For example, you may enter
keyword-clause1 after keyword-clause2. You cannot, however, enter them
before the object-clause.
Table 3-1 shows the System Dictionary command language elements.
Table 3-1. System Dictionary Language Elements
--------------------------------------------------------------------------------------------
| | |
| Language Element | Description |
| | |
--------------------------------------------------------------------------------------------
| | |
| COMMAND | The SDMAIN-defined name that specifies the action to be |
| | taken. |
| | |
| | EXAMPLE: CREATE ENTITY ship-date;ENTITY-TYPE=element. |
| | |
--------------------------------------------------------------------------------------------
| | |
| SUBCOMMAND | The SDMAIN-defined name that specifies the general target of |
| | the action. |
| | |
| | EXAMPLE: CREATE ENTITY ship-date;ENTITY-TYPE=element. |
| | |
--------------------------------------------------------------------------------------------
| | |
| OBJECT-CLAUSE | The user-defined name of the object. This is the specific |
| | target of the action specified by the command. |
| | |
| | EXAMPLE: CREATE ENTITY ship-date;ENTITY-TYPE=element. |
| | |
--------------------------------------------------------------------------------------------
| | |
| KEYWORD-CLAUSE | A keyword clause can be either a single keyword or a keyword |
| | followed by an equal sign (=) that is followed by either |
| | nothing, a single value, or a list of values separated by |
| | commas. The keywords are SDMAIN-defined, while their values |
| | are either SDMAIN-defined or user-defined.* Keyword clauses |
| | are separated by semicolons. |
| | |
| | EXAMPLE: CREATE ENTITY ship-date;ENTITY-TYPE=element. |
| | |
--------------------------------------------------------------------------------------------
* There are two exceptions to this punctuation rule:
ATTRIBUTE-LIST and SUB-REPORT
Both of these keywords must be followed by an equal sign and the keyword
value list must be enclosed in parentheses to avoid conflicts. An
example of this is:
REPORT ENTITY item-name;ENTITY-TYPE=element;
ATTRIBUTE-LIST=(max-record-size=256,min-record-size=128).
Table 3-2 lists the System Dictionary Command Language punctuation
characters.
Table 3-2. Command Language Punctuation Characters
--------------------------------------------------------------------------------------------
| | |
| CHARACTER | DESCRIPTION |
| | |
--------------------------------------------------------------------------------------------
| | |
| . | Terminates commands. The period signifies the end of a |
| | string of characters denoting a command. It is required for |
| | all commands except the COMMENT, EXIT, HELP, REDO, |
| | RESTRUCTURE, SHOW, SHOWMACRO and START commands, where it is |
| | optional. |
| | |
--------------------------------------------------------------------------------------------
| | |
| , | Separates items in a list. The comma separates objects in |
| | an object list and values in a keyword value list. |
| | |
--------------------------------------------------------------------------------------------
| | |
| ; | Separates clauses. The semicolon separates object clauses |
| | from keyword clauses and keyword clauses from each other. |
| | |
--------------------------------------------------------------------------------------------
| | |
| = | Specifies a keyword and a keyword value list, or an |
| | attribute and an attribute list, i.e., ENTITY-TYPE=element; |
| | ATTRIBUTE-LIST=(element-type=9,byte-length=8). |
| | |
--------------------------------------------------------------------------------------------
| | |
| ( | Used with the ATTRIBUTE-LIST or SUB-REPORT keyword clauses |
| | to specify the beginning and end of a keyword value list and |
| ) | within any value clause allowing selection criteria to |
| | denote precedence among Boolean operators. |
| | |
--------------------------------------------------------------------------------------------
| | |
| " | Delimits character string values. Use two double quotes |
| | ("") to represent a single double quote (") within a string. |
| | Required around variable length attribute values, the |
| | description attribute of stored reports, and the TITLE and |
| | PAGE-HEADER parameters of the FORMAT command. Optional |
| | around passwords, character attribute values, and alias |
| | attribute values, as long as the value is a valid dictionary |
| | name. If the string contains any invalid characters (See |
| | "User Defined Names" later in this Chapter) or has more than |
| | 32 characters, the value must be enclosed in quotes. |
| | |
--------------------------------------------------------------------------------------------
| | |
| ÅPP | Specifies a blank. You must use blanks to separate a |
| | command and subcommand, a command and object clause, and a |
| | subcommand and object clause. Any number of blanks may |
| | appear between any name and any punctuation character. |
| | |
--------------------------------------------------------------------------------------------
| | |
| [[Return]] | Specifies a carriage return. Treated the same as a blank. |
| | Wherever a blank is legal, a [[Return]] is legal. A |
| | [[Return]] is not legal inside a scope password. |
| | |
--------------------------------------------------------------------------------------------