Control statements

When you are coding the DFSDDLT0 control statements, keep these items in mind:

• You must fill in column 1 of each control statement. If column 1 is blank, the statement type defaults to the prior statement type. DFSDDLT0 attempts to use any remaining characters as it would for the prior statement type.
• Use of reserved fields can produce invalid output and unpredictable results.
• Statement continuations are important, especially for the CALL statement.
• Sequence numbers are not required, but they can be very useful for some DFSDDLT0 functions.
• All codes and fields in the DFSDDLTO statements must be left justified followed by blanks, unless otherwise specified.

Control statement guidelines

The order of control statements is critical in constructing a successful call. To avoid unpredictable results, follow these guidelines:

• If you are using STATUS and OPTION statements, place them somewhere before the calls that are to use them.
• Both types of COMMENT statements are optional but, if present, must appear before the call they document.
• You must code CALL FUNCTION statements and any required SSAs consecutively without interruption.
• CALL DATA statements must immediately follow the last continuation, if any, of the CALL FUNCTION statements.
• COMPARE statements are optional but must follow the last CALL (FUNCTION or DATA) statement.
• When CALL FUNCTION statements, CALL DATA statements, COMPARE DATA statements, COMPARE PCB statements, and COMPARE AIB statements are coded together, they form a call sequence. Do not interrupt call sequences with other DFSDDLT0 control statements.
  Exception: IGNORE statements are the only exception to this rule.
• Use IGNORE statements (N or period (.)) to override any statement, regardless of its position in the input stream. You can use IGNORE statements in either SYSIN or SYSIN2 input streams.