ADSM-L

Re: Volhistory errors

1998-07-15 18:49:08
Subject: Re: Volhistory errors
From: "Prather, Wanda" <PrathW1 AT CENTRAL.SSD.JHUAPL DOT EDU>
Date: Wed, 15 Jul 1998 18:49:08 -0400
I can only help with question 1 & 2:

1) There are entries for STGNEW and STGREUSE volumes, as well as STGDELETE.
SO if you aren't deleting those now, that explains why your VOLHISTORY
continues to grow so large.
You only need to keep the entries as long as you keep your oldest DBBACKUP
tapes, so you could just do
>  delete volhistory todate=today-7 type=ALL
and that should reduce your volhistory a lot. .

2) from the admin command line, you can enter:  Q VOLHIST to see all the
contents.


===============================================================
Wanda Prather
Johns Hopkins Applied Physics Lab
443-778-8769
wanda_prather AT jhuapl DOT edu

"Intelligence has much less practical application than you'd think."
              - Scott Adams/Dilbert
===============================================================


> ----------
> From:         Stefan Cina[SMTP:stefan.cina AT zurich DOT com]
> Sent:         Tuesday, July 14, 1998 5:42 PM
> To:   ADSM-L AT vm.marist DOT edu
> Subject:      Volhistory errors
>
> Hallo
>
> We are running ADSM for MVS V3.1.1.3.
> We have problems with the volhistory:
>
> 1) Our volume history file is very large (about 17000 lines, although
>    there are only 3400 tapes). Are the following daily schedules enough
>    to reduce the volhistory file:
>      delete volhistory todate=today-7 type=dbbackup
>      delete volhistory todate=today-3 type=stgdelete
> 2) Are there any administration commands to check/correct the contents
>    of the volhistory?
> 3) Almost every day an ARN9999D error message occurs after processes
>    which write to volhistory (backup volhistory):
>
> Activity log:
> 07/10/1998 08:36:20 ANR0390W A server database deadlock situation has been
>  encountered: lock request for transaction 0:51687958 will be denied to
>  resolve the deadlock.
> 07/10/1998 08:36:20 ANR9999D ICUTIL(1490): Lock acquisition (sLock) failed
>  for icvhVolumeType 4.
>
> 07/10/1998 08:36:20 ANR4513E A database lock conflict was encountered in
> processing sequential volume history information.
>
> 07/10/1998 08:36:20 ANR4510E Server could not write sequential volume
> history
>  information to 'SGSN.ADSM.VOLHIST1.DATA'.
>
>
> Can anybody help us.
>
> Regards
> Stefan Cina
>
>
>
<Prev in Thread] Current Thread [Next in Thread>