Customer Support Note

Transcription

1 Customer Support Note ASG-ViewDirect-MVS 6.4 & 6.5 Contents

2 BIND PLANVDRMVSvv MEMBERVDRDBRvv - ISOLATIONUR - KEEPDYNAMICYES - NOREOPTVARS - RELEASECOMMIT RUN PROGRAMDSNTIAD PLANDSNTIA!! LIB'DSN!!0.RUNLIB.LOAD' BIND PACKAGExxxxxxxx.VDRCOLvv - ACTIONREPLACE - CURRENTDATAYES - DBPROTOCOLDRDA - NODEFERPREPARE - DYNAMICRULESRUN - ENABLE* -

3

4

5 //* plan name must be specified in //* - the BIND PLAN statement of this JCL procedure //* - the GRANT statement of this JCL procedure //* - the DBMS Subsystem Media Table CESMTV09. //* //* 5 In the "RUN PROGRAMDSNTIAD" statement, the user must //* specify the plan name for DSNTIAD normally, DSNTIA!! //* and the load library in which DSNTIAD resides normally, //* DSN!!0.RUNLIB.LOAD, where "!!" denotes a DB2 version/release //* level. DSNTIAD is an IBM-supplied utility its plan name //* and load library are determined during DB2 installation. //* //* 6 In the "GRANT... TO" statement, replace "AUTHID" with //* the authorization ID of the VDRMVS tables to be created. //* Be sure to specify your choice of Owner ID in the //* VDR/MVS DB2 customization module CESMTV09. //* //* 7 For DB2 V9 and later releases, uncomment and add //* the following to both BIND PACKAGE and BIND PLAN. Be sure //* to include or delete the continuation character '-' //* as needed: //* //* ROUNDINGHALFUP //* //* 8 For DB2 V10 and later releases, uncomment and add //* the following to BIND PACKAGE. Be sure to include or //* delete the continuation character '-' as needed: //* //* CONCURRENTACCESSRESOLUTIONUSECURRENTLYCOMMITTED - //* //* Add the following to BIND PLAN. Be sure to include or //* delete the continuation character '-' as needed: //* //* EXTENDEDINDICATORNO - //* //* 9 Add any installation-specific package/plan management //* parameters that are needed, such as ACTION... RETAIN. //* //* BIND Options: //* //* The following are brief descriptions of specified and optional //* parameters. Consult the DB2 documentation for additional //* details and the most current information. //* //* ACQUIREUSE Obtain table space locks on first use. //* ACTIONREPLACE Replace current package/plan on bind. //* Note: RETAIN may also be specified on //* the BIND PLAN to GRANT plan execute //* privileges to the previous owner when //* the plan owner changes. //* CONCURRENTACCESSRESOLUTION DB2 V10 and later releases only: //* USECURRENTLYCOMMITTED Skip uncommitted data on read. //* CURRENTDATAYES Obtain locks for read only cursors. //* DBPROTOCOLDRDA Use DRDA protocol to connect to remote //* sites. //* NODEFERPREPARE PREPARE remote dynamic SQL immediately. //* DISCONNECTEXPLICIT Only disconnect "release pending"

6 //* threads on COMMIT. //* DYNAMICRULESRUN Set RUN behavior for dynamic SQL: //* * Application process AUTH ID and //* CURRENT SQLID value used to //* determine SQL query authorization. //* * CURRENT SCHEMA defaults to //* CURRENT SQLID qualifies tables, //* indexes, aliases. //* * Installation application program //* options apply. //* ENABLE* Permit package/plan access for all //* valid connection types, e.g., //* BATCH, CICS, DB2CALL. //* ENCODINGEBCDIC Default application encoding scheme //* is EBCDIC. //* EXPLAINNO Do not collect/store EXPLAIN //* query data. //* EXTENDEDINDICATORNO DB2 V10 and later releases only: //* Do not use extended indicator //* variables for SQL query data. //* FLAGI Display all messages, including //* informational messages. //* IMMEDWRITENO Data sharing environments only: //* perform updates at COMMIT/ROLLBACK. //* ISOLATIONUR Uncommitted reads permitted locks //* not acquired on read. //* KEEPDYNAMICYES Store dynamic SQL statements in //* cache following COMMIT. //* MEMBERVDRDBR66 DBRM name to be bound into package. //* This becomes the package name. //* OWNER******** Plan/package authorization ID. Must //* match C*SMTV09 SMT OWNERID= parameter. //* Value used to implicitly qualify //* table/index names when //* DYNAMICRULESRUN is in effect. //* PACKAGExxxxxxxx.VDRCOL66 Identifies the collection xxxxxxxx //* is the location. //* PKLISTxxxxxxxx.VDRCOL66.* Identifies the collection of packages //* to be bound into the plan xxxxxxxx //* is the location. //* PLANVDRDBR66 Specifies the bound plan name. //* QUALIFIER******** Authorization ID used as implicit //* qualifier for static distinct types, //* functions, procedures, specific names. //* This value is not used to qualify //* tables/indexes when DYNAMICRULESRUN //* is specified. Use of same value as //* OWNER is recommended. //* RELEASECOMMIT Release in-use program resources at //* COMMIT. //* REOPTNONE Do not determine dynamic statement //* access path at run time. //* ROUNDINGHALFUP DB2 V9 and later releases only: //* Round floating point values up to //* next least significant digit when //* equidistant from greater than/less //* than value. //* SQLERRORNOPACKAGE Do not create the package on SQL error.

7 //* SQLRULESDB2 Type 2 CONNECTs to an existing SQL //* connection are permitted. //* VALIDATERUN Authorization and object existence //* checks may be performed at run time //* rather than at bind time. //* //INSTALL7 PROC DISKPFX='VIEW.DIRECT', <=== DISK DATASET PREFIX // SYSOUT='*' <=== YOUR SYSOUT CLASS //* //BIND EXEC PGM=IKJEFT01,REGION=60M,DYNAMNBR=20 //STEPLIB DD DSN=DSN!!0.SDSNLOAD,DISP=SHR //DBRMLIB DD DSN=&DISKPFX..SOURCE,DISP=SHR //SYSTSPRT DD SYSOUT=&SYSOUT //SYSPRINT DD SYSOUT=&SYSOUT //SYSUDUMP DD SYSOUT=&SYSOUT // PEND //* // EXEC INSTALL7 //BIND.SYSTSIN DD * DSN SYSTEMDS!! BIND PACKAGExxxxxxxx.VDRCOL66 - ACTIONREPLACE - CURRENTDATAYES - DBPROTOCOLDRDA - NODEFERPREPARE - DYNAMICRULESRUN - ENABLE* - ENCODINGEBCDIC - EXPLAINNO - ISOLATIONUR - KEEPDYNAMICYES - MEMBERVDRDBR66 - OWNER****** - QUALIFIER****** - RELEASECOMMIT - REOPTNONE - SQLERRORNOPACKAGE - VALIDATERUN BIND PLANVDRDBR66 - ACQUIREUSE - ACTIONREPLACE - CURRENTDATAYES - DBPROTOCOLDRDA - NODEFERPREPARE - DISCONNECTEXPLICIT - DYNAMICRULESRUN - ENABLE* - ENCODINGEBCDIC - EXPLAINNO - FLAGI - IMMEDWRITENO - ISOLATIONUR - KEEPDYNAMICYES - OWNER****** - PKLISTxxxxxxxx.VDRCOL66.* - QUALIFIER****** - RELEASECOMMIT - REOPTNONE -

8

9

10

11

12 --================================================================== -- General DBMS Definitions --================================================================== ** Database -- CREATE DATABASE VDRMVSxx ** Storage Group -- CREATE STOGROUP VDRGRPid -- VOLUMES VVVVI1, VVVVI2, VVVVI3, VCAT VDRCATLG -- --================================================================== -- DBMS object for Schema Control Table --================================================================== ** Tablespace

