If you specify PUSHFTP=N (the default), and:
If you also provide the USSPATH= control card, it means that files are to be written to USS and probably collected directly by Control Center.
If you do not specify USSPATH=, it means that you will plan to copy the data written to the //ATHDATA file to the Control Center machine some other way(e.g., manually).
- If you specify PUSHFTP=Y or M or D or B, then FTP commands are generated to file //PUSHFTP to assist the “pushing” of the data.
Important! Acquire does not perform the file pushing itself. The commands in the //PUSHFTP file should be concatenated into an FTP step or job behind other parameters that define the user id, password and directories to be used. These other parameters are solely the responsibility of the user to set up correctly.
No matter where data has been written (//ATHDATA or USS), the names of files used are placed into the series of “put” and “rename” commands. The effect of this is to allow the data file(s) to be copied off the mainframe and then renamed to meet naming conventions while avoiding the attempted processing of partial files.
If you want to adopt this style of automated data transfer via FTP, then you will need access to a machine hosting an FTP server. If you implement an FTP server on the Control Center machine, you can define a share to the location where the data will end up and instruct Control Center to use that.
If you use an FTP server on another machine, you can set up Control Center to retrieve the data from there using the Windows FTP client as if it were a normal “pull” connection. The following table summarizes the effect of the valid combinations of USSPATH and PUSHFTP parameters:
|