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

On 30-Mar-2015 20:29 -0500, Charles Wilt wrote:

On Mon, Mar 30, 2015 at 6:02 PM, Vicki Wilson wrote:

<<SNIP>> I'm using RENAME to get a palatable system name
rather than the funky generated name.

I noticed that I still get a funky member name xxxxx00001. How
do I rename this? Can I do it in the same script I use to generate
the table? <<SNIP>>

<<SNIP>> or
- Remove the automatically generated member and add your own before
you start loading data.

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.