What you have said makes sense - Thanks for the assistance, we will watch
those APARs.

FOR EVERYONE ELSE who is still watching this thread:  If you use some sort of
tape automation (be it a silo or an IBM 349x library) how do you handle the
low activity files.  We have elected to allow ADSM tapes to be ejected by the
silo's management routines when the cartridge has not been accessed in a perio
d of time.  The silo routines do this automatically to insure that they have
enough slots for scratch tapes - the time span varies but is usually around 30
days.  Currently 57% of our tapes have not been referenced in the past 30
days.  What do you do with these tapes?

Jerry Lawson
jlawson AT itthartford DOT com
________________________Forward Header________________________
Author: INTERNET.OWNERAD
Subject: MVS SERVER goes to sleep.....
07-17-96 12:55 AM

Jerry -

Actually a message is part of the design change.  The ADSM server runs
as multiple threads.  The thread that is waiting for a device to become
available is waiting in allocation code in the system not in ADSM.  The
change we are looking at making is to not tell the allocation request to
wait until a device becomes available.  This way we can control a number
of retries at certain intervals and issue a message after some time of
trying to perform the allocation but failing.

At this time once we issue that dynamic allocation request in that thread
it does not get control back to issue a message until the tape drive is
available.  It would be just as much of a change to have another thread
watch for a timeout on this thread as it would be to make the change to
not wait for the device to become available.

For the approach of handling tapes with low access in an automated library
I would have to think about that for a while.  The only ideas I can come up
with offhand would require some design changes to ADSM.  Maybe some other
people on this forum have ideas for how they handle this.

David Bohm, ADSM technical support.