Re: FTP question

Reeve

If this gets to you, check your junk mail mailbox - or check quarantined email.

As for the length of parts of a multi-format - I don't think the formats are separably sendable - only the original PF, as Scott said. There is, e.g., a maximum record length attribute on these things - that is probably the length in use - and that makes sense. You cannot specify a certain format on an FTP put subcommand.

So thus comes the choice - either create a SAVF and send IT, reconstructing as needed on the remote system. Or send from the PF.

If the other system is NOT an i - you have only the 2nd choice - SAVF does you no good.

HTH
Vern
-------------- Original message --------------
From: Richard Reeve <richreeve@xxxxxxxxx>

Scott,

Unfortunately, I am not seeing responses from anyone except you.


Several people on this mailing list have suggested using a save file.
Have you tried that suggestion, and did it help you? Or does it cause
some problems that you'd like to avoid, and if so, what are they?

-The save file option doesn't work in this case because I am not
sending this file to another AS/400 so I must sent the file itself

For my part, I'm not exactly sure what you mean by a "multi record
format file". Are you referring to a logical file that's build over
multiple physical files? i.e. a multi-format logical file? If so, I
would suggest that you FTP the physical files (not the logical file) to
the other system, and then re-build the LF on that side.

-The file is a set of transactions, some (most) of which have
different formats (and lengths).

If you FTP the LF, it'll create a PF on the remote side of the
connection, and put all of the records from the LF into that PF. So
you'll have many files on the source system, and just one on the target
system... Which isn't what you want.

-correct

Thanks for your help.......I really need it!!

Rich


Richard Reeve wrote:

I am ftping a multi (record) format file to a client that is translating to an

edi transaction. The reciever needs each record to be sent in the length
defined in the program for each record format. For example,

If record a is defined as 100 positions, then the
ftp'ed record should be 100 positions

If the record is defined as 50 positions, then the
ftp'ed record should be 50.....and so on.

It appears that the ftp'd file record length is adopting the length of

the longest record format regardless of which record format is sent. Is there
any way that I can FTP this file and have it contain the proper record lengths
(the ones that I used when creating the file) of each record type rather than
sending each in the longest length?

Warmest Regards,

Richard Reeve

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.