13 As of DB2 V9, a segmented table space is recommended for schema control data. -- DROP TABLESPACE VDRMVSxx.SCHMACTL -- COMMIT CREATE TABLESPACE SCHMACTL -- for Control table IN VDRMVSxx -- by default SYSDEFLT PRIQTY 10 SECQTY 10 FREEPAGE 1 PCTFREE 0 TRACKMOD YES BUFFERPOOL BPid -- BP0, or Buffer pool designated for VDR LOCKSIZE ANY LOCKMAX SYSTEM CCSID EBCDIC MAXROWS 255 SEGSIZE 4 -- Pages per segment ** Table CREATE TABLE CONTROL SCHEMA_VERSION VARCHAR32 NOT NULL, EXT_ATTR VARCHAR64 DEFAULT NULL in VDRMVSxx.SCHMACTL ** Put the schema version into the Control table INSERT INTO CONTROL SCHEMA_VERSION values'4.0' COMMIT --================================================================== -- Document Reference DBMS object --==================================================================

14 ** Table Space DB2 V8: If you are accessing a DB2 V8 subsystem, both simple and partitioned table spaces can still be created however, you may wish to consider defining non-partitioned table spaces as segmented using the SEGSIZE parameter as discussed below. SEGSIZE cannot be used with NUMPARTS in V8 universal table spaces/option MAXPARTITIONS are not available. If any of your table spaces are partitioned, you may also choose to use table-controlled partitioning as shown below. DB2 V9 or later: As of DB2 V9, range-partitioned universal table spaces are recommended for document reference data: NUMPARTS, Number of partitions, , maximum varies with page size, DSSIZE, extended addressability SEGSIZE, Pages per segment, 4-64 multiple of 4 large, partitioned table spaces >128 pages typically have SEGSIZE 64 MEMBER CLUSTER, With data sharing, optional do not specify for segmented table space Partition definition: NUMPARTS 1000 Desired number of partitions, LOCKPART YES -- or alternate USING parameters for partitions -- MEMBER CLUSTER is optional, data sharing environment only PART 1 USING... MEMBER CLUSTER, PART 2 USING... MEMBER CLUSTER,... PART 1000 USING... MEMBER CLUSTER Table-controlled partitioning is required for universal table spaces. Other applicable parameters: DSSIZE, Maximum partition size: 1,2,4,8,16,32,64G varies with page size, DSSIZE, EA Sample definitions are provided below customize for your installation data requirements. Consult DB2 documentation for further details. -- DROP TABLESPACE VDRMVSxx.DOCREFTS -- COMMIT CREATE TABLESPACE DOCREFTS -- for DOC_REF table -- DSSIZE nng -- Maximum partition size nnn GB -- may be 1,2,4 Prior to DFSMS may be 1,2,4,8,16,32,64 DFSMS 1.5 or later

15 IN VDRMVSxx FREEPAGE 1 PCTFREE 0 TRACKMOD YES BUFFERPOOL BPid -- by default DSNDB04 -- by default SYSDEFLT -- PRIQTY and SECQTY maximum values , DFSMS , >DFSMS integer nnn KB -- integer nnn KB -- YES for security purposes -- BP0, or Buffer pool designated for VDR SEGSIZE Segment size, pages, 4-64 multiple of 4 MEMBER CLUSTER -- Data sharing only, optional -- NUMPARTS Desired number of partitions -- LOCKPART YES Alternate USING parameters for partitions -- PART 1 USING... MEMBER CLUSTER, -- PART 2 USING... MEMBER CLUSTER, PART 1000 USING... MEMBER CLUSTER -- LOCKSIZE ANY LOCKMAX SYSTEM COMPRESS YES CCSID EBCDIC MAXROWS 255 ** Table & Indexes CREATE TABLE DOC_REF DOC_ID NUMERIC19,8 not null, STARTING_PAGE_NUM INTEGER not null, STARTING_PAGE_RBA INTEGER not null, PAGE_COUNT INTEGER not null, RPT_ID CHAR10 not null, RPT_VERSION_ID_CMP CHAR14 not null, SECTION_ID CHAR30 not null in VDRMVSxx.DOCREFTS -- PARTITION BY RANGE -- DOC_ID ASC PARTITION 1 ENDING AT INCLUSIVE, -- PARTITION 2 ENDING AT INCLUSIVE, PARTITION 1000 ENDING AT INCLUSIVE --

16 CREATE UNIQUE INDEX IX_DOCREF_PK ON DOC_REF DOC_ID ASC -- by default SYSDEFLT -- CLUSTER -- PARTITIONED -- Valid for range-partitioned TS only BUFFERPOOL BPid PIECESIZE <size>g -- Non-partitioned indexes only COPY NO -- BP0, or Buffer pool designated for VDR CREATE UNIQUE INDEX IX_DOCREF_A ON DOC_REF RPT_ID RPT_VERSION_ID_CMP STARTING_PAGE_NUM BUFFERPOOL BPid ASC, ASC, ASC -- by default SYSDEFLT -- BP0, or Buffer pool designated for VDR PIECESIZE <size>g -- Non-partitioned indexes only COPY NO CREATE INDEX IX_DOCREF_D ON DOC_REF RPT_ID RPT_VERSION_ID_CMP STARTING_PAGE_NUM DESC, DESC, DESC -- by default SYSDEFLT

17 BUFFERPOOL BPid -- BP0, or Buffer pool designated for VDR COPY NO CREATE GLOBAL TEMPORARY TABLE TEMP_TOPIC_VALUE DOC_ID numeric19,8 not null, TOPIC_ID char10 not null, TOPIC_DATA_TYPE smallint not null, JOIN_GROUP smallint not null, PAGE_OF_DOC integer not null, LINE_OF_PAGE integer not null, TOPIC_VALUE varchar255 not null CCSID EBCDIC COMMIT --================================================================== --================================================================== -- Annotation DBMS objects --================================================================== ** Tablespaces DB2 V8: If you are accessing a DB2 V8 subsystem, both simple and partitioned table spaces can still be created however, you may wish to consider defining non-partitioned table spaces as segmented using the SEGSIZE parameter as discussed below. SEGSIZE cannot be used with NUMPARTS in V8 universal table spaces/option MAXPARTITIONS are not available. If any of your table spaces are partitioned, you may also choose to use table-controlled partitioning as shown below. DB2 V9 or later: As of DB2 V9, range-partitioned universal table spaces are recommended for most large ViewDirect table spaces, as long as your data provides a key that will result in even data distribution. This may not be possible with annotation tables. NUMPARTS, Number of partitions, , varies with page size, DSSIZE, extended addressability SEGSIZE, Pages per segment, 4-64 multiple of 4 large, partitioned table spaces >128 pages typically have SEGSIZE 64 MEMBER CLUSTER, With data sharing, optional do not specify for segmented table space Partition definition: NUMPARTS 256 Desired number of partitions

18 LOCKPART YES -- or alternate USING parameters for partitions -- MEMBER CLUSTER is optional, data sharing environment only PART 1 USING... MEMBER CLUSTER, PART 2 USING... MEMBER CLUSTER,... PART 256 USING... MEMBER CLUSTER Otherwise, partition-by-growth table spaces are recommended for table spaces that are expected to be large: MAXPARTITIONS, Maximum number of growth partitions, varies with page size, DSSIZE DSSIZE, Maximum partition size, 1,2,4,8,16,32,64G SEGSIZE, Pages per segment, 4-64 multiple of 4 large, partitioned table spaces >128 pages typically have SEGSIZE 64 MEMBER CLUSTER, With data sharing, optional do not specify for segmented table space Table-controlled rather than index-controlled partitioning is required for use with range-partitioned and partition-by-growth table spaces. Segmented table space definitions are provided for smaller table spaces however, if you project limited use of annotation support, the table spaces below may also be defined as segmented: select a SEGSIZE value approximately equal to but not less than the expected size of the table. The NUMPARTS, MAXPARTITIONS, and MEMBER CLUSTER parameters should not be specified for segmented table spaces. Table space VDRANNO should be defined as a segmented type. Sample definitions are provided below customize for your installation data requirements. Consult DB2 documentation for further details. -- DROP TABLESPACE VDRMVSxx.VDRANNO -- COMMIT CREATE TABLESPACE VDRANNO IN VDRMVSxx USING -- VCAT VDRCATLG STOGROUP VDRGRPid ERASE YES/NO PCTFREE 5 SEGSIZE 4 -- Pages per segment, 4-64 multiple of 4 CCSID EBCDIC

