db2bus for asg -rochade release notes · db2/alias db2/auxiliary-table db2/column db2/column-name...

Copyright © 2013 Reischmann Informatik GmbH and ASG GmbH & Co. KG, a wholly owned subsidiary of Allen Systems Group, Inc. All rights reserved. All names and products contained herein are the trademarks or registered trademarks of their respective holders.

1

DB2BUS for ASG-Rochade® Release Notes Version 10.02 for MVS and Windows January 4, 2013 DBB1100-1002

This publication describes all new features, changes and fixes of DB2BUS for ASG-Rochade introduced in this release.

Note: In this publication, the supported operating systems are referred to by these names:

- Windows denotes the operating systems Microsoft Windows XP, Vista, and 7.

- MVS denotes the operating system IBM z/OS.

1 ISP and Service Packs ASG encourages you to visit http://www.asg.com/support/support.asp and sign onto the Intelligent Support Portal (ISP) to verify whether any product or documentation revisions, new maintenance, or service packs apply to this release of the product or its accompanying documentation.

2 Product Information DB2BUS is the ASG-Rochade Bus Interface for re-engineering DB2 objects from the DB2 Catalog into ASG's Rochade Repository. It supports IBM DB2 for z/OS versions 4, 5, 6, 7, 8, 9 and 10.

Additionally, the generation of DDL statements (CREATE ALIAS, CREATE DATABASE, CREATE DISTINCT TYPE, CREATE INDEX, CREATE STOGROUP, CREATE SYNONYM, CREATE TABLE, CREATE TABLESPACE, CREATE VIEW, CREATE TRIGGER, CREATE SEQUENCE, CREATE AUXILIARY TABLE) from the ASG-Rochade Repository is supported.

DB2BUS for ASG-Rochade Release Notes

2

DB2BUS supports these item types:

- DB2/ALIAS DB2/AUXILIARY-TABLE DB2/COLUMN DB2/COLUMN-NAME DB2/CONSTRAINT DB2/DATABASE DB2/DBRM DB2/DISTINCT-TYPE DB2/INDEX DB2/INDEX-PART DB2/PACKAGE DB2/PARAMETER DB2/PLAN DB2/PROCEDURE DB2/REFERENTIAL-CONSTRAINT DB2/SEQUENCE DB2/STORAGE-GROUP DB2/SYNONYM DB2/SYSTEM DB2/TABLE DB2/TABLE-NAME DB2/TABLESPACE DB2/TABLESPACE-PART DB2/TRIGGER DB2/USER SCN/PROGRAM SCN/VOLUME SCN/VSAMCAT

2.1 Supported DB2 Objects All DB2 database oriented objects of DB2 Version 4, 5, 6, 7, 8, 9 and 10 are supported.

This includes references to Edit/Validation/Field Procedure Exit Routines, DATA CAPTURE options for TABLES, COMPRESS option for TABLE SPACES, ALIAS (LOCATION support is included in support for ALIAS), Check Constraints and Index Type 2.

Since DB2BUS version 5.00.000 the information of DB2/Packages, DB2/Plans and DB2/DBRMs of DB2 version 5 can be uploaded to Rochade.

Since DB2BUS version 6.00.000 Distinct Types, LOB column, Trigger (only for Upload) and Auxiliary Tables (only for Upload) are included.

Since DB2BUS version 8.10.000 Stored Procedures with Parameters (only for Upload) and Sequences are included, Triggers are included for Download.

Since DB2BUS version 8.20.000 Materialized Query Tables are supported for Upload and Download.


3

Starting with DB2BUS version 9.00.000, Auxiliary Tables are included for Download and Tables with “Table driven partitioning” and with “Partitioning-by-Growth” are supported for both Upload and Download.

The new DB2 Version 9 objects Rule and Trusted Context are not supported by DB2BUS version 10.01.000.

XML indices (new in DB2 Version 9) are not supported by DB2BUS version 10.01.000.

2.2 Using Rochade Long Item Names If you want to use the Rochade long item names feature for DB2BUS, consider the system requirements under Installation Instructions.

Use Rochade WebAccess or Metability for working with subject areas which were filled by DB2BUS upload to Rochade using the long item names feature.

There are certain limitations when you use AutoPilot for such subject areas. If you open such a subject area, you receive an AutoPilot message that explains these limitations.

2.3 Building DB2/COLUMN Names Without Using Rochade Long Item Names

If you do not use Rochade long item names feature, you have the option to decide if the name of a DB2/COLUMN shall be built with or without Table name prefix. Default is that the column is generated with Table name prefix.

If you want to change the way of building DB2/COLUMN names, go to member RIDBCUST in dataset <HLQ>.RIKOMP.REXX:

- Specify &RIDBCTNA = NO if you want the Column name without prefixed Table name.

- Specify &RIDBCTNA = YES if you want the Column name with prefixed Table name.

If you use Rochade long item names, the name of the column is always built with a Table name prefix.


4

3 Enhancements and Changes

Version 10.02 These modifications and enhancements have been made to DB2BUS in version 10.02.000:

DBB100200001: $, #, @ now handled as valid letters (DB2 names containing such characters no more enclosed in quotes in Rochade).


DBB100100001: IBM DB2 10 for z/OS supported.

DBB100100003: New I-RIM 1.53.001 required.

DBB1001000002: Extended Upload to ASG-Rochade: Alias:

- New DB2 10 Text Attribute DB2/SCHEMA-NAME filled with Schema name from DB2 Catalogue.

- New DB2 10 Text Attribute DB2/TBSCHEMA-TEXT filled with Schema name of referred Table.

Auxiliary Table:

- APPEND clause stored in new Text Attribute DB2/APPEND of DB2/AUXILIARY-TABLE.

- New DB2 10 Text Attribute DB2/SCHEMA-NAME filled with Schema Name from DB2 Catalogue

