U2 DataVu Quick Start Guide

C:\Users\awaite\Documents\SVN_Doc\trunk\Clients\DataVu\20\Beta\TITLE.fmOctober 11, 2011 12:28 pm

Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta

U2 DataVu

Quick Start Guide

UDV-200-QS-2

ii U2 DataVu Quick Sta

C:\Users\awaite\Documents\SVN_Doc\trunk\Clients\DataVu\20\Beta\TITLE.fmOctober 11, 2011 12:28 pm

Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta

Notices

EditionPublication date: September 2011Book number: UDV-200-QR-2

Product version: U2 DataVu Quick Start Guide

Copyright© Rocket Software, Inc. 2005-2011. All Rights Reserved.

TrademarksThe following trademarks appear in this publication:

Trademark Trademark Owner

Rocket Software™ Rocket Software, Inc.

Dynamic Connect® Rocket Software, Inc.

RedBack® Rocket Software, Inc.

SystemBuilder™ Rocket Software, Inc.

UniData® Rocket Software, Inc.

UniVerse™ Rocket Software, Inc.

U2™ Rocket Software, Inc.

U2.NET™ Rocket Software, Inc.

U2 Web Development Environment™ Rocket Software, Inc.

wIntegrate® Rocket Software, Inc.

Microsoft® .NET Microsoft Corporation

Microsoft® Office Excel®, Outlook®, Word Microsoft Corporation

Windows® Microsoft Corporation

Windows® 7 Microsoft Corporation

Windows Vista® Microsoft Corporation

Java™ and all Java-based trademarks and logos Oracle

UNIX® X/Open Company Limited

rt Guide

The above trademarks are property of the specified companies in the United States, other countries, or both. All other products or services mentioned in this document may be covered by the trademarks, service marks, or product names as designated by the companies who own or market them.

License agreementThis software and the associated documentation are proprietary and confidential to Rocket Software, Inc., are furnished under license, and may be used and copied only in accordance with the terms of such license and with the inclusion of the copyright notice. This software and any copies thereof may not be provided or otherwise made available to any other person. No title to or ownership of the software and associated documentation is hereby transferred. Any unauthorized use or reproduction of this software or documentation may be subject to civil or criminal liability. The information in the software and documentation is subject to change and should not be construed as a commitment by Rocket Software, Inc.

Restricted rights notice for license to the U.S. Government: Use, reproduction, or disclosure is subject to restrictions as stated in the “Rights in Technical Data-General” clause (alternate III), in FAR section 52.222-14. All title and ownership in this computer software remain with Rocket Software, Inc.

NoteThis product may contain encryption technology. Many countries prohibit or restrict the use, import, or export of encryption technologies, and current use, import, and export regulations should be followed when exporting this product.

Please be aware: Any images or indications reflecting ownership or branding of the product(s) documented herein may or may not reflect the current legal ownership of the intellectual property rights associated with such product(s). All right and title to the product(s) documented herein belong solely to Rocket Software, Inc. and its subsidiaries, notwithstanding any notices (including screen captures) or any other indications to the contrary.

Contact informationRocket Software275 Grove Street Suite 3-410 Newton, MA 02466-2272 USA Tel: (617) 614-4321 Fax: (617) 630-7100Web Site: www.rocketsoftware.com

U2 DataVu Quick Start Guide iii

http://www.rocketsoftware.com

Table of Contents

C:\Us(bookT

Table of Contents

Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta

Chapter 1 InstallationInstalling U2 DataVu Software . . . . . . . . . . . . . . 1-5Authorizing U2 DataVu . . . . . . . . . . . . . . . . 1-10

Chapter 2 Account SetupSetting Up a UniData Account . . . . . . . . . . . . . . 2-3

Adding Accounts to the UD.ACCOUNT File . . . . . . . 2-3Using CONVERT.SQL . . . . . . . . . . . . . . . 2-3XTOOLSUB . . . . . . . . . . . . . . . . . . . 2-5

Setting up a UniVerse Account . . . . . . . . . . . . . . 2-6Adding Accounts to the UV.ACCOUNT File . . . . . . . 2-6XTOOLSUB . . . . . . . . . . . . . . . . . . . 2-6

Chapter 3 Getting Started with the U2 DataVu Data SourcesCreating and Configuring U2 DataVu Data Sources . . . . . . . 3-3

Creating a New U2 Data Source . . . . . . . . . . . . 3-6Setting the Advanced JDBC Settings . . . . . . . . . . 3-9

Chapter 4 Log Files and Support Data CollectionCollecting Support Data . . . . . . . . . . . . . . . . 4-4

Enabling the Log File. . . . . . . . . . . . . . . . 4-4Collecting Support Data. . . . . . . . . . . . . . . 4-4

Appendix A XDEMO Account Usage NotesThe XDEMO Account . . . . . . . . . . . . . . . . . A-2

Registering the XDEMO Account in UniData . . . . . . . A-2Registering the XDEMO Account in UniVerse . . . . . . . A-2CONVERT.SQL in the UniData Version of XDEMO . . . . . A-3UNIX/Linux Support . . . . . . . . . . . . . . . A-4

ers\awaite\Documents\SVN_Doc\trunk\Clients\DataVu\20\Beta\DataVuGettingStartedTOC.fm OC.template)

