Hercules Version 3: Creating DASD

This page describes various ways of creating and loading DASD volumes for use with Hercules.


Contents

Using pre-built DASD images

Creating, formatting, and loading DASD volumes

Building a DASD volume from unloaded PDS files

Other DASD utilities


Using pre-built DASD images

IBM distributes pre-built OS/390 and z/OS systems on two different CD-ROM packages:

The OS/390 and z/OS Application Development CD (ADCD)
available only to members of IBM PartnerWorld for Developers, and
The OS/390 and z/OS DemoPkg
available only to IBM employees and qualified IBM Business Partners.

Both of these packages contain pre-built DASD image files which simply need to be unzipped onto your hard drive. The unzipped images can be directly read by Hercules.

Be aware, however, that you cannot use the ADCD images because the PartnerWorld scheme requires you to purchase or lease an IBM approved machine in order to obtain the ADCD, and the software on the ADCD is licensed for use only on the machine that it was shipped with. See http://www.ibm.com/servers/enable/site/zinfo/adcd.html. If you want Hercules to be an approved machine so that you can use the ADCD, then I suggest you lobby IBM Developer Relations at the address given on their web page.

Different rules apply to the OS/390 and z/OS DemoPkg CD which is available only to IBM employees and business partners. If you fall into this category then you probably know what the rules are -- I don't :-(


Creating, formatting, and loading DASD volumes

Creating an empty DASD volume

The dasdinit program must first be run from the Unix shell prompt to create a file containing an empty DASD volume.

The format of the dasdinit command is:


Hercules DASD image file creation program
Version 3.05
(c)Copyright 1999-2007 by Roger Bowler, Jan Jaeger, and others
Builds an empty dasd image file:

  dasdinit [-options] filename devtype[-model] [volser] [size]

where:

  -v         display version info and help
  -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
  -lfs       build a large (uncompressed) dasd file (if supported)
  -a         build dasd image file that includes alternate cylinders
             (option ignored if size is manually specified)
  -r         build 'raw' dasd image file  (no VOL1 or IPL track)
  -linux     null track images will look like linux dasdfmt'ed images
             (3390 device type only)

  filename   name of dasd image file to be created

  devtype    CKD: 2305, 2311, 2314, 3330, 3340, 3350, 3375, 3380, 3390, 9345
             FBA: 0671, 3310, 3370, 9313, 9332, 9335, 9336

  model      device model (implies size) (opt)

  volser     volume serial number (1-6 characters)
             (specified only if '-r' option not used)

  size       number of CKD cylinders or 512-byte FBA sectors
             (required if model not specified else optional)


The current list of device types and models supported is:


              CKD DEVICES

                             alt
        devtype-model  cyls  cyls

        2311           [*]
        2311-1         200    2

        2314           [*]
        2314-1         200    3

        3330           [*]
        3330-1         404    7
        3330-2         808    7
        3330-11        808    7

        3340           [*]
        3340-1         348    1
        3340-35        348    1
        3340-2         696    2
        3340-70        696    2

        3350           [*]
        3350-1         555    5

        3375           [*]
        3375-1         959    1

        3380           [*]
        3380-1         885    1
        3380-A         885    1
        3380-B         885    1
        3380-D         885    1
        3380-J         885    1
        3380-2        1770    2
        3380-E        1770    2
        3380-3        2655    3
        3380-K        2655    3
        EMC3380K+     3339    3
        EMC3380K++    3993    3

        3390           [*]
        3390-1        1113    1
        3390-2        2226    1
        3390-3        3339    1
        3390-9       10017    3
        3390-27      32760    3
        3390-54      65520    3

        9345           [*]
        9345-1        1440    0
        9345-2        2156    0


             FBA DEVICES

        devtype-model  blocks

        3310              [*]
        3310-1         125664

        3370              [*]
        3370-Al        558000
        3370-B1        558000
        3370-A2        712752
        3370-B2        712752

        9313              [*]
        9313-1         246240

        9332              [*]
        9332-200       360036
        9332-400       360036
        9332-600       554800

        9335              [*]
        9335-1         804714

        9336              [*]
        9336-10        920115
        9336-20       1672881
        9336-25       1672881

        0671-08        513072
        0671           574560
        0671-04        624456

[*] size may be specified else size defaults to the first listed model.

Volumes exceeding 2GB

For CKD volumes which exceed 2GB, such as the 3390-3, and the -lfs parameter is not specified, the DASDINIT program will create multiple files by appending the characters _1, _2, _3 etc. to the file name specified on the command line. These characters are inserted before the first dot (.) 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 specified and large file size is supported on your platform..

Examples

To create a 3330 model 1 CKD volume consisting of 404 cylinders (plus 7 alternate cylinders too) with volume serial number WORK01 in a file called work01.151:

    dasdinit -a work01.151 3330-1 work01

