UNISYS. Business Information Server. MRI Administration and User s Guide. Printed in USA May

Size: px
Start display at page:

Download "UNISYS. Business Information Server. MRI Administration and User s Guide. Printed in USA May 2004 7846 0391 013"

Transcription

1 Business Information Server MRI Administration and User s Guide UNISYS 2004 Unisys Corporation. All rights reserved. Printed in USA May

2 NO WARRANTIES OF ANY NATURE ARE EXTENDED BY THIS DOCUMENT. Any product or related information described herein is only furnished pursuant and subject to the terms and conditions of a duly executed agreement to purchase or lease equipment or to license software. The only warranties made by Unisys, if any, with respect to the products described in this document are set forth in such agreement. Unisys cannot accept any financial or other responsibility that may be the result of your use of the information in this document or software material, including direct, special, or consequential damages. You should be very careful to ensure that the use of this information and/or software material complies with the laws, rules, and regulations of the jurisdictions with respect to which it is used. The information contained herein is subject to change without notice. Revisions may be issued to advise of such changes and/or additions. Notice to U.S. Government End Users: This is commercial computer software or hardware documentation developed at private expense. Use, reproduction, or disclosure by the Government is subject to the terms of Unisys standard commercial license for the products, and where applicable, the restricted/limited rights provisions of the contract data rights clauses. Correspondence regarding this publication can be ed to doc@unisys.com. Unisys is a registered trademark of Unisys Corporation in the United States and other countries. All other brands and products referenced in this document are acknowledged to be the trademarks or registered trademarks of their respective holders.

3 Table of Contents ABOUT THIS GUIDE PLATFORM-SPECIFIC INFORMATION NOTATION CONVENTIONS INTRODUCING MRI MRI OVERVIEW MRI COMPONENTS RELATIONAL INTERFACE MANAGER (MRIM) MRI STATEMENTS LOG ON TO RELATIONAL DATABASE (LGN) DATA DEFINITION INFORMATION (DDI) RELATIONAL AGGREGATE FETCH (FCH) RELATIONAL AGGREGATE MODIFY (RAM) SUBMIT SQL (SQL) TRACE RELATIONAL SYNTAX (TRC) LOG OFF RELATIONAL DATABASE (LGF) STORED PROCEDURE INTERFACE (SPI) RELATIONAL DATABASE INTERFACE (RDI) MRI DATABASE ADMINISTRATION (MRIDBA) ACCESSING DATABASES THROUGH MRI LOCAL DATABASE CONNECTIONS REMOTE DATABASE CONNECTIONS CONFIGURING MRI WITH MRIDBA STARTING MRIDBA OBTAINING SYSTEM SETUP INSTRUCTIONS REGISTERING DATABASE NAMES REGISTERING A NAME FOR A LOCAL DATABASE

4 ENTERING A DATABASE NAME FOR A LOCAL DATABASE CHOOSING A LOCAL DATABASE TYPE PROVIDING LOCAL DATABASE REGISTRATION INFORMATION REGISTERING A DATABASE NAME FOR A REMOTE DATABASE ENTERING A REMOTE DATABASE NAME CHOOSING A REMOTE DATABASE TYPE FILLING IN THE COMMUNICATIONS TYPE MENU PROVIDING REMOTE DATABASE REGISTRATION INFORMATION UTILIZING DOMAIN NAMES FOR REMOTE 2200 MRI ACCESS DATABASE REGISTRATION AND CONFIGURATION EXAMPLES REGISTERING A LOCAL ORACLE DATABASE EXAMPLE REGISTERING A LOCAL ODBC DATABASE EXAMPLE REGISTERING A REMOTE INFORMIX DATABASE EXAMPLE SETTING UP APPLICATION GROUPS CONFIGURING SETUP PARAMETERS CREATING STORAGE AREAS CREATING DEMONSTRATION TABLES SETTING PUBLIC DEFAULTS SETTING RDI PRIVILEGES SETTING USER DEFAULTS REGISTERING LOCAL SUBROUTINES CLEANING UP ADMINISTRATION REPORTS DISPLAYING ACTIVE THREADS STATUS SETTING UP MRI FILES SETTING UP A REMOTE CONFIGURATION FILE EXAMPLE OF SETTING UP A REMOTE FILE SETTING UP A LOCAL OR REMOTE PARAMETER FILE CREATING STORAGE SPACE

5 OBTAINING DETAILED HELP SETTING UP ODBC DATA SOURCE NAMES CONFIGURING AND REGISTERING AN ODBC DATA SOURCE NAME VALID ODBC SUBTYPES SPECIFYING A PATH TO A REMOTE DATABASE FILE SETTING UP THE NORTHWIND DATA SOURCE NAME MANAGING OLE DB DATA SOURCES OLE DB PROVIDERS ACCESSING DATABASE THROUGH RDI INTRODUCING RDI ADVANTAGES OF USING RDI ACCESSING RDI FROM THE CONTROL LINE ACCESSING RDI FROM THE MENU USING THE RDI COMMANDS RETRIEVING DATA USING SELECT TABLE NAME COLUMN NAMES WHERE CLAUSE RETRIEVE ALL ROWS IF NO, HOW MANY NUMBER OF ROWS TO SKIP NULL SYMBOL EXTRA OPTIONS USING THE SELECT COMMAND SPECIAL OPTIONS MENU EXPLAIN SELECT CLAUSE DO THIS REQUEST IN THE BACKGROUND USING THE SELECT OPTIONS MENU ORDER BY

6 GROUP BY WOULD YOU LIKE DISTINCT COLUMNS WRAP ROWS IF THEY EXCEED REPORT WIDTH SIZE OF BLANK FIELDS BETWEEN EACH COLUMN DISPLAY INFORMATION VERTICALLY? (ONE LINE PER COLUMN) JUSTIFY COLUMN NAMES FOR VERTICAL DISPLAY LOCAL CODE BEFORE LOCAL CODE AFTER REPORT TEMPLATE (FROM REPORT WRITER) SAVING SQL SYNTAX IN A REPORT RETRIEVING DATA USING JOIN TABLE NAMES COLUMN NAMES WHERE CLAUSE RETRIEVE ALL ROWS? IF NO, HOW MANY NUMBER OF ROWS TO SKIP NULL SYMBOL EXTRA OPTIONS SPECIAL OPTIONS MENU USING THE JOIN OPTIONS MENU ORDER BY GROUP BY WOULD YOU LIKE DISTINCT COLUMNS? WRAP ROWS IF THEY EXCEED REPORT WIDTH SIZE OF BLANK FIELDS BETWEEN EACH COLUMN DISPLAY INFORMATION VERTICALLY (ONE LINE PER COLUMN) JUSTIFY COLUMN NAMES FOR VERTICAL DISPLAY

7 LOCAL CODE BEFORE LOCAL CODE AFTER REPORT TEMPLATE (FROM REPORT WRITER) ADDING NEW TABLE ROWS USING INSERT TABLE NAME NULL SYMBOL REMOVING DATA WITH DELETE TABLE NAME WHERE CLAUSE NULL SYMBOL CHANGING DATA USING UPDATE TABLE NAME COLUMN NAMES NEW VALUES WHERE CLAUSE NULL SYMBOL DEFINING NEW TABLES USING CREATE TABLE NAME STORAGE SPACE CREATE FROM REPORT AND DRAWER FREEFORM CREATE INSERT DATA LINES INCREASE INTEGER FIELDS NULL SYMBOL EXTRA OPTIONS SUBMITTING SQL WITH THE SQL COMMAND REPORT SQL REQUEST

8 PROCESS REQUEST IMMEDIATELY ACCESSING THE RDI UTILITIES MENU USING ALTER TABLE CHANGE COLUMNS ADD COLUMNS DROP COLUMNS ADD INDEX DROP INDEX ADD FOREIGN KEY DROP FOREIGN KEY USING RESTRICT TABLE GRANT USERS ACCESS TO A TABLE REVOKE ACCESS FROM A RESTRICTED TABLE RESTRICT AN EXISTING TABLE UNRESTRICT A RESTRICTED TABLE USING DESTROY TABLE USING CREATE VIEW NEW VIEW NAME TABLE NAMES COLUMN NAMES WHERE CLAUSE TEST ALL ROWS IF NO, ENTER MAXIMUM QUANTITY EXTRA OPTIONS USING CREATE VIEW OPTIONS GROUP BY WOULD YOU LIKE DISTINCT COLUMNS? WOULD YOU LIKE CHECKING WITH INSERTS AND UPDATES?

9 SHOULD ACCESS CONTROL BE TURNED ON? USING DROP VIEW USING MRI STATEMENTS TO ACCESS RELATIONAL DATA CREATING TABLES CREATING A TABLE WITH RAM CREATING A TABLE AND INSERTING DATA WITH RAM CREATING A TABLE WITH SQL INSERTING DATA INTO A RELATIONAL TABLE INSERTING DATA FROM A REPORT USING RAM IN CONJUNCTION WITH FCH INSERTING DATA WITH SQL RETRIEVING DATA WITH FCH RETRIEVING DATA FROM A SINGLE TABLE JOINING TABLES WITH FCH UPDATING DATA WITH FCH AND RAM USING FCH FOR DATA RETRIEVAL INSERTING UPDATED DATA WITH RAM DELETING DATA WITH FCH AND RAM RETRIEVING DATA WITH FCH DELETING DATA WITH RAM USING THE WHERE CLAUSE WITH RAM DROPPING TABLES WITH RAM RETRIEVING DATA INTO SCRIPT VARIABLES WITH SQL EXECUTING STORED PROCEDURES WITH SPI EXECUTING A STORED PROCEDURE EXAMPLE EXECUTING A STORED PROCEDURE EXAMPLE EXECUTING A STORED PROCEDURE EXAMPLE TROUBLESHOOTING

10 GUIDELINES FOR ACCESSING INFORMATION THROUGH DATABASE MANAGERS MRI INTERFACE TO ODBC DATABASE MANAGERS MODIFYING A RELATIONAL DATABASE CREATING TABLES WITH ODBC ACCESSING LISTS OF USER TABLES, VIEWS, AND SYSTEM TABLES RETRIEVING COLUMNS OF DATA WITH ODBC USING THE WHERE CLAUSE IN ODBC ALTERING TABLES WITH ODBC USING DATABASE DATA TYPES WITH ODBC UNDERSTANDING CASE SENSITIVITY IN ODBC MAKING DATA COMMITS AND RECOVERY IN ODBC ADJUSTING DECIMAL FIELDS IN ODBC RETRIEVING DATA WITH THE SQL STATEMENT IN ODBC UNDERSTANDING DATABASE ACCESS AND SECURITY IN ODBC INTERPRETING ODBC ERROR STATUS ORACLE INTERFACE CONSIDERATIONS CREATING AND CHANGING TABLES WITH ORACLE USING THE WHERE CLAUSE IN ORACLE ADDITIONAL OPERATORS ADDITIONAL FUNCTIONS CREATING DATA DEFINITIONS IN ORACLE MAKING DATA COMMITS AND RECOVERY IN ORACLE ADJUSTING DECIMAL FIELDS IN ORACLE USING SQL*NET WITH ORACLE USING ORACLE WITH THE RAM STATEMENT RETRIEVING DATA FROM ORACLE USING THE SQL STATEMENT UNDERSTANDING DATABASE ACCESS AND SECURITY IN ORACLE USING EXTRA OPTIONS FOR ORACLE

11 RELATIONAL DATABASE SERVER INTERFACE CREATING DATA DEFINITIONS IN RELATIONAL DATABASE SERVER MAKING DATA COMMITS AND RECOVERY IN RELATIONAL DATABASE SERVER ADJUSTING DECIMAL FIELDS IN RELATIONAL DATABASE SERVER USING RELATIONAL DATABASE SERVER WITH THE RAM STATEMENT RETRIEVING DATA FROM RELATIONAL DATABASE SERVER USING THE SQL STATEMENT CREATING AND CHANGING TABLES WITH RELATIONAL DATABASE SERVER UNDERSTANDING DATABASE ACCESS AND SECURITY IN RELATIONAL DATABASE SERVER PASSWORD SECURITY RECOVERY OPTIONS SECURITY INFORMIX INTERFACE CREATING AND CHANGING TABLES WITH INFORMIX USING THE WHERE CLAUSE IN INFORMIX ADDITIONAL OPERATORS ADDITIONAL FUNCTIONS CREATING DATA DEFINITIONS IN INFORMIX MAKING DATA COMMITS AND RECOVERY IN INFORMIX ADJUSTING DECIMAL FIELDS IN INFORMIX RETRIEVING DATA FROM INFORMIX USING THE SQL STATEMENT UNDERSTANDING DATABASE ACCESS AND SECURITY IN INFORMIX SYBASE INTERFACE CREATING AND CHANGING TABLES WITH SYBASE USING THE WHERE CLAUSE IN SYBASE ADDITIONAL OPERATORS ADDITIONAL FUNCTIONS CREATING DATA DEFINITIONS IN SYBASE MAKING DATA COMMITS AND RECOVERY IN SYBASE

