ADSM-L

Re: MVS Server - Expiration/Reclaim

1999-10-01 09:58:41
Subject: Re: MVS Server - Expiration/Reclaim
From: Brian Nick <BRIAN_NICK AT PHL DOT COM>
Date: Fri, 1 Oct 1999 09:58:41 -0400
Ginny,

   I am aware of the APAR that you mentioned. As a rule, and as far back as ADSM
server version 2, we do not run these types of tasks concurrently. We avoid this
due to data base contention and performance. As I said earlier we have not had
any problems with the 3.1.2.40 version of the ADSM server, no crashes, hangs
etc. Our expiration processing issue has been corrected and we have not noticed
a significant increase in the length of time that expiration runs. Last I knew
there were still issues with 3.1.2.20 which is why we avoided upgrading to that
release and opted for 3.1.2.40. Before upgrading to any release of ADSM each
individual must research and decide for themselves the path that they take.
JMHO.

Brian





Virginia Hysock <vhysock AT CSC DOT COM> on 10/01/99 08:26:40 AM

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To:   ADSM-L AT VM.MARIST DOT EDU
cc:    (bcc: BRIAN NICK/Phoenix Home Life Mutual Insurance)
bcc:  BRIAN NICK/Phoenix Home Life Mutual Insurance
Subject:  MVS Server - Expiration/Reclaim




Steve and Brian,

     Is it really true that you are not having a problem with the OS/390 Server
at 3.1.2.40 - Brian?  I was just checking APARs on it yesterday, and it seems
there is still no fix for the problem of crashing your server if running delete
functions at the same time as a move function (i.e. running expiration and
reclamation concurrently or migration and delete filespace, etc.).  Now, I'll
grant you, it's best not to do these activities concurrently anyway - but with a
very busy server, they sometimes overlap each other in the schedule.  I don't
want to deal with server crashes if I don't have to.

     As for me - Steve - I've stuck at 3.1.2.20 of the MVS server for now, until
they can clean up the code for level 40.

                         Ginny



Date:    Thu, 30 Sep 1999 11:18:51 -0400
From:    Brian Nick <BRIAN_NICK AT PHL DOT COM>
Subject: Re: MVS Server - Expiration/Reclaim
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii


Steve,

   Yup you are havin expiration problems. We had the same problems under
3.1.2.0. We have gone to the latest release of the ADSM server 3.1.2.40 and the
problem appears to have been resolved. Don't know how you feel about this new
release but we haven't had anyu problem for the last month and a half. We are
also OS/390 2.5. So far so good. If you would like more info you can e-mail me
directly at Brian_Nick AT phl DOT com. Hope this helps.

Brian.




Steve Fletcher <sfletcher AT GIANTOFMARYLAND DOT COM> on 09/30/99 11:07:31 AM

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To:   ADSM-L AT VM.MARIST DOT EDU
cc:    (bcc: BRIAN NICK/Phoenix Home Life Mutual Insurance)
bcc:  BRIAN NICK/Phoenix Home Life Mutual Insurance
Subject:  MVS Server - Expiration/Reclaim




Greetings all!
I recently upgraded from ADSMv2/MVS to v3.1.1.3.  This release had problems with
memory and CPU utilization so, the MVS guy applied his latest PTF's to the
system which brought ADSM to 3.1.2.0.  This corrected the memory/CPU problem but
now I believe I have a problem with expiration.  For example, yesterday reclaim
ran against offsite pool, then early this morning expiration ran deleting about
30k of backup objects.  This morning I checked the offsite tapepool and there
are no tapes to be reclaimed.  This is the first time this has happened in two
years of running ADSM.

My questions are:

1) Has anyone else experienced similar problem with 3.1.2.0 on OS/390?
2) To what STABLE release do I upgrade to correct this problem?
3) Are there any temporary steps I can take to get rid of the old stuff before I
upgrade to the release identified in question 2?

As an FYI, I have spent the passed few days searching the list archives and have
not seen anything definitive except for a message last January about there being
a bug in this release of which IBM was aware.

The specs on the environment are:
OS/390v2.5   ADSM v3.1.2.0

Thanks in advance for the help!
<Prev in Thread] Current Thread [Next in Thread>