no longer one of those ZPARMs made famous through a bunch of user group presentations.
Lines 2 – 5: As I will be calling the QCMDEXC API program I need to define a procedure prototype for the API. Line 6: I need to define the file, TESTFILE, with a statement.
This file will be used for update, it is keyed, and user opened.
If you are an application programmer then you will more than likely need to write TSQL code to update your SQL Server database tables.
In order to update a row in a SQL Server table you will use the UDPATE statement.
Last Thursday, the last day of this year's Information on Demand (IOD) Conference, while I was doing my presentation on universal table spaces for a second time, I was asked if the the DSNZPARM that allows you to update the partitioning key still existed. If the key was altered and a row was moved from partition 3 to partition 7, all the partitions between 3 and 7 inclusively for the table space and partition index would have to be drained along with any non partitioned indexes on that table.
However, that doesn't always mean that it will be removed in the next release, it just means "get ready, it's going away"... When I arrived back in Houston, I did some quick checking. drain locks are no longer taken when moving between partitions... Before Version 8, DB2 had to quiesce all the partitions affected by a row's movement when a column in the partition key was changed..
Line 7: As this is a test program I want to be able to run this multiple times to make sure I update the right field with the right value.
Rather than resetting the fields in the file I am going to copy the records from a "saved" file before any other processing.
I am using DB2 9.5 UDB on windows I want to update multiple rows in a single sql statement.