Specifications
120 IBM System z Personal Development Tool: Volume 3 Additional Topics
-u or --unit indicates the address (device number) of the volume that is to be copied
(migrated).
-e or --eof indicates the number of consecutive tape marks that will indicate the end of the
input tape. This is used only with z/VM tapes. The default is two tapemarks.
Either the -u or -v parameter must be supplied for DASD, but not both; the -u parameter
would normally be used for tapes.
Once the server is started on the z/OS or z/VM system, the client may be started on the Linux
system. Remember that zPDT need not be operational for this. (We generally recommend
that it should not be operational, because the migration utility can place a heavy load on the
LAN interface.) Examples of commands that could be used to run the client are as follows:
$ hckd2ckd 192.168.0.99 /z/VOL123 -v VOL123
$ hckd2ckd BIG.ZOS.ADDR:4990 /z/VOL678 -u A8F
$ hckd2ckd 192.168.0.99:4990 /z/host.WORK23 -v WORK23 --norestart
The first operand is the IP address of the z/OS system where the server is running. This may
be in dotted-decimal form or as a name that the Linux system can resolve. The TCP/IP port
number can be changed as shown in the examples, where we use port 4990 in two cases.
(The server must have been started using the same port number, of course.) The second
operand is the Linux file name used to store the migrated volume. Either the -v or -u
parameter must be specified. The -v parameter is a volser and the -u parameter is a device
address (device number) on the server system; these determine which volume is to be
processed.
11.8 Additional notes
The migration of a tape volume results in a compressed awstape output file. The -n option will
produce an uncompressed awstape output file.
Devmap
After a volume has been migrated to Linux, you can add it to your devmap and access it from
zPDT. You should also check the permission bits for the file. (The zPDT system must have
read/write access to it.) Our examples are in terms of z/OS volumes, but the volume could be
for z/VM, z/VSE, or Linux for System z.
Labelled tapes
The migration utility (z/VM version) does not inspect tape labels; they are simply treated as
files. By default, the migration function stops when two adjacent tape marks are encountered.
This can have two side effects:
A null file in a labelled multifile volume can produce two adjacent tape marks that do not
indicate the end of the tape. You must manually handle this situation. (Imbedded null files
on tape are considered bad practice; this situation should be rare.)
A multivolume labelled tape data set has only a single tape mark at the end of the first
volume(s); the last volume is terminated by two tape marks. You can handle this by using
the default termination indicator (two tape marks). This will produce an error message at
the end of each of the initial volume(s); the error can be ignored.










