5668-788 Data Extract (DXT) Version 2 Release 5

IBM U.S. Sales Manual
Revised:  January 07, 1999.

Table of contents  Document options 
IBM U.S. Product Life Cycle Dates Description
Abstract Technical Description
Product Positioning Planning Information
Highlights Security, Auditability, and Control
 
Printable version
 

 
IBM U.S. Product Life Cycle Dates
Program NumberVRMAnnounced AvailableMarketing Withdrawn Service DiscontinuedReplaced By
5668-7882.05.01991/09/111991/12/20 1995/10/051999/12/155696-703
5668-7882.04.01989/09/191989/12/15 1995/10/051992/12/315696-703
5668-7882.03.01988/02/021988/05/20 1995/10/051990/12/315696-703

Back to top
 
Abstract

(For IBM US, No Longer Available as of October 5, 1995)

Data Extract* (DXT*) extracts data from a source data base or file, reformats this data, and loads it into a target data base or file. The data sources and target can be on different systems and in different locations.

In the MVS environment, data can be extracted from:

  • IBM IMS/VS data sources
  • IBM DATABASE 2* (DB2*) data bases
  • VSAM files
  • Physical sequential files

DXT provides facilities for data extraction from a variety of MVS data sources, including those managed and maintained by non-IBM products, and Integration Exchange Format (IXF) files.

In the VM environment, data can be extracted from Structured Query Language/Data System (SQL/DS) relational data bases.

The target for data extracted from either MVS or VM sources may be:

  • A relational data base (DB2 or SQL/DS) for access by such programs as Query Management Facility (QMF*) or Application System (AS)

  • A physical sequential data set or CMS file (which can be routed to the Application System/4001*) (AS/400*)

  • An IXF data set or file. (IXF is a data format that can be used for transferring data between programs.)

DXT/D1* lets DXT Version 2 Release 5 users on MVS/Extended Architecture (MVS/XA*) and MVS/ESA extract data data sources operating under the control of DEC(1)/VMS(1) operating systems. Extracts from ORACLE(2), INGRES(3), Rdb(1) (DEC VAX Relational), and VMS/Record Management System (RMS) sequential files are supported directly. DXT/D1 users also have facilities, consistent with DXT Version 2 Release 5, to extract data from other VMS sources. DXT/D1 data targets include relational data bases (DB2 on MVS or SQL/DS on VM or VSE), MVS physical sequential files or CMS files. Extracted data can also be routed to an AS/400.
Back to top
 

Product Positioning

DXT is one of a number of tools for data-processing professionals to use to meet their varied requirements for data access. DXT is the recommended product when data is to be extracted from a data source and moved between different subsystems on the same processor or between subsystems on different processors.

For users who want to complement DXT or DXT/D1 with other IBM products:

  • QMF lets users create or run DXT extract requests from QMF.

  • AS lets users create or run DXT extract requests from AS.

  • Enhanced Connectivity Facilities (ECF) CMS or TSO/E Servers/Requesters provides a personal computer user with the ability to run a predefined DXT extract request and to download extracted data to the personal computer for use by a variety of personal computer software.

For DXT Version 2 Release 5, panels, and their associated messages and help panels, and certain publications have been translated into Japanese.

DXT/D1 Version 1 Release 1 has not been translated into Japanese. DXT/D1 does not contain any panels as the extract request is initiated from DXT Version 2 Release 5 on an MVS system.
Back to top
 

Highlights

  • Incorporates selected Data Extract Assist (DXTA) product functions into DXT to save the DXT administrator time by capturing existing data descriptions from IMS libraries and program source libraries.

  • Expands the non-relational SELECT capability with the addition of ORDER BY and numeric keys, thereby providing user applications with added flexibility

  • Improves performance when eligible extracts are performed using the Hi-Speed Sequential Retrieval (HSSR) feature of the IMS System Utilities/Data Base Tools

  • Allows user extract requests to remain queued after successful execution. These requests can then be re-executed later without the user having to resubmit them.

Back to top
 
Description

What's New in DXT Version 2 Release 5

Structures Access Program (SAP): Selected Data Extract Assist (DXTA) function has been incorporated into DXT as the Structures Access Program. The SAP function helps create DXT data descriptions using IMS data base definitions, COBOL structures, and PL/I structures that are already stored in existing IMS libraries and program source libraries. The SAP function generates the data and file description statements, DXT extract requests, and the statements needed to create a relational table and stores them in the DXT File Description Library (FDTLIB).

