Even large shops who are relatively up-to-date in z/OS release level have not made z/OSMF available to application teams in any form. Most are limiting that access to systems teams and even they don’t much like it from the posts I have seen on this list.
There have to be less intrusive / complex-to-implement--shop-wide alternatives, and an updated or open-sourced IND$FILE would provide one such. ISV's are a different kind of organization from shops that use their software, and are pushed much harder by IBM changes to adopt the latest whiz-bangs or risk being left behind. Application shops are far more conservative and even backwards in adopting them. It isn’t the right way, but it is a fact of application life. I do have FTP to and from my employer's systems, but not every application shop allows that. Peter -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Andrew Rowley Sent: Sunday, March 28, 2021 7:47 PM To: [email protected] Subject: Re: IND$FILE and zFS? 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. -- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
