If you use data sets defined in the DB2 UDB
for OS/390 system to receive the report of
the generate DDL function, or the actual
DDL that is generated, here are some examples
that show how the data sets are allocated.
Assume that the data set name is DB2.SQL.OUTPUT and that it is a new or empty data set.
Your MVS volume serial name is VOL001, and the unit name, or device type that
will be used to allocate the data set is
SYSDA.
In this case if DB2.SQL.OUTPUT is a new data set the generate DDL function
will allocate it with the following attributes:
DSN=DB2.SQL.OUTPUT,DISP=(NEW,CATLG),UNIT=SYSDA,VOL=SER=VOL001,DCB=(LRECL=80,RECFM=FB,BLKSIZE=6160,DSORG=PS),
SPACE=(CYL,(1,1))
If the data set exists it will be overwritten.
Assume that the data set name is DB2.SQL.OUTPUT(EXT) and that it is a new data set. The member
name is EXT. The unit name, or device type that will
be used to allocate the data set is SYSDA.
In this case if DB2.SQL.OUTPUT(EXT) is a new data set, the generate DDL
function will allocate it with the following
attributes:
DSN=DB2.SQL.OUTPUT(EXT),DISP=(NEW,CATLG),UNIT=SYSDA,VOL=SER=,DCB=(LRECL=80,RECFM=FB,BLKSIZE=6160,DSORG=PO),
SPACE=(CYL,(1,1,20))
If the data set already exists, a new member
will be created, or the existing member,
EXT, will be replaced.