2 U2 Da

C:\Users\awaite\Documents\SVN_Doc\trunk\Clients\DataVu\20\Beta\DataVuGettingStartedTOC.fm (bookTOC.template)

Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta

Appendix B SQL Data Type Conversions in JDBCUsing SQL Data Types in JDBC . . . . . . . . . . . . . B-2

UniVerse Conversion Rules . . . . . . . . . . . . . B-2VARCHAR . . . . . . . . . . . . . . . . . . . B-2Integers . . . . . . . . . . . . . . . . . . . . B-3UniData Conversion Rules . . . . . . . . . . . . . B-5

Appendix C Reference InformationAvailable Resources . . . . . . . . . . . . . . . . . C-2

Appendix D XTOOLSUBUpdating the XTOOLSUB Program . . . . . . . . . . . . D-2

UniData for UNIX & Linux . . . . . . . . . . . . . D-3UniData for Windows . . . . . . . . . . . . . . . D-4UniVerse for UNIX & Linux . . . . . . . . . . . . . D-5UniVerse for Windows . . . . . . . . . . . . . . . D-6

taVu Quick Start Guide

C:\UsOctob

1 Chapter

ers\awer 11, 2

Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta

Installation

Installing U2 DataVu Software . . . . . . . . . . . . . 1-5Authorizing U2 DataVu . . . . . . . . . . . . . . . . 1-9

aite\Documents\SVN_Doc\trunk\Clients\DataVu\20\Beta\CH1TOC.fm011 12:28 pm

This chapter provides installation instructions for U2 DataVu for UniData and UniVerse users.

Note: These instructions are written for U2 DataVu Dashboard and U2 DataVu Report. U2 DataVu Query users may see some differences between their product and the examples shown in this manual, and some features may not be available to U2 Query users.

1-3

U2 DataVu is implemented as a high performance, Eclipse-based desktop application, combining the portability of Java with the performance of native applications. A self-contained U2 DataVu installation package is available for each of the following supported platforms:

Note: The U2 DataVu installation package includes the JDBC driver used to create U2 DataVu data sources. If you are accessing or creating data sources outside of U2, you may need to install the appropriate JDBC drivers. For more information about installing drivers for data sources outside of U2, refer to the Installing and Managing U2 DataVu manual.

Platform Version Setup Executable

Windows XP, 2003, 2008, Vista, 7 setupwin32.exe

Macintosh 10.5 and 10.6 setupMac.zip

Red Hat Linux Enterprise WS Versions 5 and 6 setupLinux.bin

SuSELinux Versions 10 and 11 setupLinux.bin

U2 DataVu supported platforms, versions, and executable files

1-4 U2 DataVu Quick Start Guide

Installing U2 DataVu SoftwareTo install the software, run the appropriate installation package on your target platform and follow the installation prompts, as described below. Upon completion of the installation, it is recommended that you apply the latest available U2 DataVu fix packs.

Complete the following steps to install U2 DataVu on Windows:

1. In the U2 DataVu download directory, navigate to the U2 DataVu installation executable, setup.exe, and open it.

The setup program starts and after a few moments the U2 DataVu Setup Launchpad appears.

2. Select Install U2 DataVu for Windows. The U2 DataVu Introduction screen opens. Click Next to start the installation process.

Installing U2 DataVu Software 1-5

3. After accepting the licensing agreement, click Next. The Choose Install Location dialog box opens, as shown in the following example:

By default, the installation process installs U2 DataVu in the C:\Program Files\Rocket Software\ U2 DataVu folder. Click Next to install U2 DataVu in the default folder, or click Browse to search for a different location.


4. The Choose Shortcut Folder dialog box opens, as shown in the following example:

You can choose to create any or all of the following shortcuts:

In a new Program Group

In an existing Program Group

In the Start Menu

On the Desktop

In the Quick Launch Bar

You can also choose to install no shortcuts.


5. Select the shortcut folder(s) you want to create, and then click Next. The Choose Install Set dialog box opens, as shown in the following example:

You can choose to install any or all of the following components:

U2 DataVu

U2 DataVu User

U2 DataVu Administrator

U2 DataVu Web

Select the component(s) you want to install, and then click Next.

Note: For more information about any of these components, refer to the Installing and Managing U2 DataVu manual.


6. The Pre-Installation Summary dialog box opens, detailing all of the installation information, as shown in the following example:

Look over the installation summary. If everything is correct, click Install to begin the installation process. Otherwise, click Back to change any of your installation selections.


Authorizing U2 DataVuBefore you can use the application, you must activate your product license. After installing U2 DataVu, the first step before setting up your query management environment is to activate your product license. Use the serial number that came with the product to obtain an authorization code. This code is then entered into U2 DataVu to finalize the activation process.

To activate a product license:

1. Start U2 DataVu and open the Manage License dialog box in one of two ways:

If no license has been activated for this installation, a message displays telling you how many days remain on the trial instal-lation. Click OK. The Manage License dialog box opens.

If a license has already been activated, select File > Manage Licenses. The Manage License dialog box opens, as shown:

2. Click Add License. The Add U2 DataVu License dialog box opens.

Enter the serial number that you received with you product installation material in the Serial number field.


3. Select the appropriate U2 DataVu edition from the following Edition menu options:

