On 29/03/2021 10:09 am, Radoslaw Skorupka wrote:
However everytime someone ask about IND$FILE of transfer of 600 files we see "FTP is NOT an option". Why? Well, there are reasons. Maybe not reasonable, but there are. Last, but not least: still unsolved! So still we will observe such questions and problems.
I understand there are sites that prohibit FTP. I am sure it is less common to prohibit HTTPS. There may be sites that don't allow file transfers to/from the mainframe - but I doubt IBM wants to enhance IND$FILE to help people circumvent site policy on file transfers.
zOSMF? I'm sorry, but I bet it is less common than FTP. And as far as I can guess it cannot be automated like FTP (read: batch). And of course one size does not fit all. Some would need compression of transmitted data (what bandwidth do you have?), some would prefer IND$FILE and some just FTP or FTPS or SFTP.
IBM obviously intends that z/OSMF will be used everywhere as a required component of z/OS.
I have automated both z/OSMF and FTP and I would say z/OSMF is far easier. It can be done from any language that can make HTTPS requests i.e. you can start with curl. The REST APIs are probably the best and most useful feature of z/OSMF.
Compression is not required, but it is an option selectable using the Accept-Encoding: gzip header, i.e. a standard feature supported by most clients.
I see nothing wrong with using FTP etc. But if you need new features they might already be there in z/OSMF, and there is pretty much zero chance they will be added to IND$FILE.
-- Andrew Rowley Black Hill Software ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