12 USING SYBASE WITH THE RAM STATEMENT RETRIEVING DATA FROM SYBASE USING THE SQL STATEMENT ADJUSTING DECIMAL FIELDS IN SYBASE USING THE CASE-SENSITIVE FEATURE WITH SYBASE UNDERSTANDING DATABASE ACCESS AND SECURITY IN SYBASE MRI AND RELATIONAL DATABASE NETWORKING NETWORKING OPTIONS WITH RELATIONAL DATABASES NETWORKING WITH ORACLE COMMUNICATING WITH A SINGLE REMOTE DATABASE COMMUNICATING WITH DISTRIBUTED DATABASES NETWORK CONFIGURATION REPORT NETWORKING WITH ODBC NETWORKING WITH OLEDB NETWORKING WITH INFORMIX INFORMIX-NET INFORMIX-STAR NETWORKING WITH SYBASE MRI CONFIGURATION PARAMETER FILES CONFIGURATION PARAMETER DESCRIPTIONS SETTING UP THE MRI PARAMETER FILE SETTING UP THE MRI CONFIGURATION FILE CONFIGURING DATABASE ACCESS CONNECTION POOLING DATABASE ACCESS CONNECTION POOLING OVERVIEW SETTING UP A LOCAL PARAMETER CONFIGURATION FILE CONFIGURING AND VIEWING AN MRIM POOL PROCESS CONFIGURING THE NUMBER OF MRIM PROCESSES IN THE MRI PROCESS POOL STARTING THE CONFIGURED MRIM PROCESSES VIEWING THE STATUS OF CONFIGURED MRIM PROCESSES

13 MRIM PROCESS CONTROL SCREEN CONFIGURATION EXAMPLE REGISTERING BUSINESS INFORMATION SERVER SERVICES TO WORK WITH ODBC USING A WINDOWS SERVICE UNDER A USER ACCOUNT CONSIDERATIONS FOR USING ODBC WITH A WINDOWS SERVICE GLOSSARY A-E GLOSSARY F-L GLOSSARY M-R GLOSSARY S-W

14 About This Guide Copyright 2004 Unisys Corporation. All rights reserved. NO WARRANTIES OF ANY NATURE ARE EXTENDED BY THIS DOCUMENT. Any product or related information described herein is only furnished pursuant and subject to the terms and conditions of a duly executed agreement to purchase or lease equipment or to license software. The only warranties made by Unisys, if any, with respect to the products described in this document are set forth in such agreement. Unisys cannot accept any financial or other responsibility that may be the result of your use of the information in this document or software material, including direct, special, or consequential damages. You should be very careful to ensure that the use of this information and/or software material complies with the laws, rules, and regulations of the jurisdictions with respect to which it is used. The information contained herein is subject to change without notice. Revisions may be issued to advise of such changes and/or additions. RESTRICTED-Notice to Government End Users: This is commercial computer software or hardware documentation developed at private expense. Use, reproduction, or disclosure by the Government is subject to the terms of Unisys standard commercial license for the products, and where applicable, the restricted/limited rights provisions of the contract data rights clauses. Comments about documentation can also be sent through to doc@unisys.com. Unisys is a registered trademark of Unisys Corporation in the United States and other countries. TRADEMARKS-All other brands and products referenced in this document are acknowledged to be the trademarks or registered trademarks of their respective holders Release Levels: Business Information Server Platform UNIX OS Windows Server Windows Client 2200 Release 8R R1 14

15 Platform-Specific Information This Help provides information on the following platforms: Windows Server UNIX OS 2200 Windows Client Some functions on the Business Information Server may produce different results depending on the platform you are using. These platform-specific differences for the Windows Server, UNIX operating system, Windows Client, and OS 2200 platforms appear as follows: Windows Server UNIX OS AUX sn[sl report f] Windows Server UNIX OS Windows Client AUX sn [report f] Windows Client 2200 AUX

16 Notation Conventions This source uses certain style conventions that aid you in understanding both the software and the Help. Following is a description of how syntax, special characters, system-specific information, examples, screen illustrations, italics, and bold type are used. Syntax The format of a command consists of these conventions: The call is in uppercase letters (for example, CHG). However, you can type it in either uppercase or lowercase letters. Fields and subfields are italicized whenever they call for variable data. Variable data is information you supply according to the explanation that follows the command format. Fields or subfields enclosed in brackets are optional. In this example, field2, subfield1, and subfield2 are optional: field1 [field2 subfield1,subfield2] Whenever you make an entry in an optional subfield, you must type all intervening commas. For Braces around items separated by a vertical bar mean that you are to choose from among the items listed. For example: {item1 item2} Special Characters The following characters have special meanings in this guide: [ ] Used around optional entries. If you select the entry, do not type the brackets, just the character or characters inside them. { } Used to show a selection of required fields. In formats, delimits items enclosed in brackets or braces. You choose one of the items to enter, but you do not enter the brackets, braces, or vertical bars. In examples, represents a tab character ( ). > Represents the SOE character in examples and in-report-line formats such as the Add Line format. Examples The examples in this guide are shown in lowercase letters. Unless otherwise specified, you can type them in lowercase or uppercase letters. Whenever possible, examples are created and tested against the demonstration database that come with your system. You can try these examples yourself and receive the same results as shown in this guide. Caution! Be careful when trying examples that update the demonstration database. Do not use functions that add, delete, or change lines while working with report 2B0, 1C0, or 1D0. Use duplicate reports so other users start with the same basic information and get the same results as shown in this guide. Screen Illustrations To help you understand concepts and procedures, this guide uses screen illustrations that closely resemble actual screen displays. However, you may encounter some differences between the illustrations and screen displays. These differences are due to variations among systems, among terminal types, and among characteristics of the databases of each system. These are some of the differences you might find: Symbols shown in screen illustrations may not match your terminal. For example, the SOE character and cursor may be displayed as different symbols on your screen, function key bars may contain different key names, or vertical bars between fields may not display. Key names within screen text may be different. For example, a screen illustration might mention the Transmit key; on the actual screen, it is displayed as XMIT, F5, or whichever key is applicable to your terminal. 16

17 Title lines and date lines may be positioned differently and contain different information. For example, on a Business Information Server for ClearPath OS 2200, the title line might begin with an indicator called a save flag (such in the heading); save flags are not shown on the screen illustrations in this guide. Report numbers, dates, times, and user-ids shown on screen illustrations may be different from those you actually see on your screen. Italics Italics indicate the following values that you supply: The italicized letter N (n or N) stands for a numeral (nn stands for two digits, nnn for three, and so on). Other italicized letters (for example, x and y) indicate user-supplied variables. Bold Type Text in bold type is used for key names, menu or input screen fields, and information you are instructed to type. Example: To start the ICAL run, type ical on the control line and press Transmit. 17

18 Introducing MRI This topic introduces the MRI and its components. It discusses the following: MRI Overview MRI Components Accessing Databases through MRI 18

19 MRI Overview The Relational Interface (MRI) is a feature of Business Information Server that gives users access to external data managers such as OLEDB, ODBC, MS SQL Server, Oracle, INFORMIX, and Sybase. MRI lets you do the following: Retrieve data from an external data manager and bring it into the Business Information Server. The full set of Business Information Server software functions and commands are available for processing the retrieved data. Insert, update, and delete data from tables stored in external data managers, without having to know anything about how the data is actually stored. Create or delete entire tables in external data managers. Together, the Business Information Server and MRI provide a seamless connection to external data. Using MRI, you can access local databases, remote databases using networking between two MRI systems, and remote databases using the database vendor's networking capabilities. 19

20 MRI Components MRI consists of four major components: Relational Interface Manager (MRIM) MRI Statements Relational Database Interface (RDI) MRI Database Administration (MRIDBA) 20

21 Relational Interface Manager (MRIM) The Business Information Server communicates with a low-level server program called the Relational Interface Manager (MRIM). The MRIM program provides the connection between the software system and the relational database management systems supported by MRI. MRIM does the following: 1. Takes a request from the RAM and FCH statements and automatically generates Structured Query Language (SQL) syntax specific to the data manager being called. (The Business Information Server and MRI deal with the idiosyncrasies of the different data managers so you do not need to consider them.) 2. Submits SQL syntax through the application program interface (API) of the data manager. This is the same API that third-generation language (3GL) applications, such as C programs, use. 3. Sends the response (either data or a status value) from the data manager back to the Business Information Server. 21

22 MRI Statements The MRI statements let you perform the full range of relational operations in a system script. These statements instruct software scripts to open sessions with external data managers and to retrieve, create, or modify data. Sites can rapidly develop their own database applications without using 3GLs like COBOL or C. The following statements are available: Log On to Relational Database (LGN) Submit SQL (SQL) Data Definition Information (DDI) Trace Relational Syntax (TRC) Relational Aggregate Fetch (FCH) Log Off Relational Database (LGF) Relational Aggregate Modify (RAM) Stored Procedure Interface (SPI) Relational Database Interface (RDI) Related Topics See Using MRI Statements to Access Relational Data for guidelines on using these statements in Business Information Server scripts. See Guidelines for Accessing Information through Database Managers for guidelines on using MRI statements in scripts that access specific data managers. 22

23 Log On to Relational Database (LGN) The LGN statement begins a session and establishes communications with the relational database management system. After the log-on procedure is complete, the script can Transfer data between a Business Information Server system and the relational database. Turn off the search for Primary Keys for ODBC databases Specify a translation report to translate data between Business Information Server and MRI Related Topic See the Command Reference for the format and description of this statement. 23

24 Data Definition Information (DDI) The DDI statement retrieves a table definition from the relational database. The table definition lists table columns, data types, and column sizes. It also identifies the primary keys and the columns that allow null values. Related Topic See the Command Reference for the format and description of this statement. 24

25 Relational Aggregate Fetch (FCH) The FCH statement retrieves data from the relational database and places it in a temporary report. You can use the FCH statement to Retrieve data from a single table Perform a Join query Retrieve large amounts of data from a relational database and display this data in a temporary report You can manipulate the report and then enter a RAM statement to update the database. Related Topic See the Command Reference for the format and description of the FCH statement. 25

26 Relational Aggregate Modify (RAM) The RAM statement lets you define or manipulate relational data using reports. The RAM statement performs the following relational operations: Creates a table using the headings in a report as columns Inserts the data lines in a report into a relational table Changes or delete rows in a relational table based on data stored in a report Drops a table definition from the relational database does not support Delete and Update for Text and Excel ODBC Databases. Related Topic See the Command Reference for the format and description of the RAM statement. 26

27 Submit SQL (SQL) The SQL statement submits SQL syntax directly to the relational database management system. You can use it to perform tasks that cannot be accomplished with other statements, such as indexing a relational table to improve performance under certain conditions. You can include the SQL syntax in the Business Information Server run statement or store it in a report. Related Topic See the Command Reference for the format and description of the SQL statement. 27

28 Trace Relational Syntax (TRC) The TRC statement stores SQL code generated during a relational session in a report. You can use the SQL code for debug purposes, or you can save it and use it with SQL or FCH statements. Related Topic See the Command Reference for the format and description of the TRC statement. 28

29 Log Off Relational Database (LGF) The LGF statement terminates the connection with the relational database. Related Topic See the Command Reference for the format and description of this statement. 29

30 Stored Procedure Interface (SPI) Windows Server Windows Client The SPI statement provides the ability to execute a specified stored procedure and return the results. It also provides a method to query and return meta-data about stored procedures in a database catalog. Related Topic See the Command Reference for the format and description of this statement. Note: For ODBC and OLEDB databases only. Windows Server Windows Client 30

31 Relational Database Interface (RDI) The Relational Database Interface (RDI) is an application that lets you access relational databases through MRI. With this program, you can access MRI statements indirectly by specifying a relational operation and selecting or supplying a table name along with supporting information. The application then submits the information to the relational database using the appropriate MRI statement, and returns data to the RDI application for display. RDI lets you perform the full range of relational operations without extensive knowledge of Structured Query Language (SQL). Related Topic See Accessing Databases through RDI for information on how to use RDI to access relational databases through MRI to a local or remote database. 31

32 MRI Database Administration (MRIDBA) MRIDBA performs administration and configuration tasks for MRI. Using this menu-driven program, you can easily configure, administer, and manage MRI relationships with the different data managers as well as communications between two MRI systems on different hosts. You use the MRIDBA script to Set up MRI configurations to access remote and local databases. Register database names. Set up user defaults. Establish RDI script security. Related Topic See Configuring MRI with MRIDBA for information on how to use MRIDBA to configure MRI. 32

33 Accessing Databases through MRI MRI lets you configure access to relational databases on both your own host system and other host systems. In addition, you can configure MRI to allow remote systems to access your local relational databases. For example, from a Windows system, you can Access a local Oracle database Connect to a remote Relational Database Server database on an OS 2200 system Allow a remote MRI session from another system to access an ODBC data source on your local Windows system To the user, the Business Information Server itself looks the same on all hosts. You can script the Business Information Server and MRI on the hardware platform that best suits your particular needs, and still access all of your stored data. You have access to the data regardless of where the data is physically stored. Notes: When you configure connections to a database through MRI, you must set up a local configuration. If you enable remote access to a data manager, configure the same logical database name on both the local and remote systems. To actually access the remote database from your local host, the other host must be configured for a remote connection. To properly configure a remote configuration on your local system, you must use the same database names on both the local and remote host. You only need to know the logical database name regardless of whether the connection is local or remote. Related Topics Local Database Connections Remote Database Connections 33

34 Local Database Connections Access to a database is local when MRI and the database reside on the same system. Access is also considered local when MRI resides on the same machine as the client software (system A) used to access the server (system B). Notes: The Com Type column in report 1C2 is dir for local databases. The database (for example, Oracle, Sybase, or Informix) does not need to reside on the same system as the Business Information Server to be considered local (dir). Windows Server Windows Client You can configure local database connections to the following systems on a Windows system: Business Information Server database MQL Oracle (local or SQL*Net) Microsoft SQL Server Sybase ODBC (CORE level-32-bit driver, callable from a Windows service) OLEDB Windows Server Windows Client UNIX OS You can configure local database connections to the following systems on a UNIX system: Business Information Server database MQL Oracle (local or SQL*Net) Sybase UNIX OS 34

