On Fri, 21 Oct 2011 06:15:36 -0500, J Ellis <[email protected]> 
wrote:

>1. If you specify LOCANY=YES then all of the UCBs will be in ESQA.  The HCD 
>Planning manual is wrong.  The expectation is there will be 216 bytes of ESQA 
>for each UCB. We are starting the process to get this manual updated.
>
>2. They recommend you use the HCD panels vs the bottom line command because 
>this will use the user's address space to do the activate rather than the 
>Master address space and will provide more virtual storage to process all of 
>the devices

In your last post (which you didn't reference) you wrote this:

>According to IBM, with LOC=ANY, for DASD, it's 274 bytes in SQA, 136 bytes in 
>ESQA.
> and, we will knock a meg out of our private area if we add the 10K device.

That didn't make any sense, but you wrote "according to IBM" and that seemed to 
indicate you opened a PMR or had some sort of definitive information from 
someone
who knew the exact numbers.   

So now you've probably confused people and for the sake of the archives,  maybe
should should clarify the numbers.   

Also, using "HCD panels vs the bottom line command"? I assume "bottom line 
command" refers to issuing the ACTIVATE command to  a console via SDSF,  
some other method, or a "real" console as opposed to  using the panels. 

Your initial concerned seemed to be about private area "after the fact" and
at NIP vs. dynamic activation.  Those are also two different issues related
to this discussion.   

Regards,

Mark
--
Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS       
mailto:[email protected]                                        
Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html 
Systems Programming expert at http://expertanswercenter.techtarget.com/

----------------------------------------------------------------------
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

Reply via email to