I am not really a fan due to SQL's lack of support, but when you start a job and they have systems in place designed around multi-member files, it's difficult to change it (and I wouldn't change a system to not be multi-member to simply make it not multi-member).
Unlike John, I don't deal with them everyday, however the word every so often I do. Usually for SQL I end up copying the member into a test file and reference that file using sql instead.
-Kurt
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of DeLong, Eric
Sent: Friday, July 13, 2012 12:38 PM
To: Midrange Systems Technical Discussion
Subject: RE: Hooray!!! DB2 for i adds remote & local support in a single SQL statement!
I think I'm gonna be sick... Multi-member? Really? Every day?
-Eric
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Voris, John
Sent: Friday, July 13, 2012 9:22 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Hooray!!! DB2 for i adds remote & local support in a single SQL statement!
I think a better use of a 3-part name would be an easier method to handle multi-member files in SQL on System i.
But I guess we should be thankful for what IBM does deliver to us.
( Yes, every new technology is bound to have it's detractors - Maybe it is just me, but I expect the real things I use EVERY DAY to become
easier.)
- John V
message: 7
date: Fri, 13 Jul 2012 09:38:13 -0400
from: Charles Wilt
subject: Hooray!!! DB2 for i adds remote & local support in a single
SQL statement!
http://www.mcpressonline.com/database/techtip-easier-db2-for-i-data-tran
sfers-with-new-technology-refresh.html
The latest IBM i Technology Refresh for the 7.1 release lifts this
restriction for INSERT statements to simplify data transfer operations
involving three-part names.
midrange.com