To create a compressed 3350 CKD volume consisting of 560 cylinders (555 cylinders plus the 5 alternate cylinders) with volume serial number SYSRES in a file called dosvs34.24f:

    dasdinit -a -bz2 dosvs34.24f 3350-1 sysres

To create a 3370 FBA volume with only 100000 sectors (instead of the usual 558000 sectors) with volume serial number WORK02 in a file called mini.work02.140:

    dasdinit mini.work02.140 3370 work02 100000

To create a 3390 model 3 (triple density) CKD volume of 3339 cylinders with volume serial number WORK03:

    dasdinit triple.a88 3390-3 work03

Because this volume exceeds 2GB, DASDINIT will create two files with triple_1.a88 containing cylinders 0-2518 and triple_2.a88 containing cylinders 2519-3339. If you specify

    dasdinit -lfs triple.a88 3390-3 work03

then DASDINIT will create a single file triple.a88 containing all the cylinders. Your platform must support large file size to specify the -lfs option.

Formatting the empty DASD volume

After creating a DASD volume you can format it with a program such as standalone IBCDASDI or ICKDSF.

Here is an example of the IBCDASDI control statements required to initialize a 3330 volume:


WORK01 JOB  'INITIALIZE 3330 WORK VOLUME'
       MSG   TODEV=1052,TOADDR=009
       DADEF TODEV=3330,TOADDR=151,IPL=NO,VOLID=WORK01,BYPASS=YES
       VLD   NEWVOLID=WORK01,OWNERID=HERCULES
       VTOCD STRTADR=1,EXTENT=5
       END

To run IBCDASDI,to message text 'HHCXXnnnI Device cuu intervention required.' where cuu is whatever cuu was identified in the message."

The HAO is not that sophisticated (yet). Only simple plain-text commands may be defined and issued. No automatic substitution is done based on message text (although normal 'DEFSYM' symbol substitution is supported however, as that is a normal panel-command feature supported separately from the HAO). This may possibly change in the future however, depending on user need/demand.

All defined rules are checked for a match each time Hercules issues a message. There is no way to specify "stop processing subsequent rules". If a message is issued that matches two or more rules, each associated command is then issued in sequence. Thus the advice to choose your rules' target patterns carefully very much applies here.


Technical Support

For technical support, please refer our Technical Support web page.


back

Last updated $Date: 2007/06/22 12:04:39 $ $Revision: 1.47 $

./usr/share/hercules/herclic.html0000644000000000000000000001167111002715677015751 0ustar rootroot Hercules: Q Public License

THE Q PUBLIC LICENSE version 1.0


Copyright (C) 1999 Trolltech AS, Norway.
Everyone is permitted to copy and
distribute this license document.

The intent of this license is to establish freedom to share and change the software regulated by this license under the open source model.

This license applies to any software containing a notice placed by the copyright holder saying that it may be distributed under the terms of the Q Public License version 1.0. Such software is herein referred to as the Software. This license covers modification and distribution of the Software, use of third-party application programs based on the Software, and development of free software which uses the Software.

Granted Rights

1. You are granted the non-exclusive rights set forth in this license provided you agree to and comply with any and all conditions in this license. Whole or partial distribution of the Software, or software items that link with the Software, in any form signifies acceptance of this license.

2. You may copy and distribute the Software in unmodified form provided that the entire package, including - but not restricted to - copyright, trademark notices and disclaimers, as released by the initial developer of the Software, is distributed.

3. You may make modifications to the Software and distribute your modifications, in a form that is separate from the Software, such as patches. The following restrictions apply to modifications:

a. Modifications must not alter or remove any copyright notices in the Software.

b. When modifications to the Software are released under this license, a non-exclusive royalty-free right is granted to the initial developer of the Software to distribute your modification in future versions of the Software provided such versions remain available under these terms in addition to any other license(s) of the initial developer.

4. You may distribute machine-executable forms of the Software or machine-executable forms of modified versions of the Software, provided that you meet these restrictions:

a. You must include this license document in the distribution.

b. You must ensure that all recipients of the machine-executable forms are also able to receive the complete machine-readable source code to the distributed Software, including all modifications, without any charge beyond the costs of data transfer, and place prominent notices in the distribution explaining this.

c. You must ensure that all modifications included in the machine-executable forms are available under the terms of this license.

5. You may use the original or modified versions of the Software to compile, link and run application programs legally developed by you or by others.

6. You may develop application programs, reusable components and other software items that link with the original or modified versions of the Software. These items, when distributed, are subject to the following requirements:

a. You must ensure that all recipients of machine-executable forms of these items are also able to receive and use the complete machine-readable source code to the items without any charge beyond the costs of data transfer.

b. You must explicitly license all recipients of your items to use and re-distribute original and modified versions of the items in both machine-executable and source code forms. The recipients must be able to do so without any charges whatsoever, and they must be able to re-distribute to anyone they choose.

c. If the items are not available to the general public, and the initial developer of the Software requests a copy of the items, then you must supply one.

Limitations of Liability

