...@ntlworld.com
To: IBM-MAIN@listserv.ua.edu,
Date: 10/18/2012 08:28 AM
Subject:Re: DFSMShsm Abend S878
Sent by:IBM Mainframe Discussion List IBM-MAIN@listserv.ua.edu
On Wednesday, 17 October 2012 23:02:49 UTC+1, Munish Sharma wrote:
We had an issue on one system wherein
We are having a very busy system as well (for example 15 volume migration
tasks, 13 recycle tasks, and 10 recall tasks running) hence couple of things
being discussed are :
Time to run HSM's major functions(recycle/migration etc) to
ensure you have them spread out as much as possible.
consider
Gaur
Sent: Thursday, October 18, 2012 5:25 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: DFSMShsm Abend S878
We are having a very busy system as well (for example 15 volume migration
tasks, 13 recycle tasks, and 10 recall tasks running) hence couple of things
being discussed are :
Time to run HSM's
OOPS... forgot to mention... it was 878-1c
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
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
Hello
I have faced the same problem around 2 years back... I was told that this was
just CPU's mess while talking to z/OS.. and it victimized DFSMShsm.. later one
by one all the DB2 keep going down with same error... I thought IBM had fixed
it...
Best of luck with APAR...
On 10/4/2012 4:39 PM, Munish Sharma wrote:
Hello
I have faced the same problem around 2 years back... I was told that this was
just CPU's mess while talking to z/OS.. and it victimized DFSMShsm.. later one
by one all the DB2 keep going down with same error... I thought IBM had fixed
it...
-MAIN@LISTSERV.UA.EDU
Subject: Re: DFSMShsm Abend S878
On 10/4/2012 4:39 PM, Munish Sharma wrote:
Hello
I have faced the same problem around 2 years back... I was told that this
was just CPU's mess while talking to z/OS.. and it victimized DFSMShsm..
later one by one all the DB2 keep going down
