Are you sure they CPY* commands won't work on the short name version of the file ?
I think you can query the long and short names. Or better yet keep the table names you create to 10 or less chars.
I would stay away from multimember PFs for new development. Just one man's opinion......
Regards,
Richard Schoen
Director of Document Management
e. richard.schoen@xxxxxxxxxxxxxxx
p. 952.486.6802
w. helpsystems.com
------------------------------
message: 3
date: Thu, 17 Jan 2019 08:13:39 -0500
from: a4g atl <a4ginatl2@xxxxxxxxx>
subject: Sometime you need multiple members in a table.
I have a situation where I have a table defined. In the past I used PFs.
The table has a long and short name. This prevents me from using CPYF or CRTDUPOBJ. I have used RUNSQL to do a Create Table ... as (select..) with no data. This creates a table not a PF, okay.
I need a PF with Multiple members that is identical to the table. I use the member to store copies of file we send to external systems as an archive.
The member functionality has been great for this and I do not want to have hundreds of files in the library.
I do not have DDS but I could create DDS but would prefer not to. That makes it 2 different objects to maintain.
Is there a way to create a PF from a table?
TIA
Darryl Freinkel
------------------------------
message: 4
date: Thu, 17 Jan 2019 13:21:20 +0000
from: Rob Berendt <rob@xxxxxxxxx>
subject: RE: Sometime you need multiple members in a table.
Yes, it's quite easy but it involves the SPENDMONEY command.
In SQL talk a member is a partition. Hence this is why you can find a list of all "members" in SYSPARTITIONSTAT.
One difference is that SQL rather picks the partition by some criteria. For example you can partition your tables by REGION. However, unlike how people often set up their "members" on a DDS table, you would use a REGION column also. Back when disk was at a premium it would gag someone to add a column called REGION when you already knew that by the partition (aka member) name.
Search for the partition clause in the CREATE TABLE statement in the Knowledge center.
But, here's where the SPENDMONEY command comes into play. To use partitioned tables you must purchase and install DB2 Multisystem (make sure you get the right thing, many people confuse it for another option). If the cost is roughly the same as for a new P9 loaded with SSD's then you've got the right product. Even if you plan on only using partitioned tables on a single system you still need DB2 Multisystem. IBM will not unbundle partitioned tables out of DB2 Multisystem. I tried with an RFE but it got shot down.
midrange.com
