Specifications

34 IBM System z Personal Development Tool: Volume 3 Additional Topics

The dump file can be sent from Linux to z/OS using ftp. (If the file was compressed (in Linux)

it must be uncompressed before sending it to z/OS.) Our example uses IP address 10.1.1.2

for z/OS because, for demonstration purposes, we used the same zPDT z/OS system that we

used to create the dump volume. In practice, this is likely to be a different z/OS system that

might not be in a zPDT environment.

$ ftp 10.1.1.2

Name (10.1.1.2:ibmsys1): ibmuser

Password: xxxxxx

Remote system type is MVS

ftp> cd 'ogden'

ftp> lcd /tmp

ftp> bin

ftp> put xmit.dump xmitr.dump

ftp> bye

We then used TSO to reformat the dump into the original format created by ADRDSSU:

receive indsn('ogden.xmitr.dump')

(reply to the prompt with) DSN('ogden.unxmit.dump')

Finally, the volume can be restored in z/OS:

//BILL890 JOB 1,OGDEN,MSGCLASS=X

// PGM=ADRDSSU,REGION=40M

//SYSPRINT DD SYSOUT=*

//IN DD UNIT=3390,DSN=OGDEN.UNXMIT.DUMP,DISP=SHR

//OUT DD UNIT=3390,VOL=SER=TEMP03,DISP=OLD

//SYSIN DD *

RESTORE INDDNAME(IN) OUTDDNAME(OUT) PURGE ADMINISTRATOR COPYVOLID

You might not want the COPYVOLID parameter in this job, depending on your circumstances.

You cannot have two disk volumes with the same volser online to z/OS at the same time. If

you do not specify COPYVOLID then the existing volser (TEMP03 in the example) is retained.

If you specify COPYVOLID and a volume with this volser is already online, the restored

volume is taken offline after the restore operation is complete. (In our example, the restored

volser would be WAS001.)

Comments

Many variations are possible in this general process. For example, some of the z/OS

preallocation of data sets can be skipped if your ftp supports site and locsite

subcommands. While perhaps a bit longer than absolutely necessary, we think the process

shown here should work in almost any situation. With minor changes it can be used in the

other direction, to copy a volume from a non-zPDT machine to z/OS on zPDT.

This process can be used to port an older version of z/OS from a non-1090 system to a 1090.

3.8.4 Standalone restore

This section describes a method of porting a single z/OS volume from an external system

than can create awstape volumes

to a 1090 environment that has no System z software

installed. The single z/OS volume used in this example is the one-volume z/OS system that is

distributed with the AD package. Although the process we describe here is not required for

This could be a system with native awstape capabilities, or a system with an informal utility program to convert a

sequential file (the dump data set) into awstape format. Such informal utilities are not part of the 1090 package.