19 -- DROP TABLESPACE VDRMVSxx.VDRANDA -- COMMIT CREATE TABLESPACE VDRANDA -- DSSIZE nng -- Maximum partition size nnn GB -- may be 1,2,4 Prior to DFSMS may be 1,2,4,8,16,32,64 DFSMS 1.5 or later IN VDRMVSxx USING -- VCAT VDRCATLG STOGROUP VDRGRPid ERASE YES/NO PCTFREE 5 SEGSIZE Segment size, pages, 4-64 multiple of 4 -- Either NUMPARTS range-partitioned UTS/LOCKPART -- NUMPARTS Varies with page size, DSSIZE -- LOCKPART YES -- Or maxpartitions partition by growth UTS -- MAXPARTITIONS # -- Maximum number of growth partitions, varies with page size, DSSIZE -- Or SEGSIZE alone above for small, segmented table space CCSID EBCDIC -- DROP TABLESPACE VDRMVSxx.VDRANDT -- COMMIT CREATE TABLESPACE VDRANDT IN VDRMVSxx -- DSSIZE nng -- Maximum partition size nnn GB -- may be 1,2,4 Prior to DFSMS may be 1,2,4,8,16,32,64 DFSMS 1.5 or later USING -- VCAT VDRCATLG STOGROUP VDRGRPid ERASE YES/NO PCTFREE 5 SEGSIZE Segment size, pages, 4-64 multiple of 4 -- Either NUMPARTS range-partitioned UTS/LOCKPART -- NUMPARTS Varies with page size, DSSIZE -- LOCKPART YES -- Or maxpartitions partition by growth UTS -- MAXPARTITIONS # -- Maximum number of growth partitions, varies with page size, DSSIZE -- Or SEGSIZE alone above for small, segmented table space CCSID EBCDIC

20 -- DROP TABLESPACE VDRMVSxx.VDRANPG -- COMMIT CREATE TABLESPACE VDRANPG IN VDRMVSxx -- DSSIZE nng -- Maximum partition size nnn GB -- may be 1,2,4 Prior to DFSMS may be 1,2,4,8,16,32,64 DFSMS 1.5 or later USING -- VCAT VDRCATLG STOGROUP VDRGRPid ERASE YES/NO PCTFREE 5 SEGSIZE Segment size, pages, 4-64 multiple of 4 -- Either NUMPARTS range-partitioned UTS/LOCKPART -- NUMPARTS Varies with page size, DSSIZE -- LOCKPART YES -- Or maxpartitions partition by growth UTS -- MAXPARTITIONS # -- Maximum number of growth partitions, varies with page size, DSSIZE -- Or SEGSIZE alone above for small, segmented table space CCSID EBCDIC ** Tables & Indexes CREATE TABLE ANNOTATION_CTL VERSION SMALLINT NOT NULL, SCALE_FACTOR SMALLINT NOT NULL, ROTATION_FACTOR INTEGER NOT NULL, XDIMENSION SMALLINT NOT NULL, YDIMENSION SMALLINT NOT NULL, EXT_ATTR VARCHAR64 IN VDRMVSxx.VDRANNO INSERT INTO ANNOTATION_CTL VERSION, SCALE_FACTOR, ROTATION_FACTOR, XDIMENSION, YDIMENSION VALUES 2, 100, 0, 8, 12

21 CREATE TABLE ANNOTATION_DATA ANNOTATION_ID INTEGER NOT NULL, SEGMENT_ID INTEGER NOT NULL, DATA VARCHAR255 NOT NULL, EXT_ATTR VARCHAR64 IN VDRMVSxx.VDRANDA -- If range-partitioned only: -- ANNOTATION_ID may not provide effective data distribution -- select an appropriate key. -- PARTITION BY RANGE ANNOTATION_ID ASC PARTITION 1 ENDING AT 1000 INCLUSIVE, -- PARTITION 2 ENDING AT 2000 INCLUSIVE, PARTITION 1000 ENDING AT INCLUSIVE If partition-by-growth only: -- PARTITION BY SIZE -- EVERY nng -- Optional if specified must equal table space DSSIZE CREATE UNIQUE INDEX ANNOTATION_DATA_IX ON ANNOTATION_DATA ANNOTATION_ID, SEGMENT_ID -- CLUSTER -- PARTITIONED -- Valid for range-partitioned TS only CREATE TABLE ANNOTATION_DETAILS ANNOTATION_ID INTEGER NOT NULL, OBJECT_ID INTEGER NOT NULL, DATETIME_CREATED CHAR14 DEFAULT NULL, DATETIME_UPDATED CHAR14 DEFAULT NULL, RECIP_CREATED VARCHAR128 DEFAULT NULL, RECIP_UPDATED VARCHAR128 DEFAULT NULL, EXT_ATTR VARCHAR64 IN VDRMVSxx.VDRANDT -- If range-partitioned only: -- ANNOTATION_ID may not provide effective data distribution -- select an appropriate key. -- PARTITION BY RANGE --

22 -- ANNOTATION_ID ASC PARTITION 1 ENDING AT 1000 INCLUSIVE, -- PARTITION 2 ENDING AT 2000 INCLUSIVE, PARTITION 1000 ENDING AT INCLUSIVE If partition-by-growth only: -- PARTITION BY SIZE -- EVERY nng -- Optional if specified must equal table space DSSIZE CREATE UNIQUE INDEX ANNOTATION_DETS_IX ON ANNOTATION_DETAILS ANNOTATION_ID, OBJECT_ID -- CLUSTER -- PARTITIONED -- Valid for range-partitioned TS only CREATE TABLE ANNOTATION_PAGE ANNOTATION_ID INTEGER NOT NULL, ANNOTATION_TYPE INTEGER NOT NULL, RPT_ID CHAR10 NOT NULL, VERSION_ID CHAR14 NOT NULL, SECTION_ID CHAR45 NOT NULL, PAGE_NUMBER INTEGER NOT NULL, SUBPAGE_NUMBER INTEGER DEFAULT NULL, ABSOLUTE_PAGE_NUM INTEGER DEFAULT NULL, DATA_LENGTH INTEGER DEFAULT NULL, DATETIME_SAVED CHAR14 DEFAULT NULL, EXT_ATTR VARCHAR64 -- If range-partitioned only: -- ANNOTATION_ID may not provide effective data distribution -- select an appropriate key. -- PARTITION BY RANGE ANNOTATION_ID ASC PARTITION 1 ENDING AT 1000 INCLUSIVE, -- PARTITION 2 ENDING AT 2000 INCLUSIVE, PARTITION 1000 ENDING AT INCLUSIVE If partition-by-growth only: -- PARTITION BY SIZE -- EVERY nng -- Optional if specified must equal

