Using blanks and comments

These rules apply to the use of blanks and comment statements:

In the attribute section, the attribute character and all keywords that follow must be separated by one or more blanks. At least one keyword must follow the attribute character on the same line. Keywords can be continued on succeeding lines.
In the action bar choice, initialization, reinitialization, processing, and help sections, several statements can occur on the same line, separated by one or more blanks. Statements cannot be split between lines, except that listed items within parentheses and long strings within quotes can be continued on succeeding lines (see Formatting items in lists).
One or more blanks can occur on either side of operators such as an equal sign (=), a not-equal operator (¬=), greater-than symbol (>), and not-greater-than operator (¬>). Embedded blanks cannot occur in double-character operators such as the not-equal operator.
For example: ¬ = is invalid.
One or more blanks can occur on either side of parentheses, except that a blank cannot follow the right parenthesis that begins a header statement. These statements are all equivalent:
```
INTENS(LOW)
INTENS (LOW)
INTENS ( LOW )
```
One or more blanks must follow the closing parenthesis to separate it from the next statement or keyword.
Comments can be coded in the action bar choice, attribute, initialization, reinitialization, processing, ccsid, panel, point-and-shoot, list, and help sections. Comments must be enclosed with the comment delimiters, /* and */. The comment must be the last item on the line. Additional keywords or statements that follow the comment on the same line are ignored. A comment cannot be continued on the next line. For multi-line comments, the comment delimiters must be used on each line.
Blank lines can occur anywhere within the action bar choice, attribute, initialization, reinitialization, processing, and help sections.