× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. March 2015

Re: ? about SQL Long table names and funky member names

On Tue, Mar 31, 2015 at 10:19 AM, CRPence <CRPbottle@xxxxxxxxx> wrote:


There is no support to "remove" a Member from the Physical File [that is
the implementation object for the SQL TABLE; same rule applies for any SQL
object implemented as a database *FILE object, e.g. INDEX and VIEW, and
presumably also MQT]. The expected effect should be the msg CPF320A
"Member &3 cannot be removed." issued F/QDBDLTME that would prevent the
Remove Member (RMVM) request.

Note: Restore does enable the invalid effect of a zero-member SQL file
object as a special-case with possible value for /recovery/ purposes; most
any errors on such a file are non-defect because they likely would be a
consequence of the fast-path /assumption/ that the SQL file object always
will have one member.


​Well there's my learn something new for today....thanks Chuck!


Charles​

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2025 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.