Specifications

Chapter 3. z/OS notes 33
handled by ftp. The x.y positional operand is needed in xmit, but is meaningless in this
example. Note that the terse program could be used instead of xmit.
It is important to understand the reason for the xmit step. In the general case, ftp does not
understand the block and record structure of a z/OS file (such as the ADRDSSU output file).
This information is lost during ftp and the resulting file is not usable. The xmit program
changes the ADRDSSU dump file into a fixed block/fixed record format. The general ftp
process does not understand this either. However, if the ftp’ed file is stored in the receiving
z/OS with the same fixed block/LRECL size, the file is usable.
Some ftp situations allow additional parameters such that the original block/record
characteristics of a file are retained and the xmit step could be skipped. This can be done in a
z/OS to z/OS ftp transfer. The method presented in this section assumes the more general
case in which the ftp transfer does not retain the original block/record information.
3.8.2 Send dump to Linux
We then sent the xmit-formatted dump to Linux, using an ftp connection from Linux to z/OS.
We used the zPDT tunnel facility for the connection in our example, but any TCP/IP
connection to z/OS could be used. The IP address for z/OS is 10.1.1.2 in this example:
$ 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> get 'xmit.dump'
ftp> bye
This example has the ftp connection initiated from the Linux side. It could be done from the
z/OS side, provided the Linux system has an ftp server running.
The dump is now in /tmp/xmit.dump as a normal (large) Linux file. It can be transmitted
elsewhere using any technique suitable for a large Linux file. It could be compressed (using
gzip, for example.) At this point the dump (OGDEN.OUT.DUMP) and the reformatted dump
(OGDEN.XMIT.DUMP) on the source z/OS system can be deleted if disk space is a concern.
You can skip this intermediate Linux step if there is a direct ftp connection between the source
z/OS system and the target z/OS system.
3.8.3 Receive dump
There are fewer complications if two data sets are preallocated on the receiving z/OS system.
One data set is the target of an ftp transfer from Linux (or some other source) and the other is
for the output of the TSO RECEIVE function. This last data set is then the input to a
RESTORE job.
//BILL678 JOB 1,OGDEN,MSGCLASS=X
// PGM=IEFBR14
//D1 DD UNIT=3390,VOL=SER=TEMP01,DISP=(NEW,CATLG),
// SPACE=(CYL,(200,200)),DSN=OGDEN.XMITR.DUMP,
// DCB=(LRECL=80,RECFM=FB,BLKSIZE=3120)
//D2 DD UNIT=3390,VOL=SER=TEMP02,DISP=(NEW,CATLG),
// SPACE=(CYL,(200,200)),DSN=OGDEN.UNXMIT.DUMP