Been there! There is a USS system parameter which controls the maximum number of USS processes a single user can have running concurrently. If the FTP process is forked by parent process FTPD (the FTP daemon) with UID(0), and an explicit UID is not defined, it is assigned a default UID and is not subjected to the per-user concurrency limit. Because a USS process is instantiated as an MVS task, increasing the system limit would involve raising the maximum number of address spaces allowed on the MVS image.
We fixed the problem by assigning an explicit user ID to the FTP task so its maximum concurrency would be limited on a per-user basis by the MAXPROCUSER setting in BPXPRM00. All that was required was to define an OMVS segment with a unique ID in RACF. db -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Martin Kline Sent: Wednesday, September 29, 2010 9:36 AM To: [email protected] Subject: FTP and BPXAS address space spawning 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 ---------------------------------------------------------------------- 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
