DB2 Users Group. September 8, 2005

Transcription

1 DB2 Users Group September 8,

2 General Announcements September 13 RICDUG, Richmond DB2 Users Group, Richmond, VA September 18 TIB Removal of COBOL 2.2 TIB Insight on SYSW TIB CDB DB2 Utilities SYSA/B/E/S September 22 TRIDUG, RTP, NC October 13 SIRDUG, Charlotte, NC 2

3 Reminders Keywords for Storage requests through Customer Support Center Mainframe Storage REORG for V8 data Do not say or include DB2 in your request Big Projects that may impact a mid- January Development LPAR implementation of compatibility mode 1. Advance notice from clients a. Via to Customer Support center (support@ncmail.net) b. Use these keywords in the subject Mainframe Storage REORG for V8 data c. Designate in detail Test or Production (LPAR), number of volumes needed, and the date when needed. If STOGROUP other than the public DB2 groups, include STOGROUP in . i MB per volume; Approximately 709,000 4K pages per volume ii. Approximate Volume calculation : # of 4K pages * 4 / 2,500,000 d. Include ticket detail for proper routing of your ticket - CI Alias ID : DASD/Disk, Symptom type : Request, Subtype : Storage. e. Get a confirmation from the Customer support center. 2. Tickets should be received 5 days in advance for volume requirements under 10 and 14 days in advance for volume requirements equal to or over Clients can schedule weeks in advance by entering a ticket, but should be mindful that some adjustments to the schedule may be required to accommodate storage requirements and pre-scheduled maintenance. 3

4 Questions and Answers Unicode and Me? DBRMLIB and the bind Value of NEWFUN keyword NO YES YES Are new V8 functions used? No No Yes Is DBRM V8 new object and V8-dependent? No Yes Yes Can V7 or earlier bind? Yes No No Can V8 bind before new-function mode Yes Yes No Can V8 bind in new-function mode Yes Yes Yes Suggested implementation : Set NEWFUN=NO from the beginning of compatibility mode within your precompile options and leave it set to NO until we have completely converted to New Function Mode AND you are ready for developers to use the new functionality. For performance reasons, you may want to do a mass bind when you change to NEWFUN=YES. 4

5 Questions and Answers Unicode and Me? Special characters (CMP Mode) NOT CONCATENATE Range predicates (UNICODE for user data) SELECT fname, lname, midinit FROM crystal.table1 WHERE midinit BETWEEN a AND S To avoid some of these problems, you can sometimes use a different way to code your SQL statements. For example: COLA = 5 can be coded as COLA <> 5 This avoids the use of the (NOT) sign that tends to jump around in different EBCDIC code pages. A similar problem exists with the (CONCAT) operator. For example: COLA COLB = 5 can be coded as COLA CONCAT COLB EBCDIC (Symbols, lowercase, uppercase, numerals SLUN) ASCII/Unicode (Symbols, numerals, uppercase, lowercase SNUL) 5

6 More Preparation Details SYSIBM.SYSDUMMY1 Moved to new table space during ENFM (Enabling New Function Mode) migration rebind required Coded as performance enhancement SQL Stored Procedure Builder for SQL Stored Procedures 6

7 Importance of Current Statistics Meeting with IBM on Friday, September 2 nd Once we convert to V8 compatibility mode we are using the NEW DB2 V8 Optimizer IBM stressed the importance of current V7 statistics in diagnosing potential problems. Perhaps a presentation of new functions once we get to Compatibility mode (February?) 7

8 Current DDL Protection from reverting to old Type 1 indexes which are not supported At least one new partition-related function will automatically change the table description when you alter the index (index controlled partitioning in V7 vs table controlled partitioning in V8) 8

9 PLAN_TABLE New Columns TABLE_ENCODE (Encoding scheme) TABLE_SCSSID (Single Byte Coding Scheme) TABLE_MCSSID (Mixed Byte Coding Scheme) TABLE_DCSSID (Double Byte Coding Scheme) ROUTINE_ID CTEREF (Common Table Expression Ref) STMTTOKEN (User-specified statement token) Coding Schemes are related to extra information required by the introduction of UNICODE compatibility. Documentation on other changed columns and other changed tables : DB2 Version 8 Release Planning Guide, Appendix E To see new features of EXPLAIN output, use ALTER TABLE to add the new Version 8 columns to the existing PLAN_TABLE after you have converted your DB2 subsystem to Version 8 new-function mode. 9

10 IBM DB2 Utilities BACKUP SYSTEM CHECK DATA CHECK INDEX CHECK LOB COPY COPYTOCOPY EXEC SQL LOAD MERGECOPY MODIFY RECOVERY MODIFY STATISTICS REBUILD INDEX RECOVER REORG INDEX REORG TABLESPACE RESTORE SYSTEM RUNSTATS STOSPACE UNLOAD SORTKEYS is the default for the REORG, LOAD, and REBUILD SORTKEYS integer Specifies that index keys are to be sorted in parallel during the SORTBLD phase to improve performance. Optionally, you can specify a value for integer to provide an estimate of the number of index keys that are to be sorted. Integer must be a positive integer between 0 and The default is 0 if the input is on tape, a cursor, a PDS member, or for SYSREC DD *. For sequential data sets, LOAD computes an estimate based upon the input data set size. SORTDATA is the default for the REORG utility SORTDATA Specifies that the data is to be unloaded by a table space scan, and sorted in clustering order. Rows of each table are kept together and are in order by clustering index. SORTDATA is the default unless you specify UNLOAD ONLY or UNLOAD EXTERNAL. If you specify one of these options, you can also specify SORTDATA to get the unloaded data in the order of the clustering index. DB2 UDB V8 Utility Guide and Reference : 10

11 Modifications to ALTER and/or CREATE ALTER and CREATE Depreciated option LOCKPART Default LOCKPARTYES ALTER TABLESPACE,INDEX, PROCEDURE, FUNCTION LOCKPART : Starting with Version 8, DB2 treats all partitioned table spaces as if they were defined as LOCKPART YES. LOCKPART YES specified the use of selective partition locking. Changed behavior for ALTER TABLESPACE: When issuing the ALTER TABLESPACE statement, partition options that are specified after an ALTER PARTITION clause will affect only the specified partition. If you do not specify an option following the specification of a partition, an error is issued. Changed behavior for ALTER INDEX: If you do not specify an option following the ALTER PARTITION clause, a warning is issued. EXTERNAL clause for ALTER PROCEDURE and ALTER FUNCTION requires NAME: In Version 7, the EXTERNAL clause did not require the NAME keyword followed by a value on the ALTER statement. In Version 8, you must specify NAME and a value if you specify EXTERNAL. Update your application programs to include the NAME keyword and a value when you specify the EXTERNAL clause on an ALTER statement. If you do not, DB2 issues an error message. 11

12 Additional Reference Materials DB2 UDB V8 Library - DB2 UDB for z/os Version 8:Everything You Ever Wanted to Know,... and More pdf DB2 UDB Transition Class March 2006 RTP DB2 UDB Transition Class on Digital Video You can get more information on the training through the IBM training website. Choose Training from the services section on the left; DB2 UDB under DB2 Information Management; DB2 UDB for z/os; and DB2 Transition 12