35 2200 You can configure local database connections to Relational Database Server on a 2200 system You can register the logical database names and information about the database using MRIDBA, as described in Registering Database Names. Related Topics Oracle Interface Considerations MRI Interface to ODBC Database Managers 35

36 Remote Database Connections Access to a database is remote when MRI on one system (system A) must communicate with MRI on another system (system B) in order to access a database on system B. All Business Information Server to Business Information Server or MRI to MRI accesses are considered to be remote. Note: The Com Type in report 1C2 is eth for remote databases. Windows Server For example, you can establish connections to the following remote databases on a Windows system: MCP/A-series DMSII database INFORMIX ODBC (CORE level-32 bit driver) OLEDB Oracle Relational Database Server Sybase Ingres Microsoft SQL Server Windows Server You can register the logical database names and information about the database using MRIDBA, as described in Registering Database Names. You also need to register information about the database and the communications path on each host. After you properly configure MRI on both hosts, all networking is transparent to users. Using the Business Information Server and MRI, you can access data on any platform, from any platform. Related Topics INFORMIX Interface MRI Interface to ODBC Database Managers Oracle Interface Considerations 36

37 Relational Database Server Interface Sybase Interface 37

38 Configuring MRI with MRIDBA Use MRIDBA to configure MRI and administer the Relational Database Interface (RDI). Before users begin working with RDI, you can change the available defaults and privileges to meet user s needs. This topic describes how to configure MRI using MRIDBA, presents what options to set on your host system, and what to consider when setting up network connections. Starting MRIDBA Obtaining System Setup Instructions Setting User Defaults Registering Database Names Registering Local Subroutines Cleaning Up Administration Reports Setting Public Defaults Displaying Active Threads Status Setting RDI Privileges Setting Up MRI Files Obtaining Detailed Help Windows Server UNIX OS Windows Client Creating Storage Space Windows Server UNIX OS Windows Client Setting Up Application Groups Update MRI.Tables 38

39 Starting MRIDBA To display the DBA Menu 1. Enter mridba at the control line and press NumEnter. The DBA Menu appears. DBA Menu Tab to your choice and press NumEnter: System set-up -> Register database names -> Application group set-up -> Set public defaults -> Set RDI privileges -> Set user defaults -> Register local subroutines -> Clean up admin. reports -> Update MRI.TABLES -> Active Threads -> Set up MRI files -> Create storage space -> Detailed help -> 2. Tab to a selection on the DBA Menu and press NumEnter. 3. Each selection on the DBA Menu displays one or more menus. The following topics describe these menu selections. Note: DBA Menu selections that are not available on your platform appear in a different color. For example, the Application group set-up selection is not available in a Windows environment. This selection, therefore, appears in a different color. Caution! Be careful when trying examples that update the demonstration database. Do not use functions that add, delete, or change lines while working with report 2B0, 1C0, or 1D0. Use duplicate reports so other users start with the same basic information and get the same results as shown in this guide. 39

40 Obtaining System Setup Instructions 2200 Use the System set-up menu to display a result that contains instructions for setting up the MRI system. To display system setup instructions 1. Tab to System set-up on the DBA Menu, and press NumEnter. 2. As an option, you can print out the system setup instructions

41 Registering Database Names Use the Register database names menu to configure and register local and remote databases for use with the RDI script or your own scripts. Perform the steps in one of the following procedures: Registering a Name for a Local Database Registering a Database Name for a Remote Database 41

42 Registering a Name for a Local Database Do the following procedures to register a name for a local database: Entering a Database Name for a Local Database Choosing a Local Database Type Providing Local Database Registration Information For more information, see Local Database Connections. 42

43 Entering a Database Name for a Local Database To configure a local database name 1. After executing mridba from the command line, tab to Register database names on the DBA Menu, and press NumEnter. The Database configuration menu appears. Database configuration Enter the database name. Database Name -> Local or Remote MRIM (L or R)? -> L Place cursor here and press NumEnter -> 2. Enter a database name that identifies the database. MRI registers the database access information with this name. This name can be any name you wish, with a maximum length of 18 characters. For example, the name can be the database management system (such as Oracle, FoxPro, or ODBC), or a logical database name (such as PAYROLL). 3. Ensure that L appears in the Local or Remote? field. The default value of L is already filled in when the menu appears. 4. Move your cursor to Place cursor here and press NumEnter. Press NumEnter to display the Choose a database type menu. 43

44 Choosing a Local Database Type To choose a local database type 1. Perform the procedure in Entering a Database Name for a Local Database to display the Choose a database type menu. 2. MRIDBA displays all the local database types that the local and remote system supports on your platform. For example, if you are creating database configurations on a Windows platform, MRIDBA displays the following local database types. Locate: DBMS Type MQL ODBC OLEDB msql orac7 sybs Choose a database type DBMS Description MAPPER database (MQL) ODBC (CORE level - 32bit Driver) OLEDB Data Source MS SQL Server ORACLE 7.0 and above Sybase 3. Tab to a database type, and press NumEnter to display the specific Register a database source menu for your selected platform. 44

45 Providing Local Database Registration Information To provide local database registration information 1. Select your database configuration and database type as described in Entering a Database Name for a Local Database and Choosing a Local Database Type. The Register <your database source> menu appears. The fields displayed in the Register <your database source> menu depend on the database source previously selected. Register <your database source> Enter the following information. Database Name -> your database name Database Type -> your database type Communication Type -> dir Max Threads -> 5... (Depending on the database, specific fields are displayed) Place cursor here and press NumEnter -> MRIDBA fills in the Database Name, Database Type, Communication Type, and Max Threads fields. You cannot change the Database Name, Database Type, or Communication Type fields on this menu. The Communication Type field for a local database is always dir. The Communication Type field for a remote database is always eth. 2. Change the Max Threads value if desired. This value is the maximum number of users that can access the database using the network name in 1C2. 3. Fill in the remaining information depending on your database type as shown in the following table. Database Type Menu Fields Relational Database Server 2200 Max Threads -> Application Group -> MRIM Id -> Oracle Max Threads -> Oracle SID -> Oracle HOME path -> INFORMIX Max Threads -> For INFORMIX-SE enter SQLEXEC, or for INFORMIX-ONLINE enter the name of your ONCONFIG file -> For INFORMIX-SE enter the location of your database files or for INFORMIX-ONLINE enter the name of your database -> Location of INFORMIX -> Sybase or Microsoft SQL Server Max Threads -> Sybase/ MS SQL Server Database Name -> Sybase/ MS SQL Server Server Name -> ODBC Max Threads -> ODBC Data Source Name -> 45

46 OLEDB Max Threads -> OLEDB UDL filename -> 4. Move your cursor to Place cursor here and press NumEnter. Press NumEnter. MRIDBA registers the database and returns you to the Database configuration menu. The following message appears at the top of the menu: *** Database <your database name> has been entered *** 5. You can register another database, or press Resume (F1) to return to the DBA Menu. 46

47 Registering a Database Name for a Remote Database Do the following procedures to register a name for a remote database: Entering a Remote Database Name Choosing a Remote Database Type Filling in the Communications Type Menu Providing Remote Database Registration Information Utilizing Domain Names for Remote 2200 MRI Access 47

48 Entering a Remote Database Name To register a remote database 1. After executing mridba from the command line, tab to Register database names on the DBA Menu, and press NumEnter. The Database configuration menu appears. Database configuration Enter the database name. Database Name -> Local or Remote MRIM (L or R)? -> r Place cursor here and press NumEnter -> 2. Enter a database name that identifies the database. MRI registers the database access information with this name. This name can be any name you like, with a maximum length of 18 characters. For example, the name can be the database management system (such as Oracle, FoxPro, or ODBC), or a logical database name (such as PAYROLL). This name must also be registered on the remote system. 3. Type r for a remote database. 4. Move your cursor to the Place cursor here and press NumEnter. Press NumEnter to display the Choose a database type menu. 48

49 Choosing a Remote Database Type To choose a remote database type 1. Perform the procedure in Entering a Remote Database Name to display the Choose a database type menu. MRIDBA displays all the remote database types that the remote or local system supports on your platform. For example, if you are creating database configurations on a Windows system, MRIDBA displays the following remote database types: Choose a database type Locate: DBMS Type DBMS Description ASQL A series database INFX Informix ing Ingres 6.4/05 and above msql MS SQL Server ODBC ODBC (CORE level - 32Bit Driver) OLEDB OLEDB Data Source orac5 ORACLE 5.0 orac6 ORACLE 6.0 orac7 ORACLE 7.0 and above rdms4 RDMS 4R1 rdms5 RDMS 5R1 rdms6 RDMS 6R2 and above sybs Sybase 2. Tab to a database type selection and press NumEnter to select a database type. If the database type you select has more than one communications type, MRIDBA displays the Choose a communications type menu. Go to Filling in the Communications Type Menu to select a communications type. If you choose a database type that has only one type of available communications protocol, the MRIDBA script fills in the communications type on the database registration menu. Go to Providing Remote Database Registration Information to complete the database registration. 49

50 Filling in the Communications Type Menu 2200 If you choose a database manager that permits more than one communications protocol, you must select a communications method from a list of possible methods. For example, on an OS 2200 system accessing a remote database, the list includes ddp - DDP 1100 tsn - TSAM (TCP/IP) If you choose a database manager that only has one type of available communications protocol, MRIDBA fills in the communications type, and this menu does not appear. To select a communications type 1. Perform the procedure in Entering a Remote Database Name and Choosing a Remote Database Type to display the Choose a communications type menu. MRIDBA displays all the communications types that the system supports on your platform. For example, if you are creating an INFORMIX database configuration on a UNIX for the Business Information Server operating system, MRIDBA displays the following communications types: Choose a communications type Comm Type Comm Description - eth MRIM Uses Ethernet 2. Tab to the appropriate communications type, and press NumEnter to select a communications type

51 Providing Remote Database Registration Information To provide remote database registration information 1. Select your database configuration and database source as described in Entering a Remote Database Name and Choosing a Remote Database Type. The Register a database source menu appears. Register a remote database with Ethernet Enter the following information. Database Name -> your database name Database Type -> your database type Communication Type -> eth Max Threads -> 5 Ethernet node name -> Place cursor here and press NumEnter -> MRIDBA fills in the Database Name, Database Type, Communication Type, and Max Threads fields. You cannot change the Database Name, Database Type, or Communication Type fields on this menu. 2. Change the Max Threads value if desired. This value is the maximum number of users that can access the database using the network name in 1C2. 3. Enter the IP address or IP alias address of the machine you are accessing. The MRIDBA script registers the database and returns you to the Database Configuration menu. The following message appears at the top of the menu: *** Database <your database name> has been entered *** 4. You can register another database, or press Resume (F1) to return to the DBA Menu. Notes: To complete the registration of an ODBC database on a Windows system, you must also configure a Data Source Name (DSN) as described in Setting Up ODBC Data Source Names. UNIX OS When Business Information Server on one system (system A) calls a remote system (system B), the remote system (system B) utilizes a file called /user/bin/mrim to activate an mrim on system B. This file then points to the location of the mrim executable. Ensure that the mrim executable referenced in the "exec" line exists on system B. For example exec/map6r1/lbin/mrim-sa zarth $3$4$5 Where map6r1 is the location of the mrim executable. For incoming remote requests, the Business Information Server that last executed the menus features and connections and was built with the mrim parameter changing from an N to a Y, is the mrim that is executed. This changes the /user/bin/mrim file. UNIX OS 51

52 Utilizing Domain Names for Remote 2200 MRI Access 2200 Users can modify the Network Configuration Report (1C202) to specify a domain name instead of an IP address by replacing the IP address in the Network Configuration report, which resides in the Network Path Name field, with either an 18 character free form domain name or the keyword *dnr. This keyword tells MRI that the free form domain name is in the Additional Network Information field. If the first character of this field is a backslash (\), this indicates that there is an asterisk type line following this entry that contains a free form domain name of the site, starting in column 2. If the name is longer than 18 characters then the user must manually modify this report to place *dnr in the Network Path Name field and then place the free form domain name in the Additional Network Information Field. Example Network Configuration Report *.S..S.Com. * Network Name.L.Network Path Name.L.Type. Additional Network Information *==================.=.==================.=.====.================================== == odbc-txt xxx.xx.xxx.xxx tsm odbc-txt XXXX tsm odbc-txt *dnr tsm usmnjohndoe.us.cor.corporation.com odbc-txt *dnr tsm 3985*usmnjohndoe.us.cor.corporation.com odbc-txt *dnr tsm \ *3095*usmn-johndoe.us.cor.corporation.com odbc-txt xxx.xx.xxx.xxx tsm getname Notes: 2200 odbc-txt 1 If you have improper or invalid user created entries, then the error message <Error in MRI remote communications> is displayed. Be sure to enter in the correct IP address, because currently, there is no method to detect parsing errors in the IP address or domain name and relay that information back to the end user. This entry is an example of the current method of supplying a connection address. It can be created by manually modifying the Network Configuration Report. odbc-txt 2 This entry is an example of using a short domain name (18 characters or less). Both of these entries can be created using the current MRIDBA functionality. It can be created by manually modifying the Network Configuration Report. odbc-txt 3 This entry is an example of how to specify a long domain name (greater than 18 characters) using *dnr and then the Additional Network Information field. It can be created by manually modifying the Network Configuration Report. odbc-txt 4 This entry is an example of how to specify the optional port number along with a long domain name (greater than 18 characters). It can only be created by manual modification of the Network Configuration Report. odbc-txt 5 This entry is the same as the one above except it shows how to specify the long domain name (greater than 18 characters) on a supplemental line in the report. It can only be created by manual modification of the Network Configuration Report. 52

