Assuming I remember correctly, you started FTP by selecting a menu
option which opened a separate window. That window handled the transfer
and the resulting status. TSO was not informed of this action and
remained at READY. And since TSO never knew you were running the FTP,
there was no reason to lock up the TSO terminal (i.e. X-SYSTEM). Now,
someone could say locking your keyboard prevents you from, say, doing
updates to the same dataset you're running FTP against. I would expect
normal enqueues to prevent that instead of locking you out of the entire
TSO session. Note this was late 1990's and Attachmate is apparently
different now.
IND$FILE of course locks up the TSO terminal because it's a command and
commands lock you up until they complete. So my only explanation for
Attachmate's action at the time was to make FTP act more like IND$FILE
which people were already familiar with... doing a large transfer? Go
get some coffee.
On 6/10/2022 11:50 AM, Paul Gilmartin wrote:
On Fri, 10 Jun 2022 08:39:31 -0700, Tom Brennan wrote:
And I remember working with an Attachmate TN3270 emulator in the late
1990's which would (for no technical reason) lock up your TSO session
while doing an FTP transfer.
How could it have reported status or completion if it transferred concurrently?
Did it likewise, (for no technical reason) lock up your TSO session during
an IND$FILE transfer?
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
