|
2 | 2 | [Return to master README.md](../README.md) |
3 | 3 |
|
4 | 4 | # Hercules CCKD64 Support |
| 5 | + |
5 | 6 | ## Contents |
| 7 | + |
6 | 8 | 1. [About CCKD64](#About-CCKD64) |
7 | 9 | 2. [Conversion to CCKD64](#Conversion-to-CCKD64) |
8 | 10 | 3. [Procedure](#Procedure) |
9 | 11 | 4. [Additional Information](#Additional-Information) |
10 | 12 |
|
11 | 13 | ## About CCKD64 |
| 14 | + |
12 | 15 | Version 4.2 of SDL Hercules Hyperion introduced support for very large Compressed CKD (CCKD) dasd image files, called CCKD64, which can be much larger than 4GB in size. |
13 | 16 |
|
14 | 17 | The current default implementation of CCKD only supports a maximum file size of 4GB. With the current CCKD implementation, when a compressed CCKD dasd image file (or any of its associated shadow files) reaches a file size of 4GB, unrecoverable I/O errors occur. This is caused by the use of only 32-bit file offset values being used in the original design. |
15 | 18 |
|
16 | 19 | With the introduction of CCKD64 support however, the new CCKD64 file format uses 64-bit file offsets, thus allowing CCKD64 format compressed dasd image files (and their associated shadow files) to grow to the theoretical maximum of 18EB in size. (The actual maximum size that any operating system file can actually be however, is limited by the operating system itself as well as the format of the file system that the file resides on. On Windows with NTFS volumes for example, the actual maximum supported file size is 16TB.) |
17 | 20 |
|
18 | 21 | ## Conversion to CCKD64 |
| 22 | + |
19 | 23 | In order to take advantage of the new CCKD64 file format, existing emulated dasd image files in the old CCKD compressed format must first be converted to the new CCKD64 format by either: |
20 | | -- using the new 'convto64' utility to individually convert each old format base image and associated shadow files to the new format (recommended) |
21 | | -or |
22 | | -- creating brand new cckd64 base image file using the new 'dasdinit64' utility |
23 | | -or |
24 | | -- copying existing old format CCKD images to the new CCKD64 format using the new 'dasdcopy64' utility. |
25 | 24 |
|
26 | | -It is critical the dasd images being converted not have any errors before they are converted. It is highly recommended that `cckdcdsk -3` be run on each image before converting. Running cckdcomp is also recommended. |
27 | 25 |
|
28 | | -Using the 'convto64' utility to convert existing CCKD files to the CCKD64 format is recommended over using dasdcopy64 as it is not only significantly faster than dasdcopy64 but is also able to convert individual CCKD shadow files as well (which dasdcopy64 cannot currently do). That is to say, if you already have a CCKD format base dasd image file with one or more shadow files associated with it, dasdcopy64 can only copy the base image plus all of its shadow files to a single new CCKD64 base image file (i.e. the shadow files are automatically "merged" during the copy operation, resulting in a single CCKD64 BASE dasd image output file). The 'convto64' utility however, directly converts base images -OR- shadow files individually, resulting in a new CCKD64 format base image or CCKD64 format shadow file. It does NOT "merge" them together and, as previously mentioned, is significantly faster than dasdcopy64 too. It is the recommended way to convert existing CCKD dasd images to the new CCKD64 format. |
| 26 | +- Using the new **`convto64`** utility to individually convert each old format base image and associated shadow files to the new format _(recommended!)_, or |
| 27 | + |
| 28 | + |
| 29 | +- Creating brand new cckd64 base image file using the new `dasdinit64` utility, or |
| 30 | + |
| 31 | + |
| 32 | +- Copying existing old format CCKD images to the new CCKD64 format using the new `dasdcopy64` utility. |
29 | 33 |
|
30 | | -In addition to the new 'dasdinit64' and 'dasdcopy64' utilities, there are also corresponding CCKD64 versions of: |
31 | | -'cckdcdsk' check disk utility called 'cckdcdsk64' |
32 | | -'cckdcomp' utility called 'cckdcomp64' |
33 | | -'cckdswap' called 'cckdswap64' |
34 | | -'cckddiag' diagnostic utility called 'cckddiag64' |
35 | | -'dasdconv' utility called 'dasdconv64' |
36 | | -'dasdload' utility called 'dasdload64' |
37 | 34 |
|
38 | | -The existing dasdls, dasdcat, dasdpdsu, dasdisup, and dasdseq utilities do not have any specialized CCKD64 versions. However, all of them do support the new CCKD64 file format in addition to the existing CCKD file format; they just don't have separate executable names ending in '64' as they have all been updated to support either of the two formats automatically. |
| 35 | +It is critical the dasd images being converted not have any errors before they are converted. It is highly recommended that `cckdcdsk -3` be run on each image before converting. Running `cckdcomp` is also recommended. |
| 36 | + |
| 37 | +Using the **`convto64`** utility to convert existing CCKD files to the CCKD64 format is recommended over using `dasdcopy64` as it is not only significantly faster than `dasdcopy64` but is also able to convert individual CCKD shadow files as well (which `dasdcopy64` cannot currently do). That is to say, if you already have a CCKD format base dasd image file with one or more shadow files associated with it, `dasdcopy64` can only copy the base image plus all of its shadow files to a single new CCKD64 base image file (i.e. the shadow files are automatically _merged_ during the copy operation, resulting in a single CCKD64 BASE dasd image output file). The **`convto64`** utility however, directly converts base images _-OR-_ shadow files individually, resulting in a new CCKD64 format base image or CCKD64 format shadow file. It does _NOT_ "merge" them together and, as previously mentioned, and is significantly faster than `dasdcopy64` too. It is the recommended way to convert existing CCKD dasd images to the new CCKD64 format. |
| 38 | + |
| 39 | +In addition to the new `dasdinit64` and `dasdcopy64` utilities, there are also corresponding CCKD64 versions of: |
| 40 | + |
| 41 | + |
| 42 | + `cckdcdsk` check disk utility called `cckdcdsk64` |
| 43 | + `cckdcomp` utility called `cckdcomp64` |
| 44 | + `cckdswap` called `cckdswap64` |
| 45 | + `cckddiag` diagnostic utility called `cckddiag64` |
| 46 | + `dasdconv` utility called `dasdconv64` |
| 47 | + `dasdload` utility called `dasdload64` |
| 48 | + |
| 49 | + |
| 50 | +The existing `dasdls`, `dasdcat`, `dasdpdsu`, `dasdisup`, and `dasdseq` utilities do not have any specialized CCKD64 versions. However, all of them do support the new CCKD64 file format in addition to the existing CCKD file format; they just don't have separate executable names ending in '64' as they have all been updated to support either of the two formats automatically. |
39 | 51 |
|
40 | 52 | ## Procedure |
41 | | -1. Run `cckdcdsk -3` on all existing 32-bit CCKD dasds to correct any existing errors. |
42 | 53 |
|
43 | | -2. Run `cckdcomp` on all existing 32-bit CCKD dasds to remove all free space. |
| 54 | +1. Run **`cckdcdsk -3`** on all existing 32-bit CCKD dasds to correct any existing errors. _**(Critical!)**_ |
44 | 55 |
|
45 | | -3. Use `convto64` to individually convert all 32-bit CCKD base image and associated shadow files to the new 64-bit CCKD64 format. Note that the shadow file and base image must be converted separately from one another. |
| 56 | +2. Run `cckdcomp` on all existing 32-bit CCKD dasds to remove all free space. _(optional but recommended)_ |
46 | 57 |
|
47 | | -4. Optional: run `cckdcdsk64 -3` on all of the newly converted 64-bit CCKD64 dasd images to verify the conversion was successful and that no errors exist on any of the images. |
| 58 | +3. Use **`convto64`** to individually convert all 32-bit CCKD base image and associated shadow files to the new 64-bit CCKD64 format. Note that the shadow file and base image must be converted separately from one another. _(required)_ |
| 59 | + |
| 60 | +4. Run `cckdcdsk64 -3` on all of the newly converted 64-bit CCKD64 dasd images to verify the conversion was successful and that no errors exist on any of the images. _(optional)_ |
48 | 61 |
|
49 | 62 | ## Additional Information |
50 | | -Additional information regarding the new CCKD64 file format can be found on the [Compressed Dasd Emulation](https://sdl-hercules-390.github.io/html/cckddasd.html) web page. |
| 63 | + |
| 64 | +Additional information regarding the new CCKD64 file format can be found on the [Compressed Dasd Emulation](../html/cckddasd.html) web page. |
0 commit comments