53 odbc-txt 6 This entry is an example of how to utilize the getname optional functionality, which causes the Internet Name for the specified IP address to be placed in the MRI print file. It is a debug/help tool only that can only be created by manual modification of the Network Configuration Report. 53

54 Database Registration and Configuration Examples The following three examples show how to register and configure database names using the MRIDBA script: Registering a Local Oracle Database Example Registering a Local ODBC Database Example Registering a Remote INFORMIX Database Example Note: The menus in these examples may differ slightly from those on your system. 54

55 Registering a Local Oracle Database Example To register a local Oracle database 1. After executing mridba from the command line, on the DBA Menu, tab to Register database names, and press NumEnter. The Database Configuration menu appears. 2. For this example, enter oracle-s2 for the database name, and an l in the second field, indicating that the database is local. Database configuration Enter the database name. Database Name -> oracle-s2 Local or Remote MRIM (L or R) -> l Place cursor here and press NumEnter -> The Choose a database type menu appears. Tab to the database type needed, and press NumEnter. 3. For this example, tab to orac7 (ORACLE 7.0 and above) and press NumEnter. Locate: DBMS Type MQL ODBC OLEDB msql orac7 sybs Choose a database type DBMS Description MAPPER database (MQL) ODBC (CORE level - 32bit Driver) OLEDB Data Source MS SQL Server ORACLE 7.0 and above Sybase The next menu, Register an Oracle database, shows fields required to register a local Oracle database. All fields except Max Threads, Oracle SID, and Oracle HOME path are filled in, based on information entered on preceding menus. 4. On the Register an Oracle database menu, enter 6 for the Max Threads (users that can access the local database), ORCL for the Oracle SID, and c:\orant for the Oracle HOME path directory. Register an Oracle database Enter the following information. Database Name -> oracle-s2 Database Type -> orac7 Communication Type -> dir Max Threads -> 6 Oracle SID -> ORCL Oracle HOME path -> (enter on next line) c:\orant Place cursor here and press NumEnter -> 5. Press NumEnter to finish registering the current database. 55

56 Registering a Local ODBC Database Example To register a local ODBC database 1. After executing mridba from the command line, on the DBA Menu, tab to Register database names, and press NumEnter. 2. To register a remote ODBC database, fill in the fields, and press NumEnter. For this example, enter ODBC-s2 for the database name and an l (for local) in the second field. Press NumEnter. The Choose a database type menu appears. Database configuration Enter the database name. Database Name -> ODBC-s2 Local or Remote MRIM (L or R) -> l Place cursor here and press NumEnter -> 3. Tab to the database type needed and press NumEnter. For this example, select ODBC ODBC (CORE level - 32-bit Driver). Locate: DBMS Type MQL ODBC OLEDB msql orac7 sybs Choose a database type DBMS Description MAPPER database (MQL) ODBC (CORE level - 32bit Driver) OLEDB Data Source MS SQL Server Oracle 7.0 and above Sybase 4. The Register an ODBC Data Source menu appears. The following menu shows the required fields. Register an ODBC Data Source Enter the following information. Database Name -> ODBC-S2 Database Type -> ODBC Communication Type -> dir Max Threads -> 6 ODBC Data Source Name -> odbc-fox Place cursor here and press NumEnter -> 5. Move your cursor to Place cursor here and press NumEnter. Press NumEnter. 56

57 Registering a Remote INFORMIX Database Example To register a remote INFORMIX database 1. After executing mridba from the command line, on the DBA Menu, tab to Register database names, and press NumEnter. The Database configuration menu appears. 2. Fill in all the fields and press NumEnter. In this example, the database name in the first field is informix-s1, and the r in the second field indicates that the database is remote. Database configuration Enter the database name. Database Name -> informix-s1 Local or Remote MRIM (L or R) -> r Place cursor here and press NumEnter -> 3. The Choose a database type menu appears. For this example, tab to INFX (Informix) for the database type and press NumEnter. Choose a database type Locate: DBMS Type DBMS Description ASQL A series database INFX Informix ing Ingres 6.4/05 and above msql MS SQL Server ODBC ODBC (CORE level - 32Bit Driver) OLEDB OLEDB Data Source orac5 Oracle 5.0 orac6 Oracle 6.0 orac7 Oracle 7.x and above rdms4 RDMS 4R1 rdms5 RDMS 5R1 rdms6 RDMS 6R2 and above sybs Sybase 4. The next menu, Register a remote database with Ethernet, shows the fields required to register the remote database INFORMIX. MRIDBA fills in all fields except Max Threads and Ethernet node name, based on information entered on preceding menus. For this example, enter 4 for the Max Threads (users that can access the remote database) and system1 for the Ethernet node name. Register a remote database with Ethernet Enter the following information. Database Name -> informix-s1 Database Type -> INFX Communication Type -> eth Max Threads -> 4 Ethernet node name -> system1 Place cursor here and press NumEnter -> 57

58 5. Move your cursor to Place cursor here and press NumEnter. Press NumEnter to complete this registration procedure. 58

59 Setting Up Application Groups 2200 Use the Application Group set-up menu to display a result that contains instructions for setting up an application group. To display application group setup instructions 1. Enter the application group name. 2. Tab to the transmit field and press NumEnter. The following menu appears: Application Group Setup Application Group Tab to your choice and press NumEnter Set up parameters -> Create storage areas -> Create Demonstration tables -> 2200 Use each of the selections to set up the application group. 59

60 Configuring Setup Parameters 2200 The parameters on the Set up parameters menu are used for batch scripts. Batch scripts are required in order to access the Data Dictionary. To configure set up parameters 1. After executing mridba from the command line, on the DBA Menu, tab to Set up parameters on the Application Group Setup menu. The Register parameters menu appears. Register parameters Enter the following information Batch port name -> MAPPER Demand Acct. number -> 0 MAPPER User-id -> BPT MAPPER Department -> 104 MAPPER Password -> xyz DD Qualifier -> sys$lib$ DD File -> urep Storage area Qualifier -> uds$$src Place cursor here and press NumEnter -> 2. Fill in the menu fields where Batch port name Is the name of your batch port. Demand Acct. number Is the demand account number used for starting a batch job. User-id Department Password Are log-in information for the batch job. (BPT,104,XYZ is the default user-id on the release tape.) DD Qualifier Is the qualifier for the Data Dictionary. DD File Is the file name containing the Data Dictionary. If the application group applies to SB3Rx products, then the Data Dictionary is DDS. If the application group applies to SB4Rx products, then use UREP. Storage area Qualifier Is the file qualifier used for creating the storage areas. You will need a permanent file for the storage areas. 3. Fill in all required fields, and then press NumEnter to continue

61 Creating Storage Areas 2200 Use the Create storage areas menu to start a batch script containing the Data Dictionary commands necessary to create four storage areas required by RDI for the demonstration database. To create a storage area 1. Select Create Storage Areas; the batch script is displayed. You can refer to this to get file names for the storage area. 2. Press Start to begin the job. After a few minutes the terminal beeps, indicating that the job is done. 3. To continue, press Msg Wait; then acknowledge the message by typing OK. PressNumEnter

62 Creating Demonstration Tables 2200 Use the Create Demonstration tables menu to link to the RDI RESTORE function to create the demonstration tables. When the restore process is complete, a menu appears. Press NumEnter to return to the DBA Menu

63 Setting Public Defaults Use the Set public defaults menu to establish a default database name and database user-id for a public user-id (PUBLIC). The Database Defaults report contains the default values that you specify with this submenu. The RDI script uses information in this report. To set public defaults 1. After executing mridba from the command line, on the DBA Menu, tab to Set public defaults and press NumEnter. The Set public defaults menu appears. Set public defaults Enter an optional department number Department number -> Place cursor here and press NumEnter -> 2. Enter a valid department number in the Department number field, if necessary. The defaults apply to PUBLIC in this department only. If this field is blank, the public defaults apply to all departments. 3. Move your cursor to Place cursor here and press NumEnter. Press NumEnter. The Add public defaults menu appears. 4. Fill in the fields as follows, and press NumEnter to add the information to the Database Defaults report: Department number Type the same department number you entered on the Set public defaults menu. Database name Type the default database name for PUBLIC. The database name typed in this field appears as the default on the RDI DBMS menu for any user-id for which no other default exists. Default database? Type Y or N. If the value of this field is Y, RDI uses this database name as the default database for PUBLIC. Database user-id Type the default database user-id. This database user-id appears as the default on the DBMS menu for any user-id for which no other default value exists. Default qualifier Type the default table qualifier for Relational Database Server Default version Type the default table version name for Relational Database Server Default cabinet Type a default cabinet for results. If a default cabinet is not registered for a user, RDI places the results in the current cabinet. Default drawer Type a default drawer for results. If no default is registered for a user and a drawer is not entered through fast access RDI, RDI places these results in drawer A. Trace SQL syntax? Type N to disable tracing of SQL syntax on the Insert, Delete, Update, and Create commands. Disabling this option improves performance, but prevents capture and display of SQL syntax generated by these commands. Multiple logons? Type N if RDI logs on to a database manager once. Type Y to give RDI the capability to log on and log off a database before and after each relational operation. 63

64 Setting RDI Privileges Use the Set RDI privileges menu to establish privileges by user-id for the RDI script. To set RDI privileges 1. After executing mridba from the command line, on the DBA Menu, tab to Set RDI privileges and press NumEnter. The Set RDI privileges menu appears. Set RDI privileges Enter the MAPPER user-id, department number, and database name MAPPER user-id -> Department number -> Database name -> Place cursor here and press NumEnter -> 2. Fill in the fields as follows, and press NumEnter: MAPPER user-id Type the user-id to which the privileges apply. Department number Type the department number associated with the user-id. If you leave this field blank, the privileges apply to all departments. Database name Type the database name to which the privileges apply. If the field is blank, the privileges apply to all database names. 3. On the next screen, fill in the fields as follows. When all required fields are filled in, press NumEnter to add the data to the RDI security report. All privileges? Type Y in this field to extend privileges to all RDI functions. Select,...,Drop view Type Y for all functions for which the user has access privilege. Leave blank any selections to which the user should not have access. Type s for the SQL function to restrict the user-id to SELECT statements only. Maximum rows to retrieve Type the maximum number of rows that can be retrieved by the user through the Select, Join, and SQL commands executed through RDI. If the field is blank, the user can retrieve any number of rows. Access Special Options menu on Select, Join, and SQL? Type Y to enable the user to access the Special Options menu in RDI. If n is entered, the next two fields do not require a response. Explain Type Y to enable the user to display online explanations of Select statements. These explanations are accessed through the Special Options menu. Background script Type Y to enable the user to process requests with a background script. 4. Move your cursor to Place cursor here and press NumEnter. Press NumEnter to complete this task. 64

65 To check user access The RDI script determines privileges based on specific information entered in the RDI Security report. RDI checks the report in the following order: 1. user-id/department number/database name 2. user-id/department number 3. user-id/database name 4. user-id 5. PUBLIC/department number/database name 6. PUBLIC/department number 7. PUBLIC/database name 8. PUBLIC 65

66 Setting User Defaults Use the Set user defaults menu to specify a default database name and database user-id by user-id. The data entered on the menu is stored in the Database Defaults report. The information in this report applies only to the RDI script. To set user defaults 1. After executing mridba from the command line, on the DBA Menu, tab to Set user defaults and press NumEnter. The Set user defaults menu appears. Set user defaults Enter the MAPPER user-id and optional department number MAPPER user-id -> Department number -> Place cursor here and press NumEnter -> 2. Fill in the fields as follows and press NumEnter: MAPPER user-id Type the user-id for which a default database name and database user-id is to be entered. This is a required field. Department number Type the department number associated with the user-id. If this field is left blank, the default database name applies to all department numbers for which no default was established. 3. The Add user defaults menu appears. Fill in the fields as follows. When all required fields are filled in, press NumEnter to add the information to the Database Defaults report. MAPPER user-id Type the user-id entered on the Set user defaults menu. Department number Type the department number associated with the user-id. The default value is the department number entered on the Set user defaults menu. Database name Type the default database name for the user-id. The database name typed in this field is provided as the default on the DBMS menu for this user-id. Default database? Type Y or N. If the value of this field is Y, the database name is provided as the default database for this user-id in RDI. Database user-id Type the default database user-id for this user-id. This database user-id is provided as the default on the DBMS menu for this user-id and database name. Default qualifier Type the default table qualifier for Relational Database Server Default version Type the default table version name for Relational Database Server Default cabinet Type a default cabinet for results. If no default is registered for a user, RDI places the results in the current cabinet. 66

67 Default drawer Type a default drawer for results. If no default is registered for a user and a drawer is not entered through fast-access RDI, RDI places the results in drawer A. Trace SQL syntax? Type N to disable tracing of SQL syntax on the Insert, Delete, Update, and Create commands. Disabling this option improves performance, but prevents capture and display of SQL syntax generated by these commands. Multiple logons? Type N if RDI logs on to a database manager once. Type Y to give RDI the capability to log on and log off a database before and after each relational operation. 4. Move your cursor to Place cursor here and press NumEnter. Press NumEnter. 67