23 -- -- table space DSSIZE IN VDRMVSxx.VDRANPG CREATE UNIQUE INDEX ANNOTATION_ID_IX ON ANNOTATION_PAGE ANNOTATION_ID -- CLUSTER -- PARTITIONED -- Valid for range-partitioned TS only CREATE UNIQUE INDEX ANNOTATION_PAGE_IX ON ANNOTATION_PAGE RPT_ID, VERSION_ID, SECTION_ID, PAGE_NUMBER, SUBPAGE_NUMBER, ANNOTATION_TYPE COMMIT --================================================================== -- Overlay DBMS objects --================================================================== ** Tablespaces DB2 V8: If you are accessing a DB2 V8 subsystem, both simple and partitioned table spaces can still be created however, you may wish to consider defining non-partitioned table spaces as segmented using the SEGSIZE parameter as discussed below. SEGSIZE cannot be used with NUMPARTS in V8 universal table spaces/option MAXPARTITIONS are not available. If any of your table spaces are partitioned, you may also choose to use table-controlled partitioning as shown below. DB2 V9 or later: As of DB2 V9, range-partitioned universal table spaces are recommended for most large ViewDirect table spaces, as long as your data provides a key that will result in even data

24 distribution. This may not be possible with overlay tables. NUMPARTS, Number of partitions, , varies with page size, DSSIZE, extended addressability SEGSIZE, Pages per segment, 4-64 multiple of 4 large, partitioned table spaces >128 pages typically have SEGSIZE 64 MEMBER CLUSTER, With data sharing, optional do not specify for segmented table space Partition definition: NUMPARTS 256 Desired number of partitions LOCKPART YES -- or alternate USING parameters for partitions -- MEMBER CLUSTER is optional, data sharing environment only PART 1 USING... MEMBER CLUSTER, PART 2 USING... MEMBER CLUSTER,... PART 256 USING... MEMBER CLUSTER Otherwise, partition-by-growth table spaces are recommended for table spaces that are expected to be large: MAXPARTITIONS, Maximum number of growth partitions, varies with page size, DSSIZE DSSIZE, Maximum partition size, 1,2,4,8,16,32,64G SEGSIZE, Pages per segment, 4-64 multiple of 4 large, partitioned table spaces >128 pages typically have SEGSIZE 64 MEMBER CLUSTER, With data sharing, optional do not specify for segmented table space Table-controlled rather than index-controlled partitioning is required for use with range-partitioned and partition-by-growth table spaces. Segmented table space definitions are provided for smaller table spaces however, if you project limited use of overlay support, the table spaces below may also be defined as segmented: select a SEGSIZE value approximately equal to but not less than the expected size of the table. The NUMPARTS, MAXPARTITIONS, and MEMBER CLUSTER parameters should not be specified for segmented table spaces. Sample definitions are provided below customize for your installation data requirements. Consult DB2 documentation for further details. -- DROP TABLESPACE VDRMVSxx.VDROVAR -- COMMIT CREATE TABLESPACE VDROVAR

25 -- DSSIZE nng -- Maximum partition size nnn GB -- may be 1,2,4 Prior to DFSMS may be 1,2,4,8,16,32,64 DFSMS 1.5 or later IN VDRMVSxx USING -- VCAT VDRCATLG STOGROUP VDRGRPid ERASE YES/NO PCTFREE 5 SEGSIZE Segment size, pages, 4-64 multiple of 4 -- Either NUMPARTS range-partitioned UTS/LOCKPART -- NUMPARTS Varies with page size, DSSIZE -- LOCKPART YES -- Or maxpartitions partition by growth UTS -- MAXPARTITIONS # -- Maximum number of growth partitions, varies with page size, DSSIZE -- Or SEGSIZE alone above for small, segmented table space CCSID EBCDIC -- DROP TABLESPACE VDRMVSxx.VDROVRL -- COMMIT CREATE TABLESPACE VDROVRL -- DSSIZE nng -- Maximum partition size nnn GB -- may be 1,2,4 Prior to DFSMS may be 1,2,4,8,16,32,64 DFSMS 1.5 or later IN VDRMVSxx USING -- VCAT VDRCATLG STOGROUP VDRGRPid ERASE YES/NO PCTFREE 5 SEGSIZE Segment size, pages, 4-64 multiple of 4 -- Either NUMPARTS range-partitioned UTS/LOCKPART -- NUMPARTS Varies with page size, DSSIZE -- LOCKPART YES -- Or maxpartitions partition by growth UTS -- MAXPARTITIONS # -- Maximum number of growth partitions, varies with page size, DSSIZE -- Or SEGSIZE alone above for small, segmented table space CCSID EBCDIC -- DROP TABLESPACE VDRMVSxx.VDROVFI -- COMMIT CREATE TABLESPACE VDROVFI -- DSSIZE nng -- Maximum partition size nnn GB -- may be 1,2,4 Prior to DFSMS 1.5

26 -- may be 1,2,4,8,16,32,64 DFSMS 1.5 or later IN VDRMVSxx USING -- VCAT VDRCATLG STOGROUP VDRGRPid ERASE YES/NO PCTFREE 5 SEGSIZE Segment size, pages, 4-64 multiple of 4 -- Either NUMPARTS range-partitioned UTS/LOCKPART -- NUMPARTS Varies with page size, DSSIZE -- LOCKPART YES -- Or maxpartitions partition by growth UTS -- MAXPARTITIONS # -- Maximum number of growth partitions, varies with page size, DSSIZE -- Or SEGSIZE alone above for small, segmented table space CCSID EBCDIC ** Tables & Indexes CREATE TABLE OVR_RULE RPT_ID CHAR10 NOT NULL, VERSION_ID CHAR14 NOT NULL, SECTION_ID CHAR45 NOT NULL, START_PAGE INTEGER NOT NULL, FREQ INTEGER NOT NULL, OVERLAY_ID INTEGER NOT NULL, TYPE SMALLINT DEFAULT NULL, X_ORIG INTEGER DEFAULT NULL, Y_ORIG INTEGER DEFAULT NULL, X_SIZE_N INTEGER DEFAULT NULL, X_SIZE_D INTEGER DEFAULT NULL, Y_SIZE_N INTEGER DEFAULT NULL, Y_SIZE_D INTEGER DEFAULT NULL, ROTATION SMALLINT DEFAULT NULL, X_OFFSET SMALLINT DEFAULT NULL, Y_OFFSET SMALLINT DEFAULT NULL, PRIORITY SMALLINT DEFAULT NULL, ODATETIME INTEGER DEFAULT NULL, OWNER VARCHAR128 DEFAULT NULL, EXT_ATTR VARCHAR64 IN VDRMVSxx.VDROVRL -- If range-partitioned only: -- OVERLAY_ID may not provide effective data distribution -- select an appropriate key. -- PARTITION BY RANGE OVERLAY_ID ASC PARTITION 1 ENDING AT 1000 INCLUSIVE, -- PARTITION 2 ENDING AT 2000 INCLUSIVE, PARTITION 1000 ENDING AT INCLUSIVE

27 -- -- If partition-by-growth only: -- PARTITION BY SIZE -- EVERY nng -- Optional if specified must equal table space DSSIZE CREATE UNIQUE INDEX OVR_RULE_SEC_IX ON OVR_RULE RPT_ID, VERSION_ID, SECTION_ID, START_PAGE, FREQ CREATE INDEX OVR_RULE_ID_IX ON OVR_RULE OVERLAY_ID -- CLUSTER -- One clustering index per table space -- PARTITIONED -- Valid for range-partitioned TS only CREATE INDEX OVR_RULE_RPT_IX ON OVR_RULE RPT_ID -- CLUSTER -- One clustering index per table space CREATE TABLE OVR_FILE OVERLAY_ID INTEGER NOT NULL, FILE_NAME VARCHAR255 DEFAULT NULL, EXT_ATTR VARCHAR64 IN VDRMVSxx.VDROVFI -- If range-partitioned only: -- OVERLAY_ID may not provide effective data distribution -- select an appropriate key. -- PARTITION BY RANGE

