How does FTP determine it needs to spawn additional server address spaces, and is there any way to limit that expansion aside from the maximum number of address spaces applicable to all users? Is there any way to automate the termination of those address spaces besides job wait time? Our situation is that a flurry of clients connect to the FTP server at about the same time. FTPD1 spawns upwards of 25 BPXAS address spaces (BPXP024I BPXAS INITIATOR STARTED ON BEHALF OF JOB FTPD1) within a matter of a few seconds. Sometimes this number may be much higher. There seems to be no control over the spawned address spaces. They simply stick around until they reach the SMF-defined JWT, then they go away. Occasionally the added address spaces result in IEA602I ADDRESS SPACE CREATE FAILED. MAXUSERS WOULD HAVE BEEN EXCEEDED. None of the FTP configuration options seem to apply, since the waiting address spaces have no active connections. Any suggestions besides just increasing max address spaces and hoping I don't reach the new limit?
---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
