Thanks - I am tracking both of these APARs now, and while I did not go back an
look at what the last message was from ADSM prior to the server going to
sleep, I can see how PN78168 could be the cause.

Understanding how we might not be using the storage pool as intended, we could
be satisfied with some warning messages rather than a design change if the
scope of the change was significant enough that the change would be delayed
until some future date.

Also, if you have a different approach to handling the problem of tapes with
low access rates, and how we should manage them within an automated library, I
would be interested in hearing them.

Thanks for your assistance.

Jerry Lawson
jlawson AT itthartford DOT com
________________________Forward Header________________________
Author: INTERNET.OWNERAD
Subject: MVS SERVER goes to sleep.....
07-16-96 01:56 PM

Hello Jerry:

I received a note from the developer that is working on the APAR.

Take a look at APAR PN78168. This will address some of the problems we
currently experience related to SYSZTIOT.

For APAR PN84364 he has a plan for a design change so we will not wait
forever for a unit to become available.  No guarantees that the APAR will
result in a code change.  The APAR might be closed with a code change or
it might be closed with a statement to fix it in a future release if there
is a future release.
Regards - David Bohm, ADSM technical support.