U2 DataVu Report (DVR) - includes development of visual reports that incorporate graphics, conditional formatting and can be exported to Excel or output to HTML or PDF.

U2 DataVu Dashboard (DVD) - includes everything U2 DataVu Report allows and adds development of interactive visual dashboards using a drag-drop designer.

If you are activating a license for U2 DataVu Web, specify the number of concurrent connections that this license will authorize in the Number of connections combo box.

4. Copy the generated configuration code in the Configuration code field and click Close. The Add U2 DataVu License dialog box closes and the license is added to the Manage License dialog box.

5. Go to the U2 TechConnect Web page at https://u2tc.rocket-software.com/authprod.asp and follow the online instructions for obtaining your license activation code.

6. Select the license from the Manage License dialog box and click Activate License. The Activate U2 DataVu license dialog box opens.

7. In the The Activate U2 DataVu license dialog box, enter the activation code that you received from the U2 TechConnect Web page and click Activate. Focus returns to the Manage License dialog box.

8. If you are using U2 DataVu Web and want to edit the number of concurrent connections that a license allows, select the license and click Edit License. The Edit U2 DataVu License dialog box opens.

Specify the number of concurrent connections you want this license to authorize in the Number of connections combo box, then click Close. The Manage License dialog box closes and the license is activated.

Note: You must re-activate the license every time the number of concurrent U2 DataVu Web connections changes.

Authorizing U2 DataVu 1-11

To remove a license:

1. Select the license that you want to delete and click Remove. Since only one license can be saved at a time, you must remove an existing license before you can add a new license. For example, if you have a previously activated U2 DataVu Report license and want to upgrade to a U2 DataVu Dashboard license, you must first remove the U2 DataVu Report license.

2. Click Close. The Manage License dialog box closes and your license is active.


C:\UsSeptem

2 Chapter

ers\awber 21


Account Setup

Setting Up a UniData Account . . . . . . . . . . . . . 2-3 Adding Accounts to the UD.ACCOUNT File . . . . . . . 2-3 Using CONVERT.SQL . . . . . . . . . . . . . . . 2-3 XTOOLSUB . . . . . . . . . . . . . . . . . . 2-5Setting up a UniVerse Account . . . . . . . . . . . . . 2-6 Adding Accounts to the UV.ACCOUNT File . . . . . . . 2-6 XTOOLSUB . . . . . . . . . . . . . . . . . . 2-6

aite\Documents\SVN_Doc\trunk\Clients\DataVu\20\Beta\CH2TOC.fm, 2011 1:58 pm

This chapter describes how to set up your UniData or UniVerse account in U2 DataVu.

2-2

Setting Up a UniData AccountIn order to access your files in U2 DataVu, you need to properly set up your UniData account. To do this, you must add your account to the UD.ACCOUNT file, use the CONVERT.SQL command to make your files SQL compliant, and then grant appropriate privileges for access to the files.

Adding Accounts to the UD.ACCOUNT File

The first thing you need to do set up a UniData account for use with U2 DataVu is add your UniData account to the UD.ACCOUNT file. This allows you to access your files when creating a data source. You must complete this step for all files that do not currently exist in the UD.ACCOUNT.

To add an account to the UD.ACCOUNT file:

1. From the ECL prompt, log to the sys account, and then enter the following command:

AE UD.ACCOUNT account_name

2. If an item does not exist in the UD.ACCOUNT file, you must create the file and insert the path into attribute 1 of the account.

3. File and save your changes.

Using CONVERT.SQL

Once you add your account to the UD.ACCOUNT file, you must make your files accessible to JDBC. You can do this by converting your UniData files into SQL-compliant tables using the CONVERT.SQL command. The CONVERT.SQL command checks the UniData file for conformance to SQL requirements. When inconsistencies are found, UniData:

Checks the name of the file being converted. If the filename is ODBC compliant, UniData uses this name for the table. If the filename is not ODBC compliant, UniData creates a new, duplicate dictionary items with a compliant name for use by ODBC/UniData SQL.

Checks attribute specifications for missing value code and format specification.


Creates synonyms (also called aliases) in the dictionary for attribute names that do not conform to the ODBC conventions. For each noncompliant attribute name, UniData creates or adds an entry in the attributes @SYNONYM and @ORIGINAL to link the new compliant attribute name with the original attribute name.

Adds conforming names of the converted files to the UniData SQL privilege table.

To use the CONVERT.SQL command:

1. From the ECL prompt, LOGTO the UniData account that contains the files you want to use in U2 DataVu.

2. Enter CONVERT.SQL [filename].

Granting Privileges with CONVERT.SQL

The CONVERT.SQL command can also be used to grant privileges to your account for use with U2 DataVu.

To grant SELECT privileges to PUBLIC on a file being converted with CONVERT.SQL, use the following syntax:

CONVERT.SQL [filename] PUBLIC [ALL, INSERT, UPDATE, DELETE, or SELECT]

For more information about using CONVERT.SQL, refer to the Using UniData SQL manual.

You can also grant privileges to specific users using the SQL GRANT command. For more information about granting privileges and using the SQL GRANT command, refer to the UniData SQL Commands Reference manual.

Note: CONVERT.SQL will create additional dictionary items that are SQL compliant. We recommend that you create a separate account with a copy of the dictionary files and pointers to the original data files, if you do not want to add the SQL-compliant dictionaries to your production account.

