Jim is correct about TCP/IP's expanded use of C.   The sidebar to that
statement
is that the increased virtual storage requirement comes from the use of the
C
sockets code and the name resolver code in LE and CMS.   C sockets are byte
file system (BFS) file descriptors.   Even if you are not running with or
using the BFS,
every socket created is a BFS file descriptor.  Unfortunately, the BFS
control blocks
and data areas chew up a lot of virtual storage, ~5M.   Since TCP/IP
functions such
as PING, TRACERTE, and NFS use C sockets now, they need more virtual
storage
to run.

For other reasons for some of the increased storage use in z/VM 5.1.0 and
later CMS,
please see the http://www.vm.ibm.com/devpages/donovanm/zvmle.html#LEstor
web
page.   Also, you really want to make sure you have installed CMS APAR
VM63819
on both z/VM 5.1.0 and 5.2.0, LE APAR VM63820 on both releases, and TCP/IP
APAR
PK15940 on z/VM 5.1.0.  These APARs correct several out-of-storage related
conditions
discovered when running PING.

Thanks!
         Mike



                                                                           
             "Stracka, James                                               
             (GTI)"                                                        
             <[EMAIL PROTECTED]                                          To 
             .com>                     [email protected]           
             Sent by: VM/ESA                                            cc 
             and z/VM                                                      
             Discussions                                           Subject 
             <[EMAIL PROTECTED]         Re: CMS SIZE                        
             .UARK.EDU>                                                    
                                                                           
                                                                           
             02/13/2006 11:05                                              
             AM                                                            
                                                                           
                                                                           
             Please respond to                                             
              VM/ESA and z/VM                                              
                Discussions                                                
             <[EMAIL PROTECTED]                                             
                .UARK.EDU>                                                 
                                                                           
                                                                           




This was because of TCP/IP's expanded usage of C.  Testing showed doing
PING and NETSTAT commands may need up to 5M more.  IBM Level-2 suggested
going to 32M (as much as 64M is will not expand what was called the page
and segment tables).
      -----Original Message-----
      From: VM/ESA and z/VM Discussions [mailto:[EMAIL PROTECTED]
      On Behalf Of Huegel, Thomas
      Sent: Monday, February 13, 2006 10:47 AM
      To: [email protected]
      Subject: CMS SIZE



      I have a simple question for anyone that has z/VM 5.2 running.
      I seem to remember someone saying that the size of CMS machines needs
      to be increased on 5.2.
      I am sure the validity of that statement depends on what release one
      is on before going to 5.2.
      I am on z/VM 4.3.
      The book states that the minimum for 4.3 and 5.2 are both 2M to IPL
      CMS and 20M for IPL 190.


      Most of my 100+ CMS users are at 8M now.
      Will 8M suffice or should it be virtualized to 16M? Any opinions?


      Thanks







      __________________________________________________________________
      << ella for Spam Control >> has removed VSE-List messages and set
      aside VM-List for me
      You can use it too - and it's FREE!  http://www.ellaforspam.com



If you are not an intended recipient of this e-mail, please notify the
sender, delete it and do not read, act upon, print, disclose, copy, retain
or redistribute it. Click here for important additional terms relating to
this e-mail.     http://www.ml.com/email_terms/

Reply via email to