Sometimes all that's allowed, though. Some of my clients lock up FTP, and make me use IND$FILE via whatever local 3270 emulation they use.
This can be a major pain. Whenever I start at a new installation, one of my first jobs is to load up a bunch of REXX tools I've written over the years. If I have to do them one at a time, it's a big bottleneck. Most apps of that sort allow you to set up a list of files - but you have to enter the list manually, one by one, providing the filename on your PC and the target DSN on the mainframe, so it's not saving anything (and is a one-time job, after all). Last time I had to deal with it I reverse-engineered the format used for multi-file transfers and had VBA create a longer list for me. I felt a fine, self-congratulatory glow at having hacked the system, but really, it shouldn't have been necessary. --- Bob Bridges, robhbrid...@gmail.com, cell 336 382-7313 /* Cats consent to love us. Dogs beg to love us. -Cathryn Michon, Grrl Genius */ -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Charles Mills Sent: Wednesday, June 17, 2020 23:39 Also slower than a dog, and if you are working for the security folks, basically unaudited. -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of David Spiegel Sent: Wednesday, June 17, 2020 7:05 PM I have painfully experienced instances where IND$FILE (on z/VM) mangled a Binary Upload from my MS-Windows 10 Pro workstation. It works every time I use FTP, though (via CLI or WinSCP). ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
