Re: FTP changes the record format name

TA

Does the PF exist already on the target system with the correct format name? I suspect not.

Look at the destination files - I suspect they all have 1 field, while the sources may have several.

This is because when you FTP something to a PF that does not yet exist, that PF gets created as a flat file.

So either pre=create that file, or do as Rob suggests and use the SAVF method - and in that, be sure to use SAVF as the extension on the source file (assuming use of NAMEFMT 1).

You COULD have a script that sends the DDS over, then runs a command to create the file, then send the contents as BIN. All this can be done with FTP.

HTH
Vern

On 10/20/2017 9:00 AM, T. Adair wrote:

When I FTP a PF from one System i to another, FTP will preserve the filename and member name, but it (apparently always) changes the record format name from whatever it was to the same as the filename.

Example:
PUT DS_DATA/DS_PRDXF.DS_PRDXF  DS_DATA/DS_PRDXF.DS_PRDXF

This successfully puts the DS_PRDXF file in the DS_DATA library on the source system, into the same file/library on the target system.

So far, so good.  The problem is that the record format name on the source system is DSPRDXFR, but FTP changes it to DS_PRDXF (same as the filename) on the target system.

Why?

This file needs to be FTPed to multiple libraries on multiple systems. I do not relish the thought of having to transfer the DDL source member to each system, and then manually create the file in each library on every system.

Is there an FTP setting to prevent this behavior?  I've searched the archives, and I've Gaagled it, without success.  Does FTP simply not ignore the record format name, and assign a default?

FTPing to the same library name (on a remote system) or to a different library name makes no difference.  Same result.

All our systems are on 7.2.

As always, any guidance would be greatly appreciated.

~TA~