Re: 'Current unprotect used / Maximum unprotect'

>Date: Thu, 03 Jul 1997 08:00:48 -0400
>To: MIDRANGE-L@midrange.com
>From: "Al Barsa, Jr." <barsa2@ibm.net>
>Subject: Re: 'Current unprotect used / Maximum unprotect'
>In-Reply-To: <33BAF362.4919@NxTrend.com>
>References: <3.0.2.32.19970702175518.006ba1e0@pop4.ibm.net>
>
>At 08:33 PM 7/2/97 -0400, you wrote:
>>Al Barsa, Jr. wrote:
>>> 
>>> Hello,
>>> 
>>> Now that we are using RISC systems, which do not support Software
Checksum,
>>> what's the purpose of the 'Current unprotect used' and 'Maximum unprotect'
>>> on the WRKSYSSTS/DSPSYSSTS commands?  Are they used for anything other
than
>>> Checksum?
>>
>>On RISC machines:
>>
>>                  Current Unprotected                 
>>                                                              
>>  The current amount (in millions of bytes) of storage in     
>>  use for temporary objects and machine data on the system.   
>> 
>>                  Maximum Unprotected               
>>                                                          
>>  The largest amount (in millions of bytes) of storage used 
>>  for temporary objects at any one time since the last IPL. 
>>
>>On CISC machines:
>>
>>                  Current Unprotected               
>>                                                          
>>  The current amount of storage (in millions of bytes) in   
>>  use for temporary objects and machine data that are stored
>>  in unprotected storage when system checksum protection is 
>>  in effect.  This is used in conjunction with maximum      
>>  unprotected storage to determine how much unprotected     
>>  storage should be reserved when the checksum protection   
>>  provided by the system software is started.               
>>
>>                  Maximum Unprotected                
>>                                                          
>>  The largest amount of storage (in millions of bytes - for 
>>  temporary objects and machine data that are stored in     
>>  unprotected storage when the checksum protection provided 
>>  by the system software is in effect) used at any one time 
>>  since the last IPL.                                                    
>>
>>I believe on CISC machines that DIDN'T have checksum protection, that
>>this size was actually the size of your load source disk drive (first
>>drive) PLUS the temporary/machine data
>>space.                                       
>>
>Neil,
>
>On CISC, I needed to reserve enough space on DASD to omit the max
unprotected from checksum, otherwise the performance went down the tubes.
On RISC, why do I care?
>
>Al
>
>

Al Barsa, Jr. - Account for Midrange-L
Barsa Consulting, LLC.  
400 > 390

Phone:  914-251-9400
Fax:    914-251-9406





Private mail should be sent to barsa@ibm.net
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the Midrange System Mailing List!  To submit a new message,   *
* send your mail to "MIDRANGE-L@midrange.com".  To unsubscribe from     *
* this list send email to MAJORDOMO@midrange.com and specify            *
* 'unsubscribe MIDRANGE-L' in the body of your message.  Questions      *
* should be directed to the list owner / operator: david@midrange.com   *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *