5.11 DASDLOAD (DASD l
oader program)

5.11.1 Function

The Hercules DASD loader program is used to create new DASD file images and load them with data
from unloaded PDS files (e.g. a list of TSO XMIT files or a sequential file).

5.11.2 Syntax

Descriptive

DASDLOAD [-option [-option ... ]] ctlfile outfile msglevel

Diagram

Êʬ¬¬ DASDLOAD ¬¬¬§¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬§¬¬¬ ctlfile ¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬Ê

-option ¬¬¬¨¬¬¬¯

ʬ¬¬ outfile ¬¬¬
msglevel ¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬ÊÍ

5.11.3 Parameter

options:

-z

Build compressed DASD image file using zlib.

-bz2

Build compressed DASD image file using bzip2.

-0

Build compressed DASD image file with no compression (0 = zero).

-lfs

Build a large DASD image file (can exceed 2 Gb in size).

-a

Build DASD image file that includes alternate cylinders.

-b

For a volume without IPL text, make the wait PSW written to the IPL1 record a BC-
mode PSW. If this option is not specified, the wait PSW will be an EC-mode PSW.

-m

For a volume without IPL text, make the wait PSW written to the IPL1 record en-
abled for machine checks. If this option is not specified, the wait PSW will be dis-
abled for machine checks.

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.