I have just noticed that many LISTSERV functions will perform much better
if you add SET RELPAGE OFF to LISTSERV's profile. For instance, a refresh
of the LISTS database takes 24.8 seconds of VCPU on SEARN with the normal
RELPAGE ON setting and 19.8 (20% off) with RELPAGE OFF. The only drawback
is that, if LISTSERV needs a lot of storage to perform a certain function
and then  releases it,  it will not  notify CP that  the contents  of the
pages are no longer important. This forces  CP to keep page slots on DASD
for the  corresponding virtual memory  locations, and it may  take longer
for the real memory frames to be reallocated to another user since CP has
to assume  they are still needed  until they have been  unreferenced long
enough. The paging DASD allocation issue is negligible on anything bigger
than a  9370 with 5  users whereas the  recycling time problem  will only
impact small to medium page-bound systems  (on a large system LISTSERV is
just a  user among a thousand  and it doesn't make  any difference). This
command will be included in the startup code in the next release.
 
  Eric