28 -- -- OVERLAY_ID ASC PARTITION 1 ENDING AT 1000 INCLUSIVE, -- PARTITION 2 ENDING AT 2000 INCLUSIVE, PARTITION 1000 ENDING AT INCLUSIVE If partition-by-growth only: -- PARTITION BY SIZE -- EVERY nng -- Optional if specified must equal table space DSSIZE CREATE UNIQUE INDEX OVER_FILE_ID_IX ON OVR_FILE OVERLAY_ID -- CLUSTER -- PARTITIONED -- Valid for range-partitioned TS only CREATE TABLE OVR_ARCHIVE OVERLAY_ID INTEGER NOT NULL, RPT_ID CHAR10 NOT NULL, VERSION_ID CHAR14 NOT NULL, SECTION_ID CHAR45 NOT NULL, PAGE INTEGER NOT NULL, SUB_PAGE INTEGER DEFAULT NULL, EXT_ATTR VARCHAR64 IN VDRMVSxx.VDROVAR -- If range-partitioned only: -- OVERLAY_ID may not provide effective data distribution -- select an appropriate key. -- PARTITION BY RANGE OVERLAY_ID ASC PARTITION 1 ENDING AT 1000 INCLUSIVE, -- PARTITION 2 ENDING AT 2000 INCLUSIVE, PARTITION 1000 ENDING AT INCLUSIVE If partition-by-growth only: -- PARTITION BY SIZE -- EVERY nng -- Optional if specified must equal table space DSSIZE

29 CREATE UNIQUE INDEX OVR_ARCH_ID_IX ON OVR_ARCHIVE OVERLAY_ID -- PARTITIONED -- Valid for range-partitioned TS only -- CLUSTER -- One clustering index per table space CREATE INDEX OVR_ARCH_SEC_IX ON OVR_ARCHIVE RPT_ID, VERSION_ID, SECTION_ID, PAGE CREATE INDEX OVR_ARCH_VER_IX ON OVR_ARCHIVE RPT_ID, VERSION_ID -- CLUSTER -- One clustering index per table space COMMIT --================================================================== -- Page lock DBMS objects --================================================================== ** Tablespaces As of DB2 V9, segmented table spaces with SEGSIZE 4 are recommended for page lock data. -- DROP TABLESPACE VDRMVSxx.VDRPGLK -- COMMIT

30 CREATE TABLESPACE VDRPGLK IN VDRMVSxx USING -- VCAT VDRCATLG STOGROUP VDRGRPid ERASE YES/NO SEGSIZE 4 -- Pages per segment, 4-64 multiple of 4. CCSID EBCDIC PCTFREE 5 ** Tables & Indexes CREATE TABLE PAGE_LOCKS LRPT_ID CHAR10 NOT NULL, LVERSION_ID CHAR14 NOT NULL, LSECTION_ID CHAR45 NOT NULL, LPAGE_NUMBER INTEGER NOT NULL, LSUBPAGE_NUMBER INTEGER NOT NULL, LLOCK_TYPE INTEGER NOT NULL, LDATETIME CHAR14 DEFAULT NULL, LRECIP_ID VARCHAR128 DEFAULT NULL, EXT_ATTR VARCHAR64 DEFAULT NULL IN VDRMVSxx.VDRPGLK CREATE UNIQUE INDEX PAGE_LCKS_IX ON PAGE_LOCKS LRPT_ID, LVERSION_ID, LSECTION_ID, LPAGE_NUMBER, LSUBPAGE_NUMBER, LLOCK_TYPE -- CLUSTER COMMIT --================================================================== -- Retention Change event DBMS object --================================================================== ** Tablespaces

31 DB2 V8: If you are accessing a DB2 V8 subsystem, both simple and partitioned table spaces can still be created however, you may wish to consider defining non-partitioned table spaces as segmented using the SEGSIZE parameter as discussed below. SEGSIZE cannot be used with NUMPARTS in V8 universal table spaces/option MAXPARTITIONS are not available. If any of your table spaces are partitioned, you may also choose to use table-controlled partitioning as shown below. DB2 V9 or later: As of DB2 V9, range-partitioned universal table spaces are recommended for most large ViewDirect table spaces, as long as your data provides a key that will result in even data distribution. NUMPARTS, Number of partitions, , varies with page size, DSSIZE, extended addressability SEGSIZE, Pages per segment, 4-64 multiple of 4 large, partitioned table spaces >128 pages typically have SEGSIZE 64 MEMBER CLUSTER, With data sharing, optional do not specify for segmented table space Partition definition: NUMPARTS 256 Desired number of partitions LOCKPART YES -- or alternate USING parameters for partitions -- MEMBER CLUSTER is optional, data sharing environment only PART 1 USING... MEMBER CLUSTER, PART 2 USING... MEMBER CLUSTER,... PART 256 USING... MEMBER CLUSTER Otherwise, partition-by-growth table spaces are recommended for table spaces that are expected to be large: MAXPARTITIONS, Maximum number of growth partitions, varies with page size, DSSIZE DSSIZE, Maximum partition size, 1,2,4,8,16,32,64G SEGSIZE, Pages per segment, 4-64 multiple of 4 large, partitioned table spaces >128 pages typically have SEGSIZE 64 MEMBER CLUSTER, With data sharing, optional do not specify for segmented table space Table-controlled rather than index-controlled partitioning is required for use with range-partitioned and partition-by-growth table spaces. Segmented table space definitions are provided for smaller table spaces however, if you project limited use of RM support, the table spaces below may also be defined as segmented: select a SEGSIZE value approximately equal to but not less than the expected size of the table. The NUMPARTS, MAXPARTITIONS,

32 and MEMBER CLUSTER parameters should not be specified for segmented table spaces. Sample definitions are provided below customize for your installation data requirements. Consult DB2 documentation for further details. -- DROP TABLESPACE VDRMVSxx.RETCHGTS -- COMMIT CREATE TABLESPACE RETCHGTS -- for RET_CHG table -- DSSIZE nnng -- Maximum partition size nnn GB -- may be 1,2,4 prior to DFSMS may be 1,2,4,8,16,32,64 DFSMS 1.5 or later IN VDRMVSxx -- by default DSNDB04 -- by default SYSDEFLT -- YES for security purposes FREEPAGE 1 PCTFREE 0 TRACKMOD YES BUFFERPOOL BPid -- BP0, or Buffer pool designated for VDR -- MEMBER CLUSTER -- Optional for data sharing only. Do not specify for segmented table space. SEGSIZE Segment size, pages, 4-64 multiple of 4 -- Either NUMPARTS range-partitioned UTS/LOCKPART -- NUMPARTS Varies with page size, DSSIZE -- LOCKPART YES -- Or maxpartitions partition by growth UTS -- MAXPARTITIONS # -- Maximum number of growth partitions, varies with page size, DSSIZE -- Or SEGSIZE alone above for small, segmented table space LOCKSIZE ANY LOCKMAX SYSTEM COMPRESS YES CCSID EBCDIC MAXROWS 255 ** Table follows: CREATE TABLE TOPIC_RET_CHG RPT_ID CHAR10 not null, RPT_VERSION_CMP CHAR14 not null, ORIGINAL_PAGE_NUM INTEGER not null, SECTION_ID CHAR30 not null, PAGE_OFFSET INTEGER default 0,