68 Registering Local Subroutines Use the Register local subroutines menu to register local subroutines used in RDI data retrieval operations. The information is stored in the RDI Local Code report. For more information about local subroutines, see the Command Reference. To register local subroutines 1. After executing mridba from the command line, on the DBA Menu, tab to Register local subroutines and press NumEnter. The Register local subroutines menu appears. Register local subroutines Enter the following information. Routine Name -> MAPPER User-id -> Department number -> Place cursor here and press NumEnter -> 2. Fill in the fields as follows and press NumEnter: Routine Name Type the name assigned to the local subroutine. The routine is registered under this name in the RDI Local Code report. MAPPER User-id Type the user-id for access to the local subroutine. The default value for this field is PUBLIC. Department number Type the department number associated with the user-id. If this field is blank, the routine can be accessed by all departments with the user-id. 3. On the next screen, fill in the fields as follows. When all required fields are filled in, press NumEnter to add the information to the RDI Local Code report. Routine Name Type the name assigned to the routine in the preceding menu. Database Name Type the name of the database where the local routine will be used. If no value is entered in this field, the routine can be used in all databases. Select or join? Type s to use the routine with the Select command. Type j to use the routine with the Join command. Before or after data retrieval? Type b if the routine is executed before data is retrieved by the Select or Join commands. Type a if the routine is executed after the data is retrieved. Cabinet Type the cabinet containing the local subroutine. Drawer Type the drawer containing the local subroutine. Report Type the report number for the local subroutine. Label Type the report label for the local subroutine. User-id 68

69 Type the user-id entered on the previous menu. Department number Type the department number entered on the preceding menu. Comments Type a description of the routine or other information. 4. Move your cursor to Place cursor here and press NumEnter. Press NumEnter to complete the procedure. 69

70 Cleaning Up Administration Reports Use the Clean up admin. reports menu to check the RDI Administration reports for invalid entries and to delete unnecessary entries. To clean up administration reports 1. After executing mridba from the command line, on the DBA Menu, tab to Clean up admin. reports and press NumEnter. The Clean up menu appears. Clean up menu Tab to your choice and press NumEnter RDI Database Defaults report -> Database configuration report -> RDI Security report -> SQL Requests report -> Local code report -> Parameters report -> 2. Tab to the report you want to clean up and press NumEnter. The Clean up defaults menu appears. 3. Tab to one of the items and press NumEnter. Clean up defaults Tab to your choice and press NumEnter Delete unnecessary entries -> Check report for invalid data -> Notes: When you select Delete unnecessary entries, a list of entries appears as a temporary report. Mark entries to be deleted by typing a d in the X field, and then press Resume (F1) to delete the marked entries. When you select Check report for invalid data, MRI verifies data in the report for validity. Examples of invalid data are as follows: Character data in a numeric field Duplicate entries Reference to a report that does not exist After the system checks the report, it displays invalid data rows. In the spaces provided, type d to delete the entries. Click Help to display a list of possible errors. If the system finds no invalid data, it displays a message indicating that invalid data does not exist. 70

71 Displaying Active Threads Status Use the Active Threads menu to display a report containing information about all active threads. An active thread is the period of time a user is logged on to a relational database. To display information about active threads 1. After executing mridba from the command line, on the DBA Menu, tab to Active Threads and press NumEnter. A report appears that displays the following information: Station and host Logon time and date Active time if an operation is actually being performed 2. Press Repeat (F1) to redisplay the report and view an updated thread status report. 71

72 Setting Up MRI Files Use the Set up MRI files menu to set up remote configuration and remote parameter files as well as the local parameter file. MRI uses the files to store information. The files contain information used by local and remote databases. Note: The default location for both remote configuration and parameter files is MSWSITES\MRI_REM. The default location for the local parameter file is MSWSITES\<site letter>. Windows Server Windows Client To set up MRI configuration files on a Business Information Server for the Windows Operating System, you must perform one of the following actions: Specify an Administrator user-id and password in the Windows Login and Password parameter fields of the Graphical Interface for Business Information Server connection script. You can then update any parameter file without having to provide additional user-ids and passwords. After you set up the desired configurations, the Business Information Server displays a screen that requests an authorized user-id and password. Enter the Administrator user-id and password and press NumEnter. Windows Server Windows Client UNIX OS To set up MRI configuration files on a Business Information Server for the UNIX Operating System, you must perform one of the following actions: Log in to the UNIX operating system as super user and then sign onto the Business Information Server. You can then update any parameter file without entering additional user-ids and passwords. After you set up the desired configurations, the Business Information Server displays a screen that requests an authorized user-id and password (super user). Enter the proper user-id and password and press NumEnter. UNIX OS To set up MRI files 1. After executing mridba from the command line, on the DBA Menu, tab to Set up MRI files and press NumEnter. The Set up MRI files screen appears. Set up MRI files Set up remote configuration file -> Set up local parameter file -> Set up remote parameter file -> 2. Tab to the selection you want and press NumEnter. The following text describes the possible selections: Set up remote configuration file Contains a list of databases that remote systems can access. For a remote system to do this, you must have a configuration file set up with the database names. The configuration file contains information similar to the network configuration report. The database name that the remote database uses must match a name in the remote configuration file. Note: The remote configuration file is built from the 1C2 report. The configuration files are sys$lib$*mri.mrim/config 72

73 Windows Server Windows Client mswsites\mri_rem\mrimcfg Windows Server Windows Client UNIX OS map6r1/mri_remote/mrimcfg UNIX OS Set up remote parameter file Updates MRI parameters for access by a remote system. Depending on which selection you choose, refer to the following topics, as appropriate: Setting Up a Remote Configuration File Example of Setting Up a Remote File Setting Up a Local or Remote Parameter File 73

74 Setting Up a Remote Configuration File To set up a remote configuration file 1. When you choose Set up remote configuration file, a list of databases registered in the network configuration report appears. 2. Type an x in the first field next to each database to be entered in the remote file, and press NumEnter. 3. Press Resume (F1) to update the file. Windows Server Windows Client The remote configuration file name is mrimcfg. The file resides in the mri_rem subdirectory of the Business Information Server Sites directory. For example: c:\mswsites\mri_rem\mrimcfg. Windows Server Windows Client 2200 After updating the remote configuration file, the 2200 MRIM script must be restarted

75 Example of Setting Up a Remote File To set up a remote mrimcfg file 1. After executing mridba from the command line, on the DBA Menu, tab to Set up MRI files and press NumEnter. 2. On the Set up MRI files menu, tab to the selection you want and press NumEnter. For this example, select Set up remote configuration file. Set up MRI files Set up remote configuration file -> Set up local parameter file -> Set up remote parameter file -> 3. The network configuration report appears. Tab to the X field and type an x next to each database that can be accessed from remote systems. Press NumEnter, and then press Resume (F1)..DATE 29 DEC 98 14:03:29 REPORT GENERATION CARYN.Choose the databases that can be accessed from remote systems by entering an X in the X field. Press the Resume key to continue....com...thr. *X.DB Name.Network Path Name.Type..DMSType.Cnt. *=.========.=================.====.===.=======.====. x ODBC-s2 dir ODBC 5 informix-s1 system1 eth INFX 5 x oracle-s2 orcl dir orac7 5 *Reserved =======================. ODBC-FOX c:\orant 4. After pressing Resume (F1), a file called mrimcfg is written out to the Mri_rem directory. For example: C:\Mswsites\Mri_rem\Mrimcfg (for Windows) or /map6r1/mri_remote/mrimcfg (for UNIX). 5. The mrimcfg file is column sensitive (loosely based on the 1C2 report). When parsing the mrimcfg file, each column placeholder is important. It is also important to note that the mrimcfg file just has the contents of a column and not the actual column itself. The number of spaces between columns is not relevant, as long as there is at least one space separating each column. The following is a sample mrimcfg file and corresponding column name in the 1C2 report: any_name N/A dir sybs 5 \ syb_db_name@syb_server_name any_name2 oracle_sid dir sybs 5 \ oracle_home_dir any_name3 N/A dir sybs 5 \ MS_db_name@Ms_server_name any_name4 N/A dir sybs 5 \ DSN_name Column1 = Network Name Column2 = Network Path Name Column3 = Com Type Column4 = DBMS Type Column5 = Thread Count 75

76 Column6 = Additional Network Information Note: The "\"character is the linewrap character. 76

77 Setting Up a Local or Remote Parameter File MRI uses parameter files to set capacity limits and defaults for database environment information. Each Business Information Server site has its own MRI parameter file. Another MRI parameter file is for requests from remote systems. Usually, you do not use the default configuration values. Although you can edit the parameter file and add the appropriate parameter values, it is more convenient and safer to use MRIDBA to create entries in the local or remote parameter files. See Configuration Parameter Descriptions for a description of each of the possible parameters included in a parameter file. To set up a local or a remote parameter file 1. After executing mridba from the command line, on the DBA Menu, tab to Set up MRI files and press NumEnter. 2. On the MRI files menu, tab to Set up local parameter file or Set up remote parameter file and press NumEnter. 3. The system retrieves the appropriate parameter file and displays the Set up parameter file menu. 4. Fill in the fields as follows: Default database Windows Server (Optional) Type the default database for MRI access. If you configure a default database for MRI, it must also be registered through MRIDBA in the Network Configuration report (1C2). Windows Server Maximum users per database Maximum users per system Maximum active databases 2200 (Optional) Type the default database for MRI access. If you configure a default database for MRI, it must also be registered through MRIDBA in the Network Configuration report (1C202) UNIX OS Windows Client Windows Server Enter the maximum number of active MRI users allowed per database name for your site. The default is 10. Enter the maximum number of active MRI users allowed per system for your site. This value should equal or exceed the maximum active users per database parameter. The default is 50. It is not recommended that this number exceed 200, as doing so could cut into system resources, which may lead to undesired results. Enter the maximum number of active MRI database names for your site. The default is 10. Local/remote MRI access? Oracle SID Oracle home If you are setting up a local file, type Y to allow users on your site to access MRI. If you are setting up a remote file, type Y to allow users on remote systems to access MRI. Typing N prevents users from accessing MRI on both local and remote systems. (Optional) Type the default Oracle database system identifier (SID). You only use this parameter if you did not provide an Oracle SID when the database name was registered. (Optional) Type the full path name to the default directory where Oracle is installed. You only use this parameter if you did not provide an Oracle_Home when the database name was registered. 77

78 Oracle DLL MS SQL DLL Sybase DLL UNIX OS Windows Client Windows Server (Optional) Enter the specific Oracle dynamically linked library (DLL) for the Oracle level installed on your system. MRI currently looks for oci.dll. (Optional) Enter the specific MS SQL dynamically linked library (DLL) for the MS SQL level installed on your system. MRI currently looks for NTWDBLIB.dll. (Optional) Enter the specific Sybase dynamically linked library (DLL) for the Sybase level installed on your system. MRI currently looks for LIBSYB.dll. Windows Server UDL Location Maximum ODBC disconnects before MRIM restarts Maximum ODBC connections to keep open (Optional) Disconnect Pooled ODBC Connection if ODBC Error occurs? Enter the directory location of the UDL files if different than the default location. The default location is system drive:\program files\common files\system\ole db\data links\. (Optional) For local databases, enter the maximum number of allowed disconnects before MRIM restarts. Once the number of disconnects exceeds this value, the pooled MRIM frees all of its resources, restarts itself, and exits. Exiting is the only way to get rid of the driver memory leaks that accumulate with every disconnect when one of a few specific versions of some ODBC drivers are being used. See Configuring Database Access Connection Pooling for additional information about pooled MRIMs. For example, if you set this value to 125 and you connect to MRI from an Access database through an ODBC driver, each prestarted MRIM accumulates 1 MB of lost memory before exiting the system. If the ODBC driver is for a FoxPro or DBase database, the accumulated memory loss is 0.5 MB. The default is 0. For a local database, enter the maximum number of unique ODBC connections (restarted or pooled MRIMs) to keep open. Keeping multiple ODBC connections open provides the following benefits: Improves system performance. Reduces memory loss if your ODBC driver has a memory leak on connect/disconnect cycles (for example, Access, FoxPro, or DBase databases). Because your system can lose available memory each time ODBC disconnects from a database, you should minimize the number of times you connect and disconnect from an ODBC data source. For example, one version of the Microsoft Access ODBC Driver loses 8 K of memory each time you disconnect. The ODBC DSN, user-id, and password are compared to determine unique database connections. You can specify 0 to 20 open connections. The default is 0. To mark a pooled ODBC connection to disconnect when an error occurs, enter Y in this field. The actual connection will not be disconnected until is executed on this data source. Enter N if the connection should remain open regardless of what type of error is returned from the ODBC driver. 78

79 The default is N. Justification for A, F, and I variables on command. Windows Server This parameter sets the justification of numeric data fetched into A, F, and I type Business Information Server variables via command. R = Right justify data. N = No change to the justification. L = Left Justify the data. The default is N. 79

80 Creating Storage Space UNIX OS Windows Client Windows Server Use the Create storage space menu on the DBA Menu to create storage or table space. To create a storage space 1. After executing mridba from the command line, on the DBA Menu, tab to Create storage space and press NumEnter. The Create storage space menu appears. Create storage space Enter the following information. Database Name -> Database user-id -> Password -> Storage Space -> Place cursor here and press NumEnter -> 2. To create storage or table space, fill in the fields as follows and press NumEnter. Database Name Type the database in which the storage or table space is to be created. Database User-id Type a valid database user-id. Password Type the database password. Storage Space Type the storage or table space name. 3. Move your cursor to Place cursor here and press NumEnter. Press NumEnter to complete this procedure. UNIX OS Windows Client Windows Server 80

