Hercules V4.00.0 - Operations and Utilities Guide - HEUR040000-00 Page 61 (61 of 152)

5.10.5 Sample Utility Output

Sample 1:

Fix the XCTL tables in SVCLIB on volume OS36IP.148.

D:\HERCULES>dasdisup D:/MVS/DASD/OS36IP.148

Hercules IEHIOSUP program Version 3.05

HHCDS006W Member IGG019PZ is not single text record

HHCDS006W Member IGG019V6 is not single text record

HHCDS007W Member IGG019V6 size 0A20 exceeds X'7F8' bytes

HHCDS002I End of directory: 4 members selected

HHCDS010I Member IGG019PX skipped

HHCDS010I Member IGG019PY skipped

HHCDS010I Member IGG019PZ skipped

HHCDS010I Member IGG019V6 skipped

Figure 39: DASDISUP utility output

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.

Previous Page Next Page

Extracted Text (may have errors)

5.10 DASDISUP (Fix XCTL tables in SVCLIB)

5.10.1 Function

The DASDISUP utility fixes the XCTL tables in SVCLIB on OS/360 systems. On an OS/360 system the
OPEN / CLOSE / EOV modules in SYS1.SVCLIB have XCTL tables embedded within them. These tables
contain TTRs, pointing to other modules, and these TTRs need to be adjusted after loading SVCLIB to
DASD.

OS/360 provides a program called IEHIOSUP to perform this function, however the issue is that you
cannot run IEHIOSUP until you have the system up and running, and you cannot IPL the system until you
have fixed the XCTL tables.

To circumvent this problem Hercules provides a utility program called DASDISUP which can be run from
the Unix or Windows command line after running DASDLOAD and fixes the XCTL tables.

Note: Do not use this procedure except on OS/360 IPL volumes; other operating systems do not have
XCTL tables.

5.10.2 Syntax

Descriptive

DASDISUP outfile [SF=shadowfile]

Diagram

ÊÊ¬¬¬ DASDISUP ¬¬¬ outfile ¬¬¬§¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬§¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬ÊÍ

shadowfile ¬¬¬¯

5.10.3 Parameter

outfile

The name of the OS/360 IPL volume to be updated.

shadowfile

The (optional) name of the associated shadow DASD file.

5.10.4 Examples

Example 1:

Fix the XCTL tables in SVCLIB on volume OS36IP.148.

DASDISUP D:/MVS/DASD/OS36IP.148

5.10.5 Sample Utility Output

Sample 1:

Fix the XCTL tables in SVCLIB on volume OS36IP.148.

D:\HERCULES>dasdisup D:/MVS/DASD/OS36IP.148

Hercules IEHIOSUP program Version 3.05

HHCDS006W Member IGG019PZ is not single text record

HHCDS006W Member IGG019V6 is not single text record

HHCDS007W Member IGG019V6 size 0A20 exceeds X'7F8' bytes

HHCDS002I End of directory: 4 members selected

HHCDS010I Member IGG019PX skipped

HHCDS010I Member IGG019PY skipped

HHCDS010I Member IGG019PZ skipped

HHCDS010I Member IGG019V6 skipped

Figure 39: DASDISUP utility output

Help

Example 2:

Create the same DASD volume as in the previous example but create just one file (large file support)
named USR001.300 in the same directory.

DASDINIT -lfs D:\MVS\DASD\USR001.300 3390-3 USR001

Example 3:

Create a 3390 Model 3 with volume serial SYS3A0 and alternate cylinder(s), the file should be com-
pressed with ZLIB and the filename has to be TSTVOL.DSD. The DASD volume must be placed in
directory D:\MVS\DASD\.

DASDINIT -z -a D:\MVS\DASD\TSTVOL.DSD 3390-3 SYS3A0

5.9.5 Sample Utility Output

Sample 1:

Create a 3390 model 3 DASD image file named SYS3A0.3A0 with volser=SYS3A0.

D:\HERCULES>DASDINIT D:\MVS\DASD\SYS3A0.3A0 3390-3 SYS3A0

HHCDU044I Creating 3390 volume SYS3A0: 3339 cyls, 15 trks/cyl, 56832 bytes/track

HHCDU041I 2519 cylinders successfully written to file D:/MVS/DASD/SYS3A0_1.3A0

HHCDU041I 820 cylinders successfully written to file D:/MVS/DASD/SYS3A0_2.3A0

HHCDI001I DASD initialization successfully completed.

Figure 38: DASDINIT utility output

5.10 DASDISUP (Fix XCTL tables in SVCLIB)

5.10.1 Function

The DASDISUP utility fixes the XCTL tables in SVCLIB on OS/360 systems. On an OS/360 system the
OPEN / CLOSE / EOV modules in SYS1.SVCLIB have XCTL tables embedded within them. These tables
contain TTRs, pointing to other modules, and these TTRs need to be adjusted after loading SVCLIB to
DASD.

OS/360 provides a program called IEHIOSUP to perform this function, however the issue is that you
cannot run IEHIOSUP until you have the system up and running, and you cannot IPL the system until you
have fixed the XCTL tables.

To circumvent this problem Hercules provides a utility program called DASDISUP which can be run from
the Unix or Windows command line after running DASDLOAD and fixes the XCTL tables.

Note: Do not use this procedure except on OS/360 IPL volumes; other operating systems do not have
XCTL tables.

5.10.2 Syntax

Descriptive

DASDISUP outfile [SF=shadowfile]

Diagram

ÊÊ¬¬¬ DASDISUP ¬¬¬ outfile ¬¬¬§¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬§¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬ÊÍ

