Software Product Description ___________________________________________________________________ PRODUCT NAME: DEC Data Distributor Version 6.0 for OpenVMS AXP SPD 47.12.01 DESCRIPTION DEC Data Distributor manages the distribution of relational data. Op- erations called transfers define what data and data definitions are to be moved (the source) and where they are to be moved to (the tar- get). The target need not be on the same system or be the same data management system as the source. Distributing data in this way has several benefits, particularly when the target is on a different system from the source: o Users can query a database local to them rather than having to ac- cess a remote database. This provides faster and more regular ac- cess. o Congestion on the source database is reduced as a result of the use of the target. Data Sources, Targets and Gateway Dependencies The following table lists the DEC Data Distributor sources and tar- gets and the DEC DB Integrator (DBI) gateways, if any, required to ac- cess them. ___________________________________________________________________ Table_1:_DEC_Data_Distributor_Sources_and_Targets__________________ Data_Manager___Source_Target_DBI_Gateway_Requirement[1]____________ DEC DB Inte- Y Y - grator[3] DIGITAL February 1994 DEC Data Distributor Version 6.0 for OpenVMS AXP SPD 47.12.01 ___________________________________________________________________ Table_1_(Cont.):_DEC_Data_Distributor_Sources_and_Targets__________ Data_Manager___Source_Target_DBI_Gateway_Requirement[1]____________ DEC DBMS Y N DBMS DEC Rdb Y Y - DSM Y N DSM IBM DB2 Y Y DB2 IBM VSAM Y N RMS ORACLE Y Y ORACLE SYBASE Y Y SYBASE VMS RMS Y N RMS Others[2]______Y______N______Custom_Drivers________________________ Methods of Data Distribution There are three transfer types: extraction, extraction rollup, and repli- cation. For each type of transfer, the source can be all the table def- initions and data within the source database or databases, or a sub- set of those definitions and data. Extraction ____________________ [1] The use of a particular database or file system as a source or a tar- get depends on the version of the DBI gateway used. Refer to the OP- TIONAL SOFTWARE section of this SPD for the DBI gateway products and versions required to achieve the capabilities listed here. [2] DEC DB Gateway for Custom Drivers provides tools that enable access to data sources that lack turn-key DBI Gateway solutions. [3] Note that transfer of data to a DEC DB Integrator target database is contingent upon the capabilities of the underlying link databases and the gateways that access them. For example, if the DEC DB Integra- tor logical database is linked to an IBM DB2 database, which can be a target of Data Distributor transfers, then the transfer to the DEC DB Integrator database can succeed. By contrast, if for example the logical database is based on links to RMS or VSAM files, which can- not be the target of Data Distributor transfers, the transfer to the DEC DB Integrator database would fail. 2 DEC Data Distributor Version 6.0 for OpenVMS AXP SPD 47.12.01 The target can be a set of tables in any of the target databases iden- tified in Table 1. Each time the transfer executes, the existing data in these tables is deleted and replaced with current data from the source. Optionally the target may be a DEC Rdb database, as opposed to tables in a DEC Rdb database. In this case a new version of the database is created every time the transfer executes. Users can update any of the target tables, provided that they have ac- cess privilege to do so. If Data Distributor recreates the database files when the transfer next executes, the user updates will not ap- pear in the target database. If the transfer does not create new database files but the user updates were to transferred tables, the user up- dates will not appear when the table data is refreshed. User updates are preserved when they are to tables not targeted by Data Distrib- utor transfers and the target files are not recreated with each sub- sequent transfer execution. Extraction Rollup The extraction rollup function has the same range of source databases as the extraction function. However, an extraction rollup has more than one source database. The source databases can be of different types, for example, one DEC Rdb database and one DB2 database. The target must be a DEC Rdb database. A new version of the target database is created every time the transfer executes. The result of an extrac- tion rollup, like that of an extraction, can be updated by users, but those updates will not be reflected in the new database created when the next transfer executes. Replication A replication transfer initially moves all source data to the target. Subsequent executions of a replication transfer post only the changes made to the source database since the last transfer was executed. Data rows deleted on the source database may be deleted on the target or flagged as archived data. The source of a replication transfer must 3 DEC Data Distributor Version 6.0 for OpenVMS AXP SPD 47.12.01 be a DEC Rdb database. The target can be any of the targets identi- fied in Table 1. If necessary, the target can be rebuilt by reinitial- izing the transfer. Tables that are targets of replication transfers should not be updated. Other Features Schedules Each transfer may have a schedule that specifies the times and inter- vals at which a transfer will execute. A transfer may also be executed anytime on demand, whether or not a transfer schedule is defined. Pre- and Post-Transfer Command Procedures A transfer can have associated with it DCL command procedures that ex- ecute before and/or after a transfer executes. Potential uses of such procedures include: o Making the network between the source and target systems available o Notifying users by electronic mail that the transfer has completed and reporting on completion status o Creating indexes on tables in the target database Multiple Transfers A database can be the source for more than one transfer. For example, a DEC Rdb database could be the source for a replication of some ta- bles, an extraction of some columns from other tables, and also one of the source databases for an extraction rollup including yet another subset of the data. Because the target of an extraction or replication can be a set of ta- bles in an existing database, such a database can be the target of more than one transfer. However, it cannot be the target of an extraction rollup, and no table within the database can be the target of more than one transfer. 4 DEC Data Distributor Version 6.0 for OpenVMS AXP SPD 47.12.01 A database can be both a source and a target database. For example, a database may be the target of a replication transfer, and may also be the source of other replications. Centralized Storage of DEC Data Distributor Information Transfer and schedule definitions and the status of every transfer are consolidated in a DEC Rdb database known as the transfer database. VMScluster systems may contain both VAX and AXP processors. In a sin- gle VMScluster system, VAX computers running DEC Data Distributor and AXP computer systems running DEC Data Distributor share a single cluster- wide transfer database. They also share in the scheduling and execu- tion of transfers. Syntax DEC SQL includes DEC Data Distributor statements, such as: o CREATE TRANSFER, in which the source and target are specified. Spec- ification of the source includes selecting the tables, and the rows and columns of those tables, to be transferred. o CREATE SCHEDULE, in which the frequency of execution is specified. o SHOW TRANSFER, which displays the definition of the transfer and that of the associated schedule if there is one, and the status of the transfer, including the date and time at which it last executed. Security To create a transfer, it is necessary to have SELECT access to the source database and to the tables transferred. To create a replication trans- fer, it is also necessary to have CREATE privilege on the source database. If the target database is created by DEC Data Distributor, it is cre- ated with the DEC Rdb default protection. If it is necessary to be more restrictive for an extraction or replication, the database can be cre- ated in advance and the target specified as tables within it. Tables are always created with the default protection of the target database system. This can be altered in a posttransfer DCL command procedure. 5 DEC Data Distributor Version 6.0 for OpenVMS AXP SPD 47.12.01 The data in the transfer database is protected from direct access by users lacking the required privileges. Portability and Interoperability DEC Data Distributor is available on both OpenVMS VAX and OpenVMS AXP system platforms. DEC Rdb databases, DB Integrator and the DB Inte- grator gateways on both of these platforms provide a wide range of tar- gets and sources for extraction and targets for replication transfers. Relationships with Other Products DEC Data Distributor requires DEC Rdb. It can be used with any one of the three DEC Rdb packaging options. Sites may use the DEC SQL inter- face to tailor target databases by creating indexes etc. Because DEC SQL can perform operations on remote as well as local databases, the operations can be performed from another node on the network to nodes that only have a Run-Time license for the target product. If CDD/Repository is present on the target system, data definitions from DEC Rdb target databases can be placed in the dictionary by us- ing the INTEGRATE statement of the DEC SQL utility. DEC Data Distributor for OpenVMS AXP can schedule and execute trans- fers between DEC DB Integrator, DEC DB Integrator gateways or DEC Rdb servers running on OpenVMS VAX or OpenVMS AXP systems. Where to Install DEC Data Distributor It is not necessary to install DEC Data Distributor on every system involved in a transfer. It must be installed on: o The source system of a replication transfer o Either the source or the target system of an extraction or extrac- tion rollup transfer. (It may be installed on both.) Limitations 6 DEC Data Distributor Version 6.0 for OpenVMS AXP SPD 47.12.01 Because DEC Data Distributor uses a cluster-wide transfer database, only one version of DEC Data Distributor is allowed in a VMScluster system. Row selection, conditional and value expressions available in a trans- fer definition are a subset of those supported by the source database management system. Indexes, constraints, triggers, collating sequences, stored procedures, external functions and access privileges are not copied from source to target databases. DEC Data Distributor does not provide commit-time replication of changes. That is, updates to the source are transferred to the target when a replication transfer executes, not whenever an update transaction is committed on the source database. DEC Data Distributor does not support DEC SERdb for Security-Enhanced VMS. CONFORMANCE TO STANDARDS DEC Data Distributor extends the functions of DEC SQL to cover the sched- uled transfer of data between databases. These functions are not ad- dressed by the current ANSI/ISO standards for SQL. HARDWARE REQUIREMENTS Processors Supported AXP: DEC 3000 Model 300 AXP Workstation, DEC 3000 Model 400 AXP Workstation, DEC 3000 Model 400 AXP Server, DEC 3000 Model 500 AXP Workstation, DEC 3000 Model 500 AXP Server DEC 4000 Model 610 AXP System 7 DEC Data Distributor Version 6.0 for OpenVMS AXP SPD 47.12.01 DEC 7000 Model 610 AXP System DEC 10000 Model 610 AXP System Disk Space Requirements (Block Cluster Size = 1): The following counts refer to the disk space required on the system disk. The sizes are approximate; actual sizes may vary depending on the user's system environment, configuration, and software options. Disk space required for 11,000 blocks installation: 5.6M bytes Disk space required for 8,000 blocks use (permanent): 4.1M bytes Other Hardware Required: All processors require mass storage units to backup and restore es- tablished databases. CLUSTER ENVIRONMENT This layered product is fully supported when installed on any valid and licensed VMScluster configuration without restrictions. The HARD- WARE REQUIREMENTS section of this product's Software Product Descrip- tion detail any special hardware required by this product. Multiple versions of this software cannot be run on a single system or VMScluster at the same time. OpenVMS VMScluster configurations are fully described in the VMSclus- ter Software Product Description (42.18.xx) and include CI, Ethernet, and Mixed Interconnect configurations. 8 DEC Data Distributor Version 6.0 for OpenVMS AXP SPD 47.12.01 SOFTWARE REQUIREMENTS o OpenVMS AXP Operating System V1.5 o DEC Rdb for OpenVMS AXP V6.0 Full Development, Interactive or Run Time Option VMS Tailoring: The following OpenVMS classes are required for full functionality of this layered product: o VMS Required Saveset o Network Support o Programming Support o Secure User's Environment o Utilities For more information on OpenVMS classes and tailoring, refer to the OpenVMS AXP Operating System Software Product Description (SPD 41.87.xx). OPTIONAL SOFTWARE o DEC DB Integrator for OpenVMS AXP V1.0 To access DEC DB Integrator logical databases residing on the net- work as sources or targets for data transfer. You may use the Full Development, Interactive or Run Time Option. o DECnet V1.5 for OpenVMS AXP To transfer data between network nodes o DEC DB Integrator Gateway for DB2, Version 3.0, for OpenVMS AXP To access DB2 databases residing on IBM systems as sources or tar- gets for data transfer 9 DEC Data Distributor Version 6.0 for OpenVMS AXP SPD 47.12.01 o DEC DB Integrator Gateway for ORACLE, Version 3.0, for OpenVMS AXP To access ORACLE databases residing on the network as sources or targets for data transfer o DEC DB Integrator Gateway for SYBASE, Version 1.0, for OpenVMS AXP To access SYBASE databases residing on the network as sources or targets for data transfer o DEC DB Integrator Gateway for RMS, Version 3.0, for OpenVMS AXP To access VMS RMS files on OpenVMS Systems on the network and VSAM data sets on IBM MVS systems as sources for data extraction o DEC DB Integrator Gateway for Custom Drivers, Version 3.0, for Open- VMS AXP To access data sources that lack a turn-key DBI Gateway solution through customer-implemented drivers o DEC DB Integrator Gateway for DSM, Version 1.0 To access Digital Standard M (DSM) globals as sources for data trans- fer o DEC DB Integrator Gateway for DBMS, Version 1.0, for OpenVMS AXP To access DEC DBMS databases as sources for data extraction GROWTH CONSIDERATIONS The minimum hardware/software requirements for any future version of this product may be different from the requirements for the current version. DISTRIBUTION MEDIA This product is available only on the Digital CD-ROM Software Library for OpenVMS AXP. 10 DEC Data Distributor Version 6.0 for OpenVMS AXP SPD 47.12.01 ORDERING INFORMATION Traditional Software Licenses: QL-0QWA*-AA Software Media/Documentation: QA-03XAA-H8 Software Documentation: QA-VDRAA-GZ Software Product Services: QT-0QWA*-** The above information is valid at time of release. Please contact your local Digital Office for the most up-to-date information. Notes: * Denotes variant fields. For additional information on available licenses, services and media refer to the appropriate price book. SOFTWARE LICENSING This software is furnished under the licensing provisions of Digital Equipment Corporation's Standard Terms and Conditions. For more in- formation about Digital's licensing terms and policies, contact your local Digital office. License Management Facility Support This layered product supports the OpenVMS License Management Facil- ity. Traditional licenses are available. A Traditional license per- mits an unlimited number of authorized users to access this product on a single, identified processor. For more information on the License Management Facility, refer to the OpenVMS Operating System documentation. SOFTWARE PRODUCT SERVICES A variety of service options are available from Digital. For more in- formation, contact your local Digital office. 11 DEC Data Distributor Version 6.0 for OpenVMS AXP SPD 47.12.01 SOFTWARE WARRANTY Warranty for this software product is provided by Digital with the pur- chase of a license for the product as defined in the Software Warranty Addendum of this SPD. [TM]DB2 is a trademark of International Business Machines Corpora- tion. [R] ORACLE is a registered trademark of Oracle Corporation. [R] SYBASE is a registered trademark of Sybase, Inc [TM]The DIGITAL Logo, AXP, CDD/Repository, CI, DEC, DECnet, Digital, OpenVMS, VMS, VMS RMS and VMScluster are trademarks of Digital Equipment Corporation. All other trademarks and registered trademarks are the property of their respective owners. ©1994 Digital Equipment Corporation. All rights reserved. 12