Hi Tommy,
I think you've already found out that setting the CSA limit to zero in
VTAM isn't a great idea. I'm always hesitant to set storage limits on
any subsystem to zero (or no limit) - I've had a couple of similar
problems over the years.
David Stephens
Lead Systems Programmer
[email protected]
www.longpelaexpertise.com.au
<http://www.longpelaexpertise.com.au/images/logo.gif>
Ph. 0404 757 821 (from Australia)
(Longpela Expertise Logo)
Longpela Expertise - System z Mainframe Consultants
Read new expert Mainframe articles every quarter in our LongEx Mainframe
Quarterly <http://www.longpelaexpertise.com.au/ezine>
Tommy Tsui wrote:
Hi all,
One of IBM expert tell our shop to setup the CSA limit =0 in VTAM, but
we found IST561I STORAGE UNAVAILABLE: CRA4 BUFFER POOL problem when
one of mq server abnormal connect/reconnect to our host system. As we
set the CSA limit to 0 therefore VTAM use up all MVS ECSA. All
commands cannot be issued includes VTAM and MVS command. We IPL the
LPAR finally. Is it a good practise to set the CSA limit to 0. Anyone
can share ?
Any help will be appreciated.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