Expanded SELECT capability: DXT has added the ORDER BY keyword to the DXT SQL SELECT statement used when extracting data from non-relational sources. As many as eight of the extracted fields can be ordered in either ascending or descending sequence. Support has been added for numeric keys for non-relational data bases, including packed decimal, halfword binary, fullword binary, zoned decimal, and character.

Option to use HSSR: DXT supports the use of the High-Speed Sequential Retrieval (HSSR) function of the IMS/VS Data Base Tools program product to reduce the processing time when accessing IMS data bases sequentially.

Persistent extract: DXT provides a new keyword to use when submitting an extract request that allows users to specify whether they would like the extract request to remain (persist) in the extract request library, EXTLIB, after processing. With this keyword, the user can rerun the persistent extract requests without having to recreate them and send them to the EXTLIB.

Map capture exit enhancements to support data propagation: DXT provides the Map Capture Exit with the information that Data Propagator (DProp) needs to determine which DXTPCBs or DXTFILEs were referenced in the original extract request.

New relational data types: DXT supports all relational data types available with DB2 and SQL/DS data base management systems. Source data can include the DB2 and SQL/DS Extended Packed Decimal and FOR BIT DATA.

General DXT Description

DXT offers several extract methods.

  • End User Dialogs

    The End User Dialogs provide a series of panels that help the user build extract requests based on the data descriptions and JCL set up by the DXT administrator.

  • Administrative Dialogs

    Administrative Dialogs let users use the ISPF editor to create and submit extract requests. Models are provided to help users create data descriptions, JCL, and extract requests.

  • Online DXT commands

    Online DXT commands let users create data descriptions and build and submit extract requests online in the TSO foreground rather than submit a job for batch processing. The Online DXT commands are TSO REXX EXECs that can be issued at the TSO command line either inside or outside of ISPF.

  • User-written extract requests

    A user can use an editor to create a job by entering JCL and DXT commands and then submit this job for batch processing.

DXT consists of the base product and four features. In addition to installing the base product, a user must install either the General Data Extract Feature or the Relational Data Extract Feature to extract any type of data from source data bases or files.

  • The DXT base product includes the DXT dialogs and the online DXT commands.

  • The General Data Extract Feature allows extraction of data from hierarchical data bases, physical sequential data sets, and other relational and non-relational data sources under MVS. It includes:

    • User Input Manager (UIM)

      The UIM validates and stores file and data base descriptions in the file description table library (FDTLIB). The UIM also validates and puts the Data Extract Manager (DEM) extract requests in a queue -- the extract request library (EXTLIB).

    • Data Extract Manager (DEM)

      The DEM extracts data from a variety of data bases and file types including:

      • IMS data bases (MVS)

      • VSAM data sets (MVS)

      • Physical sequential data sets (MVS)

      • Data sources requiring a GDI exit (MVS, and using the DXT/D1 product, VMS)

    • Dictionary Access Program (DAP)

      This program generates data descriptions of the source files and non- relational data bases from which data is extracted. The descriptions are taken from existing definitions in the IBM Data Dictionary.

    • Structures Access Program (SAP)

      This program generates DXT data descriptions using IMS data bases definitions, COBOL structures, and PL/I structures specified by the user. The SAP can generate requests to extract data from the described data sources, as well as a statement that will create a DB2 table as the data target.

  • The Relational Data Extract Feature allows extraction of data from DB2 or SQL/DS relational data bases.

  • The Uppercase Feature allows the use of DXT dialogs on Japanese Katakana terminals.

  • The Japanese Language Feature is composed of DXT dialogs and end user messages that have been translated into Japanese.

DXT function can be extended with exit routines. Exit routines are user-written programs in PL/I, COBOL, and Assembler that work with DXT to perform a task that DXT otherwise does not perform. DXT provides six types of exits:

  • Accounting exits let users keep track of the resources used by the DXT Data Extract Manager (DEM) in the General Data Extract Feature. Typical accounting exits include:

    • Identifying authorized DEM users

    • Preventing unauthorized users from running the DEM

    • Changing the priority and output limits of extract requests

  • Data exits let users make whatever changes they want to the extracted data before DXT processes it. For example, data exits can:

    • Suppress source fields or create new fields for extraction

    • Create several logical records or segments from one physical source record or segment

    • Alter or combine data

    • Summarize data

    • Decompress or decrypt data

  • Date/time conversion exit lets users reformat data and time data into the International Organization for Standardization (ISO) format for DXT.

  • Generic data interface (GDI) exit lets users access data from many data sources that cannot be accessed directly by the Data Extract Manager (DEM) of the General Data Extract Feature. GDI exits let users to:

    • Extract data from non-IBM data sources

    • Extract data from IXF files

    • Perform a two-stage extract for DB2 data

    • Join data from among many types of data sources

  • Map capture exit provides users with all of the DXT definition and extract request information for a specified extract so that the information can be saved or used with DProp for data propagation.

  • User data type exit lets users convert any unique data types to a format DXT uses.

