RE: [SYSTEM21] Fw: Access path size limit

["Prill, Steve" <sprill@xxxxxxxxxxxxx>]

Just out of curiosity, how does FLP062 get populated.  My file has zero
records in it.

Thanks, 

Steve


-----Original Message-----
From: system21-bounces@xxxxxxxxxxxx
[mailto:system21-bounces@xxxxxxxxxxxx] On Behalf Of
gharper@xxxxxxxxxxxxx
Sent: Wednesday, August 04, 2004 8:11 AM
To: System 21 Users
Subject: Re: [SYSTEM21] Fw: Access path size limit

Unless you reduce the number of records in FLP062, I recommend you
change the other LF's. You will have to end the GLUPDATE job to remove
the lock on the files. Our 3 LF's over FLP062 are all set at
ACCPTHSIZ(*MAX1TB). 
You don't need to change FLP062 because the access path is arrival
sequence so it does not have a keyed sequence access path.

Gary Harper




GManoovaloo@xxxxxxxxxxxxx
Location of Author: 
Sent by: system21-bounces@xxxxxxxxxxxx
08/04/2004 05:22 AM
Please respond to System 21 Users

 
        To:             System 21 Users <system21@xxxxxxxxxxxx>
        cc: 
        Subject:        [SYSTEM21]   Fw: Access path size limit


We need some feedback/views  on the following situation : 

 2 weeks ago , GLUPDATE crashed because one of the logicals (GLBLINKT)
of 

FLP062 had reached the maximum size allowed . The message indicated 'no
recovery' . 
 The attribute *ACCPTHSIZ OF the 3 logicals ( GLGLTRAN , GLBLINKT ,
GLBLALLT ) based on FLP062, was found to be set to  *MAX4GB . . After
investigation ,and in view of the size of FLP062 , there was no
alternative than to CHGLF the file GLBLINKT , setting the *ACCPTHSIZ to
*MAX1TB , a value that is allowed after  O/S V3R6M0 . Since then , there
is no apparent problem . Has someone hit this problem before ? Is it
right 

to extend the CHGLF to the other logicals to prevent recurrence of
problem 

?  Also , what about additionally issuing a  CHGPF to set this same
parameter for FLP062 ? 
Thank you any help 
 
Gilbert Manoovaloo
_______________________________________________
This is the System 21 Users (SYSTEM21) mailing list To post a message
email: SYSTEM21@xxxxxxxxxxxx To subscribe, unsubscribe, or change list
options,
visit: http://lists.midrange.com/mailman/listinfo/system21
or email: SYSTEM21-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/system21.



_______________________________________________
This is the System 21 Users (SYSTEM21) mailing list To post a message
email: SYSTEM21@xxxxxxxxxxxx To subscribe, unsubscribe, or change list
options,
visit: http://lists.midrange.com/mailman/listinfo/system21
or email: SYSTEM21-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/system21.

This email and any attachment are confidential and may be 
legally privileged.  If you are not the intended recipients,
please notify the author by replying to this email message,
and then delete all copies of the email on the system.  If
you are not the intended recipient, you must not disclose,
distribute, copy, print or use this email in any manner.

Email messages and attachments may contain viruses.  Although
we take precautions to check for viruses, we make no assurances
about the absence of viruses.  We accept no liability and suggest
that you carry out your own virus checks.