Forgotten to do a FREEBUFF dcbaddr after CLOSE? Grtn, Kees.
> -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of John McKown > Sent: 21 December, 2017 18:02 > To: [email protected] > Subject: Re: Disable DYNALLOC? > > On Thu, Dec 21, 2017 at 10:50 AM, Seymour J Metz <[email protected]> wrote: > > > It's not just DYNALLOC, it's *any* code that explicitly or implicitly > > waits. Who wrote the transaction that issued the SVC 99? Why didn't he > run > > it in a subtask? Presumably he is also doing OPEN, which would be a > problem > > even without the DYNALLOC. > > > > Yeah, long ago we purchased a company. They had a rarely run transaction > which used a COBOL subroutine which did an OPEN / READ / CLOSE on a > sequential DSN. For some reason, when we were doing the processing, we > ran > the transaction a LOT. And exhausted the region; which resulted in a > S80A > (iirc) abend which took the CICS down. I "cheated" and updated the CICS > SRT > (System Recovery Table) to basically "do nothing" when an S80A happened. > The transaction would then fail until we scheduled a recycle of the > CICS. > This "moved" the problem from a "CICS is broken" problem to "the > transaction is broken" so that applications would fix it. > > > > > > > > > -- > > Shmuel (Seymour J.) Metz > > http://mason.gmu.edu/~smetz3 > > > > > -- > I have a theory that it's impossible to prove anything, but I can't > prove > it. > > Maranatha! <>< > John McKown > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN ******************************************************** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 ******************************************************** ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
