ADSM-L

FW: Primary disc stgpool full at 9 % but msg ANR0522W got!

1998-05-11 08:27:15
Subject: FW: Primary disc stgpool full at 9 % but msg ANR0522W got!
From: "Lambelet,Rene,VEVEY,FC-SIL/INF." <Rene.Lambelet AT NESTLE DOT COM>
Date: Mon, 11 May 1998 14:27:15 +0200
>Thanks Virginia,
>
>we have only 2 volumes and we also applied the corrective maintenance given
>is the following APAR.
>
>Regards,
>
>Rene
>
>APAR NUMBER: PQ10364            RESOLVED AS: PROGRAM ERROR
>
>ABSTRACT:
>PQ10364: ADSM ONLY ATTEMPTS TWO SUCCESSIVE WRITE ATTEMPTS AGAINST FILLING
>VOLUMES THEN FAILS WITH ANR0522W ERROR MESSAGE.
>
>ORIGINATING DETAILS:
>ADSM will only attempt writing to two filling, but nearly full,
>volumes before aborting the backup with an ANR0522W ... no space
>available ...  error message.
>
>
>APAR INFORMATION:
>Reported to correct a PTF in error:     NO
>Reported as a highly pervasive problem: NO
>
>PE Apar?:       NoPE
>HIPER Apar?:    NoHIPER
>Status:         CLOSED  PER
>Component Name: ADSM MVS/VM SRV
>Version:        310
>Component ID:   565511901
>Submitted:      97/11/11
>Closed:         97/11/11
>Last Modified:  98/05/04
>ChangeTeam:     TU0290
>
>FIX INFORMATION:
>Reported release thought to contain the error: R310
>Release change team expects the fix to be included in: F310
>
>APAR is fixed by one or more of the following PTFs:
>
>UQ16498  UQ16499  UQ16502  UQ16503
>
>Applicable Component Levels:
>
>R310 PSY UQ16502 UP98/04/20 P      F804
>
>-----Original Message-----
>From:  Virginia Hysock [SMTP:Virginia_L_Hysock AT CSC DOT COM]
>Sent:  Monday, May 11, 1998 2:10 PM
>To:    ADSM-L AT VM.MARIST DOT EDU
>Subject:       Re: Primary disc stgpool full at 9 % but msg ANR0522W got!
>
>     Apar PQ09463 covers a similar problem.  I had opened an ETR with IBM on
>receiving the ANR0522W Out of Space condition for writing to a tape storage
>pool -
>that had PLENTY of scratch tapes available, I might add.  They lumped my
>problem
>in with PQ09463 (which might be fixed at this point).  IBM stated that when
>the
>server is trying to write a transaction, it will try two volumes only - and
>if
>unsuccessful in finding space in those two volumes will fail with the out of
>space
>condition.
>
>     Is your disk pool split into numerous individual 'volumes'?  Is it
>possible
>that some of those volumes are nearly full, but the disk pool as a whole is
>only
>9% allocated?
>
>                         Ginny