33 NUMBER_OF_PAGES INTEGER not null, DOC_REF_ID NUMERIC19,8 default 0, PAGE_OF_DOC INTEGER default -1, LINE_OF_PAGE INTEGER default -1, ITEM_ARCH_EXP CHAR1 default 'N', ITEM_STATUS CHAR1 default 'N', ITEM_N_RET_DATE CHAR8 not null, ITEM_EVENT_DATE CHAR14 not null, ITEM_REASON VARCHAR255 not null, ITEM_TYPE VARCHAR255 not null, ITEM_DESC VARCHAR255 not null, ITEM_REASON_UC VARCHAR255, ITEM_TYPE_UC VARCHAR255, ITEM_DESC_UC VARCHAR255 IN VDRMVSxx.RETCHGTS -- If range-partitioned only: -- PARTITION BY RANGE DOC_REF_ID ASC PARTITION 1 ENDING AT INCLUSIVE, -- PARTITION 2 ENDING AT INCLUSIVE, PARTITION 1000 ENDING AT INCLUSIVE If partition-by-growth only: -- PARTITION BY SIZE -- EVERY nng -- Optional if specified must equal table space DSSIZE -- Indexes follow: CREATE INDEX IX_RETCHG_PK_A ON TOPIC_RET_CHG DOC_REF_ID ASC, PAGE_OF_DOC ASC -- by default SYSDEFLT -- CLUSTER -- PARTITIONED -- Valid for range-partitioned TS only BUFFERPOOL BPid -- BP0, or Buffer pool designated for VDR PIECESIZE <size>g -- 2, or other valid size, as desired -- Non-partitioned indexes only COPY NO CREATE INDEX IX_RETCHG_PK_D

34 ON TOPIC_RET_CHG DOC_REF_ID PAGE_OF_DOC BUFFERPOOL BPid PIECESIZE DESC, DESC -- by default SYSDEFLT -- BP0, or Buffer pool designated for VDR <size>g -- 2, or other valid size, as desired -- Non-partitioned indexes only COPY NO CREATE INDEX IX_RETCHG_DR_A ON TOPIC_RET_CHG RPT_ID ASC, RPT_VERSION_CMP ASC, ORIGINAL_PAGE_NUM ASC -- by default SYSDEFLT BUFFERPOOL BPid -- BP0, or Buffer pool designated for VDR PIECESIZE <size>g -- 2, or other valid size, as desired -- Non-partitioned indexes only COPY NO CREATE INDEX IX_RETCHG_DR_D ON TOPIC_RET_CHG RPT_ID DESC, RPT_VERSION_CMP DESC, ORIGINAL_PAGE_NUM DESC -- by default SYSDEFLT BUFFERPOOL BPid PIECESIZE -- BP0, or Buffer pool designated for VDR <size>g -- 2, or other valid size, as desired -- Non-partitioned indexes only

35 COPY NO CREATE INDEX IX_RETCHG_RSN ON TOPIC_RET_CHG ITEM_REASON BUFFERPOOL BPid PIECESIZE ASC -- by default SYSDEFLT -- BP0, or Buffer pool designated for VDR <size>g -- 2, or other valid size, as desired -- Non-partitioned indexes only NO COPY NOT PADDED CREATE INDEX IX_RETCHG_RSN_UC ON TOPIC_RET_CHG ITEM_REASON_UC BUFFERPOOL BPid PIECESIZE ASC -- by default SYSDEFLT -- BP0, or Buffer pool designated for VDR <size>g -- 2, or other valid size, as desired -- Non-partitioned indexes only NO COPY NOT PADDED CREATE INDEX IX_RETCHG_TP ON TOPIC_RET_CHG ITEM_TYPE ASC -- by default SYSDEFLT BUFFERPOOL BPid -- BP0, or Buffer pool designated for VDR

36 CLOSE PIECESIZE YES <size>g -- 2, or other valid size, as desired -- Non-partitioned indexes only NO COPY NOT PADDED CREATE INDEX IX_RETCHG_TP_UC ON TOPIC_RET_CHG ITEM_TYPE_UC ASC -- by default SYSDEFLT BUFFERPOOL BPid -- BP0, or Buffer pool designated for VDR PIECESIZE <size>g -- 2, or other valid size, as desired -- Non-partitioned indexes only COPY NO NOT PADDED CREATE INDEX IX_RETCHG_RTD_A ON TOPIC_RET_CHG ITEM_N_RET_DATE ASC -- by default SYSDEFLT BUFFERPOOL BPid -- BP0, or Buffer pool designated for VDR PIECESIZE <size>g -- 2, or other valid size, as desired -- Non-partitioned indexes only COPY NO CREATE INDEX IX_RETCHG_RTD_D ON TOPIC_RET_CHG ITEM_N_RET_DATE DESC -- by default SYSDEFLT

37 BUFFERPOOL BPid -- BP0, or Buffer pool designated for VDR PIECESIZE <size>g -- 2, or other valid size, as desired -- Non-partitioned indexes only COPY NO CREATE INDEX IX_RETCHG_RTD ON TOPIC_RET_CHG DOC_REF_ID ASC, PAGE_OF_DOC ASC, ITEM_N_RET_DATE DESC -- by default SYSDEFLT BUFFERPOOL BPid -- BP0, or Buffer pool designated for VDR PIECESIZE <size>g -- 2, or other valid size, as desired -- Non-partitioned indexes only COPY NO CREATE INDEX IX_RETCHG_EVD_A ON TOPIC_RET_CHG ITEM_EVENT_DATE ASC -- by default SYSDEFLT BUFFERPOOL BPid -- BP0, or Buffer pool designated for VDR PIECESIZE <size>g -- 2, or other valid size, as desired -- Non-partitioned indexes only COPY NO CREATE INDEX IX_RETCHG_EVD_D ON TOPIC_RET_CHG ITEM_EVENT_DATE DESC -- by default SYSDEFLT

38 BUFFERPOOL BPid -- BP0, or Buffer pool designated for VDR PIECESIZE <size>g -- 2, or other valid size, as desired -- Non-partitioned indexes only COPY NO CREATE INDEX IX_RETCHG_DESC ON TOPIC_RET_CHG ITEM_DESC ASC -- by default SYSDEFLT BUFFERPOOL BPid -- BP0, or Buffer pool designated for VDR PIECESIZE <size>g -- 2, or other valid size, as desired -- Non-partitioned indexes only COPY NO NOT PADDED CREATE INDEX IX_RETCHG_DESC_UC ON TOPIC_RET_CHG ITEM_DESC_UC ASC -- by default SYSDEFLT BUFFERPOOL BPid -- BP0, or Buffer pool designated for VDR PIECESIZE <size>g -- 2, or other valid size, as desired -- Non-partitioned indexes only COPY NO NOT PADDED -- End of indexes. -- The following section generates triggers for CPCI topics. -- A single insert trigger is generated for the table that creates -- an upper-cased column for all the CPCI topics in the table. -- Then a separate update trigger is generated for each CPCI topic -- in the table to update the upper-cased column for the topic. -- Do not change or remove the following line that changes the SQL terminator. --#SET TERMINATOR!

39 -- Generate the insert trigger for the table. CREATE TRIGGER TRINS_RET_CHG NO CASCADE BEFORE INSERT ON TOPIC_RET_CHG REFERENCING NEW AS N FOR EACH ROW MODE DB2SQL BEGIN ATOMIC SET N.ITEM_REASON_UC = UPPERN.ITEM_REASON SET N.ITEM_TYPE_UC = UPPERN.ITEM_TYPE SET N.ITEM_DESC_UC = UPPERN.ITEM_DESC END! -- Do not change or remove the following line that changes the SQL terminator. --#SET TERMINATOR -- Generate an update trigger for each CPCI column. CREATE TRIGGER TRUPD_RET_CHG_REASON NO CASCADE BEFORE UPDATE OF ITEM_REASON ON TOPIC_RET_CHG REFERENCING NEW AS N FOR EACH ROW MODE DB2SQL SET N.ITEM_REASON_UC = UPPERN.ITEM_REASON CREATE TRIGGER TRUPD_RET_CHG_TYPE NO CASCADE BEFORE UPDATE OF ITEM_TYPE ON TOPIC_RET_CHG REFERENCING NEW AS N FOR EACH ROW MODE DB2SQL SET N.ITEM_TYPE_UC = UPPERN.ITEM_TYPE CREATE TRIGGER TRUPD_RET_CHG_DESC NO CASCADE BEFORE UPDATE OF ITEM_DESC ON TOPIC_RET_CHG REFERENCING NEW AS N FOR EACH ROW MODE DB2SQL SET N.ITEM_DESC_UC = UPPERN.ITEM_DESC COMMIT --================================================================== --================================================================== -- DBMS objects for each Topic being created --==================================================================