In no event shall the initial developers or copyright holders be liable for any damages whatsoever, including - but not restricted to - lost revenue or profits or other direct, indirect, special, incidental or consequential damages, even if they have been advised of the possibility of such damages, except to the extent invariable law, if any, provides otherwise.

No Warranty

The Software and this license document are provided AS IS with NO WARRANTY OF ANY KIND, INCLUDING THE WARRANTY OF DESIGN, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.

Choice of Law

This license is governed by the Laws of England.


back

Last updated 3 December 2000 ./usr/share/hercules/hercload.html0000644000000000000000000005407511002715677016126 0ustar rootroot Hercules Version 3: Creating DASD

Hercules Version 3: Creating DASD

This page describes various ways of creating and loading DASD volumes for use with Hercules.


Contents

Using pre-built DASD images

Creating, formatting, and loading DASD volumes

Building a DASD volume from unloaded PDS files

Other DASD utilities


Using pre-built DASD images

IBM distributes pre-built OS/390 and z/OS systems on two different CD-ROM packages:

The OS/390 and z/OS Application Development CD (ADCD)
available only to members of IBM PartnerWorld for Developers, and
The OS/390 and z/OS DemoPkg
available only to IBM employees and qualified IBM Business Partners.

Both of these packages contain pre-built DASD image files which simply need to be unzipped onto your hard drive. The unzipped images can be directly read by Hercules.

Be aware, however, that you cannot use the ADCD images because the PartnerWorld scheme requires you to purchase or lease an IBM approved machine in order to obtain the ADCD, and the software on the ADCD is licensed for use only on the machine that it was shipped with. See http://www.ibm.com/servers/enable/site/zinfo/adcd.html. If you want Hercules to be an approved machine so that you can use the ADCD, then I suggest you lobby IBM Developer Relations at the address given on their web page.

Different rules apply to the OS/390 and z/OS DemoPkg CD which is available only to IBM employees and business partners. If you fall into this category then you probably know what the rules are -- I don't :-(


Creating, formatting, and loading DASD volumes

Creating an empty DASD volume

The dasdinit program must first be run from the Unix shell prompt to create a file containing an empty DASD volume.

The format of the dasdinit command is:


Hercules DASD image file creation program
Version 3.05
(c)Copyright 1999-2007 by Roger Bowler, Jan Jaeger, and others
Builds an empty dasd image file:

  dasdinit [-options] filename devtype[-model] [volser] [size]

where:

  -v         display version info and help
  -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
  -lfs       build a large (uncompressed) dasd file (if supported)
  -a         build dasd image file that includes alternate cylinders
             (option ignored if size is manually specified)
  -r         build 'raw' dasd image file  (no VOL1 or IPL track)
  -linux     null track images will look like linux dasdfmt'ed images
             (3390 device type only)

  filename   name of dasd image file to be created

  devtype    CKD: 2305, 2311, 2314, 3330, 3340, 3350, 3375, 3380, 3390, 9345
             FBA: 0671, 3310, 3370, 9313, 9332, 9335, 9336

  model      device model (implies size) (opt)

  volser     volume serial number (1-6 characters)
             (specified only if '-r' option not used)

  size       number of CKD cylinders or 512-byte FBA sectors
             (required if model not specified else optional)


The current list of device types and models supported is:


              CKD DEVICES

                             alt
        devtype-model  cyls  cyls

        2311           [*]
        2311-1         200    2

        2314           [*]
        2314-1         200    3

        3330           [*]
        3330-1         404    7
        3330-2         808    7
        3330-11        808    7

        3340           [*]
        3340-1         348    1
        3340-35        348    1
        3340-2         696    2
        3340-70        696    2

        3350           [*]
        3350-1         555    5

        3375           [*]
        3375-1         959    1

        3380           [*]
        3380-1         885    1
        3380-A         885    1
        3380-B         885    1
        3380-D         885    1
        3380-J         885    1
        3380-2        1770    2
        3380-E        1770    2
        3380-3        2655    3
        3380-K        2655    3
        EMC3380K+     3339    3
        EMC3380K++    3993    3

        3390           [*]
        3390-1        1113    1
        3390-2        2226    1
        3390-3        3339    1
        3390-9       10017    3
        3390-27      32760    3
        3390-54      65520    3

        9345           [*]
        9345-1        1440    0
        9345-2        2156    0


             FBA DEVICES

        devtype-model  blocks

        3310              [*]
        3310-1         125664

        3370              [*]
        3370-Al        558000
        3370-B1        558000
        3370-A2        712752
        3370-B2        712752

        9313              [*]
        9313-1         246240

        9332              [*]
        9332-200       360036
        9332-400       360036
        9332-600       554800

        9335              [*]
        9335-1         804714

        9336              [*]
        9336-10        920115
        9336-20       1672881
        9336-25       1672881

        0671-08        513072
        0671           574560
        0671-04        624456

[*] size may be specified else size defaults to the first listed model.

Volumes exceeding 2GB

For CKD volumes which exceed 2GB, such as