An MFT system should handle this (Managed File Transfer). It
should have auto recovery where the system that started this
transfer has a restart after some time period, so that the
transfer can be completed. This should be especially true if only
part of the file was transferred. Then that system should have
check-point records that it checks out so that if the xfer were
interrupted, it can restart and not have to start over.
Hmmmmm. I think I was a developer for such a system. NDM, renamed
to Connect:Direct. And it handled GDGs so that you didn't get
multiple generations of the file.
Just say'n'
Steve Thompson
On 5/8/2025 8:52 PM, Paul Gilmartin wrote:
On Tue, 6 May 2025 11:29:33 -0500, Peter Vander Woude wrote:
We have a file transfer tool, that is used to send data to z/OS, however if the
dataset is a gdg, and there is a disp=old on the gdg, the dynamic allocation
fails and the transfer job also fails.
Transfer to a z/OS UNIX file or an intermediate data set which will have
no ENQ entanglement, then submit a batch job to copy to the target GDG.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
