This is the same road we traversed a few years back when RECEIVE FROM NETWORK stopped working with vanilla FTP. We are not technically capable of running FTPS directly from z/OS to IBM because we depend on an appliance (BlueCoat) to 'punch through' the standard firewall. BlueCoat does not--and I'm told never will--support TLS syntax.
Fortunately HTTPS was made available for RFN, so we've maintained business as usual. I see no mention of HTTPS in the current change. This looks like a road with No Outlet. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW [email protected] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Pew, Curtis G Sent: Wednesday, May 23, 2018 9:57 AM To: [email protected] Subject: (External):Re: File transfer Red Alert On May 23, 2018, at 10:07 AM, Paul Gilmartin <[email protected]> wrote: > > Why didn't the supplier, as a courtesy to the customer, deliver the > file with the needed extension and save that step? This is just a guess, but maybe some firewalls or other policy enforcing software block .jar files but allow .zip files. If you have a Java VM on your system, .jar files contain executable code and in some circumstances might be executed inadvertently. -- Pew, Curtis G [email protected] ITS Systems/Core/Administrative Services ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
