Pushing data with FTP - syncsort_capacity_management - 12 - 12.40

Syncsort Capacity Management Installation Guide

Product type
Software
Portfolio
Integrate
Product family
Syncsort
Product
Syncsort Capacity Management
Version
12.40
Language
English
Product name
Syncsort Capacity Management
Title
Syncsort Capacity Management Installation Guide
Topic type
How Do I
Copyright
2023
First publish date
1985
If you will use FTP to copy data from the mainframe to a Windows system where Control Center can then collect the data, or perhaps directly to its Work area, you can use the PUSHFTP= control card to generate commands for FTP to copy a z/OS dataset and give it a name Control Center will recognize.
  • 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:

USSPATH

PUSHFTP

Result

(not present)

N

Data only written to //ATHDATA file, no FTP commands generated

(not present)

Y

“put” and “rename” commands written for //ATHDATA file, using the z/OS dataset name for input and a file name with the target number in if only one system is present, or MULTIZOS if more than one system’s data is processed

(not present)

M

“put” and “rename” commands written for //ATHDATA file, using the MULTIZOS option even if only one system’s data is processed

(not present)

D

“put” and “rename” commands written for //ATHDATA file, using the FTP //DD: option, for example:

put //DD:ATHDATA +20090929000000_aszs00010000.1010

The purpose of this is to allow users who write Acquire output to tape to retain the volume on a drive instead of having z/OS dis­mount it and then have to remount it to be used by FTP.

(not present)

B

Combine PUSHFTP=D and PUSHFTP=M - use the //DD: option and create a MULTIZOS output file name

(not present)

G

“put” and “rename” commands written for //ATHDATA file, using the z/OS dataset name for input and a file name with the target number in when only one system is present. Prefix the final file name with a letter “G” to indicate that Syncsort Capacity Management Gatekeeping is requested

<value>

N

Data written to both //ATHDATA and USS, no FTP commands generated

<value>

Y

“put” and “rename” commands written for each USS file