Column:

- INLINE LENGTH clause stored in new Text Attribute DB2/INLINE_LENGTH of DB2/COLUMN.

- GENERATED clause stored in new Text Attribute DB2/GENERATED of DB2/COLUMN.

- PERIOD SYSTEM_TIME / BUSINESS_TIME clause stored in new Text Attribute DB2/PERIOD of DB2/COLUMN.

Function:

- New DB2 10 Text Attribute DB2/SECURE of DB2/PROCEDURE populated.

- New DB2 10 Text Attribute DB2/INLINE_FUNCTION of DB2/PROCEDURE populated.


5

- New DB2 10 Text Attribute DB2/SYSTEM_DEFINED of DB2/PROCEDURE populated.

- New DB2 10 Text Attribute DB2/PARAMETER_VARCHARFORM of DB2/PROCEDURE populated.

Index:

- BUSINESS_TIME WITHOUT OVERLAPS clause stored in new Text Attribute DB2/BS_TIME_WITHOUT_OVERLAP of DB2/INDEX.

- INCLUDE clause stored in new Link Attribute DB2/INCLUDES_COLUMNS of DB2/INDEX.

- New Text Attribute DB2/SCHEMA-NAME filled with Schema name from DB2 Catalogue.

Package:

- New DB2 10 Text Attribute DB2/CONCURR_ACCESS_RESOLUTION of DB2/PACKAGE populated.

- New DB2 10 Text Attribute DB2/EXTENDED_INDICATOR of DB2/PACKAGE populated.

- New DB2 10 Text Attribute DB2/PLANMGMT of DB2/PACKAGE populated.

- New DB2 10 Text Attribute DB2/PLANMGMTSCOPE of DB2/PACKAGE populated.

- New DB2 10 Text Attribute DB2/APRETAINDUP of DB2/PACKAGE populated.

- New DB2 10 Text Attribute DB2/RECORDTEMPORALHIST of DB2/PACKAGE populated.

Plan:

- New DB2 10 V10 Text Attribute DB2/CONCURR_ACCESS_RESOLUTION of DB2/PLAN populated.

Primary Key / Unique Constraint:

- BUSINESS_TIME WITHOUT OVERLAPS clause stored in new Text Attribute DB2/BS_TIME_WITHOUT_OVERLAP of DB2/CONSTRAINT.

Table:

- ORGANIZE BY HASH clause stored in new Link Attribute DB2/HAS_HASHKEY_COLUMNS and new Text Attribute DB2/HASHSPACE of DB2/TABLE.

- New Text Attribute DB2/SCHEMA-NAME filled with Schema name from DB2 Catalogue.

- New Text Attribute DB2/CONTROL of DB2/TABLE populated.

Tablespace:

- MEMBER CLUSTER clause stored in new Text Attribute DB2/MEMBER-CLUSTER of DB2/TABLESPACE.

- Text Attribute DB2/TARGETSYSTEM added.


6

Type:

- INLINE LENGTH clause stored in new Text Attribute DB2/INLINE_LENGTH of DB2/DISTINCT-TYPE.

Trigger:

- New DB2 10 Text Attribute DB2/SECURE of DB2/TRIGGER populated.


DBB91000001: New I-RIM 1.52.006 required.

DBB91000002: Performance improvement for DB2 Catalog unloading for Upload of one Database only.

DBB91000003: Upload of extended DB2 Information supported: DB2/ALTERED for DB2/TABLE, DB2/INDEX, DB2/DATABASE, and DB2/TABLESPACE DB2/TSTMP-BOUNDTS for DB2/PLAN DB2/TSTMP-BINDTIME for DB2/PACKAGE

DBB91000004: Added Link Qualifier COLSEQ=nnn (nnn = Column Position in Primary Key) for DB2/TABLE Link Attribute DB2/HAS-PRIMKEY.

DBB91000005: UNIQUERULE=X supported for DB2/INDEX (unique for column with XML values) supported for DB2/INDEX.

DBB91000006: DB2/TARGETSYSTEM added for DB2/SYNONYM, DB2/ALIAS, DB2/AUXILIARY-TABLE.

DBB91000007: DB2/TABLE-NAME and DB2/COLUMN-NAME now always added as "active" items.

DBB91000008: DB2/TRIGGER on DB2/VIEW now uploaded and generated in DDL.

DBB91000009: Existence of required RPL procedures (e.g. RO-CREATE-SHORTNAME) checked when accessing ROCHADE.

DBB91000010: New Batch parameters supported: STD_DEFINIT_USER, ROSTARTCMD, ROSENDCMD, RITRACE=YES


DBB90200001: New Batch parameters supported: STD_DEFINIT_USER, ROSTARTCMD, ROSENDCMD, RITRACE=YES



7

DBB90100001: Progress Display can be suppressed for DB2BUS Batch (Windows):

New command line parameter: DISPLAY_PROGRESS=Y/N (Default: Y)


DBB90000001: Upload of Auxiliary Tables corrected

Auxiliary Tables are not longer uploaded as DB2/TABLE to Rochade, columns of Auxiliary Tables are not longer uploaded as DB2/COLUMN.

Now Auxiliary Tables are uploaded as DB2/AUXILIARY_TABLE only, without columns.

Indices on Auxiliary Tables are uploaded as DB2/INDEX, with new link attribute “DB2/FOR-AUXILIARY-TABLE” and without index columns.

DBB90000002: Generating CREATE Statements for Auxiliary Tables added

When generating a “CREATE TABLE” statement for a table with LOB columns, the “CREATE AUXILIARY TABLE” and the “CREATE INDEX” statements for the auxiliary table are generated, too, if this information is contained in Rochade or in DB2 Catalog.

DBB90000003: DB2 DDL Statement delimiter can be changed