DXT includes sample exit routines and interface control blocks for each type of exit routine.
Back to top
 

Technical Description
Operating Environment Hardware Requirements Software Requirements


Operating Environment

See Hardware and Software Requirements.

Hardware Requirements

DXT Version 2 operates on any IBM processor supported by the operating systems specified in the section "Software required for DXT function."

The processors must have sufficient real storage to satisfy the combined requirements of the data sources and targets, the operating system(s), appropriate access methods, DXT and its software prerequisites, batch requirements, and other customer-required applications. The configuration must include a sufficient number of input/output (I/O) devices to support the requirements for system output, system residence, and system data sets. Sufficient direct access storage must be available to satisfy the user's information storage requirements and may consist of any direct access facility supported by the system configuration and operating system.

DXT/D1 Version 1 Release 1 will operate on any DEC VAX processor supported by VAX/VMS Version 5.0 or later.

The processors must have sufficient real storage to satisfy the combined requirements of VMS, VMS/SNA Version 1.3, DECnet(1)/SNA VMS APPC/LU6.2 Version 2.1-7, DXT/D1 Version 1 Release 1, appropriate data sources, as well as other customer-required applications.

To install DXT/D1, the user needs:

  • One VAX/VMS system with a minimum of 15,000 blocks available on the system disk
  • One VAX terminal
  • Related VAX hardware associated with VMS/SNA Version 1.3 or DECnet/SNA VMS Gateway
  • Either one nine-track VAX tape drive and controller or one cartridge VAX TK50 drive and controller.

Software Requirements

Software Required for DXT Function

The following section lists the programs required to install and use DXT Version 2 Release 5. Later releases are supported unless noted.

  • MVS/370

    Note: This is the last release of DXT to support MVS/370.

    • MVS/SP-JES2 (5740-XYS) Version 1 Release 3 Modification 4, or MVS/SP-JES3 (5740-XYN) Version 1 Release 3 Modification 4
    • MVS/370 Data Facility Product (5665-295) Version 1 Release 1 Modification 2
    • System Modification Program Extended (SMP/E) (5668-949) Version 1 Release 5 for installation of DXT

  • MVS/XA
    • MVS/XA-JES2 (5740-XC6) Version 2 Release 2, or MVS/XA-JES3 (5665-291) Version 2 Release 2 Modification 1
    • MVS/XA Data Facility Product (5665-XA2) Version 2 Release 4
    • System Modification Program Extended (SMP/E) (5668-949) Version 1 Release 5 for installation of DXT

  • MVS/ESA
    • MVS/System Product-JES2 (5685-001) Version 3 Release 1, or
    • MVS/System Product-JES2 (5695-047) Version 4 Release 1, or
    • MVS/System Product-JES3 (5685-002) Version 3 Release 1, or
    • MVS/System Product-JES3 (5695-048) Version 4 Release 1
    • MVS/Data Facility Product (5665-XA3) Version 3 Release 2
    • System Modification Program Extended (SMP/E) (5668-949) Version 1 Release 5 for installation of DXT

  • VM/SP
    • VM/SP (5664-167) Version 1 Release 5 with APAR VM34760
    • VM/SP (5664-167) Version 1 Release 6

  • VM/XA
    • VM/XA SP (5664-308) Version 1 Release 2 Modification 1

  • VM/ESA
    • VM/ESA SP (5684-112) Version 1 Release 1

Software Required for Optional Function