Setting Up a UniData Account 2-4

XTOOLSUB

The first time you connect to the database server, U2 DataVu calls the XTOOLSUB program, a server-side BASIC program used by all U2 Eclipse-based clients and tools. The XTOOLSUB program must be updated periodically, as described in Appendix D, XTOOLSUB. You can download the latest version of XTOOLSUB from the public Tech Note site at:

https://u2tc.rocketsoftware.com/documentation/1410028.asp





Setting up a UniVerse AccountIn order to access your files in U2 DataVu, you need to properly set up your UniVerse account. To do this, you must add your account to the UV.ACCOUNT file.

Adding Accounts to the UV.ACCOUNT File

The first thing you need to do set up a UniVerse account for use with U2 DataVu is add your UniVerse account to the UV.ACCOUNT file. This allows you to access your files when creating a data source. You must complete this step for all account entries that do not currently exist in UV.ACCOUNT.

To add an account to the UV.ACCOUNT file:

1. From the TCL prompt, log to the UV account, and then enter the following command:

ED UV.ACCOUNT account_name

2. If an item does not exist in the UV.ACCOUNT file, you must create the entry and insert the account file path into attribute 11.

3. File and save your changes.

XTOOLSUB

The first time you connect to the database server, U2 DataVu calls the XTOOLSUB program, a server-side BASIC program used by all U2 Eclipse-based clients and tools. The XTOOLSUB program must be updated periodically, as described in Appendix D, XTOOLSUB. You can download the latest version of XTOOLSUB from the public Tech Note site at:


Setting up a UniVerse Account 2-6




C:\UsOctob

3 Chapter

ers\awer 11, 2


Getting Started with the U2 DataVu Data Sources

Creating and Configuring U2 DataVu Data Sources . . . . . . 3-3 Creating a New U2 Data Source . . . . . . . . . . . 3-6 Setting the Advanced JDBC Settings . . . . . . . . . . 3-9


This chapter describes how to create and configure the U2 DataVu data sources.

3-2

Creating and Configuring U2 DataVu Data SourcesYou must create a repository to store your U2 DataVu objects before you can work with your data sources. Personal repositories serve a single user and are stored in the personal settings directory of the workstation (server) that is running the U2 DataVu application interface. For example, in a Windows operating system, the personal repository is saved under the following path (shown here on two lines):

C:\Documents and Settings\[UserName]\Application Data\Rocket Software\U2 DataVu\Personal Repositories

The easiest way to make a personal repository is to create a sample repository from the Welcome page. The sample repository contains all of the sample files, and can be used as your personal storage repository as well.

To create a sample repository:

1. From the Welcome screen, click the Create Sample Repository icon, as shown:

Note: The sample repository is not available in U2 DataVu Query. Refer to the next section for instructions on how to create a new repository.

2. Click Next at the prompt.


3. Select the Go To Workbench icon from the Welcome screen, as shown:

4. The U2 DataVu workstation opens in the User perspective. Select Windows > Open Perspective > Administrator to switch to the Administrator perspective.

Note: All examples in this manual are created in the Administrator perspective. For more information about User perspective and the Administrator perspective, refer to the Getting Started with U2 DataVu manual.

When the workstation opens, the sample repository appears in the Administrator pane, as shown:

Creating and Configuring U2 DataVu Data Sources 3-4

You can also choose to create a new personal repository, independent of the sample repository.

To create a new personal repository:

1. Select File > New > Other. The New Wizard dialog box opens. Choose Personal Repository from the menu options. The Create New Personal Repository dialog opens:

2. Enter a meaningful name for the repository in the Name field.

3. Optionally, you can specify a comment that describes the repository in the Comment field.

4. Select the Connect immediately check box if you want to immedi-ately connect to your new repository.


5. Click Finish. The personal repository is created and saved in the workstation’s personal settings directory.

Note: For more information about using repositories, refer to the Getting Started with U2 DataVu manual.

Creating a New U2 Data Source

Once you create your sample repository and are in the Administrator perspective, you are ready to create a new data source.

To create a new data source:

1. From the Repository view, expand the Samples node, and then select U2 Data Sources > New > U2 Data Source, as shown:


2. The Create New U2 Data Source dialog opens, as shown:

In the Data Source Name field, enter a name for your data source. In this example, we name the data source UVTestDS.

In the Host name field, enter the name of your host connection. In this example, we use localhost.

Select either UniVerse or UniData as your Database type.


3. Click Set User Information.... The User Information dialog box opens. Enter the User name and Password for your system, then click OK. Focus returns to the Create New U2 Data Source dialog.

Click Test Connection to test the U2 DataVu connection to your sys-tem.A message box opens, confirming a successful connection.

4. Click the Refresh icon, located next to the Account field to propagate the list of available accounts to which your data source will connect, as shown in the red box below:

5. Select the account to which your data source will connect. In this example, we select the HS.SALES account.


6. If you are an SB/XA user, you also need to log on to your SB/XA account. To do this, select the Is SB+ Account check box. The Set SB+ User Information button, which had previously been dimmed, becomes available. Click Set SB+ User Information, as shown:

The Set SB+ User Information dialog box opens. Enter your SB/XA user information into the appropriate User name and Password field, as shown, then click OK:

