CICS Transaction Gateway V5 The WebSphere ... - IBM Redbooks

Example 7-1 Using FTP to send the z/OS gateway to the /tmp= directory
C:\>ftp wtsc66oe.itso.ibm.com
Connected to wtsc66oe.itso.ibm.com.
220-FTPDOE1 IBM FTP CS V1R2 at wtsc66oe.itso.ibm.com, 18:50:46 on 2002-06-13.
220 Connection will not timeout.
User (wtsc66oe.itso.ibm.com:(none)): cicsrs2
331 Send password please.
Password:
230 CICSRS2 is logged on. Working directory is "/u/cicsrs2".
ftp> cd /tmp
250 HFS directory /tmp is the current working directory
ftp> lcd d:\gateways\os390
Local directory now D:\gateways\OS390.
ftp> bin
200 Representation type is Image
ftp> put ctg-500m.tar.Z
200 Port request OK.
125 Storing data set /tmp/ctg-500m.tar.Z
250 Transfer completed successfully.
ftp: 21256941 bytes sent in 60.14Seconds 353.48Kbytes/sec.
ftp> quit
221 Quit command received. Goodbye.
Tip: If you only have an MVS FTP server, you can FTP the CICS TG tar file to
an MVS data set name using a binary transfer. The record format of the MVS
data set is not important, but it should be allocated with at least 30 cylinders.
Once the CICS TG compressed file is in an MVS data set, you can move it
over to UNIX System Services using one of the following methods:
Using ISHELL Use File -> New and File -> Replace From
Using UNIX System Services Use the command tso oget
Using TSO Use the command TSO OPUT
Using batch TSO Use OPUT
Again, regardless of which method you use, you should specify binary format.
Once the CICS TG install archive was in the UNIX System Services /tmp
directory, we created an environment where we could install the CICS TG for
z/OS. Many of these tasks can also be performed by running the JCL found in
/usr/lpp/ctg500/ctg/samples/jcl. The file /usr/lpp/ctg500/ctg/samples/samples.txt
explains the members in this directory.
Chapter 7. TCP connections to the Gateway daemon on z/OS 137