We had z/OS 1.13 HSM abend S878-10 at 1am Monday.  IBM tracked down an
open APAR.  It allocates a small amount of space for each volser
during migration.  Forgets to free the memory, and eventually chews up
all private memory below the 24 bit line in SYSHSM*.  It was opened in
Sept, Should be out by the end of the year.

Local fix is to bound HSM periodically (weekly/monthly).  We were up
on a busy LPAR for 2 months before it crashed.

On Wed, Oct 17, 2012 at 5:02 PM, Munish Sharma <[email protected]> wrote:
> We had an issue on one system wherein hsm cds backups were failing on LPAR1 
> with RC=12 and REAS=08. The jrnl backups were going fine.
>
> When browsing through the activity logs, I came across the following:
>
> ADR376E (ttt)-mmmmm(yy), UNABLE TO ACQUIRE ADDITIONAL STORAGE FOR THE TASK
>
> Since dfdss tries a concurrent backup of all 3 cds' to tape, I think it is 
> facing a memory issue. But since journal is not included in this concurrency, 
> it  always goes fine. Also, situation is compounded for hsm since mcds is 
> multi-cluster. So it requires the more memory.
>
> But the backup on LPAR2 was running fine. So I think it comes down to the 
> region size on both tasks. LPAR1 has 8M but LPAR2 has 0M. Therefore I guess 
> LPAR2 has the capability to scale up the region size required by dfdss.
>
> Shall we try modifying the REGION parm for LPAR1 and test the backvolcds 
> command
>
> OR As earlier suggested the << Use the DSSXMMODE(?) SETSYS parm to run DSS in 
> its own cross-memory address space>> ..clearly in this case as well... It's 
> happening as too many DFDSS tasks are running in HSM., to backup the multiple 
> CDS's
>
> Regards
> Munish Sharma
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO IBM-MAIN



-- 
Mike A Schwab, Springfield IL USA
Where do Forest Rangers go to get away from it all?

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to