Focus returns to the Create New Data Source dialog box.

7. Click Finish to create the connection, or you can choose to edit the JDBC settings, as described in the next section.

Setting the Advanced JDBC Settings

You can edit the JDBC connection string keywords available to your U2 DataVu application. You do this by changing the keyword values for yourU2 files. This is an optional step, and is typically reserved for situations where either the row length or the column length exceed the buffer size.

To edit the advanced JDBC settings:


1. From the Create New U2 Data Source dialog box, click Advanced. The Advanced JDBC Settings dialog box opens, as shown:

The dialog box opens with two driver-specific connection string keywords available to you: MAXFETCHBUFF and MAXFETCHCOLS.

MAXFETCHBUFF controls the maximum buffer size on the server to hold data rows.

MAXFETCHCOLS controls the maximum number of column values the server can put in the buffer before sending data to the client.

2. Change the value of the MAXFETCHBUFF parameter by selecting the MAXFETCHBUFF check box and then entering a new value for the parameter in the Value field, as shown:

In our example, we change the value to 70000.


3. Change the value of the MAXFETCHCOLS parameter by selecting the MAXFETCHCOLS check box and then entering a new value for the parameter in the Value field, as shown:

In our example, we change the value to 10000.

Note: For more information about MAXFETCHBUFF or MAXFETCHCOLS, refer to the Administrative Supplement for Client APIs manual. For more information on using JDBC with U2 DataVu, refer to the Installing and Managing U2 DataVu manual.

4. When you are done making changes, click OK. Focus returns to the Create New U2 Data Source dialog box. Click Finish. Focus returns to the workstation and your data source is available for use in U2 DataVu.

You are now ready to create your queries and reports in U2 DataVu.


C:\UsOctob

4 Chapter

ers\awer 11, 2


Log Files and Support Data Collection

Collecting Support Data . . . . . . . . . . . . . . . . 4-4 Enabling the Log File . . . . . . . . . . . . . . . 4-4 Collecting Support Data . . . . . . . . . . . . . . 4-4


This chapter describes how to collect support data in U2 DataVu.


Collecting Support DataU2 DataVu allows you to collect support data for your U2 DataVu application in two ways: Log files and data collection.

Enabling the Log File

The log file is the file to which logging information is written, and can be helpful when debugging an issue. It can be delivered as a report or to your workstation in the Output view.

To enable the log file:

1. Select View >Preferences. The Preferences dialog box opens. Select Log from the available options.

2. Check Enable log to activate the log file for debugging purposes and deliver the information in the Output view of your workstation. If this check box is selected, the log file option fields are enabled. Check one or more of the log file options to indicate what information should be gathered. We recommend that all options remain checked.

3. Click OK to close the Preferences dialog box.

Note: For details about the log file and the options available in the log file, refer to the Getting Started with U2 DataVu manual.

Collecting Support Data

U2 DataVu offers users the option to collect support data directly from the workstation. This information can then be sent directly to Rocket U2 Support. The support data is used by U2 technical support providers and customers to diagnose problems with U2 DataVu. Typically, you will not use this feature unless instructed to by a member of Rocket U2 support.

To collect support data:

1. Start U2 DataVu or U2 DataVu Web.

Collecting Support Data 4-4

2. Select Help > Collect Support Data... from the workstation menu options. The Collect Support Data dialog box opens, as shown:

3. Enter the details about your issue in the Problem details field.

4. Click Save Report. The Save As dialog box opens. Enter a name for your report. Choose a name that does not already exist in the directory you are currently in. This name commonly includes the support case number or the current date, such as U2DataVu_469503_022508.

5. When the file contains all of the information necessary support information, click Save. The file is saved as a zip file, and can be sent directly to Rocket U2 Support.


AAppendix

XDEMO Account Usage Notes

This appendix provides information about using the XDEMO sample account in U2 DataVu.

The XDEMO AccountThe XDEMO account contains a group of test files used in UniData and UniVerse sample applications. You can use the XDEMO account to access and utilize the samples provided with U2 DataVu.

The minimum database releases required for this account are:

UniData: 6.1.15 or 7.1.2

UniVerse: 10.1.15

Registering the XDEMO Account in UniData

Before you can use the XDEMO account in UniData, you must create an entry for it in the ud.account file. This registers the account in UniData and allows you to create new data sources based on XDEMO.

To register the XDEMO account in UniData, create the following entry in the ud.account file:

:LOGTO sys

:AE UD.ACCOUNT XDEMOTop of "XDEMO" in "UD.ACCOUNT", 1 line, 17 characters.*--: P001: C:\IBM\ud72\xdemoBottom.*--:

Registering the XDEMO Account in UniVerse

Before you can use the XDEMO account in UniVerse, you must create an entry for it in the uv.account file. This registers the account in UniVerse and allows you to create new data sources based on XDEMO.

A-2 U2 DataVu Quick Start Guide

To register the XDEMO account in UniVerse, create the following entry in the uv.account file:

---->LOGTO UV

>AE UV.ACCOUNT XDEMOTop of "XDEMO" in "UV.ACCOUNT", 14 lines, 31 characters.*--: P001:002:003:004:005:006:007:008:009:010:011: C:\IBM\UV\XDEMO012:013:014: YESBottom.*--:

