|
On 18-May-2015 08:53 -0500, Tim Bronski wrote:
Anyone know HOW this could have happened? Doing a DSPFD shows Maximum members allowed: 1 but Number of members: 2.
Restore Object (RSTOBJ) [or Restore Library (RSTLIB) or equivalent APIs] and possibly even Reclaim Storage (RCLSTG) could effect that. The Database considers the effect of NbrMbrs>MaxMbrs [as visualized with Display File Description (DSPFD)] to be an /acceptable/ illogical condition. The condition is logged with CPI320C "Too many members for the MAXMBRS value." during restore [as a faolowup reply from Rob already notes] with the member renamed as ORIG_##### with TEXT() overwritten using the text from the msg CPX8109 [much like the similar outcome for database files renamed with TEXT() overwritten from the text from the msg CPX8105]. I do not recall if\what the reclaim would log about placing a member back into the member-chain, but the member would not be renamed unless a duplicate; the TEXT() would be changed.
Searching the archives for MAXMBRS will find a number of past discussions, including some where I responded explaining either the likely origin or at least some of the design\implementation details:
<https://www.google.com/search?q=maxmbrs++"restore"+OR+"rstobj"+OR+"rstlib"+site%3Aarchive.midrange.com>
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
