Welllllll...it's doing a 3270 write, is the point. You have up to one 3270 screen at a time: it's not going to be something that can run as a background process without a pretty big architectural change, one that will break it for every emulator until they catch up. So where's the win there? "Just use FTP." In fact, if I were still an emulator vendor and this change did happen, I would probably look into supporting FTP before I'd change my IND$FILE support.
Anyone remember where the IND$FILE protocol was documented? I do... -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Charles Mills Sent: Wednesday, September 25, 2024 4:57 PM To: [email protected] Subject: Re: Mainframe FTP status That was true once upon a time but has not been true since about 1995. IND$FILE uses a 3270 sub-protocol called "structured fields" and can transfer up to 32K of binary data in a block. It's still single-task and half-duplex, and layered into TSO, all of which makes it a lot slower than FTP, but it is NOT 3270 screen oriented. Charles On Wed, 25 Sep 2024 15:30:50 -0400, David Spiegel <[email protected]> wrote: >Hi Gil, >If IND$FILE replaces FTP, it would be slow beyond belief. >The way that IND$FILE works is that it reads a screenfull (24*80=1920 >Bytes) at a time and deals with the this buffer. >I cannot imagine the time it would take to Upload/Download a large TRS >Dataset. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