CONVERT.SQL in the UniData Version of XDEMO

Starting with XDEMO version 2.00, and in the UniData version of the account, CONVERT.SQL has been executed on the following files:

FUR_REV

PLOCATION

STATES_MAPS

WORLD_MAP

ZIPCODES.

CONVERT.SQL converts the files to tables and must be modified with CREATE/DROP TABLE commands.

The CONVERT.SQL command has not been run on the remaining base files in the XDEMO account. You can run CONVERT.SQL on all the XDEMO files at once by running the following command:

CONVERT.SQL.XDEMO

A-3

This includes the files noted above.

You can also choose to run CONVERT.SQL on only the remaining XDEMO files. To do this, run the following command:

CONVERT.SQL.XDEMO.CORE

UNIX/Linux Support

The XDEMO account is built on Windows. You can use XDEMO in a UNIX or Linux environment, but you will need to migrate the account using the instructions below.

To migrate the XDEMO account:

1. Transfer the account to the UNIX/Linux system and convert the file formats.

■ On UniVerse, transfer the account with uvbackup/uvrestore or run the fnuxi command on the files in the account.

■ On UniData, run $UDTBIN/convcode .and $UDTBIN/convdata –r .

2. Once logged into the account, run RECATALOG.XDEMO. This will fix the catalog entries in the VOC files.

A-4 U2 DataVu Quick Start Guide

3. Before you can use the BUILD.XDEMO.DATAS & BUILD.XDEMO.DICTS programs, you must add the UniVerse bin or UniData bin path to your library path. These programs use the XML functions and will abort with an error. See U2 Tech Note 1177867 (Use the Exact Phrase search option).

The syntax for the library environment variable (U2BIN = Uni-Verse/UniData bin) is shown below:

# AIX

LIBPATH=$LIBPATH:$U2BIN export LIBPATH

# HP

SHLIB_PATH=$SHLIB_PATH:$U2BIN export SHLIB_PATH

# SOLARIS

LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$U2BIN export LD_LIBRARY_PATH

# LINUX

LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$U2BIN export LD_LIBRARY_PATH

A-5

BAppendix

SQL Data Type Conversions in JDBC

This appendix describes the expected JDBC data types depending on the different dictionary specifications.

Using SQL Data Types in JDBCWhen creating a U2 data source in U2 DataVu, the initial data type is determined from the information that U2 DataVu gets from JDBC. UniData and UniVerse provide JDBC data types based on the different data type conversions specified in your dictionary. This section is intended to help you understand how the data type is determined and any limitations associated with that data type.

UniVerse Conversion Rules

To fine-tune or define data type, precision, and scale values for columns and I-descriptors in files, you can either edit the conversion and format fields of the dictionary or you can edit the DATATYPE field of the corresponding dictionary entry (field 8 in D- and I-descriptors, field 6 in A- and S- descriptors).

If you are not satisfied with how your data displays, check to ensure that your dictionary entries are set up correctly. It is important to note the following rules about the values in your conversion and format fields.

The following rules apply if you do not use the DATATYPE dictionary field. When the DATATYPE field is present, then the data type is set to the one specified, after the conversion has been applied, if specified.

For more information about data types and conversion information, refer to the UniVerse UCI Developer’s Guide and Using the JDBC Driver for UniData and UniVerse.

VARCHAR

For fields in which a data type conversion is not specified and the format is left-justified, the default data type is VARCHAR (254). Note that JDBC does not truncate data that is longer than the specified data type length.

B-2 U2 DataVu Quick Start Guide

Integers

For right-justified dictionary items without a conversion code, and items defined as MD0, MR0, or ML0, UniVerse considers the data type to be an integer.

An integer data type cannot contain a value that is greater than the maximum integer (MAXINT) limit of 2147483647. Therefore, guided by the FORMAT specification, UniVerse either returns a NULL or attempts to upgrade the data type to decimal when it is expected that the stored numbers may exceed MAXINT. For example, if the length in the FORMAT specification is 12 or above, UniVerse automatically changes the output data type to decimal; however, if the length in the FORMAT specification is 11 or lower, it is assumed that the stored numbers are within the MAXINT limit and UniVerse leaves the data type as an integer. When this occurs and a larger number is encountered, UniVerse returns <Null>.

You can always override the UniVerse default data type calculations by specifying the desired data type in the DATATYPE field of the dictionary.

In the U2 DataVu query result set below, the return value shown in columns 2, 3, and 4 highlight the differences in how UniVerse handles different integer situations. The values in column 2 show the return values when the output format is set to 10 (i.e. 10R). The values in column 3 show the return values when the output format is set to 12. The values in column 4 show the return values when the output format is set to 20.

Decimal Numbers

Any dictionary item whose conversion specification is MDn, MRn and MLn, where n is greater than zero, will have a JDBC data type of decimal.

B-3

For MDn, MRn, and MLn conversions, UniVerse defines the decimal precision and scale output to JDBC. The dictionary output format influences the precision and scale as well.

Decimal numbers with a scale of 2

If the length in the FORMAT specification is 14 or less, then UniVerse returns a data type of Decimal(n,2), where n is format length.

