Re: Unprotected Storage

The first history of unprotected storage being an issue was when checksum
was brought into the architecture at CPF Release 8.0 of the System/38.
Checksum was parity protection, like RAID-5, but done at the software
level.  When you had a disk failure, you still failed, but the disk still
had to be replaced, and then the system re-ipled, so you had the effect of
abnormal end of CPF.

Al Barsa, Jr.
Barsa Consulting Group, LLC

400>390

914-251-1234
914-251-9406 fax

http://www.barsaconsulting.com
http://www.taatool.com





                                                                                
                                                          
                      Justin Haase                                              
                                                          
                      <JHaase@xxxxxxxxxxxx        To:       "'Midrange Systems 
Technical Discussion'" <midrange-l@xxxxxxxxxxxx>           
                      m>                          cc:                           
                                                          
                      Sent by:                    Subject:  Unprotect Storage   
                                                          
                      midrange-l-bounces@x                                      
                                                          
                      idrange.com                                               
                                                          
                                                                                
                                                          
                                                                                
                                                          
                      03/31/2003 11:22 AM                                       
                                                          
                      Please respond to                                         
                                                          
                      Midrange Systems                                          
                                                          
                      Technical Discussion                                      
                                                          
                                                                                
                                                          
                                                                                
                                                          




I've asked this once before, never got an answer - perhaps some new blood
in
the list (or someone who may have passed-by it in the past) can shed some
light on this.

On a WRKSYSSTS screen you have the "current unprotect used" and "maximum
unprotect" - I equate this to essentially being like virtual memory on a
PC.

What I don't know is an easy way to see WHAT is using it.  I do know that
runaway ODBC jobs can start chewing it up - you kill the job, the usage
goes
down.  I don't know how to see any other use.

Is there an easy command or way to see what is consuming this unprotect
memory, since it does eat DASD just as an object would.  Thanks in advance
for the assistance.

Justin C. Haase
Sr. Technical Support Specialist - OutLink
Jack Henry and Associates - Allen, TX
www.jackhenry.com
_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.