Restrictions on member expansion and member parts lists

These restrictions apply only to the member expansion and member parts listing functions:

These restrictions apply to all languages:
- Expansion triggers must follow their respective language coding conventions unless otherwise noted.
- Multiple names and preprocessor variables on trigger statements are not permitted.
- User triggers and their start column are specified at installation time and must be:
  - No more than 20 characters long
  - Uppercase with no imbedded blanks.
  No part of the user trigger can be in a comment or continuation field.
- Macros cannot be in packed form.
- The trigger statement must be the only statement in the logical record. No continuation is allowed into or from a trigger statement. Also, the trigger keyword must be the first character on the trigger statement that is not a blank and can be followed by only one statement delimiter.
- For compilers that allow names longer than 8 characters, the name is truncated at 8.
- For compilers that allow uppercase and lowercase names, all referenced names are converted to uppercase.
This restriction applies to assembler only:
- The user trigger cannot start in column 1.
This restriction applies to FORTRAN only:
- The member expansion function allows only the fixed form of coding.
This restriction applies to PL/I, Pascal, and COBOL:
- Free form coding is allowed except in trigger statements.
Other COBOL restrictions are:
- The name is truncated at 8 characters or the first hyphen (-), whichever comes first.
- The first statement in the COBOL program must be either an expansion trigger, a valid COBOL division header, a TITLE, a PROCESS, or a CBL statement. The expansion trigger can precede all other statements, but it must start in FIELD B.
  If an expansion trigger is the first statement, it must eventually resolve (through multiple expansion triggers if needed) to a valid COBOL division header, TITLE, PROCESS, or CBL statement.
- In the COPY statement, the text-name is the only value processed. The statement must end on the same line as the COPY keyword with a period followed by a space. If any option is found, the COPY statement is not expanded.
- In the IDENTIFICATION DIVISION, the division header or paragraph header statements must be blank except for the division or paragraph name. The trigger statement must be on the next line that is neither blank nor a comment.
- In all other divisions, the trigger statement (line) can be on any line in the division.
- If the WITH DEBUGGING MODE clause is not found in the SOURCE COMPUTER paragraph, all debug lines are passed to the compiler without being scanned for expansion triggers, as if they were comment lines. If the clause is found, valid trigger statements found on debug lines are expanded and a D is inserted in column 7 of all the non-comment, non-continuation lines included.
- Any character found in FIELD A that is not a blank causes the end of the paragraph form of the NOTE statement.
These are SCRIPT/VS restrictions:
- The .im statement must be the only statement in the logical record and must start in the first valid column. The first logical record is tested for line numbers, as follows:
  - For fixed-length records, if the last 8 characters are all numeric, they are skipped for the complete library.
  - For variable-length records, if the first 8 characters are all numeric, processing begins with column 9.
  The statements can be in either uppercase, lowercase, or mixed case.
- Because ISPF creates a sequential data set from the imbedded members, use of the .EF control word will cause all statements in the sequential data set following the .EF to be ignored. The use of .EF is not recommended with packed data.