If the length in the FORMAT specification is 15 or higher, then UniVerse returns a data type of Decimal (25, n), where n = 27 - format length. For example, if your format length is set to 17R, then your output value would be Decimal(25, 10).

Note: Format specifications that have a length greater than 25, or a decimal scale value greater than 12, are invalid and may cause unpredictable results.

You can change the way your output displays by defining your own DATATYPE value, for example Numeric,23, 2, which is translated as Decimal (25, 2) in JDBC.

In the U2 DataVu query result set below, when the conversion value is set to MD2, the return value shown in columns 2, 3, and 4 highlight the differences in how UniVerse handles different decimal situations. The values in column 2 show the return values when the output format is set to 5 (for example, 5R). The values in column 3 show the return values when the output format is set to 14. The values in Column 4 show the return values when the output format is set to 15:

B-4 U2 DataVu Quick Start Guide

UniData Conversion Rules

The data type conversions in UniData do not rely on the column justification, specified in the dictionary FORMAT field. If there is no conversion specified, then the JDBC data type is VARCHAR (254). Note that JDBC does not truncate data that is longer than the specified data type length.

If the conversion specified is MD0, MR0, or ML0, the JDBC data type is integer. If the conversion specification is MDn, MRn, or MLn, where n > 0, then the corresponding JDBC data type is set to FLOAT.

For integer values, once you exceed the maximum integer value, a null value is returned. This occurs when your returned value is greater than 2147483647.

UniData ignores the format definition if a conversion data type is specified.

For more information about data types and conversion information, refer to Using the JDBC Driver for UniData and UniVerse.

B-5

CAppendix

Reference Information

This appendix provides a list of resources that provide detailed information about the topics addressed in this manual.

Available ResourcesAll U2 DataVu documentation can be found on the Web at:

http://www.rocketsoftware.com/u2/pubs/library

For more information about installing drivers for data sources outside of U2, configuring repositories, setting up resource limits, using JDBC within U2 DataVU, or other administration information, refer to the Installing and Managing U2 DataVu manual.

For more information about using U2 DataVu perspectives, queries, reports, and repositories, refer to the Getting Started with U2 DataVu manual.

For more information about using SQL functionality in a UniVerse application, refer to the Using UniData SQL manual.

For more information about using SQL functionality in UniData, refer to the UniData SQL Commands Reference manual.

For more information about MAXFETCHBUFF or MAXFETCHCOLS, refer to the Administrative Supplement for Client APIs manual.

For more information on using U2 DataVu Web, refer to the following resources:

Installing and Managing U2 DataVu

Getting Started with U2 DataVu

Tech Note UCC-912 - Entitled users can view this Tech Note by navigating to the U2 TechConnect site at https://u2tc.rocket-software.com/ and then selecting U2 knowledge base from the menu options.

You can also watch video tutorials that illustrate U2 DataVu usage. These tutorials are available on the U2 Developer Zone website, at https://u2devzone.rocketsoftware.com/accelerate

C-2 U2 DataVu Quick Start Guide

https://u2tc.rocketsoftware.com/

https://u2tc.rocketsoftware.com/


https://u2devzone.rocketsoftware.com/accelerate



DAppendix

XTOOLSUB

This appendix describes the XTOOLSUB program, and how to upgrade to the latest version of XTOOLSUB on various platforms.

Updating the XTOOLSUB ProgramThe XTOOLSUB program is a U2 database server-side BASIC program used by various U2 Client Tools. This includes U2 DataVu, U2 Web DE, Basic Developer's Toolkit (BDT), Extensible Administration Tool (XAdmin), Web Services Developer, and more. It also includes any tool that uses the U2 Resource View.

Periodically, the XTOOLSUB program needs to be updated to support new functionality. You can download the latest version of XTOOLSUB from the public Tech Note site at:


The XTOOLSUB program contains several zip and tar files, and includes three or four files, depending on the environment. The XTOOLSUB program is used by all the tools, but the other files included are only used for the Basic Developer's Toolkit (BDT).

The XTOOLSUB_EXECPRE/XTOOLSUB_XPRE programs are for pre-execution functionality and XTOOLSUB_EXECPOST/XTOOLSUB_XPST are for post-execution functionality. These programs are discussed further in the related public Tech Note, BDT Extensibility Details. If you have added your own code to the pre- and post-functionality, copy those modified programs to the older database versions rather than the pre- and post- files located here.

The files included for UniData are:

XTOOLSUB

XTOOLSUB_EXECPRE

XTOOLSUB_EXECPOST

EDAMAPSUB (UDT 6.1 and lower)

The files included for UniVerse are:

XTOOLSUB

XTOOLSUB_XPRE

XTOOLSUB_XPST

EDAMAPSUB (UV 10.3 and lower)

D-2 U2 DataVu Quick Start Guide


Do not catalog the EDAMAPSUB subroutine when using UDT 7.1 or UV 11.1 and higher. This program already exists on those versions.

There is a difference between the databases because UniVerse's catalog environment is a type 1 file and has a 14 character filename limit.

Only extract the file that is needed for the database server/version and OS type you are using. The ...UX.tar (Unix) files come from AIX. You will need to run fnuxi/convcode if you use other UNIX/Linux operating systems. Files are not included for all operating systems in order to avoid unnecessary confusion. The files in the zip/tar files are the object code for the given programs; do not open them in a text editor.

