Introduction › Syntax Conventions › Command Syntax Rules
Command Syntax Rules
History reporting commands must follow certain syntax rules.
When the Report Writer encounters a syntax error, it does the following:
- Displays a dollar sign ($) underneath the unexpected word or character
- Includes a message about a possible cause
When the Report Writer encounters a syntax error, it does the following:
- Continues to read commands to look for more syntax errors
- Does not generate a report
Keep in mind the following points when writing history reporting commands:
- Commands and their operands can be entered in either uppercase or lowercase letters.
- Each command must go on a new line. Do not enter more than one command on a line.
- Commands must be the first (leftmost) word on a line. You can start a command in any column, but it must always be the first word on the line.
- If you run out of space on one line for a command and its operands, you can continue it on the next line. To continue on the next line, type a comma after the last (rightmost) word on the line. You cannot split words with a continuation comma or a hyphen. When you continue a command, you can start the continued part of the command in any column, as long as it is the first (leftmost) word on the line.
- Separate operands and commands by blanks, commas, or parentheses lets them be considered separate words. Use one or more blanks to separate all words not separated by commas or parentheses. If you must use commas or parentheses, you do not have to separate words with blanks. Multiple blank spaces are treated as single blank spaces. You can type as many blanks as you want between words.
- Blank lines are ignored. You can include blank lines anywhere, in any number, even between a command and its continuation.
- Control statements are processed in the order in which they are read. Reports are printed in the order you request them.
- Any line whose first (leftmost) nonblank character is an asterisk (*) is a comment. The asterisk can be in any column. Anything after the asterisk is ignored.
- You can embed comments anywhere except between a command and its continuation lines. You cannot continue a comment with a continuation comma; to continue a comment, repeat the asterisk for each line of the comment.