40 ** Tablespace DB2 V8: If you are accessing a DB2 V8 subsystem, both simple and partitioned table spaces can still be created however, you may wish to consider defining non-partitioned table spaces as segmented using the SEGSIZE parameter as discussed below. SEGSIZE cannot be used with NUMPARTS in V8 universal table spaces/option MAXPARTITIONS are not available. If any of your table spaces are partitioned, you may also choose to use table-controlled partitioning as shown below. DB2 V9 or later: As of DB2 V9, range-partitioned universal table spaces are recommended for most large ViewDirect table spaces, as long as your data provides a key that will result in even data distribution. This may not be possible with all topic tables. NUMPARTS, Number of partitions, , varies with page size, DSSIZE, extended addressability SEGSIZE, Pages per segment, 4-64 multiple of 4 large, partitioned table spaces >128 pages typically have SEGSIZE 64 MEMBER CLUSTER, With data sharing, optional do not specify for segmented table space Partition definition: NUMPARTS 256 Desired number of partitions LOCKPART YES -- or alternate USING parameters for partitions -- MEMBER CLUSTER is optional, data sharing environment only PART 1 USING... MEMBER CLUSTER, PART 2 USING... MEMBER CLUSTER,... PART 256 USING... MEMBER CLUSTER Otherwise, partition-by-growth table spaces are recommended for table spaces that are expected to be large: MAXPARTITIONS, Maximum number of growth partitions, varies with page size, DSSIZE DSSIZE, Maximum partition size, 1,2,4,8,16,32,64G SEGSIZE, Pages per segment, 4-64 multiple of 4 large, partitioned table spaces >128 pages typically have SEGSIZE 64 MEMBER CLUSTER, With data sharing, optional do not specify for segmented table space Table-controlled rather than index-controlled partitioning is required for use with range-partitioned and partition-by-growth table spaces. If you expect a topic table to be small, the table space below may also be defined as segmented: select a SEGSIZE value

41 approximately equal to but not less than the expected size of the table. The NUMPARTS, MAXPARTITIONS, and MEMBER CLUSTER parameters should not be specified for segmented table spaces. Sample definitions are provided below customize for your installation data requirements. Consult DB2 documentation for further details. -- DROP TABLESPACE VDRMVSxx.TPCxxxTS -- COMMIT CREATE TABLESPACE TPCxxxTS -- for TOPIC_<TABLE_SUFFIX> table IN VDRMVSxx PRIQTY <size> SECQTY <size> FREEPAGE 1 PCTFREE 0 TRACKMOD YES -- DSSIZE nng -- Maximum partition size nn GB -- 1,2, 4 Prior to DFSMS ,2,4,8,16,32,64 DFSMS 1.5 or later BUFFERPOOL BPid -- MEMBER CLUSTER -- Data sharing only optional. Do not specify for segmented table space. SEGSIZE Segment size, pages, 4-64 multiple of Either NUMPARTS range-partitioned UTS/LOCKPART -- NUMPARTS Varies with page size, DSSIZE -- LOCKPART YES -- Or maxpartitions partition by growth UTS -- MAXPARTITIONS # -- Maximum number of growth partitions, varies with page size, DSSIZE -- Or SEGSIZE alone above for small, segmented table space -- LOCKSIZE ANY LOCKMAX SYSTEM CCSID EBCDIC MAXROWS 255 ** Table & Indexes -- Topic Item table definition CREATE TABLE TOPIC_<TABLE_SUFFIX> DOC_ID NUMERIC19,8 not null, PAGE_OF_DOC INTEGER not null, LINE_OF_PAGE INTEGER not null default -1,

42 ITEM_<COLUMN_SUFFIX> <VALUE_TYPE> not null, --<BEGIN_CPCI_COLUMNS> - Do not remove or change this line. ITEM_<COLUMN_SUFFIX>_UC <VALUE_TYPE> --<END_CPCI_COLUMNS> - Do not remove or change this line. in VDRMVSxx.TPCxxxTS -- If range-partitioned only: -- PARTITION BY RANGE -- ITEM_<COLUMN_SUFFIX> ASC -- Select a suitable key. If an appropriate key is not available, use a partition-by-growth table space PARTITION 1 ENDING AT 'A' INCLUSIVE, -- PARTITION 2 ENDING AT 'B' INCLUSIVE, PARTITION 26 ENDING AT 'Z' INCLUSIVE If partition-by-growth only: -- PARTITION BY SIZE -- EVERY nng -- Optional if specified must equal table space DSSIZE CREATE INDEX IXI_<TABLE_SUFFIX> ON TOPIC_<TABLE_SUFFIX> DOC_ID ASC, PAGE_OF_DOC ASC, LINE_OF_PAGE ASC PRIQTY <size> SECQTY <size> -- PARTITIONED -- Valid for partitioned TS only -- CLUSTER -- One clustering index per table space BUFFERPOOL BPid PIECESIZE <size> G COPY NO --<BEGIN_COLUMN_INDICIES> - Do not remove or change this line. CREATE INDEX IXV_<TABLE_SUFFIX> ON TOPIC_<TABLE_SUFFIX> ITEM_<COLUMN_SUFFIX> ASC PRIQTY <size> SECQTY <size>

43 BUFFERPOOL BPid PIECESIZE <size> G COPY NO NOT PADDED -- PARTITIONED -- Valid for partitioned TS only -- CLUSTER -- One clustering index per table space --<END_COLUMN_INDICIES> - Do not remove or change this line. --<BEGIN_CPCI_SECTION> - Do not remove or change this line. --<BEGIN_COLUMN_INDICIES> - Do not remove or change this line. CREATE INDEX IXVUC_<TABLE_SUFFIX> ON TOPIC_<TABLE_SUFFIX> ITEM_<COLUMN_SUFFIX>_UC ASC PRIQTY <size> SECQTY BUFFERPOOL BPid PIECESIZE <size> G COPY NO NOT PADDED <size> --<END_COLUMN_INDICIES> - Do not remove or change this line. -- The following section generates triggers for CPCI topics. -- A single insert trigger is generated for the table that creates -- an upper-cased column for the CPCI topic. -- Then an update trigger is generated for the base topic item -- column to automatically update the upper-cased column for the -- topic item. CREATE TRIGGER TRINS_<TABLE_SUFFIX> NO CASCADE BEFORE INSERT ON TOPIC_<TABLE_SUFFIX> REFERENCING NEW AS N FOR EACH ROW MODE DB2SQL --<BEGIN_COLUMN_TRIGGERS> - Do not remove or change this line. SET N.ITEM_<COLUMN_SUFFIX>_UC = UPPERN.ITEM_<COLUMN_SUFFIX> --<END_COLUMN_TRIGGERS> - Do not remove or change this line. --<BEGIN_COLUMN_TRIGGERS> - Do not remove or change this line. CREATE TRIGGER TRUPD_<TABLE_SUFFIX> NO CASCADE BEFORE UPDATE OF

