arguments:

ctlfile

This is the name of the control file that specifies the datasets to be loaded onto the
newly created volume.

outfile

The name of the DASD image file to be created.

msglevel

This can be a number from 0 to 5, it controls the detail level of messages issued
during the load.

Note that the DASDLOAD defaults for the wait PSW written to the IPL1 record on non-IPLable volumes
have changed from earlier releases of Hercules. In the past, the wait PSW created by DASDLOAD o
n
volumes without IPL text was a BC-mode PSW enabled for machine check interrupts. The current default
for the wait PSW is EC-mode, disabled for machine checks. To obtain the earlier behaviour, run the
DASDLOAD utility with the ‘-b’ and ‘-m’ flags.

5.11.4 Control File

The control file required by the DASDLOAD program is an ASCII text file consisting of a volume
statement followed by one dataset statement for each dataset to be created.

5.11.4.1 Volume Statement

Descriptive

volser devtype[-model] [cyls [ipltext]]

Diagram

Êʬ¬¬ volser ¬¬¬
devtype ¬¬¬§¬¬¬¬¬¬¬¬¬¬¬¬¬¬§¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬Ê

-model ¬¬¬¯

ʬ¬¬§¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬§¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬ÊÍ

cyls ¬¬¬§¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬«

ipltext ¬¬¬¯

where:

volser

Volser is the volume serial number of the newly created volume.

devtype

This specifies the emulated device type (2311, 3330, 3350, 3375, 3380, 3390) of
the new volume. FBA device types are not supported by the DASDLOAD program.

A list of Hercules supported device types and models can be found in Appendix A.

model

This specifies the device model. The model implies the size of the volume.

A list of Hercules supported device types and models can be found in Appendix A.

cyls

Cyls specifies the size of the new volume in cylinders. If cyls is coded as “*” (aste-
risk), as “0” or is omitted, then the default size for the device type and model is
used. Cylinders is ignored for compressed devices.

ipltext

An optional parameter specifying the name of a file containing the IPL text which
will be written to the volume. The file must be in the form of an object deck con-
taining fixed length 80-byte records in the same format as expected by IBCDASDI
or ICKDSF.

5.11.4.2 Dataset Statement

Descriptive

dsname method units pri sec
dir dsorg recfm lrecl blksize keylen

Diagram

Êʬ¬¬ dsname ¬¬¬
method ¬¬¬ units ¬¬¬ pri ¬¬¬ sec ¬¬¬ dir ¬¬¬ dsorg ¬¬¬¬¬¬¬¬¬Ê

ʬ¬¬ recfm ¬¬¬ lrecl ¬¬¬ blksize ¬¬¬ keylen ¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬ÊÍ

where:

dsname

The name of the dataset to be created.

method

The dataset loading method can be one of the following:

XMIT filename
The dataset is loaded from an unloaded PDS created by the TSO XMIT command.
The input is a binary file containing fixed length 80 byte records with no record
delimiters.

VS filename
The dataset is loaded from an unloaded PDS created by IEBCOPY. The input is a
binary file containing variable length spanned records with the record descriptor
words omitted and with no record delimiters.

SEQ filename
The dataset is loaded from an binary file. ASCII / EBCDIC conversion is not cur-
rently supported. Also the DSORG must be ‘PS’ or ‘DA’ and RECFM must either be
‘F’ or ‘FB’.

XMSEQ filename
The dataset is loaded from a dump of a sequential dataset created by the TSO
XMIT command. The input is a binary file containing fixed length 80 byte records
with no record delimiters.

EMPTY
The dataset is initialized with an end-of-file record (if DSORG is ‘PS’) or is an empty
PDS directory (if DSORG is ‘PO’).