When generating “CREATE …” statements, the DB2 DDL statement delimiter can be changed from semicolon (;) to a different character (for example #) by setting parameter &RIDBDELI = #

This is useful when generating “CREATE TRIGGER” statements containing DB2 statements with semicolon.

DBB90000004: Additional information for Materialized Query Tables supported

The new attributes DB2/ENABLE, DB2/MAINTENANCE and DB2/REFRESH are populated for Materialized Query Tables.

When generating “CREATE TABLE” statements for Materialized Query Tables, this information is generated, too.

DBB90000005: Additional information for Sequences supported

The new attributes DB2/COLTYPE, DB2/HAS-DISTINCT-TYPE and DB2/TARGET-SYSTEM are populated for DB2/SEQUENCE.

When generating “CREATE SEQUENCE” statements, this information is generated, too.

DBB90000006: Errors with long DB2 Comments corrected

The error which caused the wrong or incomplete upload and download of long DB2 Comments has been corrected.

DBB90000007: DB2 Comments, Labels and character constants containing DBCS characters are supported


8

The upload and download of text information with DBCS characters is now supported, if the Rochade installation supports the used language.

DBB90000008: DB2 Table driven partitioning supported

The DB2 “Table driven partitioning” feature is supported.

During upload from DB2 to Rochade, the new attributes DB2/NUMPARTS, DB2/PARTITION-ELEMENTS and DB2/HAS-PARTITIONING-COLUMNS of DB2/TABLE and DB2/PARTITIONED of DB2/INDEX are populated.

During download, the “CREATE TABLE” statement is generated with partitioning information and the “CREATE INDEX” statement is generated with “PARTITIONED”, if the information above is contained in Rochade or DB2 Catalog.

DBB90000009: New JCL Procedure #ROCLI used

In DB2BUS / MVS, for executing Rochade update commands, the new JCL procedure #ROCLI used instead of JCL procedure ROCLIENT (which is obsolete).

DBB90000010: New Options for Storage Groups supported

The new DB2 Version 9 options DATACLAS, MGMTCLAS and STORCLAS for Storage Groups are supported in upload (new attributes DB2/DATA_CLASS, DB2/MANAGEMENT_CLASS, DB2/STORAGE_CLASS for DB2/STORAGE-GROUP in Rochade RIM) and in DDL generation.

DBB90000011: New “instead of” Triggers supported

The new DB2 Version 9 “instead of” triggers on views are supported in upload and in DDL generation.

DBB90000012: New built-in Data Types supported

The new DB2 Version 9 built-in data types BIGINT (for SEQUENCE, DISTINCT TYPE and COLUMN), DECFLOAT, BINARY, VARBINARY (for DISTINCT TYPE and COLUMN) and XML (for COLUMN) are supported in upload and in DDL generation.

DBB90000013: New Option IMPLICITLY HIDDEN for Columns supported

The new DB2 Version 9 option IMPLICITLY HIDDEN for Columns is supported in upload (new attribute DB2/HIDDEN for DB2/COLUMN in Rochade RIM) and in DDL generation.

DBB90000014: New Option AS ROW CHANGE TIMESTAMP for columns supported

The new DB2 Version 9 option FOR EACH ROW ON UPDATE AS ROW CHANGE TIMESTAMP is supported in upload and in DDL generation.

DBB90000015: New Option APPEND YES / NO for Tables supported

The new DB2 Version 9 option APPEND YES/NO for Tables is supported in upload (new attribute DB2/APPEND for DB2/TABLE in Rochade RIM) and in DDL generation.

DBB90000016: New “Partition-by-Growth” Tablespaces and Tables supported


9

The new DB2 Version 9 “Partition-by-Growth” tablespaces and tables are supported in upload (new attribute DB2/MAXPARTITIONS for DB2/TABLESPACE in Rochade RIM) and in DDL generation (MAXPARTITIONS in CREATE TABLESPACE and PARTITION BY SIZE EVERY nG in CREATE TABLE).

DBB90000017: Data Compression for Indices supported

The new DB2 Version 9 option COMPRESS YES/NO for Indices is supported in upload (new attribute DB2/COMPRESS for DB2/INDEX in Rochade RIM) and in DDL generation.

DBB90000018: Random Sequence for Index Columns supported

The new DB2 Version 9 option RANDOM for Index Columns is supported in upload and in DDL generation.

DBB90000019: New Extended Indices supported

The new DB2 Version 9 “extended Indices” containing Key Expressions instead of or in combination with Key Columns are supported in upload (new attribute DB2/KEY_EXPRESSIONS for DB2/INDEX in Rochade RIM) and in DDL generation.

DBB90000020: Rounding Information for Packages and Plans supported

The new DB2 Version 9 information ROUNDING for Packages and Plans is supported in upload (new attribute DB2/ROUNDING for DB2/PACKAGE and DB2/PLAN in Rochade RIM).


- DBB82100001: New link from DB2/PROCEDURE to SCN/PROGRAM There is a new link attribute for DB2/PROCEDURE called DB2/EXTERNAL-PRC. This link attribute is filled with the name of the external procedure (contained in text attribute DB2/EXTERNAL-NAME) if DB2/LANGUAGE is neither JAVA nor COMPJAVA and if Parameter &RIDBLPRC=YES is set

- DBB82100002: Rochade password with more than 8 chars supported The panel where the Rochade password can be entered is changed to support passwords with more than 8 chars.

- DBB82100003: Time stamps for DB2/TABLE populated If Parameter &RIDBUTCA=YES is set for DB2/UNLOAD Program, the new text attributes DB2/ALTERED and DB2/CREATED are filled for DB2/TABLE

- DBB82100004: Grants for DB2/DISTINCT-TYPE uploaded If Selection Parameter GRANTS=YES is set for DB2/UNLOAD Program, a new link attribute DB2/GRANTS is filled for DB2/DISTINCT-TYPE pointing to the DB2/USER which have usage privilege on the DB2/DISTINCT-TYPE


10

- DBB82100005: Grants for DB2/PROCEDURE uploaded If Selection Parameter GRANTS=YES is set for DB2/UNLOAD Program, a new link attribute DB2/GRANTS is filled for DB2/PROCEDURE pointing to the DB2/USER which have execute privilege on the DB2/PROCEDURE

- DBB82100006: Statistics line for unloaded parameters added There is an additional line in DB2 Catalogue unload statistics showing the number of parameters unloaded from catalogue.

- DBB82100007: New unload parameter ONLY-OWNER supported There is a new catalogue unload parameter ONLY-OWNER=CCC. This parameter controls the unload of packages as follows: If ONLY-OWNER=CCC is specified, selected packages which do not have OWNER=CCC are suppressed, but ONLY-CREATOR=CCC is not used to suppress packages. If ONLY-OWNER=* is specified, no selected packages are suppressed, even if ONLY-CREATOR=CCC is specified. If ONLY-OWNER= is not specified, ONLY-CREATOR is used to suppress selected packages as before.

Version 8.20 - DB2BUS 8.20 extends support for DB2 version 8 by optionally using the Rochade

long item name feature to store names of DB2 objects in Rochade which are longer than 32 characters.

- If you want to use this new feature, you have to do the following:

- - Define a new Rochade subject area which supports names > 32 chars based on the I-RIM 1.50.002 or higher.

- If you want to change to long item names and you have already data in Rochade loaded by earlier versions of DB2BUS, please contact Rochade support for migration procedures.

- - Set the parameter &RIROXNS=YES as described in DB2BUS User Guide.

- - Define a dataset for your selection files used with DB2BUS functions D1/R1/U1/G1 with FB, LRECL=300 (instead of LRECL=80).

- With this new feature, the structure of Rochade item names is changed for particular DB2 Item types. See the DB2BUS User Guide for details.

- DB2BUS Version 8.20.000 download (DDL creation) does not support the full new name lengths allowed by DB2 Version 8 (see DB2BUS User Guide for the restrictions), but DB2BUS Version 8.20.000 upload to Rochade supports the full new name lengths allowed by DB2 Version 8.

- DBB82000001: Materialized Query Tables supported Materialized Query Tables are supported with DB2BUS upload and download. In Rochade, they are stored like Views, (i.e. the complete CREATE Statement is stored in VIEWTEXT) with DB2/TYPE set to MATERIALIZED.


11

- DBB82000002: DB2/TARGET-SYSTEM is filled With DB2BUS upload, for DB2/STORAGE-GROUP, DB2/DATABASE, DB2/TABLE, DB2/INDEX, DB2/DISTINCT-TYPE, DB2/TRIGGER and DB2/PROCEDURE, a new value attribute DB2/TARGET-SYSTEM is set to Z/OS.

- DBB82000003: DB2/BITDATA, allowed values With DB2BUS upload, only allowed values B, S, M are put into value attribute DB2/BITDATA

- DBB82000004: DB2/CONSISTENCY-TOKEN, binary values With DB2BUS upload, value attribute DB2/CONSISTENCY-TOKENis filled with hexadecimal equivalent of binary values.

- DBB82000005: DB2/PACKAGE upload Errors were corrected which occurred when uploading DB2/PACKAGES for which different versions are stored in DB2 Catalogue.

- DBB82000006: DB2/PROCEDURE upload extended Additional information is uploaded for DB2/PROCEDURE, especially text attribute DB2/ROUTINE_BODY is populated with the source code of the routine which is contained in DB2 Catalogue table SYSROUTINES_SRC.

- DBB82000007: DB2/COMMENT_ON_TABLE etc. upload changed DB2/COMMENTS which are not longer than 255 characters are not longer broken down into 72 char lines, but are stored as one long line in Rochade. DB2/COMMENTS which are longer than 255 characters, are broken down into 72 char lines as before.

Version 8.10 - DBB81000001: DB2/SEQUENCE (Upload and Download)

DB2 SEQUENCE can be uploaded to ROCHADE into DB2/SEQUENCE. CREATE SEQUENCE commands are generated by DB2BUS download.

- DBB81000002: DB2/Stored Procedures and Parameters (Upload only) DB2 Stored Procedures including Parameters can be uploaded to ROCHADE into DB2/PROCEDURE and DB2/PARAMETER.

- DBB81000003: DB2/PACKAGE, Consistency Token (Upload only) When uploading DB2/PACKAGEs, new value attribute DB2/CONSISTENCY-TOKEN is populated.

- DBB81000004: DB2/PACKAGE, Comments (Upload only) When uploading DB2/PACKAGEs, new text attribute DB2/COMMENT_ON_PACKAGE is populated.

- DBB81000005: DB2/PACKAGE, Usage of Stored Procedures and Sequences (Upload only) When uploading DB2/PACKAGEs, new link attributes DB2/USES-SEQUENCE and DB2/USES-PROCEDURE are populated.

- DBB81000006: DB2/PLAN, Comments (Upload only) When uploading DB2/PLANs, new text attribute DB2/COMMENT_ON_PLAN is populated.


12

- DBB81000007: DB2/PLAN, Usage of Stored Procedures and Sequences (Upload only) When uploading DB2/PLAN, new link attributes DB2/USES-SEQUENCE and DB2/USES-PROCEDURE are populated.

- DBB81000008: DB2/TABLE, VOLATILE When uploading DB2/TABLE, new value attribute DB2/VOLATILE is populated. When generating DDL statements for DB2 version 8, CREATE TABLE is generated with new clause: VOLATILE CARDINALITY / NOT VOLATILE CARDINALITY

- DBB81000008: DB2/REFERENTIAL-CONSTRAINT, ENFORCED When uploading DB2/REFERENTIAL-CONSTRAINT, new value attribute DB2/ENFORCED is populated. When generating DDL statements for DB2 version 8, ALTER TABLE ... ADD CONSTRAINT is generated with new clause: ENFORCED / NOT ENFORCED

- DBB81000009: DB2/INDEX, PADDED When uploading DB2/INDEX, new value attribute DB2/PADDED is populated. When generating DDL statements for DB2 version 8, CREATE INDEX is generated with new clause: PADDED / NOT PADDED

- DBB81000010: DB2/REFERENTIAL-CONSTRAINT, ENABLE QUERY OPTIMIZATION When generating DDL statements for DB2 version 8, ALTER TABLE ... ADD CONSTRAINT is always generated with new clause: ENABLE QUERY OPTIMIZATION

- DBB81000011: DB2/DISTINCT TYPE, WITH COMPARISONS When generating DDL statements for DB2 version 8, CREATE DISTINCT TYPE not longer contains clause: WITH COMPARISONS

- DBB81000012: DB2/TABLESPACE, formal changes When generating DDL statements for DB2 version 8, CREATE TABLESPACE not longer contains clause: LOCKPART ... PARTITION is generated instead of PART

- DBB81000013: DB2/INDEX, formal changes for partitioned indices When generating DDL statements for DB2 version 8, CREATE INDEX for partitioned indices contains: PARTITIONED PARTITION BY RANGE For each partition is generated: PARTITION n ENDING AT (...,...,...) INCLUSIVE

- DBB81000014: DB2/COLUMN, AS SECURITY LABEL When uploading DB2/COLUMNs which contain security label values, value attribute DB2/DEFAULT is populated with new value L. When generating DDL statements for DB2 version 8, CREATE TABLE for column which contains security label values is generated with new clause: AS SECURITY LABEL

- DBB81000015: DB2/COLUMN, AS IDENTITY ... ORDER When uploading DB2/COLUMNs with AS IDENTITY, new value attribute DB2/ORDER is populated. When generating DDL statements for DB2 version 8, CREATE TABLE for column with AS IDENTITY is generated with new clause: ORDER / NO ORDER


13

DBB81000016: DB2/TRIGGER can be downloaded When generating DDL statements for DB2 version 7 and 8, CREATE TRIGGER statements can be generated (including COMMENT ON TRIGGER), if CREATE TABLE statements are generated and there are DB2/TRIGGERs defined for the table within ROCHADE. To do this, parameter TRIGGERS-USED=Y must be set.


14

4 Installation Instructions Two ways of storing the DB2BUS analysis results in the Rochade database and of providing information that is stored in the Rochade database to DB2BUS are available:

- Directly with an MVS batch client (no file transfer required)

- Use this option when a licensed MVS batch client is available (e.g., through a Rochade server installation in MVS). Installation of DB2BUS in Windows is not required in this case, but the Rochade long name procedure package ROUTIL version 2.30, which is a part of DB2BUS (Windows) must always be installed in Rochade.

- With DB2BUS under Windows, via file transfer

In this case, you must install DB2BUS also under Windows.

Use this option if you do not wish to license a MVS batch client.

The DB2BUS installation is composed of these component installations:

- I-RIM installation

This installation is always necessary. It contains the I-RIM, which is required for generating an information model for exchanging information between Rochade and DB2BUS.

- DB2BUS installation in MVS

This installation is always necessary. It includes installation of all programs, libraries and datasets on MVS for analyzing DB2 catalog, storing the analysis results generated by DB2BUS in Rochade and providing analysis results generated in Rochade to DB2BUS via a MVS batch client.

- DB2BUS installation in Windows

This installation is optional and includes the installation of all programs and parameter files on Windows for storing the analysis results generated by DB2BUS in Rochade and providing analysis results generated in Rochade to DB2BUS via a Windows client.

- ROUTIL installation in Windows

This installation is always necessary and will be requested during the optional DB2BUS installation in Windows implicitly. This installation installs RPL procedures required for importing the analysis results into Rochade properly.

Software Requirements - Rochade Client 7.0 (or higher)

- AutoPilot 3.60 or later

- I-RIM 1.53.001


15

4.1 I-RIM Installation DB2BUS requires a Rochade subject area based on the I-RIM 1.53.001.

After you have installed I-RIM, use the I-RIM Information Model Composer to generate your information model based on C-RIM (this information model is called C-RIM here, but could have a different name). For details, see the ASG-Rochade I-RIM System Administrator’s Guide.

If your Rochade installation does not contain a subject area based on the C-RIM, generate a subject area based on it.

If your Rochade installation already contains a subject area based on a lower C-RIM version and you want to use this subject area for DB2BUS, you must reorganize this subject area. Check if all item types of the subject area are activated (in the AutoPilot Application Administration by Update View).

4.2 Installation of DB2BUS (MVS) Install DB2BUS as described in the chapter about installing Rochade under MVS in the ASG-Rochade Installation Guide.

4.2.1 How to LINK and BIND DB2 Catalog Access Program This DB2BUS installation contains different programs to access the DB2 Catalog. (Note: This is necessary because some tables in DB2 Catalog are not compatible with previous versions.):

- Program RIDBU11 for DB2 Catalog Version 4




- Program RIDBU118 for DB2 Catalog Version 8 (Rochade long item names not used)

- Program RIDBU218 for DB2 Catalog Version 8 (Rochade long item names used)

- Program RIDBU119 for DB2 Catalog Version 9 (Rochade long item names not used)

- Program RIDBU219 for DB2 Catalog Version 9 (Rochade long item names used)

- Program RIDBU11A for DB2 Catalog Version 10 (Rochade long item names not used)

- Program RIDBU21A for DB2 Catalog Version 10 (Rochade long item names used)

If you have problems with this topic or if you do not have sufficient DB2 access rights to execute the following steps, please contact your DB2 Administrator.


16

Linking the DB2 Catalog access program If you are using DB2 Catalog version 4, you have to link program RIDBU11 using the job contained in member DBBLINK4 in dataset <HLQ>.DB2BUS.CNTL.

If you are using DB2 Catalog version 5, you have to link program RIDBU115 using the job contained in member DBBLINK5 in dataset <HLQ>.DB2BUS.CNTL.



If you are using DB2 Catalog version 8 without the Rochade long item name feature enabled and the encoding scheme of your DB2 Catalog Tables is ASCII or UNICODE, you have to link program RIDBU118 using the job contained in member DBBLINK8 in dataset <HLQ>.DB2BUS.CNTL.

If you are using DB2 Catalog version 8 without the Rochade long item name feature enabled and the encoding scheme of your DB2 Catalog Tables is EBCDIC, you have to link program RIDBU118 using the job contained in member DBBLINE8 in dataset <HLQ>.DB2BUS.CNTL.

If you are using DB2 Catalog version 8 with the Rochade long item name feature enabled and the encoding scheme of your DB2 Catalog Tables is ASCII or UNICODE, you have to link program RIDBU218 using the job contained in member DBBLIN28 in dataset <HLQ>.DB2BUS.CNTL.

If you are using DB2 Catalog version 8 with the Rochade long item name feature enabled and the encoding scheme of your DB2 Catalog Tables is EBCDIC, you have to link program RIDBU218 using the job contained in member DBBLINF8 in dataset <HLQ>.DB2BUS.CNTL.

If you are using DB2 Catalog version 9 without the Rochade long item name feature enabled and the encoding scheme of your DB2 Catalog Tables is ASCII or UNICODE, you have to link program RIDBU119 using the job contained in member DBBLINK9 in dataset <HLQ>.DB2BUS.CNTL.

If you are using DB2 Catalog version 9 without the Rochade long item name feature enabled and the encoding scheme of your DB2 Catalog Tables is EBCDIC, you have to link program RIDBU119 using the job contained in member DBBLINE9 in dataset <HLQ>.DB2BUS.CNTL.

If you are using DB2 Catalog version 9 with the Rochade long item name feature enabled and the encoding scheme of your DB2 Catalog Tables is ASCII or UNICODE, you have to link program RIDBU219 using the job contained in member DBBLIN29 in dataset <HLQ>.DB2BUS.CNTL.

If you are using DB2 Catalog version 9 with the Rochade long item name feature enabled and the encoding scheme of your DB2 Catalog Tables is EBCDIC, you have to link program RIDBU219 using the job contained in member DBBLINF9 in dataset <HLQ>.DB2BUS.CNTL


17

If you are using DB2 Catalog version 10 without the Rochade long item name feature enabled and the encoding scheme of your DB2 Catalog Tables is ASCII or UNICODE, you have to link program RIDBU11A using the job contained in member DBBLINKA in dataset <HLQ>.DB2BUS.CNTL.

If you are using DB2 Catalog version 10 without the Rochade long item name feature enabled and the encoding scheme of your DB2 Catalog Tables is EBCDIC, you have to link program RIDBU11A using the job contained in member DBBLINEA in dataset <HLQ>.DB2BUS.CNTL.

If you are using DB2 Catalog version 10 with the Rochade long item name feature enabled and the encoding scheme of your DB2 Catalog Tables is ASCII or UNICODE, you have to link program RIDBU21A using the job contained in member DBBLIN2A in dataset <HLQ>.DB2BUS.CNTL.

If you are using DB2 Catalog version 10 with the Rochade long item name feature enabled and the encoding scheme of your DB2 Catalog Tables is EBCDIC, you have to link program RIDBU21A using the job contained in member DBBLINFA in dataset <HLQ>.DB2BUS.CNTL

If you do not know the encoding scheme of your Catalog Tables, you can check it with this query:

SELECT ENCODING_SCHEME FROM SYSIBM.SYSTABLES WHERE NAME = "SYSTABLES" AND CREATOR = "SYSIBM"

Possible values are: A for ASCII, E for EBCDIC, and U for UNICODE.

Accessing the correct DB2 Catalog Tables The DB2BUS program that accesses the DB2 Catalog uses static SQL statements which look like 'SELECT ... FROM SYSTABLES'.

Before you can bind the plan for the access program, you have to make sure that the correct DB2 Catalog Tables can be accessed.

Accessing original Catalog Tables SYSIBM.SYS... If you want to use the original catalog tables SYSIBM.SYS..., you have to bind the plan with QUALIFIER(SYSIBM).

The user who executes the BIND must have READ privilege for the original catalog tables SYSIBM.SYS.


18

Accessing copies of Catalog Tables SYSIBM.SYS... If you have copies of the catalog tables SYSIBM.SYS..., we strongly recommend accessing these copies instead of the original catalog tables, in order to improve performance and avoid deadlock situations.

If your copied catalog tables have the same names as the original tables (and only a different QUALIFIER XXX.SYS...), you have to bind the plan with QUALIFIER(XXX).

If your copied catalog tables have different names from the original tables, you must first create SYNONYMS for the copy catalog tables.

If you are using DB2 Catalog version 4, you can use the statements contained in member DBBSYN41 in dataset <HLQ>.DB2BUS.CNTL.






If you are using DB2 Catalog version 10, you can use the statements contained in member DBBSYNA1 in dataset <HLQ>.DB2BUS.CNTL.

Modify the JCL statements using the names of your copied catalog tables.

Then you have to bind the plan with QUALIFIER(USERID), where USERID is the USERID of the user who has created the SYNONYMS.

The user who creates the SYNONYMS and executes the BIND must have READ privilege for the copied catalog tables.

Binding the DB2 Catalog access plan If you are using DB2 Catalog version 4, you have to bind plan RIDBU11 using the job contained in member DBBBIND4 in dataset <HLQ>.DB2BUS.CNTL.

If you are using DB2 Catalog version 5, you have to bind plan RIDBU115 using the job contained in member DBBBIND5 in dataset <HLQ>.DB2BUS.CNTL.




19

If you are using DB2 Catalog version 8 without the Rochade long item name feature enabled and the encoding scheme of your DB2 catalog tables is ASCII or UNICODE, you have to bind plan RIDBU118 using the job, contained in member DBBBIND8 in dataset <HLQ>.DB2BUS.CNTL.

If you are using DB2 Catalog version 8 without the Rochade long item name feature enabled and the Encoding Scheme of your DB2 catalog tables is EBCDIC, you have to bind plan RIDBU118 using the job, contained in member DBBBINE8 in dataset <HLQ>.DB2BUS.CNTL.

If you are using DB2 Catalog version 8 with the Rochade long item name feature enabled and the Encoding Scheme of your DB2 catalog tables is ASCII or UNICODE, you have to bind plan RIDBU218 using the job contained in member DBBBIN28 in dataset <HLQ>.DB2BUS.CNTL.

If you are using DB2 Catalog version 8 with the Rochade long item name feature enabled and the Encoding Scheme of your DB2 catalog tables is ECBDIC, you have to bind plan RIDBU218 using the job contained in member DBBBINF8 in dataset <HLQ>.DB2BUS.CNTL.

If you are using DB2 Catalog version 9 without the Rochade long item name feature enabled and the encoding scheme of your DB2 catalog tables is ASCII or UNICODE, you have to bind plan RIDBU119 using the job, contained in member DBBBIND9 in dataset <HLQ>.DB2BUS.CNTL.

If you are using DB2 Catalog version 9 without the Rochade long item name feature enabled and the Encoding Scheme of your DB2 catalog tables is EBCDIC, you have to bind plan RIDBU119 using the job, contained in member DBBBINE9 in dataset <HLQ>.DB2BUS.CNTL.

If you are using DB2 Catalog version 9 with the Rochade long item name feature enabled and the Encoding Scheme of your DB2 catalog tables is ASCII or UNICODE, you have to bind plan RIDBU219 using the job contained in member DBBBIN29 in dataset <HLQ>.DB2BUS.CNTL.

If you are using DB2 Catalog version 9 with the Rochade long item name feature enabled and the Encoding Scheme of your DB2 catalog tables is ECBDIC, you have to bind plan RIDBU219 using the job contained in member DBBBINF9 in dataset <HLQ>.DB2BUS.CNTL.

If you are using DB2 Catalog version 10 without the Rochade long item name feature enabled and the encoding scheme of your DB2 catalog tables is ASCII or UNICODE, you have to bind plan RIDBU11A using the job, contained in member DBBBINDA in dataset <HLQ>.DB2BUS.CNTL.

If you are using DB2 Catalog version 10 without the Rochade long item name feature enabled and the Encoding Scheme of your DB2 catalog tables is EBCDIC, you have to bind plan RIDBU11A using the job, contained in member DBBBINEA in dataset <HLQ>.DB2BUS.CNTL.

If you are using DB2 Catalog version 10 with the Rochade long item name feature enabled and the Encoding Scheme of your DB2 catalog tables is ASCII or UNICODE, you have to bind plan RIDBU21A using the job contained in member DBBBIN2A in dataset <HLQ>.DB2BUS.CNTL.


20

If you are using DB2 Catalog version 10 with the Rochade long item name feature enabled and the Encoding Scheme of your DB2 catalog tables is ECBDIC, you have to bind plan RIDBU21A using the job contained in member DBBBINFA in dataset <HLQ>.DB2BUS.CNTL.

Before running this job, please pay attention to accessing the correct DB2 catalog tables.

Maybe you have to change QUALIFIER(SYSIBM).

After running this job, you have to grant the RUN privilege on plan RIDBU11, RIDBU11x, or RIDBU21x to every user which should run DB2BUS.

4.2.2 Customizing the TOOLBUS Interface

To define the parameters for DB2BUS 1. If you have already a member RIDBCUST in dataset <HLQ>.RIKOMP.REXX,

save this member with a different name.

2. Copy member RIDBCDEF of dataset <HLQ>.RIKOMP.REXX to a new member RIDBCUST (Creation of Customization file).

3. RIDBCUST now contains the default settings for DB2BUS parameters.

With these settings you can test the product if you have DB2 Version 8 and do not want to use the Rochade long item name feature.

If you want to use the Rochade long item name feature, first set &RIROXNS = YES

If you have DB2 Version 10, you first must set &RIDB2VER = V10






If you decide to change some additional settings, do this in RIDBCUST.

Maybe you want to reuse your old settings, which you have saved under (1).

Setting of DB2BUS parameters is described in the DB2BUS User Guide.

Note: If you have not created a Customization file RIDBCUST, you will get an error 'Command RIDBCUST not found'.


21

To set the Rochade logon commands for the DB2BUS API step 1. If you are using more than two databases in Rochade, please enhance the Rochade

Logon commands in members RIROUNLS, RIROXNLS, RIROUPDS and RIRONAMS of dataset <HLQ>.DB2BUS.SKELETON

2. To do this, search for the PARMS section and add the necessary $DB statements

Note: If you have not enhanced the Rochade logon commands, an error in step RIROU12 will appear, e.g., an RC of 2 by $mget, which indicates an invalid item type.

To change used DB2 version or Use Rochade Long Item Name Feature after Installation of DB2BUS

If you have already installed DB2BUS for DB2 version 7 and want to change to DB2 version 8, 9 or 10, or if you want to use Rochade long item name feature after installation of DB2BUS, you have to repeat the steps described in "How to LINK and BIND DB2 Catalog Access Program" and "Customizing the TOOLBUS Interface" for DB2 version 8, 9 or 10 and Rochade long item name feature.

4.3 Installation of DB2BUS and ROUTIL (Windows) DB2BUS and ROUTIL under Windows are installed in two steps, the ADM installation and the Application installation.

- The ADM installation imports and installs DB2BUS in the Rochade database. It requires that you have Operator or Administrator rights; hence this installation should be carried out by a system or database administrator. DB2BUS is not yet available to the end user after the ADM installation.

- The Rochade long name procedure package ROUTIL version 2.30 is a part of this DB2BUS package and is to be installed the same way as well.

- The Application installation makes DB2BUS available on your local computer. It does so by installing files, programs, and libraries of DB2BUS on the local computer.

To start ADM installation

1. Double-click the icon of your Rochade ADM installation (ADM icon) to start the ADM installation.

2. In the subsequent dialog select DB2BUS.

To start Application installation 1. Double-click the icon of your Rochade Application installation (Application icon)

for starting the application installation.

2. In the subsequent dialog select DB2BUS and ROUTIL.

A default target directory is suggested (e.g. c:\rochade\DB2BUS).You may choose a different directory if you wish, but it is necessary to install each BUS in a separate subdirectory.


22

The target directory will be created, and all necessary files will be copied into this directory.

A DB2BUS icon will be created in the ROCHBUS folder.

Note: Customization of DB2BUS is described in the DB2BUS User's Guide.

4.4 Starting and Using DB2BUS (MVS) To start DB2BUS

1. Execute this TSO command: TSO EX '<HLQ>.RIKOMP.REXX(RIDB00C)'

The first panel of DB2BUS appears.

Note: If you have not created a customization file RIDBCUST, you will get an error 'Command RIDBCUST not found...'. For creating the customization file, see "Customizing the TOOLBUS Interface".

2. Execute the option 'J - Jobcards Maintenance' and enter a correct MVS JCL job card specification.

The MVS JCL job card for your jobs will be set.

4.4.1 Executing Unload from DB2 Catalog to ROCHBUS File

To execute unload from DB2 Catalog to ROCHBUS file

1. Execute the option 'R1 - for selected DB2 Objects' or 'R3 - for one complete DB2 DATABASE.'

For a first test, you can use option R3 with IBM sample database:

DB2 Database DSN8D10A if you have DB2 version 10 or






DB2 Database DSN8D41A if you have DB2 version 4.

2. To test option R1 you can use the sample selection file contained in <HLQ>.DB2BUS.TABLES(SAMPLE). If you are using the Rochade long item name feature, you must copy this file into a dataset with FB, LRECL=300 before you can start the job.

The DB2BUS Unload from DB2 Catalog to ROCHBUS file panel appears.

3. Enter the TSO sub command.

The Unload from DB2 Catalog job will be generated and executed


23

4.4.2 Executing Upload from DB2 Catalog to Rochade

To execute upload from DB2 Catalog to Rochade 1. Execute the option 'U1 - for selected DB2 Objects' or 'U3 - for one complete DB2

DATABASE'.

For a first test, you can use option U3 with IBM sample database: DB2 Database DSN8D10A if you have DB2 version 10 or DB2 Database DSN8D91A if you have DB2 version 9 or DB2 Database DSN8D81A if you have DB2 version 8 or DB2 Database DSN8D71A if you have DB2 version 7 or DB2 Database DSN8D61A if you have DB2 version 6 or DB2 Database DSN8D51A if you have DB2 version 5 or DB2 Database DSN8D41A if you have DB2 version 4.

2. To test option U1 you can use the sample selection file contained in <HLQ>.DB2BUS.TABLES(SAMPLE). If you are using the Rochade long item name feature, you must copy this file into a dataset with FB, LRECL=300 before you can start the job.

The DB2BUS Upload from DB2 Catalog to Rochade panel appears

3. Enter the TSO sub command

The Upload from DB2 Catalog job will be generated and executed

4.4.3 Executing Download from Rochade and Generating CREATE Statements

To execute Download from Rochade and generate CREATE statements

1. Execute the option 'D1 - for selected DB2 Objects' or 'D3 - for one complete DB2 DATABASE'

For a first test, you can use option D3 with the IBM sample database (after you have uploaded this database from DB2 to Rochade):

- DB2 Database DSN8D10A if you have DB2 version 10 or






- DB2 Database DSN8D41A if you have DB2 version 4.

2. To test option D1, you can use the sample selection file contained in <HLQ>.DB2BUS.TABLES(SAMPLE). If you are using the Rochade long item name feature, you must copy this file into a dataset with FB, LRECL=300 before you can start the job.

The DB2BUS Download from Rochade and generate CREATE Statements panel appears.


24

3. Enter the TSO sub command

The Download from Rochade and generate CREATE Statements job will be generated and executed

4.4.4 Executing Unload from DB2 Catalog and Generating CREATE Statements

To execute Unload from DB2 Catalog and generate CREATE statements

1. Execute the option 'G1 - for selected DB2 Objects' or 'G3 - for one complete DB2 DATABASE'.

For a first test, you can use option G3 with IBM sample database:







- DB2 Database DSN8D41A if you have DB2 version 4.

2. To test option G1, you can use the sample selection file contained in <HLQ>.DB2BUS.TABLES(SAMPLE). If you are using the Rochade long item name feature, you must copy this file into a dataset with FB, LRECL=300 before you can start the job.

The DB2BUS Unload from DB2 Catalog and generate CREATE Statements panel appears.

3. Enter the TSO sub command. The Unload from DB2 Catalog and generate CREATE Statements job will be generated and executed

4.5 Starting and Using DB2BUS (Windows) Starting and using DB2BUS is described in the DB2BUS User's Guide.

db2bus for asg -rochade release notes · db2/alias db2/auxiliary-table db2/column db2/column-name...

Documents