81 Obtaining Detailed Help Use the Detailed help menu of the MRIDBA Menu to display online help for the MRIDBA script. 81

82 Setting Up ODBC Data Source Names Windows Client Windows Server This topic describes how to configure and register an ODBC data source name on a Windows system. This name must match the database name you provide when setting up an ODBC connection through MRIDBA, as described in Registering Database Names. Topics covered include Configuring and Registering an ODBC Data Source Name Valid ODBC Subtypes Specifying a Path to a Remote Database File SettingUptheNorthwindDataSourceName Windows Client Windows Server Note: For setting up Business Information Server services to work with ODBC on IBM platforms, see Registering Business Information Server Services to Work with ODBC. 82

83 Configuring and Registering an ODBC Data Source Name Windows Client Windows Server To configure and register an ODBC data source name 1. Sign on to Windows. 2. Go to the Main menu Settings option and select Control Panel. 3. Double-click Administrative Tools. 4. Select the Data Sources (ODBC) icon. The ODBC Data Source Administrator menu appears. 5. Click the System DSN tab to display a list of system data sources that already exist on your Windows system. 6. To configure a new data source name, click the Add button. The Create New Data Source menu appears. 7. Select the ODBC driver from the list. For example, Microsoft Access Driver (*.mdb) Microsoft dbase Driver (*.dbf) Microsoft Excel Driver (*.xls) Microsoft FoxPro Driver (*.dbf) Microsoft ODBC for Oracle Microsoft Paradox Driver (*.dbf) Microsoft Text Driver (*.txt; *.csv) SQL Server UniAccess UnisDB32 Unisys Data Access 8. Click Finish. The setup menu for the selected driver appears on your screen. Each ODBC server driver has a unique setup menu with applicable fields. For example, if you select the ODBC SQL driver, the ODBC SQL Server Setup menu appears. 9. Fill in the fields as described in the Help for this system. At a minimum, you must supply the Data Source Name and Description fields on the setup menu. 10. Refer to the Windows Help associated with the setup menu for additional information about filling in the remaining fields. 11. Click OK to complete adding a new data source. 12. Repeat steps 2 through 9 for each data source that uses the ODBC interface. Windows Client Windows Server 83

84 84

85 Valid ODBC Subtypes Subtypes MS SQL Server 7.0 MS SQL Server 2000 Oracle Oracle DB2 RDMS DMS Drivers SQL Server SQL Server Oracle ODBC Driver Oracle ODBC Driver IBM DB2 ODBC Driver UniAccess Unisys ODBC Access 8R2 DMSII Unisys ODBC Access 8.2 Access Excel Paradox Text Informix PostgreSQL Sybase 12.0 MySQL Microsoft Access Driver Microsoft Excel Driver Intersolv Bit Paradox File Microsoft Text Driver Informix bit PostgreSQL Sybase ASE ODBC MySQL does not support Delete and Update for Text and Excel Databases. 85

86 Specifying a Path to a Remote Database File Windows Client Windows Server Follow this procedure if you need to connect to a remote database file. As part of defining the data source name, you must specify a path name to the remote site database file. One method of specifying a remote path name is to map a drive to the remote database file. In this case, you should not map to a drive because drive mappings require that the user who mapped the drive be logged onto the server console. If not, the drive mapping becomes unavailable. To solve this drive mapping problem, enter a path name that follows the Uniform Naming Convention (UNC). Specifying the UNC makes this path name independent of what user is logged onto a system. To enter a UNC file path name in a data source name 1. Sign on to Windows. 2. Go to the Main menu Settings option and select Control Panel. 3. Double-click Administrative Tools. 4. Select the Data Sources (ODBC) icon. The ODBC Data Source Administrator menu appears. 5. Click the System DSN tab to display a list of system data sources that already exist on your Windows system. 6. To configure a new data source name, click the Add button. The Create New Data Source menu appears. 7. Select the ODBC driver from the list. For example, Microsoft Access Driver (*.mdb). 8. Fill in the fields and select the database. For an Access database, click Select. The Select Database screen appears. Enter the UNC path name in the Database Name field. 9. Click OK to complete selecting the database file. 10. Click OK to finish adding the new data source name for the remote database file. Windows Client Windows Server 86

87 Setting Up the Northwind Data Source Name Windows Client Windows Server The following steps present an example of configuring and registering the Northwind data source name for a local site. This data source is an Access database. To set up the Northwind Data Source Name 1. Sign on to Windows. 2. Go to the Main menu Settings option and select Control Panel. 3. Double-click Administrative Tools. 4. Select the Data Sources (ODBC) icon. The ODBC Data Source Administrator menu appears. 5. Click the System DSN tab to display a list of system data sources that already exist on your Windows system. 6. Click the Add button. The Create New Data Source menu appears. 7. Select the Microsoft Access Driver (*.mdb) driver from the list. 8. Click Finish. The ODBC Microsoft Access Setup screen appears. 87

88 9. Enter Northwind for the Data Source Name and Northwind Database for the Description. 10. Click Select to choose the Northwind data base file. The Select Database screen appears. Select the Northwind.mdb from the c:\ directory. 88

89 11. Click OK. The ODBC Microsoft Access Setup screen appears again. Note that the path to the Northwind.mdb file appears in the Database field. 12. Click OK to complete adding a new data source. The ODBC Data Source Administrator screen appears. Note that the Northwind data source name now appears in the list of system data source names. 13. Click OK to complete the procedure. Windows Client Windows Server 89

FileMaker 11. ODBC and JDBC Guide

FileMaker 11. ODBC and JDBC Guide FileMaker 11 ODBC and JDBC Guide 2004 2010 FileMaker, Inc. All Rights Reserved. FileMaker, Inc. 5201 Patrick Henry Drive Santa Clara, California 95054 FileMaker is a trademark of FileMaker, Inc. registered

More information

UNISYS. ClearPath Enterprise Servers. Authentication Sentinel for OS 2200 User Guide. ClearPath OS 2200 Release 8.2

UNISYS. ClearPath Enterprise Servers. Authentication Sentinel for OS 2200 User Guide. ClearPath OS 2200 Release 8.2 ClearPath Enterprise Servers Authentication Sentinel for OS 2200 User Guide UNISYS 2004 Unisys Corporation. All rights reserved. ClearPath OS 2200 Release 8.2 Printed in USA September 2004 4729 2016 000

More information

FileMaker 12. ODBC and JDBC Guide

FileMaker 12. ODBC and JDBC Guide FileMaker 12 ODBC and JDBC Guide 2004 2012 FileMaker, Inc. All Rights Reserved. FileMaker, Inc. 5201 Patrick Henry Drive Santa Clara, California 95054 FileMaker and Bento are trademarks of FileMaker, Inc.

More information

SEER Enterprise Shared Database Administrator s Guide

SEER Enterprise Shared Database Administrator s Guide SEER Enterprise Shared Database Administrator s Guide SEER for Software Release 8.2 SEER for IT Release 2.2 SEER for Hardware Release 7.3 March 2016 Galorath Incorporated Proprietary 1. INTRODUCTION...

More information

Horizon Debt Collect. User s and Administrator s Guide

Horizon Debt Collect. User s and Administrator s Guide Horizon Debt Collect User s and Administrator s Guide Microsoft, Windows, Windows NT, Windows 2000, Windows XP, and SQL Server are registered trademarks of Microsoft Corporation. Sybase is a registered

More information

Thoroughbred Basic TM ODBC Client Capability Customization Supplement

Thoroughbred Basic TM ODBC Client Capability Customization Supplement Thoroughbred Basic TM ODBC Client Capability Customization Supplement Version 8.8.0 46 Vreeland Drive, Suite 1 Skillman, NJ 08558-2638 Telephone: 732-560-1377 Outside NJ 800-524-0430 Fax: 732-560-1594

More information

Business Intelligence Tutorial

Business Intelligence Tutorial IBM DB2 Universal Database Business Intelligence Tutorial Version 7 IBM DB2 Universal Database Business Intelligence Tutorial Version 7 Before using this information and the product it supports, be sure

More information

Quick Start SAP Sybase IQ 16.0

Quick Start SAP Sybase IQ 16.0 Quick Start SAP Sybase IQ 16.0 UNIX/Linux DOCUMENT ID: DC01687-01-1600-01 LAST REVISED: February 2013 Copyright 2013 by Sybase, Inc. All rights reserved. This publication pertains to Sybase software and

More information

Server Sentinel Monitored Server

Server Sentinel Monitored Server Server Sentinel Monitored Server Installation and Reinstallation Guide for Systems Monitoring Third-Party Products Server Sentinel 4.4.3 and Higher April 2007 . unisys imagine it. done. Server Sentinel

More information

KB_SQL SQL Reference Guide Version 4

KB_SQL SQL Reference Guide Version 4 KB_SQL SQL Reference Guide Version 4 1995, 1999 by KB Systems, Inc. All rights reserved. KB Systems, Inc., Herndon, Virginia, USA. Printed in the United States of America. No part of this manual may be

More information

Server Sentinel Client Workstation

Server Sentinel Client Workstation Server Sentinel Client Workstation Installation and Reinstallation Guide Server Sentinel 4.4.3 and Higher April 2008 . unisys imagine it. done. Server Sentinel Client Workstation Installation and Reinstallation

More information

Forms Printer User Guide

Forms Printer User Guide Forms Printer User Guide Version 10.51 for Dynamics GP 10 Forms Printer Build Version: 10.51.102 System Requirements Microsoft Dynamics GP 10 SP2 or greater Microsoft SQL Server 2005 or Higher Reporting

More information

ICE for Eclipse. Release 9.0.1

ICE for Eclipse. Release 9.0.1 ICE for Eclipse Release 9.0.1 Disclaimer This document is for informational purposes only and is subject to change without notice. This document and its contents, including the viewpoints, dates and functional

More information

XMailer Reference Guide

XMailer Reference Guide XMailer Reference Guide Version 7.00 Wizcon Systems SAS Information in this document is subject to change without notice. SyTech assumes no responsibility for any errors or omissions that may be in this

More information

Connecting LISTSERV to an Existing Database Management System (DBMS)

Connecting LISTSERV to an Existing Database Management System (DBMS) Whitepaper Connecting LISTSERV to an Existing Database Management System (DBMS) September 14, 2010 Copyright 2010 L-Soft international, Inc. Information in this document is subject to change without notice.

More information

Setting Up ALERE with Client/Server Data

Setting Up ALERE with Client/Server Data Setting Up ALERE with Client/Server Data TIW Technology, Inc. November 2014 ALERE is a registered trademark of TIW Technology, Inc. The following are registered trademarks or trademarks: FoxPro, SQL Server,

More information

Business Intelligence Tutorial: Introduction to the Data Warehouse Center

Business Intelligence Tutorial: Introduction to the Data Warehouse Center IBM DB2 Universal Database Business Intelligence Tutorial: Introduction to the Data Warehouse Center Version 8 IBM DB2 Universal Database Business Intelligence Tutorial: Introduction to the Data Warehouse

More information

FileMaker 13. ODBC and JDBC Guide

FileMaker 13. ODBC and JDBC Guide FileMaker 13 ODBC and JDBC Guide 2004 2013 FileMaker, Inc. All Rights Reserved. FileMaker, Inc. 5201 Patrick Henry Drive Santa Clara, California 95054 FileMaker and Bento are trademarks of FileMaker, Inc.

More information

EMC NetWorker Module for Microsoft Applications Release 2.3. Application Guide P/N 300-011-105 REV A02

EMC NetWorker Module for Microsoft Applications Release 2.3. Application Guide P/N 300-011-105 REV A02 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide P/N 300-011-105 REV A02 EMC Corporation Corporate Headquarters: Hopkinton, MA 01748-9103 1-508-435-1000 www.emc.com Copyright

More information

EMC NetWorker Module for Microsoft Exchange Server Release 5.1

EMC NetWorker Module for Microsoft Exchange Server Release 5.1 EMC NetWorker Module for Microsoft Exchange Server Release 5.1 Installation Guide P/N 300-004-750 REV A02 EMC Corporation Corporate Headquarters: Hopkinton, MA 01748-9103 1-508-435-1000 www.emc.com Copyright

More information

Legal Notes. Regarding Trademarks. 2012 KYOCERA Document Solutions Inc.

Legal Notes. Regarding Trademarks. 2012 KYOCERA Document Solutions Inc. Legal Notes Unauthorized reproduction of all or part of this guide is prohibited. The information in this guide is subject to change without notice. We cannot be held liable for any problems arising from

More information

Heterogeneous Replication Guide. Replication Server 15.7.1 SP100

Heterogeneous Replication Guide. Replication Server 15.7.1 SP100 Heterogeneous Replication Guide Replication Server 15.7.1 SP100 DOCUMENT ID: DC36924-01-1571100-01 LAST REVISED: May 2013 Copyright 2013 by Sybase, Inc. All rights reserved. This publication pertains to

More information

ODBC Driver Version 4 Manual

ODBC Driver Version 4 Manual ODBC Driver Version 4 Manual Revision Date 12/05/2007 HanDBase is a Registered Trademark of DDH Software, Inc. All information contained in this manual and all software applications mentioned in this manual

More information

v4.8 Getting Started Guide: Using SpatialWare with MapInfo Professional for Microsoft SQL Server

v4.8 Getting Started Guide: Using SpatialWare with MapInfo Professional for Microsoft SQL Server v4.8 Getting Started Guide: Using SpatialWare with MapInfo Professional for Microsoft SQL Server Information in this document is subject to change without notice and does not represent a commitment on

More information

Silect Software s MP Author