44 ITEM_<COLUMN_SUFFIX> ON TOPIC_<TABLE_SUFFIX> REFERENCING NEW AS N FOR EACH ROW MODE DB2SQL SET N.ITEM_<COLUMN_SUFFIX>_UC = UPPERN.ITEM_<COLUMN_SUFFIX> --<END_COLUMN_TRIGGERS> - Do not remove or change this line. --<END_CPCI_SECTION> - Do not remove or change this line. --================================================================== COMMIT --================================================================== --==================================================================== -- DBMS objects for each Topic being created - MH schema - wide tbl --==================================================================== ** Tablespace DB2 V8: If you are accessing a DB2 V8 subsystem, both simple and partitioned table spaces can still be created however, you may wish to consider defining non-partitioned table spaces as segmented using the SEGSIZE parameter as discussed below. SEGSIZE cannot be used with NUMPARTS in V8 universal table spaces/option MAXPARTITIONS are not available. If any of your table spaces are partitioned, you may also choose to use table-controlled partitioning as shown below. DB2 V9 or later: As of DB2 V9, range-partitioned universal table spaces are recommended for most large ViewDirect table spaces, as long as your data provides a key that will result in even data distribution. This may not be possible with all topic tables. NUMPARTS, Number of partitions, , varies with page size, DSSIZE, extended addressability SEGSIZE, Pages per segment, 4-64 multiple of 4 large, partitioned table spaces >128 pages typically have SEGSIZE 64 MEMBER CLUSTER, With data sharing, optional do not specify for segmented table space Partition definition: NUMPARTS 256 Desired number of partitions LOCKPART YES -- or alternate USING parameters for partitions -- MEMBER CLUSTER is optional, data sharing environment only PART 1 USING... MEMBER CLUSTER, PART 2 USING... MEMBER CLUSTER,... PART 256 USING... MEMBER CLUSTER

45 Otherwise, partition-by-growth table spaces are recommended for table spaces that are expected to be large: MAXPARTITIONS, Maximum number of growth partitions, varies with page size, DSSIZE DSSIZE, Maximum partition size, 1,2,4,8,16,32,64G SEGSIZE, Pages per segment, 4-64 multiple of 4 large, partitioned table spaces >128 pages typically have SEGSIZE 64 MEMBER CLUSTER, With data sharing, optional do not specify for segmented table space Table-controlled rather than index-controlled partitioning is required for use with range-partitioned and partition-by-growth table spaces. If you expect a topic table to be small, the table space below may also be defined as segmented: select a SEGSIZE value approximately equal to but not less than the expected size of the table. The NUMPARTS, MAXPARTITIONS, and MEMBER CLUSTER parameters should not be specified for segmented table spaces. Sample definitions are provided below customize for your installation data requirements. Consult DB2 documentation for further details. -- DROP TABLESPACE VDRMVSxx.TPCxxxTS -- COMMIT CREATE TABLESPACE TPCxxxTS -- for TOPIC_<TABLE_SUFFIX> table IN VDRMVSxx PRIQTY <size> SECQTY <size> FREEPAGE 1 PCTFREE 0 TRACKMOD YES -- DSSIZE nng -- Maximum partition size nn GB -- 1,2,4 Prior to DFSMS ,2,4,8,16,32,64 DFSMS1.5 or later BUFFERPOOL BPid -- MEMBER CLUSTER -- Data sharing only optional. Do not specify for segmented table space. SEGSIZE Segment size, pages, 4-64 multiple of Either NUMPARTS range-partitioned UTS/LOCKPART -- NUMPARTS Varies with page size, DSSIZE -- LOCKPART YES -- Or maxpartitions partition by growth UTS -- MAXPARTITIONS # -- Maximum number of growth partitions, varies with page size, DSSIZE

46 -- Or SEGSIZE alone above for small, segmented table space -- LOCKSIZE ANY LOCKMAX SYSTEM CCSID EBCDIC MAXROWS 255 ** Table & Indexes -- Topic Item table definition CREATE TABLE TOPIC_<TABLE_SUFFIX> RPT_ID CHAR10 not null, RPT_VERSION_CMP CHAR14 not null, ORIGINAL_PAGE_NUM INTEGER not null, SECTION_ID CHAR30 not null, PAGE_OFFSET INTEGER not null, NUMBER_OF_PAGES INTEGER not null, DOC_REF_ID NUMERIC19,8 not null, PAGE_OF_DOC INTEGER not null, LINE_OF_PAGE INTEGER not null default -1, ITEM_<COLUMN_SUFFIX> <VALUE_TYPE>, --<BEGIN_CPCI_COLUMNS> - Do not remove or change this line. ITEM_<COLUMN_SUFFIX>_UC <VALUE_TYPE>, --<END_CPCI_COLUMNS> - Do not remove or change this line. in VDRMVSxx.TPCxxxTS -- If range-partitioned only: -- PARTITION BY RANGE -- ITEM_<COLUMN_SUFFIX> ASC -- Select a suitable key. If an appropriate key is not available, use a partition-by-growth table space PARTITION 1 ENDING AT 'A' INCLUSIVE, -- PARTITION 2 ENDING AT 'B' INCLUSIVE, PARTITION 26 ENDING AT 'Z' INCLUSIVE If partition-by-growth only: -- PARTITION BY SIZE -- EVERY nng -- Optional if specified must equal table space DSSIZE CREATE INDEX IXI_<TABLE_SUFFIX> ON TOPIC_<TABLE_SUFFIX> DOC_REF_ID ASC PRIQTY <size> SECQTY <size>

47 BUFFERPOOL BPid PIECESIZE <size>g COPY NO -- PARTITIONED -- Valid for partitioned TS only -- CLUSTER -- One clustering index per table space CREATE INDEX IX_<TABLE_SUFFIX> ON TOPIC_<TABLE_SUFFIX> RPT_ID ASC, RPT_VERSION_CMP ASC, ORIGINAL_PAGE_NUM ASC -- by default SYSDEFLT PRIQTY <size> SECQTY <size> BUFFERPOOL BPid -- BP0, or Buffer pool designated for VDR PIECESIZE <size>g COPY NO --Create an index on each topic item in the row of the table --<BEGIN_COLUMN_INDICIES> - Do not remove or change this line. CREATE INDEX IXV_<TABLE_SUFFIX>_<COLUMN_SUFFIX> ON TOPIC_<TABLE_SUFFIX> ITEM_<COLUMN_SUFFIX> ASC PRIQTY <size> SECQTY <size> BUFFERPOOL BPid PIECESIZE <size>g COPY NO NOT PADDED -- PARTITIONED --<END_COLUMN_INDICIES> - Do not remove or change this line.

48 -- Begin section that is only generated for CPCI topics. --<BEGIN_CPCI_SECTION> - Do not remove or change this line. -- The following section marks start of repeating generation of -- indices for each upper-case CPCI topic item column. --<BEGIN_COLUMN_INDICIES> - Do not remove or change this line. CREATE INDEX IXVUC_<TABLE_SUFFIX>_<COLUMN_SUFFIX> ON TOPIC_<TABLE_SUFFIX> ITEM_<COLUMN_SUFFIX>_UC ASC PRIQTY <size> SECQTY <size> BUFFERPOOL BPid PIECESIZE <size>g COPY NO NOT PADDED --<END_COLUMN_INDICIES> - Do not remove or change this line. -- The following section generates triggers for CPCI topics. -- A single insert trigger is generated for the table that creates -- an upper-cased column for all the CPCI topics in the table. -- Then a separate update trigger is generated for each CPCI topic -- in the table to update the upper-cased column for the topic. -- Do not change or remove the following line that changes the SQL terminator. --#SET TERMINATOR! -- Generate the insert trigger for the table. CREATE TRIGGER TRINS_<TABLE_SUFFIX> NO CASCADE BEFORE INSERT ON TOPIC_<TABLE_SUFFIX> REFERENCING NEW AS N FOR EACH ROW MODE DB2SQL BEGIN ATOMIC -- Begin repeating section for each CPCI topic column. --<BEGIN_COLUMN_TRIGGERS> - Do not remove or change this line. SET N.ITEM_<COLUMN_SUFFIX>_UC = UPPERN.ITEM_<COLUMN_SUFFIX> --<END_COLUMN_TRIGGERS> - Do not remove or change this line. END! -- Do not change or remove the following line that changes the SQL terminator. --#SET TERMINATOR