Note: Log in as a root or administrator user when doing these steps to avoid any permissions errors. If an overwrite message occurs, select "yes" to overwrite the file in question.

UniData for UNIX & Linux

The $UDTBIN referenced below is an environment variable pointing to your UniData bin directory, for example, /usr/ud##/bin (where ##, is 61,71,72, etc.). If this variable is not set, then reference the full path to the UniData bin directory in the commands.

1. Copy the XTOOLSUB_UDT_UX.tar or XTOOLSUB_UDT_61_UX.tar file to a temporary directory on your server (ie. /tmp). If transferring using ftp, remember to use binary format.

2. Extract the file to the $UDTHOME/sys/SYS_BP directory.

With UniData 6.1 and lower, the commands will be:

cd $UDTHOME/sys/SYS_BP

tar -xvf /tmp/XTOOLSUB_UDT_61_UX.tar

With UniData 7.1 and higher, the commands will be:

cd $UDTHOME/sys/SYS_BP

tar -xvf /tmp/XTOOLSUB_UDT_UX.tar

3. If you are using a non-AIX operating system, run convcode $UDTHOME/sys/SYS_BP:

$UDTBIN/convcode .

D-3

Note: The convcode command includes a period at the end of the line. This will convert everything in the SYS_BP file to the current format. All files report that they were converted, but this is the default answer for convcode. The existing files should already be in the correct format.

4. cd to $UDTHOME/sys and execute udt

cd .. (or cd $UDTHOME/sys)

$UDTBIN/udt

5. Catalog the three XTOOLSUB programs, as follows:

CATALOG SYS_BP XTOOLSUB FORCE

CATALOG SYS_BP XTOOLSUB_EXECPRE FORCE

CATALOG SYS_BP XTOOLSUB_EXECPOST FORCE

6. If you are using UniData 6.1 or lower, also run this command:

CATALOG SYS_BP EDAMAPSUB FORCE

7. Connect with your U2 client tool to the U2 database server.

UniData for Windows

1. Copy the XTOOLSUB_UDT_NT.zip or XTOOLSUB_UDT_61_NT.zip file to a temporary directory on your server (for example, c:\temp).

2. Extract the file to the c:\u2\ud##\sys\SYS_BP (## refers to the UDT major version, i.e. 61, 71, 72, etc.) directory using your preferred unzipping utility. If UniData is installed in another location, change the path accordingly.

3. Log into the sys account via telnet or execute a udt shell in the sys directory on the server.


CATALOG SYS_BP XTOOLSUB FORCE

CATALOG SYS_BP XTOOLSUB_EXECPRE FORCE

CATALOG SYS_BP XTOOLSUB_EXECPOST FORCE

5. If you are using UniData 6.1 or lower, also run this command:

CATALOG SYS_BP EDAMAPSUB FORCE



UniVerse for UNIX & Linux

1. Copy the XTOOLSUB_UV_UX.tar or XTOOLSUB_UV_103_UX.tar file to a temporary directory on your server (for example, /tmp). If transferring using ftp, remember to use binary format.

2. Extract the file to the /usr/uv/BP.O directory. If UniVerse is installed in another location, change the path accordingly. Use 'cat /.uvhome' to find the path if needed.

Note: `cat /.uvhome` references include back quotes. This retrieves the current value for the UniVerse home directory prior to executing the command.

For UniVerse 10.3 and lower, the commands are:

cd `cat /.uvhome`/BP.O

tar -xvf /tmp/XTOOLSUB_UV_103_UX.tar

For UniVerse 11.1 and higher, the commands are:

cd `cat /.uvhome`/BP.O

tar -xvf /tmp/XTOOLSUB_UV_UX.tar

3. If you are using a non-AIX operating system, run fnuxi, as follows:

`cat /.uvhome`/bin/fnuxi XTOOLSUB*

4. cd to the UniVerse home directory and execute uv:

cd `cat /.uvhome`

bin/uv

5. Click Escape to get out of the menu.


CATALOG BP *XTOOLSUB FORCE

CATALOG BP *XTOOLSUB_XPRE FORCE

CATALOG BP *XTOOLSUB_XPST FORCE

Note: You will receive a catalog error if you try to catalog all three programs on that same command line.

7. If you are using UniVerse 10.3 or lower, also run this command:

CATALOG BP *EDAMAPSUB FORCE


D-5

UniVerse for Windows

1. Copy the XTOOLSUB_UV_NT.zip or XTOOLSUB_UV_103_NT.zip file to a temporary directory on your server (for example, c:\temp).

2. Extract the file to the c:\u2\uv\BP.O directory using your preferred unzipping utility. If UniVerse is installed in another location, change the path accordingly.

3. Log in to the UV home account via Telnet. The account name is UV or uv in the UV.ACCOUNT file.


CATALOG BP *XTOOLSUB FORCE

CATALOG BP *XTOOLSUB_XPRE FORCE

CATALOG BP *XTOOLSUB_XPST FORCE

Note: You will receive a catalog error if you try to catalog all three programs on that same command line.

5. If you are using UniVerse 10.3 or lower, also run this command:

CATALOG BP *EDAMAPSUB FORCE



Date post:	07-Oct-2014
Category:	Documents
Upload:	jon-searle
View:	87 times
Download:	3 times