RE: List Spooled File API SLOW (again)

Have they done a RCLSPLSTG lately?  They may have thousands of deleted
spool files taking up index space that the API has to skip through?
Just a shot in the dark. 


Christopher Bipes
Information Services Director
CrossCheck, Inc.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Brad Stone
Sent: Thursday, May 25, 2006 7:59 AM
To: Midrange Systems Technical Discussion
Subject: List Spooled File API SLOW (again)

I posted a while back about this and got a few ideas.

The PTFs listed at
http://www-912.ibm.com/n_dir/nas4apar.nsf/ALLAPARS/SE24829
were applied, but no help.

A recap, the QGYOLSPL API is being used and on 2 systems (out of a few
thousand) they are seeing that the first time the command is run to list
spooled files (using just an output queue as a filter) takes anywhere
from 15-30 minutes, no matter if there are zero, 16, or 100 spooled
files in the list.

I can't get it to happen on my V5R2 machine, or any of the
V5R3 machines I have access too.

Once it's been run once, after that it's normal speed, so to me it seems
like it has something to do with the QGYSERVER job that is started when
this API is used.  I would think that the same issue would be popping up
with OpsNav as it uses the same API (I assume it does, since it also
starts the QGYSERVER job when listing spooled files).

Any ideas?  Anyone else seeing this issue?