ADSM-L

Bad Performace for deleting Volumes

1998-08-12 08:41:20
Subject: Bad Performace for deleting Volumes
From: buser andreas <andreas.buser AT BASLER DOT CH>
Date: Wed, 12 Aug 1998 08:41:20 -0400
We recently throw away all data on COPYPOOL where all volumes (about
1000) were offsite. After deletion of the data with discard=yes I run an

UPDATE VOLUME * ACCESS=READWRITE WHERESTGPPPL=COPYPOOLName

After about 50 to 100 Volumes this request got slower and slower. I
wanted to cancel the session, but this did not work. I had to shutdown
ADSM.

If I do the same update for every single volume in tha pool with:

UPDATE VOLUME volname ACCESS=READWRITE WHERESTGPPPL=COPYPOOLName

this works well. But this is not the way we want to proceed in
generatingtmonsterlists of cmds, if we could have it in one simple cmd.

We are runnning ADSM MVS 3.1.1.3 on OS/390 2.4 on IBM9672 R54.

Why is there such a difference in this procedure?

Does anyone have same expiriences?

Kind regards
Andreas Buser

Tel:   ++41 61 285 73 21
Fax   ++41 61 285 70 70
mail: Andreas.Buser AT Basler DOT ch

Address:
Basler Versicherungsgesellschaft
Andreas Buser
Abt. Informatik
Aeschengraben 21
4002 Basel
Switzerland
<Prev in Thread] Current Thread [Next in Thread>
  • Bad Performace for deleting Volumes, buser andreas <=