Re: Backup of SQL tables and multi-member files

I found this in CL manual for 7.2 for CPYF

CREATE FILE (CRTFILE)

<QUOTE>
If the from-file is an SQL table, view, or index, that contains a user defined type, datalink, LOB field type, or XML field type, the physical file created will be an SQL table. In all other instances the to-file created will be a database physical file that is not an SQL table.
</QUOTE>


Our file has timestamps, a date, and a time field and various packed and alpha fields. But none of these should cause the file to be SQL. Or would it?
Anyone have an idea?

=====

Paul


On 2018-03-01 17:31, Dan wrote:

On Thu, Mar 1, 2018 at 2:01 PM, Paul Therrien <
paultherrien@xxxxxxxxxxxxxxxxxx> wrote:

We are on V7R2 and when we execute a CPYF on an SQL table to create a new
table we get an SQL table:

Can you show me how you executed your CPYF?

2 > CHGPF FILE(DAN/AAA) MAXMBRS(2)
Maximum-member value not valid for file AAA. <CPD3213>
File AAA in DAN not changed.
2 > CPYF FROMFILE(DAN/AAA) TOFILE(DAN/ZZZ) MBROPT(*REPLACE) CRTFILE(*YES)
Physical file ZZZ created in library DAN.
Member AAA added to file ZZZ in DAN.
179191 records copied from member AAA.
2 > CHGPF FILE(DAN/ZZZ) MAXMBRS(*NOMAX)
File ZZZ in library DAN changed.
2 > CPYF FROMFILE(DAN/AAA) TOFILE(DAN/ZZZ) TOMBR(MEMBER2) MBROPT(*REPLACE)
Member MEMBER2 added to file ZZZ in DAN.
179191 records copied from member AAA.
2 > CPYF FROMFILE(DAN/AAA) TOFILE(DAN/ZZZ) TOMBR(MEMBER3) MBROPT(*REPLACE)
Member MEMBER3 added to file ZZZ in DAN.
179191 records copied from member AAA.

- Dan