I think that it is to provide support for "shared" storage between the
FTP client exits that are new with z/OS V2, EZAFCCMD and EZAFCREP.
There is a sample member in TCPIP.SEZAINST named EZAFCEXT. The sample
exit talks about "Persistent session data in shared storage". This storage is
shared between the command exit and the reply exit. There are more details in
the sample!!!
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf
Of Tom Brennan
Sent: Wednesday, October 05, 2016 5:43 PM
To: [email protected]
Subject: Re: ftp name/token.
Just some wild guesses: If we can assume the token is to provide a common spot
for multiple tasks or address spaces, then I'm trying to think why FTP would
need more than one TCB or ASCB. I know that an FTP transfer has two TCPIP
connections - one for the text commands and another for the actual data. And
multiple TCPIP connections are often coded in separate tasks so each can wait
to receive input without blocking other processing.
Itschak Mugzach wrote:
> Each time I start ftp, a new name-token pair is created. The name is
> EZAFTPnnnn. the numeric part is changed on each iteration. I am trying
> to understand the purpose of this name-token pair and it seems to be
> undocumented. Any idea?
>
> Best,
> ITschak
>
> ----------------------------------------------------------------------
> 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
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