The following section lists the software required to run the optional- use functions included with the DXT base product. Later releases will also be supported unless noted.

  • Online DXT commands
    • TSO/E (5685-025) Version 2 Release 1

  • MVS End User or Administrative Dialogs
    • Interactive System Productivity Facility (ISPF-MVS) (5665-319) Version 2 Release 3, or Interactive System Productivity Facility (ISPF-MVS) (5685-054) Version 3 Release 2
    • Interactive System Productivity Facility/Program Development Facility (ISPF/PDF-MVS) (5665-317) Version 2 Release 3, or Interactive System Productivity Facility/Program Development Facility (ISPF/PDF-MVS) (5665-402) Version 3 Release 2

  • VM End User or Administrative Dialogs
    • Interactive System Productivity Facility (ISPF-VM/SP) (5664-282) Version 2 Release 2, or Interactive System Productivity Facility (ISPF-VM/SP) (5684-043) Version 3 Release 2
    • Interactive System Productivity Facility/Program Development Facility (ISPF/PDF-VM/SP) (5664-285) Version 2 Release 2, or Interactive System Productivity Facility/Program Development Facility (ISPF/PDF-VM/SP) (5684-123) Version 3 Release 1

The following section lists the software required to run the optional- use features of DXT Version 2 Release 5 Later releases will also be supported unless noted.

  • General Data Extract Feature (Only available in MVS)

    • Extract data from IMS/VS DL/I data base
      • IMS/VS (5740-XX2) Version 1 Release 3, or IMS/VS (5665-332) Version 2 Release 2
      • IMS/ESA* (5665-408 for batch mode) Version 3 Release 1
      • Optionally, Hi-Speed Sequential Access (HSSR) which is a feature of the IMS/VS Data Base Tools (DBT) program product (5685-093) Version 2 Release 1

    • Extract data from CICS/OS/VS DL/I data base
      • CICS/OS/VS (5740-XX1) Version 1 Release 7
      • CICS/MVS* (5665-403) Version 2 Release 1
      • CICS/ESA* (5685-083) Version 3 Release 1

    • Extract data descriptions with Dictionary Access Program (DAP)

    • OS/VS DB/DC Data Dictionary (5740-XXF) Version 1 Release 6

    • ORDER BY

      • Data Facility Sort (5740-SM1) Version 1 Release 11

    • Write exit routines

      For exits written in COBOL/370:

      • Language Environment/370 Version 1 Release 1 (5688-198) (includes the runtime environment and library of runtime services for IBM SAA AD/Cycle COBOL/370 application development and execution) is required to write exit routines using COBOL/370.
      • COBOL/370 Version 1 Release 1 (5688-197) (includes the COBOL/370 compiler supporting Language Environment/370 is required to compile exit routines written in COBOL/370.

      For exits written in PL/I:

      • OS PL/1 Optimizing Compiler (5668-910) Version 2 Release 2

      For exits written in VS COBOL II:

      • VS COBOL II (5668-958) Version 1 Release 3.0

      For exits written in ASSEMBLER:

      • ASSEMBLER H (5668-962) Version 2 Release 1

    • RACF for data security
      • Resource Access Control Facility (RACF) (5740-XXH) Version 1 Release 8

    • Structures Access Program (SAP) for generating data descriptions

    • OS PL/I Runtime Library (5668-910) Version 2 Release 2

  • Relational Data Extract Feature

    • Extracting data from DB2
      • IBM DATABASE 2* (5740-XYR) Version 1 Release 3, or IBM DATABASE 2 (5665-DB2) Version 2 Release 2

      Using FOR BIT DATA, extended packed decimal, or 750 columns:

      • IBM DATABASE 2 (5665-DB2) Version 2 Release 3

    • Extracting data from SQL/DS data base
      • SQL/Data System (SQL/DS) Product (5688-004) Version 2 Release 1

      If using SINGLE PRECISION FLOATING POINT data types, or VM/XA 31 Bit Addressing:

      • SQL/Data System (SQL/DS) Product (5688-004) Version 2 Release 2

      If using VM/ESA or FOR BIT DATA:

      • SQL/Data System (SQL/DS) Product (5688-103) Version 3 Release 1

      If using extended packed decimal support:

      • SQL/Data System (SQL/DS) Product (5688-103) Version 3 Release 2

The following section lists the functions of optional-use programs that work with DXT Version 2 Release 5 and specifies the product releases required. Later releases are also supported unless otherwise noted.

  • Send objects between VM or MVS nodes
    • Remote Spooling Communications Subsystem (RSCS) (5664-188) Version 2 Release 2, or Remote Spooling Communications Subsystem (RSCS) (5684-096) Version 3 Release 1

  • Data propagation between IMS and DB2 data bases

    • Data Propagator MVS/ESA (DProp) (5685-124) Release 1

  • QMF report writing

    In MVS:

    • Query Management Facility (QMF) in MVS (5668-721) Version 2 Release 4, or Query Management Facility (QMF) in MVS (5706-254) Version 3 Release 1

    In VM:

    • Query Management Facility (QMF) in VM (5668-AAA) Version 2 Release 4, or Query Management Facility (QMF) in VM (5706-255) Version 3 Release 1

  • AS decision support
    • Application System (AS) (5767-032) Version 1 Release 5, or Application System (AS) (5688-108) Version 2 Release 1

  • Enhanced Connectivity Facilities (ECF) PC-to-host connection

    For MVS:

    • Enhanced Connectivity Facilities TSO/E Servers/Requestors (5665-396) Version 1 Release 2 for MVS

    For VM:

    • Enhanced Connectivity Facilities CMS Servers/Requestors (5664-327) Version 1 Release 2 for VM

  • Invoke DXT/D1 product on a DEC operating system
    • ACF/VTAM (5665-289) Version 3 Release 3
    • C/370 Runtime Library (5688-039) Version 1 Release 2, or C/370 Runtime Library (5688-188) Version 2 Release 1

One of the following programs is required to use the displayable softcopies of the DXT manuals:

  • BookManager READ/MVS (5695-046), BookManager READ/VM (5684-062), BookManager READ/2 (5601-454), or BookManager READ/DOS (5601-453)

DXT/D1 software requirements: The following programs are required to install and use DXT/D1 Version 1 Release 1:

  • Data Extract (DXT) (5668-788) base product and General Data Extract Feature Version 2 Release 5 installed together on an MVS operating system
  • Data Extract/D1 (DXT/D1) (5684-077) installed on a DEC VMS operating system
  • IBM C/370 Runtime Library (5688-039)
  • ACF/VTAM MVS/370 or MVS/XA (5665-289) Version 3 Release 3
  • DECnet/SNA VMS APPC/LU6.2 Programming Interface Version 2.1-7
  • VMS/SNA Version 1.3 or DECnet/SNA VMS Gateway

Software required for optional DXT/D1 function: The following programs are required to install and use the optional functions and components of DXT/D1 Version 1 Release 1.

  • Writing GDI exits
    • VAX COBOL Version 4, or VAX PASCAL Version 3.7, or VAX C Version 3.1

  • Extracting from ORACLE
    • ORACLE DBMS Version 5.1.22 and 6.0

  • Extracting from ORACLE with a user-written GDI exit
    • ORACLE PRO*C(2) Version 1.3.16

  • Extracting from INGRES
    • INGRES DBMS Version 6.1

  • Extracting from Rdb
    • VAX Rdb/VMS Version 2.3
    • VAX SQL Version 1.1

  • Double Byte Character Set (DBCS) Support for DXT Version 2 Release 4 requires:
    • IBM 5550 3270 Emulation Software (5600-JTE) or equivalent
    • IBM 5550 Kanji workstation or equivalent

    Japanese Language Feature is supported by DXT Version 2 Release 4 DBCS support.

  • Katakana Keyboard support by DXT Version 2 Release 4 requires DXT Upper Case Feature.

Back to top
 
Planning Information

Customer Responsibilities

A customer installing DXT Version 2 Release 5 and DXT/D1 Version 1 Release 1 must:

  • Perform user administration tasks, such as setting up user profiles and providing data descriptions to users.
  • Provide adequate protection against the accidental loss or misuse of user data.

If a customer is extracting data created by a third party vendor program, it is the customer's responsibility to ensure that the extraction of the data and use of the data formats conforms to any third party vendor restrictions imposed by the vendor's license or otherwise.

Factors to be considered for installing the Japanese language feature are documented in the Data Extract (DXT) Version 2 Release 5 "Planning and Administration Guide". The Japanese language feature must be installed only after the base product is installed.

Limitations

Limitations on MVS/370 systems: Certain new features in DXT Version 2 Release 5 require prerequisite products that are not available for MVS/370. Therefore, only persistent extract, Structure Access Program, support for numeric keys for non-relational data bases, and the ORDER BY keyword in UIM/DEM extracts are supported for MVS/370.

Storage limitations: DXT Version 2 Release 4 resides in 24-bit or 3 1-bit storage and accesses 24-bit and 31-bit storage. Two modules, the Dictionary Access Program and the Sequential File I/O Program, cannot be loaded above the 16MB line.

The Data Extract Module, when used with HSSR, cannot be loaded above the 16MB line.

Virtual Storage Requirements

Storage used by the DXT set of functions will vary depending on the nature of the extract request. The minimum virtual storage requirements for DXT Version 2 Release 5 are as follows:

  • DXT Base Product

    790KB to store the base load modules

    • Dialogs

      3500KB region size to run a job (ISPF/TSO logon size)

    • Data Reformat Utility

      400KB region size to run a job

    • MIT Build Program

      800KB region size to run a job

    • Dialogs Migration Utility for administration tables

      800KB region size to run a job

  • DXT Relational Data Extract Feature

    • Relational Extract Manager (REM)

      • 290KB to store the load module

      • 750KB region size to run a job

  • DXT General Data Extract Feature

    3031KB to store the load modules

    • DXT Dictionary Access Program (DAP)

      4096KB region size to run in an IMS batch region (in addition to OS/VS DB/DC Data Dictionary requirements)

    • DXT User Input Manager (UIM)

      2048KB region size to execute a typical job

    • DXT Data Extract Manager (DEM)

      • 2048KB region size to execute an IMS batch job

      • 2048KB region size to execute a non-IMS batch job

    • DXT Migration for FDTLIB

      500KB region size to execute a typical job.

    • Structures Access Program (SAP)

      1024KB ISPF/TSO batch region size

DXT/D1 Version 1 Release 1:

The VAX disk requirements are 15,000 blocks to store DXT/D1.

The minimum virtual storage requirements for DXT/D1 on VAX are 9,000 blocks to execute a typical job plus user GDI exits (if using them).

The minimum storage requirements for DXT/D1 on MVS are:

  • 65KB to store load module
  • 400KB of MVS virtual storage to run DXT/D1 communications module

Because of the presence of national language characters in the Japanese language feature, use of that feature requires terminals, controllers, keyboards, and printers that use the corresponding national language code page, and appropriate machine logic.

Compatibility

The following are migration considerations if a previous release of DXT is installed:

  • If DXT Version 2 Release 3 is installed:

    • During installation the migration utility must be used to migrate the Master Index Table (MIT).

    • For dialog migration, extract requests, data description requests, and JCL/JCS files are automatically migrated the first time the dialogs are run.

    • Accounting exits must be link-edited to the new release and data exits must be recompiled.

    • All user exits must be recompiled and link-edited.

    • COBOL user exit routines must be recompiled using the COBOL/370 compiler if access to the routine is to be via Language Environment/370.

    • FDTLIB migration utility must be run.

  • If DXT Version 2 Release 4 is installed:

    • Accounting exits must be link-edited to the new release.

    • COBOL user exit routines must be recompiled using the COBOL/370 compiler if access to the routine is to be via Language Environment/370.

DXT/D1 Version 1 Release 1: There are no migration considerations for DXT/D1.
Back to top
 

Security, Auditability, and Control

DXT Version 2 Release 5: DXT Version 2 Release 5 uses the security and auditability features of the MVS and VM operating systems, the SQL/DS, DB2, and IMS data base systems, and RACF in an MVS environment. When DXT is installed on MVS, System Authorization Facility (SAF) can be used to conditionally direct control to RACF to use other equipment manufacturer's security packages with DXT.

The DXT Administrative Dialogs can be used to set up a security system which permits End User Dialogs users to see only the definitions for data for which they have authorization.

DXT/D1 Version 1 Release 1: DXT/D1 depends on the security features employed on the MVS system (from which the request is initiated) as well as the existing security software available on the VMS system. RACF is employed on the MVS system to restrict unauthorized users from accessing DXT data. VMS-supported security mechanisms include User Identification Code (UIC) protection and Access Control List (ACL) protection. The security features of the various database managers may be used to provide an additional layer of security. Proxy accounts will provide access to VMS data sources. User management is responsible for evaluation, selection, and implementation of security features, administrative procedures, and appropriate controls in application systems and communication facilities.

(1) Trademarks of Digital Equipment Corporation. (2) Registered trademark of Oracle Corporation. (3) Trademark of Relational Technology, Inc.  

Trademarks

(R), (TM), * Trademark or registered trademark of International Business Machines Corporation.

** Company, product, or service name may be a trademark or service mark of others.
 © IBM Corporation 2003.

Share this page

Digg Linked In

Contact IBM

Feedback

-->