Re: Max number of Database files exceeded -- MIDRANGE-L

At 09:27 PM 01/12/2000 +0000, you wrote:

Different libraries for PFs and LFs are bad from a save/restore 
perspective.  Aside from the fact that files may not be restorable 
(although in this case, with the PFs in libraries ahead in alphabetic order 
of the LFs, they would be), the access paths would typically have to be 
rebuilt.

Al


> >What we always did was for each application have a PF library and a LF
>library.
> >They followed the naming convention xxPROGP for LF's and xxDATAP for PF's
>so for
> >example OEPROGP for Order Entry Logical files and OEDATAP for Order Entry
>Physical
> >files. That way the xxDATAP's would always be restored before the
>xxPROGP's. For a
> >logical spanning multiple physicals there are a number of ways to handle
>that - in
> >this scenario a ZZPROGP library maybe...
> >
> >Also are you SURE it is actual FILES and NOT those DREADED MEMBERS ??
> >
> >At my last job we used Silvon's SalesTracker and it was NOTHING for several
>of
> >their files to have 10's of thousands of members because it was saving the
>viewing
> >criteria user used on the assumption it would use that again and not have
>to
> >rebuild it. From what we saw, even with HUNDREDS of people using this
>product - no
> >one ever picked one already defined <BG>...
> >
> >We also are using a faxing product here that if we don't purge the master
>file
> >every so often, our backups bomb. This was my first introduction to that
>maximum
> >problem...
> >
> >Chuck
> >
> >"Al Barsa, Jr." wrote:
> >
> >> At 09:42 AM 01/11/2000 -0800, you wrote:
> >>
> >> It's not just that simple.  Every reference to that library needs to be
> >> addressed.  This includes execution of commands such as CHGLIBL,
>ADDLIBLE,
> >> RMVLIBLE, and every reference to the library in every job description on
> >> the system.  It addition the *LIBL system values need to be checked.
> >>
> >> Furthermore, you don't want to split up PF/LF relationships.  Keep in
>mind
> >> that one LF can span multiple PFs through multi-record format LFs and
>joins.
> >>
> >> This is not a trivial job.
> >>
> >> Al
> >>
> >> >Why not just create a second library for files, add it to the
> >> >library list the same way you do this library, and move half
> >> >the files there?
> >> >
> >> >Or are you hard coding library names?
> >> >
> >> >Regards,
> >> >
> >> >Jim Langston
> >> >
> >> >"Chuck M.Drye" wrote:
> >> >
> >> > > New guy on the block.   I have a library with 75,000 + files in
> >> > it.  This exceeds the threshold of 55,500 maximum number of database
> >> > files in a single library restriction.  I cannot move the files or
>delete
> >> > any as they are all production files.  Does anyone have a method to
>save
> >> > to tape in one save ?  How about restoring these files ?
> >> > >
> >> > >         Thanks for your help
> >> > >
> >> > >                         Chuck D.



+--------------------------------------------------+
| Please do not send private mail to this address. |
| Private mail should go to barsa@ibm.net.         |
+--------------------------------------------------+

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

Phone:          914-251-1234
Fax:            914-251-9406
http://www.barsaconsulting.com
http://www.taatool.com

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---