shadowfile ¬¬¬¯

5.10.3 Parameter

outfile

The name of the OS/360 IPL volume to be updated.

shadowfile

The (optional) name of the associated shadow DASD file.

5.10.4 Examples

Example 1:

Fix the XCTL tables in SVCLIB on volume OS36IP.148.

DASDISUP D:/MVS/DASD/OS36IP.148

Previous Page Next Page

Extracted Text (may have errors)

-m

Enable the wait PSW in the IPL1 record for machine check interruptions. If this
option is not specified, the wait PSW will be disabled for machine checks.

-linux

Null track images will look like Linux DASDFMT’ed images (3390 device type only).

arguments:

filename

The name of the DASD image file to be created.

devtype

Specifies the device type. Valid device types are:

FBA: 0671, 3310, 3370, 9313, 9332, 9335, 9336

CKD: 2311, 2314, 3330, 3340, 3350, 3375, 3380, 3390, 9345

A complete list of all Hercules supported DASD device types and models with
additional information can be found in Appendix A.

model

Specifies the device model (note – this implies size). A list of Hercules supported
device types and models can be found in Appendix A.

volser

Volume serial number (1-6 characters).

size

Number of CKD cylinders or 512-byte FBA sectors (required if model not specified,
otherwise optional).

For CKD volumes which exceed 2GB, such as the 3390-3, if the -lfs parameter is not specified the DASD-
INIT program will create multiple files by appending the characters _1, _2, _3 etc. to the file name speci-
fied on the command line. These characters are inserted before the first dot (.) occurring after the last
slash (/). If there is no dot then the characters are appended to the end of the name. Each file contains a
whole number of cylinders.

Hercules CKD support recognizes the files as belonging to a single logical volume. Specify the full name
of just the first file in the Hercules configuration file (e.g. "filename_1").

The DASDINIT program cannot create FBA volumes exceeding 2GB unless the -lfs parameter is speci-
fied and large file size is supported on your platform.

Note that the defaults for the wait PSW written to the IPL1 record have changed from earlier releases of
Hercules. In the past, the wait PSW created by DASDINIT was a BC-mode PSW enabled for machine in-
terrupts. The current default for the wait PSW is EC-mode, disabled for machine checks. To obtain the
earlier behaviour, run DASDINIT with the ‘-b’ and ‘-m’ options.

5.9.4 Examples

Example 1:

Create a 3390 Model 3 with volume serial USR001, the file(s) should be named USR001.300 and place
them into directory D:\MVS\DASD\. Note that the utility creates actually two files called USR001_1.300
and USR001_2.300 because no large file support is requested.

DASDINIT D:\MVS\DASD\USR001.300 3390-3 USR001

Example 2:

Create the same DASD volume as in the previous example but create just one file (large file support)
named USR001.300 in the same directory.

DASDINIT -lfs D:\MVS\DASD\USR001.300 3390-3 USR001

Example 3:

Create a 3390 Model 3 with volume serial SYS3A0 and alternate cylinder(s), the file should be com-
pressed with ZLIB and the filename has to be TSTVOL.DSD. The DASD volume must be placed in
directory D:\MVS\DASD\.

DASDINIT -z -a D:\MVS\DASD\TSTVOL.DSD 3390-3 SYS3A0

5.9.5 Sample Utility Output

Sample 1:

Create a 3390 model 3 DASD image file named SYS3A0.3A0 with volser=SYS3A0.

D:\HERCULES>DASDINIT D:\MVS\DASD\SYS3A0.3A0 3390-3 SYS3A0

HHCDU044I Creating 3390 volume SYS3A0: 3339 cyls, 15 trks/cyl, 56832 bytes/track

HHCDU041I 2519 cylinders successfully written to file D:/MVS/DASD/SYS3A0_1.3A0

HHCDU041I 820 cylinders successfully written to file D:/MVS/DASD/SYS3A0_2.3A0

HHCDI001I DASD initialization successfully completed.

Figure 38: DASDINIT utility output

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’).

Previous Page Next Page

Extracted Text (may have errors)

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.

5.10.5 Sample Utility Output

5.11 DASDLOAD (DASD l oader program)

5.11.1 Function

5.11.2 Syntax

5.11.3 Parameter

Page 81. Preface click to expand contents

Page 112. Related Publications click to expand contents

Page 123. Summary of changes click to expand contents

Page 144. Hercules Operations click to expand contents

Page 385. Hercules Supplied Utilities click to expand contents

Page 1006. Third Party Utilities click to expand contents

Page 1307. Mainframe Utilities click to expand contents

Page 144Appendix B. Syntax click to expand contents

Extracted Text (may have errors)

5.10 DASDISUP (Fix XCTL tables in SVCLIB)

5.10.1 Function

5.10.2 Syntax

5.10.3 Parameter

5.10.4 Examples

5.10.5 Sample Utility Output

Help

loading

5.9.5 Sample Utility Output

5.10 DASDISUP (Fix XCTL tables in SVCLIB)

5.10.1 Function

5.10.2 Syntax

5.10.3 Parameter

5.10.4 Examples

Extracted Text (may have errors)

5.9.4 Examples

5.9.5 Sample Utility Output

5.11.4 Control File

5.11.4.1 Volume Statement

5.11.4.2 Dataset Statement

Extracted Text (may have errors)

5.11 DASDLOAD (DASD l oader program)

5.11.1 Function

5.11.2 Syntax

5.11.3 Parameter

5.11.4 Control File

5.11.4.1 Volume Statement

5.11 DASDLOAD (DASD l
oader program)

5.11 DASDLOAD (DASD l
oader program)