Parameter Statement

Purpose

The parameter statement specifies override processing options for the DDDL generator. Under z/VSE, this statement must be used to specify options; under z/OS, parameters can be specified in the execution JCL by using the PARM clause of the EXEC statement.

Coding rules

The following rules apply to coding a parameter statement for the DDDL Generator:

Parameter statements, if used, must be input first before the data usage files.
Multiple parameter statements can be entered.
Statements can be coded in positions 1 through 72.
Options can be specified in any order, with one or more options per statement and at least one blank or comma between specifications.

Syntax

►►─┬────────────┬─────────────────────────────────────────────────────────────►
   ├─ LISt ◄ ─┬─┘
   └─ NOLISt ─┘

 ►─┬─────────────────────────────────────────────────────┬────────────────────►
   │           ┌─────────────────────────────────────┐   │
   ├─ LIBrary ─▼─ member-name ──┬──────────────────┬─┴─┬─┘
   │                            └─ = program-name ─┘   │
   └─ NOLIBrary ◄ ─────────────────────────────────────┘

 ►─┬────────────┬─────────────────────────────────────────────────────────────►◄
   ├─ DISk ◄ ─┬─┘
   └─ NODisk ─┘

Parameter list

LISt/NOList

Specifies whether the file of generated DDDL statement is to be listed, as follows:

LIST (default)—The generated DDDL statements are to be listed.
NOLIST—The generated DDDL statements are not to be listed.

LIBrary/NOLIBrary

Specifies information about the data usage files to be input to the DDDL Generator, as follows:

LIBRARY—Identifies the data usage files. Each occurrence of member-name identifies a data usage file. All files specifies must be members of the same partitioned data set (z/OS) or source statement library (z/VSE). The optional entry, program-name, can be specified for any member and overrides the use of the specified member as the program ID on the generated ADD PROGRAM syntax.
LIBRARY must always be specified with NODISK (see below) and must be specified with DISK if data usage files are to be read from both sequential data sets and from a partitioned data set (z/OS) or a source statement library (z/VSE).
NOLIBRARY—Specifies that data usage files are not to be read from a partitioned data set (z/OS) or source statement library (z/VSE). If the default of NOLIBRARY is taken, then the default of DISK (see below) must also be taken.

DISk/NODisk

Are options used with LIBRARY/NOLIBRARY, as follows:

DISK (default)—Specifies that data usage files are to be read from a sequential data set. DISK must always be specified with NOLIBRARY. DISK can be specified with LIBRARY if the data usage files are to be read from both sequential data set and from partitioned data set (z/OS) or source statement library (z/VSE).
NODISK—Specifies that data usage files are not to be read from a sequential data set. LIBRARY (see above) must be specified with NODISK if all of the data usage files are stored in a partitioned data set (z/OS) or source statement library (z/VSE).