Silect Software s MP Author Silect MP Author for Microsoft System Center Operations Manager Silect Software s MP Author User Guide September 2, 2015 Disclaimer The information in this document is furnished for informational use only,

More information

Simba ODBC Driver with SQL Connector for Apache Cassandra

Simba ODBC Driver with SQL Connector for Apache Cassandra Simba ODBC Driver with SQL Connector for Apache Cassandra Installation and Configuration Guide May 7, 2013 Simba Technologies Inc. Copyright 2012-2013 Simba Technologies Inc. All Rights Reserved. Information

More information

CA ARCserve Backup for Windows

CA ARCserve Backup for Windows CA ARCserve Backup for Windows Agent for Sybase Guide r16 This Documentation, which includes embedded help systems and electronically distributed materials, (hereinafter referred to as the Documentation

More information

Enterprise Server. Application Sentinel for SQL Server Installation and Configuration Guide. Application Sentinel 2.0 and Higher

Enterprise Server. Application Sentinel for SQL Server Installation and Configuration Guide. Application Sentinel 2.0 and Higher Enterprise Server Application Sentinel for SQL Server Installation and Configuration Guide Application Sentinel 2.0 and Higher August 2004 Printed in USA 3832 1097 000 . Enterprise Server Application Sentinel

More information

ODBC Driver User s Guide. Objectivity/SQL++ ODBC Driver User s Guide. Release 10.2

ODBC Driver User s Guide. Objectivity/SQL++ ODBC Driver User s Guide. Release 10.2 ODBC Driver User s Guide Objectivity/SQL++ ODBC Driver User s Guide Release 10.2 Objectivity/SQL++ ODBC Driver User s Guide Part Number: 10.2-ODBC-0 Release 10.2, October 13, 2011 The information in this

More information

Copyright 2012-2013 Software Technology, Inc. 1621 Cushman Drive Lincoln, NE 68512 (402) 423-1440 www.practicemaster.com

Copyright 2012-2013 Software Technology, Inc. 1621 Cushman Drive Lincoln, NE 68512 (402) 423-1440 www.practicemaster.com Copyright 2012-2013 Software Technology, Inc. 1621 Cushman Drive Lincoln, NE 68512 (402) 423-1440 www.practicemaster.com Tabs3, PracticeMaster, and the pinwheel symbol ( ) are registered trademarks of

More information

Sage 300 ERP 2014. Installation and Administration Guide

Sage 300 ERP 2014. Installation and Administration Guide Sage 300 ERP 2014 Installation and Administration Guide This is a publication of Sage Software, Inc. Copyright 2013. Sage Software, Inc. All rights reserved. Sage, the Sage logos, and the Sage product

More information

Import Filter Editor User s Guide

Import Filter Editor User s Guide Reference Manager Windows Version Import Filter Editor User s Guide April 7, 1999 Research Information Systems COPYRIGHT NOTICE This software product and accompanying documentation is copyrighted and all

More information

DB Administration COMOS. Platform DB Administration. Trademarks 1. Prerequisites. MS SQL Server 2005/2008 3. Oracle. Operating Manual 09/2011

DB Administration COMOS. Platform DB Administration. Trademarks 1. Prerequisites. MS SQL Server 2005/2008 3. Oracle. Operating Manual 09/2011 Trademarks 1 Prerequisites 2 COMOS Platform MS SQL Server 2005/2008 3 Oracle 4 Operating Manual 09/2011 A5E03638301-01 Legal information Legal information Warning notice system This manual contains notices

More information

Data Access Guide. BusinessObjects 11. Windows and UNIX

Data Access Guide. BusinessObjects 11. Windows and UNIX Data Access Guide BusinessObjects 11 Windows and UNIX 1 Copyright Trademarks Use restrictions Patents Copyright 2004 Business Objects. All rights reserved. If you find any problems with this documentation,

More information

Matisse Installation Guide for MS Windows

Matisse Installation Guide for MS Windows Matisse Installation Guide for MS Windows July 2013 Matisse Installation Guide for MS Windows Copyright 2013 Matisse Software Inc. All Rights Reserved. This manual and the software described in it are

More information

How To Use A Microsoft Networker Module For Windows 8.2.2 (Windows) And Windows 8 (Windows 8) (Windows 7) (For Windows) (Powerbook) (Msa) (Program) (Network

How To Use A Microsoft Networker Module For Windows 8.2.2 (Windows) And Windows 8 (Windows 8) (Windows 7) (For Windows) (Powerbook) (Msa) (Program) (Network EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide P/N 300-011-105 REV A03 EMC Corporation Corporate Headquarters: Hopkinton, MA 01748-9103 1-508-435-1000 www.emc.com Copyright

More information

Sage 300 ERP 2012. Installation and Administration Guide

Sage 300 ERP 2012. Installation and Administration Guide Sage 300 ERP 2012 Installation and Administration Guide This is a publication of Sage Software, Inc. Version 2012 Copyright 2012. Sage Software, Inc. All rights reserved. Sage, the Sage logos, and the

More information

Governance, Risk, and Compliance Controls Suite. Preventive Controls Governor Audit Rules User s Guide. Software Version 7.2.2.3

Governance, Risk, and Compliance Controls Suite. Preventive Controls Governor Audit Rules User s Guide. Software Version 7.2.2.3 Governance, Risk, and Compliance Controls Suite Preventive Controls Governor Audit Rules User s Guide Software Version 7.2.2.3 Preventive Conrols Governor: Audit Rules User s Guide Part No. AR002-7223A

More information

P R O V I S I O N I N G O R A C L E H Y P E R I O N F I N A N C I A L M A N A G E M E N T

P R O V I S I O N I N G O R A C L E H Y P E R I O N F I N A N C I A L M A N A G E M E N T O R A C L E H Y P E R I O N F I N A N C I A L M A N A G E M E N T, F U S I O N E D I T I O N R E L E A S E 1 1. 1. 1.x P R O V I S I O N I N G O R A C L E H Y P E R I O N F I N A N C I A L M A N A G E

More information

MGC WebCommander Web Server Manager

MGC WebCommander Web Server Manager MGC WebCommander Web Server Manager Installation and Configuration Guide Version 8.0 Copyright 2006 Polycom, Inc. All Rights Reserved Catalog No. DOC2138B Version 8.0 Proprietary and Confidential The information

More information

Oracle Enterprise Manager. Description. Versions Supported

Oracle Enterprise Manager. Description. Versions Supported Oracle Enterprise Manager System Monitoring Plug-in Installation Guide for Microsoft SQL Server Release 10 (4.0.3.1.0) E14811-03 June 2009 This document provides a brief description about the Oracle System

More information

Business Portal for Microsoft Dynamics GP. Key Performance Indicators Release 10.0

Business Portal for Microsoft Dynamics GP. Key Performance Indicators Release 10.0 Business Portal for Microsoft Dynamics GP Key Performance Indicators Release 10.0 Copyright Copyright 2007 Microsoft Corporation. All rights reserved. Complying with all applicable copyright laws is the

More information

Oracle Enterprise Manager

Oracle Enterprise Manager Oracle Enterprise Manager System Monitoring Plug-in for Oracle TimesTen In-Memory Database Installation Guide Release 11.2.1 E13081-02 June 2009 This document was first written and published in November

More information

How To Use The Correlog With The Cpl Powerpoint Powerpoint Cpl.Org Powerpoint.Org (Powerpoint) Powerpoint (Powerplst) And Powerpoint 2 (Powerstation) (Powerpoints) (Operations

How To Use The Correlog With The Cpl Powerpoint Powerpoint Cpl.Org Powerpoint.Org (Powerpoint) Powerpoint (Powerplst) And Powerpoint 2 (Powerstation) (Powerpoints) (Operations orrelog SQL Table Monitor Adapter Users Manual http://www.correlog.com mailto:info@correlog.com CorreLog, SQL Table Monitor Users Manual Copyright 2008-2015, CorreLog, Inc. All rights reserved. No part

More information

Preface. DirXmetahub Document Set. Notation Conventions

Preface. DirXmetahub Document Set. Notation Conventions Preface DirXmetahub Document Set Preface The DirXmetahub Troubleshooting Guide describes how to solve problems that can occur in DirXmetahub installations. DirXmetahub Document Set The DirXmetahub document

More information

FileMaker 14. ODBC and JDBC Guide

FileMaker 14. ODBC and JDBC Guide FileMaker 14 ODBC and JDBC Guide 2004 2015 FileMaker, Inc. All Rights Reserved. FileMaker, Inc. 5201 Patrick Henry Drive Santa Clara, California 95054 FileMaker and FileMaker Go are trademarks of FileMaker,

More information

Heterogeneous Replication Guide. SAP Replication Server 15.7.1 SP200

Heterogeneous Replication Guide. SAP Replication Server 15.7.1 SP200 Heterogeneous Replication Guide SAP Replication Server 15.7.1 SP200 DOCUMENT ID: DC36924-01-1571200-02 LAST REVISED: April 2014 Copyright 2014 by SAP AG or an SAP affiliate company. All rights reserved.

More information

Installing RMFT on an MS Cluster

Installing RMFT on an MS Cluster Installing RMFT on an MS Cluster RMFT Software Version 2.4.3 Supported on: Windows Server 2003 Enterprise Edition Windows Server 2000 Advanced Windows Server 2003 Datacenter Edition Windows Server 2008

More information

Using ODBC with MDaemon 6.5

Using ODBC with MDaemon 6.5 Using ODBC with MDaemon 6.5 Alt-N Technologies, Ltd 1179 Corporate Drive West, #103 Arlington, TX 76006 Tel: (817) 652-0204 2002 Alt-N Technologies. All rights reserved. Other product and company names

More information

Sage Accpac Extended Enterprise Edition 5.6A. Installation and System Administrator's Guide

Sage Accpac Extended Enterprise Edition 5.6A. Installation and System Administrator's Guide Sage Accpac Extended Enterprise Edition 5.6A Installation and System Administrator's Guide 2009 Sage Software, Inc. All rights reserved. Sage, the Sage logos, and all Sage Accpac product and service names

More information

Sage ERP Accpac 6.0A. Installation and System Administrator's Guide

Sage ERP Accpac 6.0A. Installation and System Administrator's Guide Sage ERP Accpac 6.0A Installation and System Administrator's Guide 2010 Sage Software, Inc. All rights reserved. Sage, the Sage logos, and all Sage ERP Accpac product and service names mentioned herein

More information

1 Changes in this release

1 Changes in this release Oracle SQL Developer Oracle TimesTen In-Memory Database Support Release Notes Release 4.0 E39883-01 June 2013 This document provides late-breaking information as well as information that is not yet part

More information

Using the Caché SQL Gateway

Using the Caché SQL Gateway Using the Caché SQL Gateway Version 2007.1 04 June 2007 InterSystems Corporation 1 Memorial Drive Cambridge MA 02142 www.intersystems.com Using the Caché SQL Gateway Caché Version 2007.1 04 June 2007 Copyright

More information

CA Workload Automation Agent for Databases

CA Workload Automation Agent for Databases CA Workload Automation Agent for Databases Implementation Guide r11.3.4 This Documentation, which includes embedded help systems and electronically distributed materials, (hereinafter referred to as the

More information

Unisys INFOIMAGE FOLDER ON WINDOWS NT. Connector for Microsoft Exchange. Getting Started Guide

Unisys INFOIMAGE FOLDER ON WINDOWS NT. Connector for Microsoft Exchange. Getting Started Guide INFOIMAGE FOLDER ON WINDOWS NT Connector for Microsoft Exchange Unisys Getting Started Guide Copyright 1999 Unisys Corporation. All rights reserved. Unisys is a registered trademark of Unisys Corporation.

More information

TSM Studio Server User Guide 2.9.0.0

TSM Studio Server User Guide 2.9.0.0 TSM Studio Server User Guide 2.9.0.0 1 Table of Contents Disclaimer... 4 What is TSM Studio Server?... 5 System Requirements... 6 Database Requirements... 6 Installing TSM Studio Server... 7 TSM Studio

More information

DataFlex Connectivity Kit For ODBC User's Guide. Version 2.2

DataFlex Connectivity Kit For ODBC User's Guide. Version 2.2 DataFlex Connectivity Kit For ODBC User's Guide Version 2.2 Newsgroup: news://dataaccess.com/dac-public-newsgroups.connectivity- Kit_Support Internet Address (URL): http://www.dataaccess.com FTP Site:

More information

Symantec Endpoint Encryption Full Disk

Symantec Endpoint Encryption Full Disk Symantec Endpoint Encryption Full Disk Policy Administrator Guide Version 8.0.1 Copyright 2011 Symantec Corporation. All rights reserved. Symantec and the Symantec Logo are trademarks or registered trademarks

More information

Configuring an Alternative Database for SAS Web Infrastructure Platform Services

Configuring an Alternative Database for SAS Web Infrastructure Platform Services Configuration Guide Configuring an Alternative Database for SAS Web Infrastructure Platform Services By default, SAS Web Infrastructure Platform Services is configured to use SAS Framework Data Server.

More information

National Fire Incident Reporting System (NFIRS 5.0) Configuration Tool User's Guide

National Fire Incident Reporting System (NFIRS 5.0) Configuration Tool User's Guide National Fire Incident Reporting System (NFIRS 5.0) Configuration Tool User's Guide NFIRS 5.0 Software Version 5.6 1/7/2009 Department of Homeland Security Federal Emergency Management Agency United States

More information

"SQL Database Professional " module PRINTED MANUAL

SQL Database Professional  module PRINTED MANUAL "SQL Database Professional " module PRINTED MANUAL "SQL Database Professional " module All rights reserved. No parts of this work may be reproduced in any form or by any means - graphic, electronic, or

More information

UNISYS. Server Management 2.0. Software Release Announcement. imagine it. done. Server Management 2.0 and Higher. May 2008 8216 3445 000

UNISYS. Server Management 2.0. Software Release Announcement. imagine it. done. Server Management 2.0 and Higher. May 2008 8216 3445 000 UNISYS imagine it. done. Server Management 2.0 Software Release Announcement Server Management 2.0 and Higher May 2008 8216 3445 000 NO WARRANTIES OF ANY NATURE ARE EXTENDED BY THIS DOCUMENT. Any product

More information

Microsoft Dynamics GP. Workflow Installation Guide Release 10.0

Microsoft Dynamics GP. Workflow Installation Guide Release 10.0 Microsoft Dynamics GP Workflow Installation Guide Release 10.0 Copyright Copyright 2008 Microsoft Corporation. All rights reserved. Complying with all applicable copyright laws is the responsibility of

More information

FileMaker Server 14. FileMaker Server Help

FileMaker Server 14. FileMaker Server Help FileMaker Server 14 FileMaker Server Help 2007 2015 FileMaker, Inc. All Rights Reserved. FileMaker, Inc. 5201 Patrick Henry Drive Santa Clara, California 95054 FileMaker and FileMaker Go are trademarks

More information

Microsoft Dynamics GP. SmartList Builder User s Guide With Excel Report Builder

Microsoft Dynamics GP. SmartList Builder User s Guide With Excel Report Builder Microsoft Dynamics GP SmartList Builder User s Guide With Excel Report Builder Copyright Copyright 2008 Microsoft Corporation. All rights reserved. Complying with all applicable copyright laws is the responsibility

More information

Cloud Server powered by Mac OS X. Getting Started Guide. Cloud Server. powered by Mac OS X. AKJZNAzsqknsxxkjnsjx Getting Started Guide Page 1

Cloud Server powered by Mac OS X. Getting Started Guide. Cloud Server. powered by Mac OS X. AKJZNAzsqknsxxkjnsjx Getting Started Guide Page 1 Getting Started Guide Cloud Server powered by Mac OS X Getting Started Guide Page 1 Getting Started Guide: Cloud Server powered by Mac OS X Version 1.0 (02.16.10) Copyright 2010 GoDaddy.com Software, Inc.

More information

Active Directory Management. Agent Deployment Guide

Active Directory Management. Agent Deployment Guide Active Directory Management Agent Deployment Guide Document Revision Date: June 12, 2014 Active Directory Management Deployment Guide i Contents System Requirements...1 Hardware Requirements...1 Installation...3

More information

Oracle Essbase Integration Services. Readme. Release 9.3.3.0.00

Oracle Essbase Integration Services. Readme. Release 9.3.3.0.00 Oracle Essbase Integration Services Release 9.3.3.0.00 Readme To view the most recent version of this Readme, see the 9.3.x documentation library on Oracle Technology Network (OTN) at http://www.oracle.com/technology/documentation/epm.html.

More information

HELP DESK MANUAL INSTALLATION GUIDE

HELP DESK MANUAL INSTALLATION GUIDE Help Desk 6.5 Manual Installation Guide HELP DESK MANUAL INSTALLATION GUIDE Version 6.5 MS SQL (SQL Server), My SQL, and MS Access Help Desk 6.5 Page 1 Valid as of: 1/15/2008 Help Desk 6.5 Manual Installation

More information

Oracle WebLogic Server

Oracle WebLogic Server Oracle WebLogic Server Creating Templates and Domains Using the pack and unpack Commands 10g Release 3 (10.3) November 2008 Oracle WebLogic Server Oracle Workshop for WebLogic Oracle WebLogic Portal Oracle

More information

Retrieving Data Using the SQL SELECT Statement. Copyright 2006, Oracle. All rights reserved.

Retrieving Data Using the SQL SELECT Statement. Copyright 2006, Oracle. All rights reserved. Retrieving Data Using the SQL SELECT Statement Objectives After completing this lesson, you should be able to do the following: List the capabilities of SQL SELECT statements Execute a basic SELECT statement

More information

CA ARCserve Backup for Windows

CA ARCserve Backup for Windows CA ARCserve Backup for Windows Agent for Sybase Guide r16.5 This Documentation, which includes embedded help systems and electronically distributed materials, (hereinafter referred to as the Documentation

More information

Oracle Enterprise Manager

Oracle Enterprise Manager Oracle Enterprise Manager System Monitoring Plug-in Installation Guide for Microsoft Active Directory Release 12.1.0.1.0 E28548-04 February 2014 Microsoft Active Directory, which is included with Microsoft

More information

Out n About! for Outlook Electronic In/Out Status Board. Administrators Guide. Version 3.x

Out n About! for Outlook Electronic In/Out Status Board. Administrators Guide. Version 3.x Out n About! for Outlook Electronic In/Out Status Board Administrators Guide Version 3.x Contents Introduction... 1 Welcome... 1 Administration... 1 System Design... 1 Installation... 3 System Requirements...

More information

QACenter Installation and Configuration Guide. Release 4.4.2

QACenter Installation and Configuration Guide. Release 4.4.2 QACenter Installation and Configuration Guide Release 4.4.2 ii Please direct questions about QACenter or comments on this document to: QACenter Technical Support Compuware Corporation 31440 Northwestern

More information

PaperClip32. Installation Guide. for Workgroup and Enterprise Editions. Document Revision 2.1 1

PaperClip32. Installation Guide. for Workgroup and Enterprise Editions. Document Revision 2.1 1 PaperClip32 Installation Guide for Workgroup and Enterprise Editions Document Revision 2.1 1 Copyright Information Copyright 2005, PaperClip Software, Inc. The PaperClip32 product name and PaperClip Logo

More information

TIBCO Spotfire Metrics Modeler User s Guide. Software Release 6.0 November 2013

TIBCO Spotfire Metrics Modeler User s Guide. Software Release 6.0 November 2013 TIBCO Spotfire Metrics Modeler User s Guide Software Release 6.0 November 2013 Important Information SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH EMBEDDED OR BUNDLED TIBCO SOFTWARE

More information

VMware vcenter Discovered Machines Import Tool User's Guide Version 5.3.0.25 for vcenter Configuration Manager 5.3

VMware vcenter Discovered Machines Import Tool User's Guide Version 5.3.0.25 for vcenter Configuration Manager 5.3 VMware vcenter Discovered Machines Import Tool User's Guide Version 5.3.0.25 for vcenter Configuration Manager 5.3 This document supports the version of each product listed and supports all subsequent

More information

Teradata SQL Assistant Version 13.0 (.Net) Enhancements and Differences. Mike Dempsey

Teradata SQL Assistant Version 13.0 (.Net) Enhancements and Differences. Mike Dempsey Teradata SQL Assistant Version 13.0 (.Net) Enhancements and Differences by Mike Dempsey Overview SQL Assistant 13.0 is an entirely new application that has been re-designed from the ground up. It has been

More information

Querying Databases Using the DB Query and JDBC Query Nodes

Querying Databases Using the DB Query and JDBC Query Nodes Querying Databases Using the DB Query and JDBC Query Nodes Lavastorm Desktop Professional supports acquiring data from a variety of databases including SQL Server, Oracle, Teradata, MS Access and MySQL.

More information

FileMaker Server 13. FileMaker Server Help

FileMaker Server 13. FileMaker Server Help FileMaker Server 13 FileMaker Server Help 2010-2013 FileMaker, Inc. All Rights Reserved. FileMaker, Inc. 5201 Patrick Henry Drive Santa Clara, California 95054 FileMaker and Bento are trademarks of FileMaker,

More information

CA XCOM Data Transport for Windows Server/Professional

CA XCOM Data Transport for Windows Server/Professional CA XCOM Data Transport for Windows Server/Professional Installation Guide Release 11.6 Second Edition This Documentation, which includes embedded help systems and electronically distributed materials,

More information

Sybase Replication Agent

Sybase Replication Agent Installation Guide Sybase Replication Agent 15.0 [ Linux, Microsoft Windows, and UNIX ] DOCUMENT ID: DC38268-01-1500-02 LAST REVISED: October 2007 Copyright 1998-2007 by Sybase, Inc. All rights reserved.

More information

ODBC Overview and Information

ODBC Overview and Information Appendix A ODBC ODBC Overview and Information ODBC, (Open Database Connectivity), is Microsoft s strategic interface for accessing data in an environment of relational and non-relational database management

More information

Matisse Installation Guide for MS Windows. 10th Edition

Matisse Installation Guide for MS Windows. 10th Edition Matisse Installation Guide for MS Windows 10th Edition April 2004 Matisse Installation Guide for MS Windows Copyright 1992 2004 Matisse Software Inc. All Rights Reserved. Matisse Software Inc. 433 Airport

More information

KeyAdvantage System DMS Integration. Software User Manual

KeyAdvantage System DMS Integration. Software User Manual KeyAdvantage System DMS Integration Software User Manual ii Copyright Disclaimer Trademarks and patents Intended use EMC Directive Regulatory 2013 United Technologies Corporation. All rights reserved.

More information

HP Web Jetadmin Database Connector Plug-in reference manual

HP Web Jetadmin Database Connector Plug-in reference manual HP Web Jetadmin Database Connector Plug-in reference manual Copyright notice 2004 Copyright Hewlett-Packard Development Company, L.P. Reproduction, adaptation or translation without prior written permission

More information

Dell Statistica 13.0. Statistica Enterprise Installation Instructions

Dell Statistica 13.0. Statistica Enterprise Installation Instructions Dell Statistica 13.0 2015 Dell Inc. ALL RIGHTS RESERVED. This guide contains proprietary information protected by copyright. The software described in this guide is furnished under a software license or

More information

Sage 100 ERP. Installation and System Administrator s Guide

Sage 100 ERP. Installation and System Administrator s Guide Sage 100 ERP Installation and System Administrator s Guide This is a publication of Sage Software, Inc. Version 2014 Copyright 2013 Sage Software, Inc. All rights reserved. Sage, the Sage logos, and the

More information

EMC NetWorker. Licensing Guide. Release 8.0 P/N 300-013-596 REV A01

EMC NetWorker. Licensing Guide. Release 8.0 P/N 300-013-596 REV A01 EMC NetWorker Release 8.0 Licensing Guide P/N 300-013-596 REV A01 Copyright (2011-2012) EMC Corporation. All rights reserved. Published in the USA. Published June, 2012 EMC believes the information in

More information

Turning ClearPath MCP Data into Information with Business Information Server. White Paper

Turning ClearPath MCP Data into Information with Business Information Server. White Paper Turning ClearPath MCP Data into Information with Business Information Server White Paper 1 Many Unisys ClearPath MCP Series customers have Enterprise Database Server (DMSII) databases to support a variety

More information

Oracle Enterprise Manager. Description. Versions Supported

Oracle Enterprise Manager. Description. Versions Supported Oracle Enterprise Manager System Monitoring Plug-in Installation Guide for Microsoft SQL Server Release 12 (4.1.3.2.0) E18740-01 November 2010 This document provides a brief description about the Oracle

More information

Version 7.5 Backup and Recovery Guide

Version 7.5 Backup and Recovery Guide IBM Cognos Business Intelligence Series 7 IBM Cognos Series 7 Deployment Manager Version 7.5 Backup and Recovery Guide Product Information This document applies to IBM Cognos Series 7 Deployment Manager

More information

Getting Started with IntelleView POS Administrator Software

Getting Started with IntelleView POS Administrator Software Getting Started with IntelleView POS Administrator Software Administrator s Guide for Software Version 1.2 About this Guide This administrator s guide explains how to start using your IntelleView POS (IntelleView)

More information

System Monitoring and Diagnostics Guide for Siebel Business Applications. Version 7.8 April 2005

System Monitoring and Diagnostics Guide for Siebel Business Applications. Version 7.8 April 2005 System Monitoring and Diagnostics Guide for Siebel Business Applications April 2005 Siebel Systems, Inc., 2207 Bridgepointe Parkway, San Mateo, CA 94404 Copyright 2005 Siebel Systems, Inc. All rights reserved.

More information

Citrix Access Gateway Plug-in for Windows User Guide

Citrix Access Gateway Plug-in for Windows User Guide Citrix Access Gateway Plug-in for Windows User Guide Access Gateway 9.2, Enterprise Edition Copyright and Trademark Notice Use of the product documented in this guide is subject to your prior acceptance

More information

Centran Version 4 Getting Started Guide KABA MAS. Table Of Contents

Centran Version 4 Getting Started Guide KABA MAS. Table Of Contents Page 1 Centran Version 4 Getting Started Guide KABA MAS Kaba Mas Welcome Kaba Mas, part of the world-wide Kaba group, is the world's leading manufacturer and supplier of high security, electronic safe

More information

Synametrics Technologies. WinSQL Professional User s Guide Version 8.5

Synametrics Technologies. WinSQL Professional User s Guide Version 8.5 Synametrics Technologies WinSQL Professional User s Guide Version 8.5 August 20, 2010 Copyright notice Copyright 2010 Synametrics Technologies, a division of IndusSoft Technologies, Inc. and/or one of

More information

FileMaker Server 11. FileMaker Server Help

FileMaker Server 11. FileMaker Server Help FileMaker Server 11 FileMaker Server Help 2010 FileMaker, Inc. All Rights Reserved. FileMaker, Inc. 5201 Patrick Henry Drive Santa Clara, California 95054 FileMaker is a trademark of FileMaker, Inc. registered

More information