Improving System Performance During Heavy FTP Usage

Answer

Use the Dynamic LPA feature of z/OS to load a copy of the modules into common storage.

Advantages:

• Reduced demand on system storage resources during periods having higher volumes of FTP connections. This includes:

• Auxiliary (AUX) storage
• Paging rates
• Real storage
• Reduction in CPU usage and FTP response delays, since the associated program code does not have to be copied into new address spaces.

• Page frames for code associated with low use features (such as FTP use of JES spool access, SQL queries, or Unix Pipes) will tend to stay paged out.

• Under certain system configurations, this can also reduce I/O to the DASD volume containing the SEZALOAD data set.

• You will need 2.0M of ECSA for the two server modules, plus another 1.7M for the client (figures based on z/OS 2.2 module sizes). You may have to increase the size of ECSA specified on the CSA statement in the IEASYSxx PARMLIB member to accommodate the increased demand.

• If any maintenance is applied (without an IPL), remember to also load the new copy into ECSA (and remove the old after address spaces using these modules terminate).

• Benefits will not be significant on systems with low volumes of FTP usage.

Use the following SETPROG LPA,ADD commands to add the FTP modules to Dynamic LPA. You can add these to the COMMNDxx PARMLIB member so that it is performed automatically at IPL.

FTP Server:
     SETPROG LPA,ADD,MODNAME=(EZAFTPLD,FTPD),DSNAME=LNKLST
     SETPROG LPA,ADD,MODNAME=(EZAFTPLS,FTPDNS),DSNAME=LNKLST


FTP Client:


     SETPROG LPA,ADD,MODNAME=(EZAFTPLC,FTP),DSNAME=LNKLST


Notes:

• The DSNAME specification assumes that the SEZALOAD data set is in the Linklist.

• You can also specify the PAGEPROTPAGE keyword to provide a minor reduction in the ECSA storage used. If specified, this can leave a portion of the modules unprotected.