Installing and Licensing UniData 7.2 Products · 3/8/2010 · Please be aware: Any images or indications reflecting ownership or branding of the product(s) documented herein may

C:\Program Files\Adobe\FrameMaker8\UniData 7.2\7.2rebranded\INSTALL\INSTTITL.fmMarch 8, 2010 11:53 am

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

UniData

Installing and Licensing UniData 7.2 Products

UDT-720-INST-1

ii Installing and Lice

C:\Program Files\Adobe\FrameMaker8\UniData 7.2\7.2rebranded\INSTALL\INSTTITL.fmMarch 8, 2010 11:53 am

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

Notices

EditionPublication date: July 2008Book number: UDT-720-INST-1Product version: UniData 7.2

Copyright© Rocket Software, Inc. 1988-2008. 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 Sun Microsystems, Inc.

UNIX® X/Open Company Limited

nsing UniData 7.2 Products

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-410Newton, MA 02466-2272 USA Tel: (617) 614-4321 Fax: (617) 630-7100Web Site: www.rocketsoftware.com

Installing and Licensing UniData 7.2 Products iii

http://www.rocketsoftware.com

http://www.rocketsoftware.com

Table of Contents

:\ProgMarch

Table of Contents

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

Chapter 1 Introduction

Chapter 2 Introduction to Installing the UniData RDBMSDetermining the Installation Type on UniData for UNIX . . . . . . . 2-3Determining the Installation Type on UniData for Windows Platforms . . 2-5Preinstallation Tasks on UniData for UNIX . . . . . . . . . . . 2-7Preinstallation Tasks on UniData for Windows Platforms . . . . . . 2-13Understanding the UniData Directories . . . . . . . . . . . . 2-14Determining the Location of Log Files for RFS on UniData for UNIX . . 2-17

Chapter 3 UniData RDBMS Basic InstallationStep-by-Step Installation on UniData for UNIX . . . . . . . . . 3-3Installing Using the install.param File on UniData for UNIX . . . . . 3-17Troubleshooting Tips . . . . . . . . . . . . . . . . . . 3-21Step-by-Step Installation on UniData for Windows Platforms . . . . . 3-23

Chapter 4 UniData RDBMS Advanced InstallationStep-by-Step Installation on UniData for UNIX . . . . . . . . . 4-3Installing Using the install.param File . . . . . . . . . . . . . 4-17Troubleshooting Tips . . . . . . . . . . . . . . . . . . 4-21Step-by-Step Advanced Installation on UniData for Windows Platforms . . 4-23

Chapter 5 UniData RDBMS Concurrent InstallationConsiderations for Concurrent Installations . . . . . . . . . . . 5-3Step-by-Step Installation on UniData for UNIX . . . . . . . . . 5-5Installing Using the install.param File . . . . . . . . . . . . . 5-20Troubleshooting Tips . . . . . . . . . . . . . . . . . . 5-24Step-by-Step Installation on UniData for Windows Platforms . . . . . 5-26

Chapter 6 UniData RDBMS Upgrade InstallationStep-by-Step Installation on UniData for UNIX . . . . . . . . . 6-3

ram Files\Adobe\FrameMaker8\UniData 7.2\7.2rebranded\INSTALL\INSTTOC.fm (bookTOC.template)8 2010 11:39 am

Updating Multiple UDTHOME Accounts on UniData for UNIX . . . . 6-20Installing Using the install.param File . . . . . . . . . . . . . 6-21Troubleshooting Tips . . . . . . . . . . . . . . . . . . 6-25Step-by-Step Installation on UniData for Windows Platforms . . . . . 6-27

Chapter 7 UniData RDBMS Patch InstallationPatch Installation Considerations . . . . . . . . . . . . . . 7-3Step-by-Step Installation . . . . . . . . . . . . . . . . . 7-5Installing Using the install.param File . . . . . . . . . . . . . 7-22Troubleshooting Tips . . . . . . . . . . . . . . . . . . 7-25

Chapter 8 Licensing UniData ProductsAbout Licensing . . . . . . . . . . . . . . . . . . . 8-3Licensing UniData . . . . . . . . . . . . . . . . . . . 8-4Licensing Steps on UniData for UNIX . . . . . . . . . . . . 8-7How UniData Counts Licenses . . . . . . . . . . . . . . . 8-16Licensing Steps for UniData for Windows Platforms . . . . . . . . 8-17Updating a UniData License . . . . . . . . . . . . . . . . 8-20

Table of Contents v

1Chapter

Introduction

1-2

This manual takes you through the steps of installing, licensing, and setting up your UniData Release 7.2 products. These instructions consist of the following:

“ Introduction”“ UniData RDBMS Basic Installation”“ UniData RDBMS Advanced Installation”“ UniData RDBMS Concurrent Installation”“ UniData RDBMS Upgrade Installation”“ UniData RDBMS Patch Installation”“ Licensing UniData Products”

2Chapter

Introduction to Installing the UniData RDBMS

Determining the Installation Type on UniData for UNIX . . . . . . 2-3 Basic Installation . . . . . . . . . . . . . . . . . 2-3 Advanced Installation . . . . . . . . . . . . . . . . 2-3 Concurrent Installation . . . . . . . . . . . . . . . 2-3 Upgrade Installation . . . . . . . . . . . . . . . . 2-4 Patch Installation . . . . . . . . . . . . . . . . . 2-4Determining the Installation Type on UniData for Windows Platforms . . 2-5 No Previous UniData Installation . . . . . . . . . . . . 2-5 UniData Installed on Windows NT 3.5.1 . . . . . . . . . . 2-5 UniData 3.3.1.4 (or Later) Installed on Windows NT 4.0 . . . . . 2-5 Earlier UniData Version on Windows NT 4.0 . . . . . . . . 2-6Preinstallation Tasks on UniData for UNIX . . . . . . . . . . 2-7 Verify Operator Knowledge . . . . . . . . . . . . . . 2-7 Assemble Materials . . . . . . . . . . . . . . . . 2-7 Check System Requirements. . . . . . . . . . . . . . 2-8 Create and Verify All Needed Backups . . . . . . . . . . 2-11 Mount the Distribution Media . . . . . . . . . . . . . 2-11Preinstallation Tasks on UniData for Windows Platforms . . . . . . 2-13 Verify Hardware and Software Compatibility . . . . . . . . 2-13 Assemble Required Materials . . . . . . . . . . . . . 2-13Understanding the UniData Directories . . . . . . . . . . . . 2-14 Directory Structure on UniData for UNIX . . . . . . . . . 2-14 Directory Structure on UniData for Windows Platforms . . . . . 2-16Determining the Location of Log Files for RFS on UniData for UNIX . . 2-17

This chapter describes information you should be aware of before installing the UniData RDBMS. This consists of:

Determining the Installation Type on UniData for UNIXDetermining the Installation Type on UniData for Windows PlatformsPreinstallation Tasks on UniData for UNIXPreinstallation Tasks on UniData for Windows PlatformsUnderstanding the UniData DirectoriesDetermining the Location of Log Files for RFS on UniData for UNIX

1-2

Determining the Installation Type on UniData for UNIXMake one of the following choices about how you want to install UniData before proceeding:

Basic InstallationYou are installing UniData for the first time on this machine and you want to use the default directories. For step-by-step procedures, see Chapter 3, “UniData RDBMS Basic Installation.”

Advanced InstallationYou are installing UniData for the first time on this machine and you want to choose directories other than the default directories. Carefully review the section “Under-standing the UniData Directories” later in this chapter for information on how directory names impact your configuration. For step-by-step procedures, see Chapter 4, “UniData RDBMS Advanced Installation.”

Concurrent InstallationYou already have a previous version of UniData running on the machine where you are installing UniData 7.1, and you want to run these two versions concurrently. For step-by-step procedures, see Chapter 5, “UniData RDBMS Concurrent Installation.”

Users running different versions of UniData should not try to update the same files at the same time. If you want to test your application by installing UniData 7.1 concur-rently, set up a separate demo database for your testing. Do not try to update live files with two versions of UniData at the same time.

There are some limitations for concurrent execution of UniData 7.2, which are described in Chapter 5, “UniData RDBMS Concurrent Installation.”

1-3 Installing and Licensing UniData 7.2 Products

Upgrade InstallationYou are upgrading to UniData 7.2 from a previous version of UniData. For step-by-step procedures, see Chapter 6, “UniData RDBMS Upgrade Installation.”

Patch InstallationYou have a version of UniData 7.2 running on your system and are installing a patch version of UniData 7.2. For step-by-step procedures, see Chapter 7, “UniData RDBMS Patch Installation.”

Determining the Installation Type on UniData for UNIX 1-4

Determining the Installation Type on UniData for Windows PlatformsThe process for installing UniData for Windows Platforms depends on whether you have installed earlier versions of UniData. Review the information below to determine which sequence of steps you should complete. The procedures for new installation, upgrade installation, licensing, and uninstalling are described in detail in the remaining sections of this manual.

No Previous UniData InstallationMake certain your Windows system is upgraded to Windows NT 4.0 or greater.Install UniData 7.2 on your system. See Chapter 3, “ UniData RDBMS Basic Installation,” for more information.

UniData Installed on Windows NT 3.5.1If you have any UniData version running on Windows NT 3.5.1, you must:

Uninstall your UniData product (See “Uninstalling UniData” in this chapter)Delete any remaining components of the UniData directory structureShutdown and restart your Windows machineUpgrade your Windows machine to Windows NT 4.0 or greaterInstall UniData 7.1 (See “Before Installing UniData” and Chapter 6, “ UniData RDBMS Upgrade Installation”).

UniData 3.3.1.4 (or Later) Installed on Windows NT 4.0Beginning at Release 3.3.1.4, you can upgrade to UniData 7.2 without uninstalling the previous version. See Chapter 6, “ UniData RDBMS Upgrade Installation,” for more information.


Earlier UniData Version on Windows NT 4.0If you have a UniData release previous to UniData 3.3.1.4 running on Windows NT 4.0, you must:

Uninstall your previous UniData version Delete any remaining components of the UniData directory structureShutdown and restart your Windows NT machineInstall UniData 7.2

Determining the Installation Type on UniData for Windows Platforms 1-6

Preinstallation Tasks on UniData for UNIXFor UniData installations, there are a number of tasks to complete and factors to consider before conducting the installation. Regardless of the type of installation you are performing, the basic preparatory steps are:

Verify operator knowledge.Assemble materials.Check system requirements.Mount the distribution media.Understand the UniData directories and determine their location for your installation.Determine the location of the log files for the Recoverable File System (RFS).

Verify Operator KnowledgeBefore beginning a UniData installation, make sure you know:

How to log on as root.How to edit a UNIX text file.The device name (in other words, the name of the associated configuration file) of the tape drive, diskette drive, or CD-ROM drive you plan to use for the installation. You will most often find these defined in your /dev directory.The serial number or a descriptive name you want to use to identify your CPU. The type of shell with which you are working. (If you are not sure, try the UNIX echo $SHELL command.)

Assemble MaterialsMake sure you have all needed materials on hand before beginning a UniData installation:

A UniData tape, set of disks, or CD-ROM containing the UniData software.


The Product Configuration Sheet shipped with the UniData software.These instructions.

Check System Requirements

Operating System Requirement

IBM ports UniData for UNIX products to many versions of UNIX. Verify that the product you have received matches your UNIX operating system, and verify that the installation media is appropriate for your system.

UniData requires that certain kernel parameters have adequate settings in order for UniData to accommodate the full number of licensed users. The following table lists some recommended kernel parameters.

Kernel Parameters

Description HPUX Solaris DG IntelRecommended Value

Semaphore undo structures systemwide

semmnu semmnu semmnu 3 * (number of autho-rized users) + (number of authorized users / 4)

Shared memory segments

shmmni shmmni shmmni Must be greater than SHM_GNTBLS

Number of message queues

msgmni msgmni msgmni Non-RFS: 10 + the number of concurrent journal processes if you are using UniData Journaling.RFS: ((number of authorized users / 4) * 2) + 10

Semaphore identifiers

semmni semmni semmni NUSERS/NSEM_PSET + 1

Number of semaphores available systemwide

semmns semmns semmns NUSERS + 10

Preinstallation Tasks on UniData for UNIX 1-8

Warning: Beginning at Release 4.1, UniData required more systemwide semaphores than previous releases of UniData. The number of semaphores systemwide, normally semmns, should be a miminum of NUSERS + 10. The number of semaphore identifiers, normally semmni, must be a minimum of NUSERS/NSEM_PSET + 1. If either of these kernel parameters are not adequate for the number of licensed users, an error message similar to “Exit: smm: cannot allocate semaphore for udtno xx errno 28. Exit: SMM can’t setup Control Table List” will be displayed, and UniData will fail to start.

Product Configuration

A UniData Product Configuration sheet was shipped with your UniData product. This sheet lists customer information, hardware information, and the products and number of users you are authorized to install. Verify that all the information on the Product Configuration sheet is correct. You will need this sheet when authorizing UniData.

Disk Space

On most systems, you must have at least 125 megabytes (MB) of free disk space under one mount point for the UniData installation to run. Depending on the type of installation, some space — as much as 10 MB — may be released after installation.

Note: If you are installing UniData from disks, your system will need twice the disk space as is required for installing from tape (or at least 250 MB). This space does not need to be under a single mount point. You still need 125 MB under one mount point for the installation. The remaining space, which can be elsewhere on your system, is required to unload and uncompress the tar file on the disks. You can free that space after you have extracted the UniData files from the tar file.

If you decide to install UniData on a partition other than the default /usr partition, you will still need to have approximately 2 MB available on /usr. This space is used for the /usr/ud72/include directory

If you are planning to use the Recoverable File System (RFS), use the following formula to determine the minimum disk space you need for logging:

8 MB + 4096 * (NUSERS + 1)

These requirements are based on the default of two before image and after image logs per set.


Each archive should be a minimum of 8 MB to contain two sets of after image logs.

Note: If you turn on archiving, you need to plan for additional resources (either disk or tape) to handle regular backup of archive files.

To determine the space available on your system, use the UNIX df or du command at the shell prompt. See your host operating system documentation for help with these commands.

Tip: Most UNIX systems provide an online manual, also known as the “man pages.” At the UNIX prompt, enter the man man command to see if your system provides an online manual, and if so, refer to the man pages about the specific syntax for df or du commands.

Memory

The exact memory needs for a UniData installation are highly platform and appli-cation specific. Aside from the memory required by other applications on your system, if any, you can use the following guidelines to estimate the memory required for your UniData installation:

Approximately 10–20 MB of free memory for the operating system. Consult your host operating system documentation for the amount of memory needed for your operating system.2 MB of free memory per UniData session if you do not use RFS, just to run UniData.3-5 MB of free memory per UniData session if you do use RFS, just to run UniData. Remember that more memory is required if you use Transaction Processing, if you have a large number of writes in one transaction, and if you are using archiving. Any additional memory required by your application. Compute your memory needs, then add 10 percent more memory for the UNIX file system buffer.


The following example illustrates how to calculate the amount of memory necessary for 50 users running an application that requires 1 MB of memory per session. In this example, RFS is not considered:

Memory needed for OS 10 MB Memory needed for UniData (2 MB * 50 users) 100 MB Additional memory needed for application (1 MB * 50 users) 50 MBSubtotal 160 MB10 percent for file system buffer 16 MBTotal memory required 176 MB

In the next example, memory is calculated for the same scenario running RFS:

Memory needed for OS 10 MB Memory needed for UniData (4 MB * 50 users) 200 MB Additional memory needed for application (1 MB * 50 users) 50 MBSubtotal 260 MB10 percent for file system buffer 26 MBTotal memory required 286 MB

Create and Verify All Needed BackupsIBM recommends that you complete a full backup of the device on which you want to install UniData before you begin installation. If you already backed up that device, verify that the backup is complete and valid. If you are upgrading, you should also perform and verify a full backup of all your UniData data files.

Warning: If you are upgrading from a previous version of UniData with RFS to UniData 7.2 with RFS, it is important that you create and verify a full backup of all your recoverable data files. IBM suggests you use only log files or archive files created under UniData 7.2 to recover from system or media failures that occur at UniData 7.2.

Mount the Distribution MediaHere are some tips for mounting the tape on the device from which you intend to run the installation:

If you are loading the UniData software from an 8-mm cassette onto an IBM RS6000, make sure that the tape drive’s block size is set to 0. Use the AIX smit utility to check and change the tape drive’s block size.If you do not know the device name of the tape drive you are using to load UniData, enter the command as tar xv to specify the default device.


Installing from Disk

If you purchased UniData on disks, be aware that the product is shipped as a tar file in compressed format. The product is shipped in this format for the following reasons:

It unloads more quickly than an uncompressed format.Reducing the number of disks reduces the possibility of corrupted media.

Before you can actually start the UniData installation, you need to unload the compressed tar file from the disks and uncompress it. The step-by-step installation instructions include information you need to unload and uncompress the tar file.

Note: You need disk space on your system to unload and uncompress the tar file in addition to the space required to complete the installation. You can unload the tar file in a separate location (such as /tmp) and then extract the UniData files and directories into your bin directory.

Installing from CD-ROM

If your installation media is a CD-ROM, complete the following steps:

1. Load the CD into your CD-ROM drive.2. Mount the CD-ROM drive if it is not already mounted. See your host

operating system and vendor documentation for information about mounting the drive.

3. List the contents of the CD by using the UNIX ls command. You will find a file called BIN.TAR. If you do not want to load UniData directly from the CD-ROM drive, complete step 4. Otherwise, simply proceed with the instal-lation steps.

4. Copy the BIN.TAR file from the CD-ROM to some other location on your system, using the UNIX cp command. We suggest that you copy the tar file into the directory which will be your UniData bin directory. By default, this is /usr/ud72/bin. After you copy the tar file, you can execute tar xvf to load the contents into the bin directory.


Preinstallation Tasks on UniData for Windows PlatformsThe information in this sections applies to both new and upgrade installation of UniData for Windows platforms.

Verify Hardware and Software CompatibilityVerify that your Windows system meets the following criteria:

Intel processor, 486 SX33 or better, or DEC Alpha processor configured for Windows NT Version 4.0 or greater.

Tip: Consult the Microsoft and Digital Equipment Corporation web sites for information about hardware compatibility.

At least 32 MB of RAM.A CD-ROM drive.At least 30MB of disk space on an NTFS partition for installing the UniData system files. This requirements does not include space for your UniData database files.Windows NT Server, Windows NT Workstation, Version 4.0, or greater. UniData 7.2 is not certified for Windows NT Version 3.51.TCP/IP. You must have TCP/IP installed on your Windows system if you plan to install and use UniData ODBC, the UniData Telnet Service, or NFA.

Note: You must install UniData on NTFS partition, not a FAT partition. UniData is supported for NTFS file systems only.

Assemble Required MaterialsYou must have:

UniData distribution media (CD-ROM disc)UniData Product Configuration Sheet (shipped with distribution media)


Understanding the UniData DirectoriesThe UniData installation process creates several directories that contain components of the software.

Directory Structure on UniData for UNIXWhen you use the basic installation instructions, all the directories are under /usr/ud72 and have the default names. The advanced and other installation processes allow you to specify other names for some directories:

Default Directory Description

/usr/ud72 or udthome By default, contains the bin, demo, lib, log, objcall, sys, and work subdirectories. May contain other subdirectories. This important directory can have any valid UNIX directory name. For that reason, this publication sometimes refers to it as udthome. (The italics show that udthome is a variable expression in the text.)

/usr/ud72/bin or udtbin Contains the UniData binary (executable) files. It is the directory into which you load the software from the tape. The directory does not have to be in udthome, and it can have any name. In this publication, it is sometimes referred to as udtbin.

usr/ud72/work or udtwork

Contains files needed to rebuild the UniData “kernel,” which is an executable called udt. The files are required if you ever intend to use CallBasic or CALLC. The work directory is loaded into udthome unless you specify another path during installation. If the directory is not named “work,” you must create the environment variable WORKPATH to define the path. In this publication, the work directory is sometimes referred to as udtwork.

/usr/ud72/lib orudthome/lib

Contains libraries for all UniData executables. It is loaded into udthome unless you specify another path during installation. The directory can have any name. If you change its location or name, also change libpath in udtwork/base.mk and udtwork/callbas.mk.

Default UniData Directories

Understanding the UniData Directories 1-14

/usr/ud72/include Contains the files path72, udtconfig, sysconfig, repconfig, repsys, and files needed for the Recoverable File System (RFS). Also contains header files needed to link the libraries in /lib. The name of this directory cannot be changed.

/usr/ud72/demo or udthome/demo

A demonstration account created by default in udthome/demo; may be moved, removed, or renamed any time after installation.

/usr/ud72/sys or udthome/sys

Contains UniData compiled programs provided with UniData, including the Alternative Editor (AE), and files used by AE. Also contains the default global catalog, which includes globally cataloged UniBasic object code. This directory also contains the master VOC file for your installation, and other system files such as the error message files. This directory must reside under the udthome directory.

/usr/ud72/bin/ods Contains control files, client demo, and include directories for ObjectCall. The name of this directory cannot be changed.

/usr/unishared Contains information necessary for the unirpcd daemon.


Default UniData Directories (continued)


Directory Structure on UniData for Windows PlatformsWhen you use the basic installation instructions, all these directories are under \IBM\ud72 and have the default names. The advanced and other installation processes allow you to specify other names for some directories:

Default UniData Directories


\IBM\ud72 or udthome By default, contains the bin, demo, include, sys, odbc, NTMIGRATE, master, and udtmon subdirectories. May contain other subdirectories. This important directory can have any valid directory name. For that reason, this publi-cation sometimes refers to it as udthome. (The italics show that udthome is a variable expression in the text.)

\IBM\ud72\bin or udtbin

Contains the UniData binary (executable) files. The directory does not have to be in udthome, and it can have any name. In this publication, it is sometimes referred to as udtbin.

\IBM\ud72\demo or udthome\demo

A demonstration account created by default in udthome\demo; may be moved, removed, or renamed any time after installation.

\IBM\ud72\sys or udthome\sys

Contains UniData compiled programs provided with UniData, including the Alternative Editor (AE), and files used by AE. Also contains the default global catalog, which includes globally cataloged UniBasic object code. This directory also contains the master VOC file for your instal-lation, and other system files such as the error message files. This directory must reside under the udthome directory.

\IBM\ud72\odbc or udthome\odbc

Contains the charsets and locales directories.

\IBM\unishared Contains information necessary for the unirpc service.

Understanding the UniData Directories 1-16

Determining the Location of Log Files for RFS on UniData for UNIXThis preparation is applicable if you plan to install the Recoverable File System (RFS) as part of your UniData 7.2 installation process. You may also enable RFS after you have installed UniData 7.2. For detailed information on the log files and RFS, see Administering the Recoverable File System.

The types of log files are:

Before image log files.After image log files.File-level log file.

If you include RFS when you install UniData 7.2, UniData automatically creates a set of log files in the destination you specify by using a default log configuration table. You can use the default files for testing, but you may need to reconfigure if you want to use RFS in production.

Note: If you are upgrading from a previous release of UniData with RFS to UniData 7.2 with RFS, and you want to keep your log files in the same location, be aware that the upgrade process will overwrite existing log files. Make sure you have backed up your data files, and stop UniData with stopud before you begin the upgrade.

Tip: IBM recommends that you create the log files on a different physical device than your UniData data files. You can create log files on a raw disk or UNIX file system.


3Chapter

UniData RDBMS Basic Installation

Step-by-Step Installation on UniData for UNIX . . . . . . . . . 3-3Installing Using the install.param File on UniData for UNIX . . . . . 3-17Troubleshooting Tips . . . . . . . . . . . . . . . . . 3-21Step-by-Step Installation on UniData for Windows Platforms . . . . . 3-23

This chapter is intended for those who are installing UniData Release 7.2 on UNIX or Windows platforms. These instructions guide you through the basic installation process. Use the basic installation instructions when you are installing UniData for the first time and want to use the default directories.

On UniData for UNIX, answers to the prompts in the installation script are kept in the install.param file located in udtbin. This file contains responses that are most likely inappropriate for your installation after it is loaded from tape. After you complete the installation process, your responses to the installation prompts are written to this file.

You can edit the install.param file to customize your installation, then use the customized file as part of the installation process without having to provide input to the installation prompts. If you want to use this option, proceed to “Installing Using the install.param File on UniData for UNIX” on page 17.


Step-by-Step Installation on UniData for UNIXFollow the steps in this section for a basic installation.

You must be logged in as root to perform the installation.

1. Check or Create Your bin DirectoryThe installation process uses a default directory called /usr/ud72/bin. You must create this directory and its parent directory, udthome. Enter the following example as shown to create these directories:

# mkdir /usr/ud72 # mkdir /usr/ud72/bin # cd /usr/ud72/bin

2. Install the Media

Installing from Tape

Mount the tape on your tape drive. Load the UniData software into the /usr/ud72/bin directory with the UNIX tar command. In the example below, tape.device is the name of the tape drive you are using. For more information on the tar command, see your UNIX documentation.

# tar xvf /dev/tape.device

Installing from Diskette

Your installation media contains a tar file in compressed format. Unload the compressed tar file from diskette, and then uncompress. Then, extract the UniData files and directories from the tar file. To accomplish these tasks, your system needs roughly twice the amount of disk space required for an ordinary UniData installation. You can complete the unload, uncompress, and extract procedures in the /usr/ud72/bin directory if you have enough disk space at that location. Consider performing the unload and uncompress steps in another location (such as /tmp) if the /usr/ud72/bin directory has less than 250 MB of space available.

Step-by-Step Installation on UniData for UNIX 1-3

Tip: Do not unload and uncompress the file in your root partition (/). If you run out of space in the root partition, you will cause problems for yourself and other users.

Unloading the Compressed tar File

Set the current working directory to the location where you want to unload and uncompress the tar file. Insert disk 1 into your disk drive, and execute the tar command just as if you were installing from tape. For example, if your disk drive’s device name is /dev/fd0, and you want to unload the file into /tmp, use the following commands:

# cd /tmp# tar xvf /dev/fd0

You will be prompted each time you need to insert a new disk. When this procedure is complete, your current working directory contains a compressed-format tar file, whose name is prodname.tar.Z.

Tip: Use the UNIX ls command to identify the compressed tar file. prodname varies with each individual release. For example, sco72.tar.Z is the compressed tar file for a release of UniData 7.2 for a SCO platform.

Uncompressing the tar File

Use the UNIX uncompress command to generate an uncompressed tar file. For example, if the name of the compressed tar file is sco72.tar.Z, enter the following command at the UNIX prompt:

# uncompress sco72.tar.Z

Now, your current working directory contains an ordinary tar file, prodname.tar.

Extracting UniData Files from the tar FileSet your current working directory to /usr/ud72/bin. Use the UNIX tar command to extract the UniData files and subdirectories. Make sure you specify the full path name of the tar file. For example, if your udtbin directory is /usr/ud72/bin, and the tar file (named sco72.tar) is in /tmp, use the following commands:

# cd /usr/ud72/bin# tar xvf /tmp/sco72.tar


This command extracts your UniData files into udtbin. After this has completed successfully, you can remove the tar file from your system to release disk space. Use the UNIX rm command as shown below:

# rm /tmp/sco72.tar

Proceed to step 3.


Execute the tar command from the /usr/ud72/bin directory just as if you were installing from tape. For example, suppose the device file for your CD-ROM drive is /dev/cdrom, and your bin directory path is /usr/ud72/bin. Use the following commands:

% cd /usr/ud72/bin% tar xvf /dev/cdrom/BIN.TAR

3. Enter ./udtinstallEnter ./udtinstall at the system prompt. This begins the installation process.

International Installation

The UNIX LANG environment variable affects the behavior of UniData. Before you install UniData, you should be aware of the consequences of using a LANG setting other than “C.” If you use a LANG setting other than “C,” note that certain UniData commands may cause unpredictable results, such as the UniBasic UPCASE and DOWNCASE commands, and the MCU and MCL conversion codes.

If you are installing UniData in an environment that does not support ASCII characters 250 through 255, and ASCII character 192 as internal markers, read UniData International before proceeding with the installation.

Tip: IBM strongly recommends that the value of LANG is consistent for all users. Consider setting the LANG environment variable in the .profile or .login script.


Choosing a LANG Setting

When choosing a LANG setting for your system, make sure the LANG setting you choose is supported by UniData. To find the supported LANG settings for your system, execute the locale -a command, as shown in the following example:

# locale -aCPOSIXC.iso88591C.utf8univ.utf8ar_DZ.arabic8ar_SA.arabic8ar_SA.iso88596bg_BG.iso88595cs_CZ.iso88592da_DK.iso88591da_DK.roman8nl_NL.iso88591nl_NL.roman8...#

During the installation process, UniData changes the LANG environment variable to “C” for installation processing and displays the following message:

# udtinstall

Welcome to the UniData RDBMS.

http://www.ibm.com/software/data/u2

WARNING:

-- environment variable LANG is not set to ‘C’ -- it will be set to ‘C’ by Unidata for installation -- see Unidata Installation Guide for more details

Would you like to continue? [Yes]:

If you press ENTER to accept the default answer of “Yes,” UniData continues the installation process using the LANG group of “C.” If desired, you can change your LANG environment variable after the installation process is complete. If you answer “No” to the above prompt, UniData exits the installation process.


NonInternational Installation

If you are executing a default installation, the following screen appears:

# cd $UDTBIN#./udtinstall



WARNING: If UniData system is still running, it will be stopped with force. This may not guarantee the consistency of your database files, so we recommend that you stop the system with ‘stopud’ before installing/upgrading UniData.


Press ENTER to accept the default of “Yes” if you want to continue with the instal-lation process. If you do not want to proceed at this time, enter “No.”

Note: You must enter “Yes” , “yes”, or “YES” and “No”, “no” or “NO” rather than “Y” or “N” for all prompts in the installation process.

4. Enter the UDTHOME DirectoryUniData prompts for the full path of the UDTHOME directory. For the basic instal-lation, accept the default /usr/ud72 directory by pressing ENTER:

Enter the full path name of udt home directory [/usr/ud72]:

WARNING: The path you selected doesn't equal to UDTHOME. The environment variable UDTHOME will be ignored and it needs to be changed after the installation.

UniData displays the preceding warning message because the UDTHOME environment variable is not set. You can set environment variables in step 19 of these instructions.

5. Enter the udtwork Directory The system displays the default work directory where it will load the files to rebuild UniData. Press ENTER to accept the default:

Enter the full path name of work directory [/usr/ud72/work]:


6. Enter the udtlib DirectoryThis directory contains libraries for all UniData executables. Press ENTER to accept the default:

Enter the full path name of lib directory [/usr/ud72/lib]:

7. Enter the Location of the log FilesThis directory contains the location where UniData will build the log files for the Recoverable File System (RFS). Press ENTER to accept the default:

Enter the full path name of log directory [/usr/ud72/log]:

8. Enter the Location of the unishared DirectoryThe unishared directory contains files necessary for the unirpcd daemon. Press ENTER to accept the default location of /usr/unishared:

Enter the full path name of unishared directory [/usr/unishared]:

9. Enter a Group NameUniData uses the group name associated with the root login name. If the group name displayed is correct, press ENTER. If the default is not correct, enter the correct group name:

Enter a valid group name for changing files' group [sys]:

10. Enter the Serial Number Enter the serial number found on your IBM Software Product Configuration sheet in response to the following prompt. This information is not required as part of the installation.

Enter the Serial Number displayed on your "IBM Software ProductConfiguration" sheet: [serial_number]:


11. Install the Recoverable File SystemIf you do not want to install the Recoverable File System(RFS) at this time, press ENTER to accept the default of “No.” You must purchase the RFS product separately. If you are not sure whether you have purchased RFS, check the Product Configu-ration Sheet included with your UniData tape. You can install RFS at a later time without rerunning the installation process. To enable RFS postinstallation, see Administering the Recoverable File System.

If you choose to install RFS at this time, enter “Yes.” The installation process creates a default log configuration table, creates the log files, and turns on RFS:

Turn on the Recoverable File System? [No]:

12. Install ReplicationIf you do not want to install Replication at this time, press ENTER to accept the default of “No.” You can install Replication at a later time without rerunning the installation process. To enable Replication postinstallation, see Using UniData Replication.

If you choose to install Replication at this time, enter “Yes.” The installation process creates a default configuration file, creates the log files, and turns on Replication:

Turn on the Replication System? [No]:

13. Back Up Existing DirectoriesThis option does not apply to a basic installation, since it backs up existing UniData 7.1 directories. Press ENTER to accept the default of “No”.

Backup the existing directories? [No]:


14. Decide When to Authorize UniDataUniData prompts you to indicate whether you want to configure the product at the end of the installation process. If you enter “Yes” at this prompt, UniData automati-cally runs the confprod utility as part of the installation. If you do not want to configure the product at the end of the installation process, press ENTER to accept the default of “No.” UniData will run for 30 days after installation without requiring authorization.

Config product at the end of installation? [No]:

Warning: When licensing UniData, you must be using a terminal supported by vvtermcap. vvtermcap is a special UniData termcap-like file located in the udtbin directory. UniData supports the following terminal types: ANSI, DEC VT100, DEC VT220, VT52, and WYSE 50. If you are installing UniData from a different type of terminal, do not configure the product at the end of the installation process.

15. Review Input DataUniData displays a summary of the information input at each prompt before proceeding with the installation. Review the summary carefully. If all the values are correct, press ENTER to accept the values and proceed with the installation process. If some information is incorrect, enter “No.” UniData exits the installation process. You need to restart the installation and make any corrections to prompt responses.

Summary of your inputs

CheckLang Yes SaveDir save OverWrite Yes Confirm No StopSys Yes WorkDir /usr/ud72/work LibDir /usr/ud72/lib LogDir /usr/ud72/log UnisharedDir /usr/unishared Group sys Serial serial_number RFSflag No

REPflagNo Backup No ConfProduct No Are those values correct? [Yes]:


16. Proceed with the Installation ProcessThe installation process first makes sure that the version of UniData identified by UDTBIN is not running. The installation process then changes the file’s ownership to root, and the group name to the name you specified.


Next, the installation process tests the system configuration by running the systest utility, then creates the include, ods, lib, sys, demo, work, include, lib, sys, demo, work, sybase, unishared, and objcall directories.

11 Start installing/upgrading UniData RDBMS Release 6.2.111 Using UDTBIN=/usr/ud72/bin11 UniData is not running.1 SM has already been stopped.1 CLEANUPD has already been stopped.1 SMM is not running.1 SBCS has already been stopped.1 SMM is not running.1 Unirpcd is being shared by other U2 database products11 Unidata R7.2 has been shut down.11 Changing files’ ownership and group name ...11 Testing system configuration ...11 Creating/Updating /usr/ud72/include directory...11 Creating/Updating /usr/ud72/ods directory...11 Creating/Updating /usr/ud72/lib directory...11 Creating/Updating /usr/ud72/sys directory...11 Creating/Updating /usr/ud72/demo directory...11 Creating/Updating /usr/ud72/work directory...11 Creating/Updating /usr/ud72/objcall directory...1111 You now have completed the installation process. The

following1 directories are not required for running udt, you may

either1 remove them to save some disk space or keep them there

for1 future use:11 /usr/ud72/bin/include1 /usr/ud72/bin/lib1 /usr/ud72/bin/work1 /usr/ud72/bin/demo1


1 Do you want to save those directories (save/delete) [save]:

1

17. Authorize UniDataIf you answered “Yes” to the “Config product at the end of installation” prompt, UniData automatically runs the confprod utility at this time. Refer to Chapter 8, “ Licensing UniData Products,” for information about licensing UniData. If you answered “No” at the “Config product at the end of installation” prompt, proceed to the next step. You have 30 calendar days from the date you install UniData to license the product.

If you authorize UniData as part of the installation process, UniData executes the systest command again to determine configuration parameters for the number of authorized users. If your kernel parameters are not adequate to support the number of authorized users, UniData displays messages similar to the following:

You may not be able to run full number of users sessions (1250)as configured due to the current semmnu setting (100) inyour Unix system. You need to increase semmnu to 3750 andrebuild your Unix kernel.The number of global tables(SHM_GNTBLS) should not be greater than SHMMNI.No enough message queue identifiers. Please make N_TMQ and N_PGQ smaller or enlarge MSGMNI.There’s no enough semaphore identifiers in the system. Please decrease NUSERS or enlarge SEMMNI.There’s no enough semaphore undo structures in the system. Please decrease NUSERS or enlarge SEMMNU.

If you see messages similar to those in the preceding example, you must change your kernel parameters before you will be able to start UniData.

See Administering the Recoverable File System for information on RFS configuration parameters and Administering UniData for information about config-uration parameters and system tuning.


18. Choose to Release Disk SpaceUniData prompts you to save or remove the include, lib, work, and demo directories from udtbin, because they are not needed in the udtbin directory for running UniData. If you remove these directories, you free up approximately 10 MB of disk space, but you will have to tar the UniData tape again if you need to reinstall UniData. If you do not remove these directories, you can reinstall UniData without having to tar the tape.

You now have completed the installation process. The followingdirectories are not required for running udt, you may eitherremove them for saving some disk space or keep them there forthe future use: /usr/ud72/bin/include /usr/ud72/bin/lib /usr/ud72/bin/work /usr/ud72/bin/demo Do you want to save those directories? [Yes]:

19. Installation CompleteThe installation process is now complete. If you need to authorize UniData at this time, follow the steps outlined in Chapter 8, “ Licensing UniData Products.” If you licensed UniData in step 17, you can proceed with the next step.

Install unishared components...Installed /usr/unishared/icsdk version 2.5.Installed /usr/unishared/unirpc version 10.0.0.Installed /usr/unishared/uojsdk version 1.2.Installed /usr/unishared/jdbc version 1.0.0.Updating /usr/unishared/sharedby...Done.Updating /usr/unishared/unirpc/unirpcservices...Done.

Congratulations! You have successfully installed/upgraded toUniData RDBMS 7.2. Run startud to start UniData 7.2.#


20. Check install.logThe responses to the installation prompts and any messages directed to the terminal screen are captured in the install.log located in /usr/ud72/bin. Check the install.log to ensure that no error messages appear in the log. If any error messages appear, correct the indicated problems before proceeding.

21. Set Environment VariablesBefore you can test the installation by starting UniData and invoking a UniData session, you need to define the environment variables for udthome and udtbin. The following examples show how to do this by using the default names from a basic installation.

From the Bourne or Korn shell:UDTHOME=/usr/ud71;export UDTHOMEUDTBIN=/usr/ud71/bin;export UDTBINFrom the C shell:% setenv UDTHOME /usr/ud72% setenv UDTBIN /usr/ud72/bin

If you are using XML, you must also set your library path. The following table shows the library path environment variables by platform:

Library Path Environment Variables

Platform Library Path Environment Variable

AIX LIBPATH=$LIBPATH:$UDTBIN

HP SHLIB_PATH=$SHLIB_PATH:$UDTBIN

SOLARIS LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$UDTBIN

LINUX LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$UDTBIN

TRU64 LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$UDTBIN

SCO LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$UDTBIN


22. Run makeudtIf your application links in C routines with CALLC, you need to link the udt executable by running makeudt now. For information on makeudt, see Administering UniData and Developing UniBasic Applications.

23. Start UniDataYou can now start UniData with the startud command. The following example shows the output from startud:

# ./startudUsing UDTBIN=/usr/ud72/bin

All output and error logs have been saved to ./saved_logs directory.

SMM is started.SBCS is started.CLEANUPD is started.Unirpcd is startedUniData R7.2 has been started.#

You can now run UniData. Change directories using the UNIX cd command to the demo account located in /usr/ud72/demo. Enter the full path name of the bin directory, followed by the udt command (if you have set your environment variables, the default is udtbin/udt, as in the following example). If you have already authorized device licensing, enter udtts.

# cd ../demo# udt

The following screen appears:

UniData Release 7.2 Build: (3137)(c) Copyright IBM Corporation 2008.All rights reserved.

Current UniData home is /usr/ud72/.Current working directory is /usr/ud72/demo.

Note: Before users can access UniData, you must set environment variables for all users. Consider using a .login or .profile script. You can include the full UniData paths there. You also need to make sure each user’s path includes the udtbin path. For detailed information about this, see Administering UniData.


Installing Using the install.param File on UniData for UNIXIf you do not want to answer each prompt during the installation, you can customize the install.param file located in /usr/ud71/bin, then use this file for the prompt responses. The following example displays the contents of the install.param file before any customization:

# pg install.paramCheckLang YesUdtHome /disk2/srcman/alpha/ud_PEAK_981110WorkDir /disk2/srcman/alpha/ud_PEAK_981110/workLibDir /disk2/srcman/alpha/ud_PEAK_981110/libLogDir /disk2/srcman/alpha/ud_PEAK_981110/logUnisharedDir /usr/unisharedSerial HPUX11Group unisrcStopSys YesRFSflag YesOverWrite NoBackup NoConfProduct NoSaveDir save

Use any UNIX text editor to customize the prompt responses listed in the install.param file, or create your own file with the required responses. In the following example, the default paths are used for UdtHome, WorkDir, LibDir and LogDir. Group is changed to sys:

# pg install.paramCheckLang YesStopSys YesUdtHome /usr/ud72WorkDir /usr/ud72/workLibDir /usr/ud72/libLogDir /usr/ud72/logUnisharedDir /usr/unisharedGroup sysSerial serial_numberRFSflag NoREPflag NoBackup NoConfProduct NoOverWrite YesConfirm YesSaveDir save

Next, execute the udtinstall command with the -f option.

Installing Using the install.param File on UniData for UNIX 1-17

Syntax:

udtinstall -f filename


In the following example, udtinstall is executed by using the install.param file:

# ./udtinstall -f install.paramWelcome to the UniData RDBMS.


Enter the Serial Number displayed on your "IBM Software Product

Start installing/upgrading UniData RDBMS Release 7.2.

Using UDTBIN=/usr/ud72/bin

SM has already been stopped.CLEANUPD has already been stopped.SMM is not running.SBCS has already been stopped.SMM is not running.Unirpcd has already been stopped

Unidata 7.2 has been shut down.

Changing files’ ownership and group name ......Creating/Updating /usr/ud72/include directory...

Creating/Updating /usr/ud72/ods directory...

Creating/Updating /usr/ud72/lib directory...

Creating/Updating /usr/ud72/sys directory...

Creating/Updating /usr/ud72/demo directory...

Creating/Updating /usr/ud72/work directory...

Creating/Updating /usr/ud72/objcall directory...

Checking UNIX system configuration for running UniData ...

Update VOC files in /usr/ud72/sys /usr/ud72/demo ...

You now have completed the installation process. The followingdirectories are not required for running udt, you may eitherremove them to save some disk space or keep them there forfuture use:

/usr/ud72/bin/include /usr/ud72/bin/lib /usr/ud72/bin/work

Installing Using the install.param File on UniData for UNIX 1-19

/usr/ud72/bin/demo

Install unishared components...Installed /usr/unishared/icsdk version 2.5.Installed /usr/unishared/unirpc version 10.1.0.Updating /usr/unishared/sharedby...Done.Updating /usr/unishared/unirpc/unirpcservices...Done.

Congratulations! You have successfully installed/upgraded toUniData RDBMS 7.2. Run startud to start UniData 7.2.

You should now complete steps 19 through 23 of the step-by-step installation instructions.


Troubleshooting TipsThis section describes the cause of three problems commonly encountered during the UniData installation.

Problem:

Installation completes, but UniData will not start.

Cause:

These failures are usually related to a UniData configuration parameter or a UNIX kernel parameter. Check the smm.errlog file located in udtbin. The most common adjustments are:

N_PUT

This UniData configuration parameter, which controls the size of the system buffer for RFS, has a default value of 8192. You may have to decrease it to 4096, depending on the size of shmmax * shmseg. If this result is greater than 8 MG, you will have to adjust N_PUT.

N_TMQ and N_PGQ

These UniData configuration parameters are numbers of UNIX message queues created for communication between user processes and the Recoverable File System. By default, each parameter is set to one queue for every four users. Add these to the number of message queues required by the UniData lock control process (one queue for every five users), plus ten queues for the other UniData daemons, and adjust the UNIX kernel parameter msgmni (number of message queues on your system) accordingly. If you cannot increase msgmni, temporarily reduce N_TMQ and N_PGQ until the kernel can be rebuilt.

Problem:

The smm.errlog contains a message similar to:

Exit: smm: cannot allocate semaphore for udtno xx errno xx

Exit: SMM can’t setup Control Table List

Cause:

Troubleshooting Tips 1-21

The number of semaphores available systemwide is not adequate for the number of users on your system. Increase the kernel parameter defining the number of semaphores available systemwide, normally semmns, to at least NUSERS + 10. If you cannot rebuild the kernel, you must decrease the NUSERS parameter in the udtconfig file, located in /usr/ud72/include, until the kernel can be rebuilt.

Problem:

Message “Warning: As the ‘ranlib’ command is not available for this system, UniData libraries will not be ready for rebuilding udt. The utilities makeudt and makesvr will not work” is displayed during installation.

Cause:

This occurs on an AIX system that has not had the Application Development Toolkit installed. This is not a problem unless your application requires C routines that need to be linked into UniData. This linking process (makeudt) requires other utilities from this toolkit as well. If you do not need to link C routines, ignore these messages. If you need to link C routines, install the AIX Toolkit and rerun udtinstall.

Note: If you answered the last prompt in udtinstall with exit, you need to reload your UniData tape first.

Problem:

Shared memory problems when editing large items with the Alternative Editor (AE). An example of a shared memory error is:

Error when creating a shared memory segment size=1440416), errno=22

Cause:

If you experience shared memory errors, see Administering UniData for information on shared memory configuration parameters.


Step-by-Step Installation on UniData for Windows PlatformsComplete the following steps to install UniData 7.2 products for the first time on your Windows system. If you are upgrading from a previous version of UniData for Windows Platforms, see Chapter 6, “ UniData RDBMS Upgrade Installation.”

1. Log On As an AdministratorYou must log on with Administrator privileges to install UniData. Either log on to the Administrator account on the Windows system, or log on as a member of the local Administrators group.

2. Stop Current Installed ServicesIf you are already using a Telnet service or a serial terminal support service from another vendor, and you want to install UniData’s Telnet or serial terminal support services, you must stop your existing services before you proceed with the UniData installation.

Use either the Control Panel or vendor documentation to disable your previously-installed Telnet/serial terminal support services before proceeding.

Warning: After the installation is complete, you cannot run UniData’s Telnet Service or UniData’s Serial Terminal Support Service at the same time as other Telnet or Serial terminal support services. You must stop these services whenever you wish to use the ones you previously installed.

3. Load the UniData CDPlace the UniData CD in your CD-ROM drive. Make sure you have the UniData Product Configuration sheet that is included with your media. You will need this form when you license the product after installation.

Step-by-Step Installation on UniData for Windows Platforms 1-23

4. Execute the InstallationFrom the Setup screen, double-click UniData RDBMS, as shown in the following example:

Note: If the Setup screen does not automatically display when you insert your UniData CD, double-click Install.exe in the \IBM\ud72 directory to access the screen.

Click UniData RDMS to begin in the installation process.


You will see a message that the system is building an InstallShield wizard. Next the Welcome screen appears, as shown in the following example:

Click Next to proceed with the installation.


5. Accept License AgreementThe Software License Agreement dialog box appears, as shown in the following example:

If you agree with the license agreement, click Accept. If you do not agree with the license agreement, click Decline.


6. Enter Customer InformationEnter your name, your company name, and your serial number in Customer Infor-mation dialog box, and shown in the following example:


7. Choose Destination Location for UniDataVerify the location to install UniData. The default UniData directory is \IBM\ud72, and the default unishared directory is \IBM\unishared, as shown in the following example.

If you do not want to accept the default, click Browse and choose the directory where you want to install UniData and unishared.

Click Back to return to the previous screen. Click Next to continue with the instal-lation. Click Cancel to exit the installation process without saving changes.


8. Choose Components and DirectoryThe next dialog box allows you to select any or all of the UniData components to install. This dialog box also displays information about how much disk space you need and how much disk space is available on the default target partition, as shown in the following example:

Notice the following points about the Select Components dialog box:

You may install components one at a time if you wish, repeating the instal-lation procedure for each components or group of components.As you select or clear components, the Space Required figure changes.

Select the components you want to install, and then click Next to start the installation.

Click Back to return to the previous screen. Click Cancel to exit the installation process without saving changes.


Note: Do not install the UniData Telnet Service or the UniData Serial Terminal Support Service if there is a Telnet service or serial terminal support service from another vendor currently running on your Windows system. Exit the installation, stop any such services, and restart the installation process.

8. Choose Program Folder NameNext, you will be prompted for a program folder for UniData. The default is \IBM U2\UniData RDBMS 7.2, as shown in the following example.

Enter the name of the Program Folder for UniData 7.2 if you do not want to accept the default, and then click Next to continue with the installation process.



9. Copy FilesThe installation process now copies files, creates the program group and icons, and updates the Registry. The following window appears:

Click Next to begin copying files. Click Back to return to the previous screen. Click Cancel to exit the installation process without saving changes.


10. Complete the InstallationWhen the installation is finished, a window similar to the following appears:

Click Finish to complete the installation. Click Back to return to the previous screen.


11. Restart Your Computer You must restart your computer before starting a UniData session. A dialog box similar to the following appears:

Select Yes, I want to restart my computer now, and then click OK to restart your computer. If you want to restart your computer at a later time, click No, I will restart my computer later, and then click OK.

12. Start a UniData SessionFrom the Start menu, select Programs, select IBM U2, select UniData RDBMS 7.2, and then click UDT to start a UniData session.

You are now ready to license UniData. For information about licensing UniData, see Chapter 8, “ Licensing UniData Products.”

Note: When you install UniData products, you have a thirty day trial period before you must authorize your configuration with IBM. For the UniData RDBMS, the trial period starts automatically.


13. Set Library Path Environment VariableIf you are using XML, you must also set your library path. The following table shows the library path environment variables by platform:



Windows platforms PATH=$PATH:$UDTBIN


4Chapter

UniData RDBMS Advanced Installation

Step-by-Step Installation on UniData for UNIX . . . . . . . . . 4-3Installing Using the install.param File . . . . . . . . . . . . 4-17Troubleshooting Tips . . . . . . . . . . . . . . . . . 4-21Step-by-Step Advanced Installation on UniData for Windows

Platforms . . . . . . . . . . . . . . . . . . . . 4-23

This chapter is intended for those who are installing UniData Release 7.2 on UNIX or Windows platforms. These instructions guide you through an advanced instal-lation process.


You may edit the install.param file to customize your installation, then use the customized file as part of the installation process without having to provide input to the installation prompts. If you want to use this option, proceed to “Installing Using the install.param File” on page 4-17.


Step-by-Step Installation on UniData for UNIXFollow the steps in this section for an advanced installation.

You must log on with root permissions to perform the installation.

1. Check or Create Your bin DirectoryYour current working directory must be the directory where you want the UniData executables installed. Create the directories for udthome and udtbin, then cd to the directory you have specified for udtbin. Verify your location by entering pwd. In the following example, /disk1 is created for udthome and /disk1/ud72/bin is created for udtbin:

# pwd/disk1# mkdir ud72# cd ud72# mkdir bin# cd bin# pwd/disk1/ud72/bin#



Mount the tape on your tape drive. Load the UniData software into the udtbin directory you created in step 1 with the UNIX tar command. In the example below, tape.device is the name of the tape drive you are using. For more information on the tar command, see your UNIX documentation.




Your installation media contains a tar file in compressed format. Unload the compressed tar file from diskette and then uncompress it. Then, extract the UniData files and directories from the tar file. To accomplish these tasks requires roughly twice the amount of disk space required for an ordinary UniData installation. You can complete the unload, uncompress, and extract procedures in the udtbin directory if you have enough disk space at that location. Consider performing the unload and uncompress steps in another location (such as /tmp) if the udtbin directory has less than 250 MB of space available.






Use the UNIX ls command to identify the compressed tar file. prodname varies with each individual release. For example, sco72.tar.Z is the compressed tar file for a release of UniData 7.2 for a SCO platform.






Extracting UniData Files from the tar File

Set your current working directory to the udtbin directory. Use the UNIX tar command to extract the UniData files and subdirectories. Make sure you specify the full path name of the tar file. For example, if your udtbin directory is /disk1/ud72/bin, and the tar file (named sco72.tar) is in /tmp, use the following commands:

# cd /disk1/ud72/bin# tar xvf /tmp/sco72.tar


# rm /tmp/sco72.tar

Proceed to step 3.


Execute the tar command from the udtbin directory just as if you were installing from tape. For example, suppose the device file for your CD-ROM drive is /dev/cdrom, and your bin directory path is /disk1/ud72/bin. Use the following commands:

% cd /disk1/ud72/bin% tar xvf /dev/cdrom/BIN.TAR











# udtinstall



WARNING:




If you enter ENTER to accept the default answer of “Yes”, UniData continues the installation process using the LANG group of “C”. If desired, you can change your LANG environment variable after the installation process is complete. If you answer “No” to the above prompt, UniData exits the installation process.



# cd /disk1/ud72/bin#./udtinstall





Press ENTER to accept the default of “Yes” if you want to continue with the instal-lation process. If you do not want to proceed at this time, enter “No”.

Note: You must enter “Yes”, “yes” or “YES” and “No”, “no”, or “NO” rather than “Y” or “N” for all prompts in the installation process.

4. Enter the UDTHOME DirectoryUniData prompts for the full path of the UDTHOME directory. For the advanced installation, enter the udthome directory created in step 1:

Enter the full path name of udt home directory [/usr/ud72]:/disk1/ud72




5. Enter the udtwork Directory The system displays the work directory where it will load the files to rebuild UniData based on the location of udthome you entered in step 4. If the path UniData displays is correct, press ENTER. If you want the location of your work directory in another location, enter the full path:

Enter the full path name of work directory [/disk1/ud72/work]:

6. Enter the udtlib DirectoryThis directory contains libraries for all UniData executables. UniData displays the path where it will load this directory based on the location of udthome you entered in step 4. If the path UniData displays is correct, press ENTER. If you want the location of the lib directory in another location, enter the full path:

Enter the full path name of lib directory [/disk1/ud72/lib]:

7. Enter the Location of the log FilesThis directory contains the location where UniData will build the log files for the Recoverable File System (RFS) based on the location of udthome you entered in step 4. If the path UniData displays is correct, press ENTER. If you want the log files in another directory, enter the full path. In the following example, a different path is entered for the log files. You do not have to create the log file directory:

Enter the full path name of log directory [/disk1/ud72/log]:/home/logs

8. Enter the Location of the unishared DirectoryThe unishared directory contains files necessary for the unircpd daemon. Press ENTER to accept the default location of udthome/unishared, or enter an alternate path:

Enter the full path name of unishared directory [/disk1/unishared]:


9. Enter a Group NameUniData uses the group name associated with the root login name. If the group name displayed is correct, press ENTER. If the default is not correct, enter the correct group name:


10. Enter the Serial Number Enter the serial number found on your IBM Product Configuration sheet in response to the following prompt. This information is not required as part of the installation.


11. Install the Recoverable File SystemIf you do not want to install the Recoverable File System (RFS) at this time, press ENTER to accept the default of “No.” You must purchase the RFS product separately. If you are not sure whether you have purchased RFS, check the Product Configu-ration Sheet included with your UniData tape. You can install RFS at a later time without rerunning the installation process. To enable RFS post installation, see Administering the Recoverable File System.

If you choose to install RFS at this time, enter “Yes” or “yes.” The system creates a default log configuration table, creates the log files, and turns on RFS:






13. Back Up Existing DirectoriesThis option does not apply to the advanced installation since it backs up existing UniData 6.1 directories. Press ENTER to accept the default of “No”.


14. Decide When to Authorize UniDataUniData prompts you to indicate whether you want to configure the product at the end of the installation process. If you enter “Yes” at this prompt, UniData automati-cally runs the confprod utility as part of the installation. If you do not want to configure the product at the end of the installation process, press ENTER to accept the default. UniData will run for 60 days after installation without requiring authorization.






CheckLang Yes SaveDir save OverWrite Yes Confirm No StopSys Yes WorkDir /disk1/ud72/work LibDir /disk1/ud72/lib LogDir /disk1/ud72/log UnisharedDir /usr/unishared Group sys Serial serial_number RFSflag No


16. Proceed with the Installation ProcessThe installation process first makes sure that the version of UniData identified by UDTBIN is not running. The installation process then changes the file’s ownership to root, and the group name to the name you specified.


Next, the installation process tests the system configuration by running the systest utility, then creates the include, ods, lib, sys, demo, work, unishared, and objcall directories.

Start installing/upgrading UniData RDBMS Release 7.2. Using UDTBIN=/disk1/ud72/bin SM stopped successfully.CLEANUPD stopped successfully.SBCS stopped successfully.SMM stopped successfully.Unirpcd stopped successfully.

Unidata R7.2 has been shut down.

Changing files' ownership and group name ... Testing system configuration ......Creating/Updating /disk1/ud72/include directory...

Creating/Updating /disk1/ud72/ods directory...

Creating/Updating /disk1/ud72/lib directory...

Creating/Updating /disk1/ud72/sys directory...

Creating/Updating /disk1/ud72/demo directory...

Creating/Updating /disk1/ud72/work directory...

Creating/Updating /disk1/ud72/objcall directory... Checking UNIX system configuration for running UniData ...

17. Authorize UniDataIf you answered “Yes” to the “Config product at the end of installation” prompt, UniData automatically runs the confprod utility at this time. Refer to Chapter 8, “Licensing UniData Products,” for information about licensing UniData. If you answered “No” the “Config product at the end of installation” prompt, proceed to the next step. You have 60 calendar days from the date you install UniData to license the product.


If you authorize UniData as part of the installation process, UniData executes the systest command again to determine configuration parameters based on the number of authorized users. If your kernel parameters are not adequate to support the number of authorized users, UniData displays messages similar to the following:

You may not be able to run full number of users sessions (1250)as configured due to the current semmnu setting (100) inyour Unix system. You need to increase semmnu to 3750 andrebuild your Unix kernel.The number of global tables(SHM_GNTBLS) should not be greater than SHMMNI.No enough message queue identifiers. Please make N_TMQ and N_PGQ smaller or enlarge MSGMNI.There's no enough semaphore identifiers in the system. Please decrease NUSERS or enlarge SEMMNI.There's no enough semaphore undo structures in the system. Please decrease NUSERS or enlarge SEMMNU.



18. Choose to Release Disk SpaceThe installation is now complete. UniData prompts you to save or remove the include, lib, work, and demo directories from udtbin, because they are not needed in the udtbin directory for running UniData. If you remove these directories, you free up approximately 10 MB of disk space, but you will have to tar the UniData tape again if you need to reinstall UniData. If you do not remove these directories, you can reinstall UniData without having to tar the tape.

You now have completed the installation process. The followingdirectories are not required for running udt, you may eitherremove them for saving some disk space or keep them there forthe future use: /disk1/ud72/bin/include /disk1/ud72/bin/lib /disk1/ud72/bin/work /disk1/ud72/bin/demo Do you want to save those directories? [Yes]:


19. Installation CompleteThe installation process is now complete. If you need to authorize UniData at this time, follow the steps outlined in Chapter 8, “Licensing UniData Products.” If you licensed UniData in Step 17, you can proceed with the next step.




21. Set Environment VariablesBefore you can test the installation by starting UniData and invoking a UniData session, you need to define the environment variables for udthome and udtbin. The following examples show how to do this by using the paths previously provided for udthome and udtbin:

From the Bourne or Korn shell:UDTHOME=/disk1/ud72;export UDTHOMEUDTBIN=/disk1/ud72/bin;export UDTBINFrom the C shell:% setenv UDTHOME /disk1/ud71% setenv UDTBIN /disk1/ud71/bin











22. Run makeudtIf your application links in C routines with CALLC, you need to relink the new udt by running makeudt now. For information on makeudt, see Administering UniData and Developing UniBasic Applications.


# ./startudUsing UDTBIN=/disk1/ud72/bin


SMM is started.SBCS is started.CLEANUPD is started.Unirpcd is started

#


You can now run UniData. Change directories using the UNIX cd command to the udthome/demo account. Enter the full path name of the bin directory, followed by the udt command (if you have set your environment variables, the default is udt, as shown in the following example). If you are using device licensing, enter udtts.

# cd ../demo# udt


UniData Release 7.2 Build: (3727)(c) Copyright IBM Corporation 2007, 2008.All rights reserved.

Current UniData home is /disk1/ud72/.Current working directory is /disk1/ud72/demo.



Installing Using the install.param FileIf you do not want to answer each prompt during the installation, you can customize the install.param file located in udthome/bin, then use this file for the prompt responses. The following example displays the contents of the install.param file before any customization:

# pg install.paramCheckLang YesUdtHome /disk2/srcman/alpha/ud_PEAK_981110WorkDir /disk2/srcman/alpha/ud_PEAK_981110/workLibDir /disk2/srcman/alpha/ud_PEAK_981110/libLogDir /disk2/srcman/alpha/ud_PEAK_981110/logSerial HPUX11Group unisrcStopSys YesRFSflag YesOverWrite NoBackup NoConfProduct NoSaveDir save

Use any UNIX text editor to customize the prompt responses listed in the install.param file, or create your own file with the required responses. In the following example, the paths for UdtHome, WorkDir, LibDir and LogDir are customized using /disk1/ud61 as udthome. Group is changed to sys:

# pg install.paramCheckLang YesStopSys YesUdtHome /disk1/ud72WorkDir /disk1/ud72/workLibDir /disk1/ud72/libLogDir /disk1/ud72/logUnisharedDir /usr/unisharedGroup sysSerial serial_numberRFSflag NoREPflag NoBackup NoConfProduct NoOverWrite YesConfirm YesSaveDir save


Installing Using the install.param File 4-17

Syntax:








Using UDTBIN=/disk1/72/bin









Creating/Updating /disk1/ud72/objcall directory...




/disk1/ud72/bin/include /disk1/ud72/bin/lib /disk1/ud72/bin/work


/disk1/ud72/bin/demo






Problem:

Installation completes, but UniData will not start. In this case, you will not see the normal message at the end of the installation.

Cause:


N_PUT


N_TMQ and N_PGQ

These UniData configuration parameters are numbers of UNIX message queues created for communication between user processes and the Recoverable File System. By default, each parameter is set to one queue for every four users. Add these to the ten queues for the other UniData daemons, and adjust the UNIX kernel parameter msgmni (number of message queues on your system) accordingly. If you can’t increase msgmni, temporarily reduce N_TMQ and N_PGQ until the kernel can be rebuilt.

Problem:





Cause:


Problem: Message “Warning: As the ‘ranlib’ command is not available for this system, UniData libraries will not be ready for rebuilding udt. The utilities makeudt and makesvr will not work” is displayed during installation.

Cause:

This occurs on an AIX system that has not had the Application Development Toolkit installed. This is not a problem unless your application requires C routines that need to be linked into UniData. This linking process (makeudt) requires other utilities from this toolkit as well. If you don’t need to link C routines, ignore these messages. If you need to link C routines, install the AIX Toolkit and rerun udtinstall.

Note: If you answered the last prompt in udtinstall with exit, you will need to reload your UniData tape first.

Problem:



Cause:

If you experience shared memory errors, see Administering UniData.


Step-by-Step Advanced Installation on UniData for Windows PlatformsComplete the following steps to install UniData 7.2 products for the first time on your Windows system. If you are upgrading from a previous version of UniData for Windows Platforms, see Chapter 6, “UniData RDBMS Upgrade Installation.”

1. Log On As an AdministratorYou must log on with Administrator privileges to install UniData. Either log in to the Administrator account on the Windows system, or log on as a member of the local Administrators group.





Step-by-Step Advanced Installation on UniData for Windows Platforms 4-23

4. Execute the InstallationFrom the Setup screen, double-click UniData RDBMS, as shown in the following example:



You will see a message that the system is building an InstallShield wizard. Next the Welcome screen displays, as shown in the following example:






6. Choose Destination Location for UniDataVerify the location to install UniData and the unishared directory. The default direc-tories are \IBM\ud72, and \IBM\unishared, as shown in the following example.

If you do not want to accept the default, click Browse and choose the directory where you want to install UniData.










8. Choose Program Folder NameNext, you will be prompted for the folder name for UniData. The default is IBM U2\UniData RDBMS 7.2, as shown in the following example.










10. Restart Your Computer You must restart your computer before starting a UniData session. A dialog box similar to the following example appears:

Select Yes, I want to restart my computer now, and then click OK to restart your machine. If you want to restart your computer at a later time, click No, I will restart my computer later, and then click OK.




Windows platform PATH=$PATH:$UDTBIN



You are now ready to license UniData. For information about licensing UniData, see Chapter 8, “Licensing UniData Products.”



5Chapter

UniData RDBMS Concurrent Installation

Considerations for Concurrent Installations . . . . . . . . . . 5-3 Static Hashed File Considerations . . . . . . . . . . . . 5-3 Dynamic File Considerations . . . . . . . . . . . . . 5-3 Index File Considerations . . . . . . . . . . . . . . 5-4 Recoverable File Considerations . . . . . . . . . . . . 5-4Step-by-Step Installation on UniData for UNIX . . . . . . . . . 5-5Installing Using the install.param File . . . . . . . . . . . . 5-20Troubleshooting Tips . . . . . . . . . . . . . . . . . 5-24Step-by-Step Installation on UniData for Windows Platforms . . . . . 5-26

This chapter is intended for those who are installing UniData Release 7.2 on UNIX or Windows platforms. These instructions guide you through a concurrent instal-lation process. Use a concurrent installation when you have a previous version of UniData running on the same machine where you are installing UniData Release 7.2, and you want to run the two versions concurrently.

Warning: Users running different versions of UniData should not try to update the same files at the same time with both UniData versions. If you want to test your appli-cation by installing Release 7.2 concurrently, set up a separate demo database for your testing. Do not try to update live files with two versions of UniData at the same time.

5-2

Considerations for Concurrent InstallationsThere are limitations for concurrent execution of UniData 7.2 and previous versions of UniData. These limitations are discussed in this section.

Static Hashed File ConsiderationsEach UniData version uses its own locking mechanism, and the versions do not communicate. If two versions of UniData access the same files, you could have database integrity problems because a user can lock a record in one version that was already locked by another version. This should not cause physical file corruption problems.

Dynamic File ConsiderationsAccessing the same dynamic files from two versions of UniData is not supported for the following reasons:

It is not possible to access a dynamic file created in UniData 7.2 with the KEYDATA option from releases of UniData prior to UniData 4.1. UniData displays a message “hashtype 96 not supported yet. Open file error.” If you need to access the file, you must use the memresize command to resize the file with the KEYONLY option in UniData 7.2. You can then access it from earlier versions.Each lock mechanism uses a “scan lock” to prevent dynamic files from splitting and merging during certain operations. If you access the same file from two versions of UniData, a user process could trigger a split when they should not be able to. This could result in physical file corruption.Each version’s shared memory manager (smm) keeps its own current modulo table for dynamic files. With two smm processes, a user could write a record to the wrong group because the modulo in its smm is wrong. This results in file corruption.


Index File ConsiderationsBeginning with UniData 4.1, index files are decompressed. If you built alternate key indexes for a file with UniData 4.1 and try to access it from a previous release of UniData, UniData displays the message “hashtype 96 not supported yet. Open file error.” If you need to access the file in a previous release of UniData, you must delete the index using the DELETE.INDEX filename ALL command in UniData 7.2, then rebuild the index using the earlier version.

Recoverable File ConsiderationsIf you want to run UniData 7.2 with RFS concurrently with a previous version of with RFS, consider locating your log files and archive files on different devices, or at least in different file systems. The default log file names at UniData 7.2 are the same as they were in previous versions, so you are in danger of overwriting the log from a previous version if you use the same log directory at UniData 7.2. Locating the log files and archive files separately for UniData 7.2 is also desirable for distributing I/O load across your file systems.

Considerations for Concurrent Installations 5-4

Step-by-Step Installation on UniData for UNIXAnswers to the prompts in the installation script are kept in the install.param file located in udtbin. This file contains responses that are most likely inappropriate for your installation after it is loaded from tape. After you complete the installation process, your responses to the installation prompts are written to this file.

You may edit the install.param file to customize your installation, then use the customized file as part of the installation process without having to provide input to the installation prompts. If you want to use this option, proceed to “Installing Using the install.param File” later in this chapter.

Follow the steps in this section for a concurrent installation.

You must log in with root permissions to perform the installation.

1. Check or Create Your bin DirectoryYour current working directory must be the directory where you want the UniData executables installed. Create the directories for udthome and udtbin, then cd to the directory you have specified for udtbin. Verify your location by entering pwd. In the following example, the udthome and udtbin directories are created:

# pwd/disk1# mkdir ud72# cd ud72# mkdir bin# cd bin# pwd/disk1/ud72/bin#




Mount the tape on your tape drive. Load the UniData software into the udtbin directory you created in step 1 with the UNIX tar command. In the example below, tape.device is the name of the tape drive you are using. For more information on the tar command, see your UNIX documentation.



Your installation media contains a tar file in compressed format. Unload the compressed tar file from diskette and then uncompress it. Then, extract the UniData files and directories from the tar file. To accomplish these tasks, your system requires roughly twice the amount of disk space required for an ordinary UniData installation. You can complete the unload, uncompress, and extract procedures in the udtbin directory if you have enough disk space at that location. Consider performing the unload and uncompress steps in another location (such as /tmp) if the udtbin directory has less than 250 MB of space available.













Set your current working directory to the udtbin directory. Use the UNIX tar command to extract the UniData files and subdirectories. Make sure you specify the full path name of the tar file. For example, if your udtbin directory is /disk1/ud72/bin, and the tar file (named sco72.tar) is in /tmp, use the following commands:



# rm /tmp/sco72.tar

Proceed to step 3.

Installing from CD-ROMExecute the tar command from the udtbin directory just as if you were installing from tape. For example, suppose the device file for your CD-ROM drive is /dev/cdrom, and your bin directory path is /disk1/ud72/bin. Use the following commands:













# udtinstall



WARNING:



If you enter ENTER to accept the default answer of “Yes”, UniData continues the installation process using the LANG group of “C”. If desired, you can change your LANG environment variable after the installation process is complete.If you answer “No” to the above prompt, UniData exits the installation process.



# cd $UDTBIN#./udtinstall





Press ENTER to accept the default of “Yes” if you want to continue with the instal-lation process. If you do not want to proceed at this time, enter “No”.

Note: You must enter “Yes”, “yes”, or “YES” and “No”, “no”, or “NO” rather than “Y” or “N” for all prompts in the installation process.


4. Enter the UDTHOME DirectoryUniData prompts for the full path of the UDTHOME directory. For the advanced installation, enter the udthome directory created in step 1:

Enter the full path name of udt home directory [/usr/ud72]:/disk1/ud72



5. Enter the udtwork Directory The system displays the work directory where it will load the files to rebuild UniData based on the location of udthome you entered in step 4. If the path UniData displays is correct, press ENTER. If you want the location of your work directory in another location, enter the full path:


6. Enter the udtlib DirectoryThis directory contains libraries for all UniData executables. UniData displays the path where it will load this directory based on the location of udthome you entered in step 4. If the path UniData displays is correct, press ENTER. If you want the location of the lib directory in another location, enter the full path:



7.Enter the Location of the log FilesThis directory contains the location where UniData will build the log files for the Recoverable File System (RFS) based on the location of udthome you entered in step 4. If the path UniData displays in correct, press ENTER. If you want the log files in another directory, enter the full path. In the following example, a different path is entered for the log files. You do not have to create the log file directory:

Enter the full path name of log directory [/disk1/ud72/log]:/home/logs

Warning: Make sure the path of the log directory is different that the log directory for the concurrent version of UniData.



9. Enter a Group NameUniData uses the group name associated with the root login name as the default. If the group name displayed is correct, press ENTER. If the default is not correct, enter the correct group name:


10. Enter the Serial NumberEnter the serial number found on your IBM Software Configuration sheet in response to the following prompt. This information is not required as part of the installation.

Enter the Serial Number displayed on your "IBM Software Product Configuration" sheet: [serial_number]:


11. Install the Recoverable File SystemIf you do not want to install the Recoverable File System (RFS) at this time, press ENTER to accept the default of “No.” You must purchase the RFS product separately. If you are not sure whether or not you have purchased RFS, check the Product Configuration Sheet included with your UniData tape. You can install RFS at a later time without rerunning the installation process. To enable RFS post installation, see Administering the Recoverable File System.

If you choose to install RFS at this time, enter “Yes.” The installation process creates a default log configuration table, creates the log files, and turns on RFS:





13. Back Up Existing DirectoriesThis option does not apply to a concurrent installation since it backs up certain UniData 7.2 directories if they already exist. Press ENTER to accept the default of “No”.



14. Decide When to Authorize UniDataUniData prompts you to indicate whether you want to configure the product at the end of the installation process or not. If you enter “Yes” or “yes” at this prompt, UniData automatically runs the confprod utility as part of the installation. If you do not want to configure the product at the end of the installation process, press ENTER to accept the default of “No.” UniData will run for 30 days after installation without requiring authorization.





CheckLang Yes SaveDir save OverWrite Yes Confirm No StopSys Yes WorkDir /disk1/ud72/work LibDir /disk1/ud72/lib LogDir /disk1/ud72/log UnisharedDir /usr/unishared Group sys Serial serial_number RFSflag No



16. Proceed with the Installation ProcessThe installation process first makes sure that the version of UniData identified by UDTBIN is not running. If it is, this version of UniData is stopped with force. The installation process the changes the file’s ownership to root, and the group name to the name you specified.

Next, the installation process tests the system configuration by running the systest utility, then creates the include, ods, lib, sys, demo, work, unishared, and objcall directories.

Using UDTBIN=/disk1/ud72/bin SM stopped successfully.CLEANUPD stopped successfully.SBCS stopped successfully.SMM stopped successfully.Unirpcd stopped successfully.








Creating/Updating /disk1/ud72/objcall directory... Checking UNIX system configuration for running UniData ...


17. Authorize UniDataIf you answered “Yes” to the “Config product at the end of installation” prompt, UniData automatically runs the confprod utility at this time. See Chapter 8, “ Licensing UniData Products,” for information about licensing UniData. If you answered “No” at the “Config product at the end of installation” prompt, proceed to the next step. You have 60 calendar days from the date you install UniData to license the product.

If you authorize UniData as part of the installation process, UniData executes the systest command again to determine configuration parameters based on the number of authorized users. If your kernel parameters are not adequate to support the number of authorized users, UniData displays messages similar to the following:

You may not be able to run full number of users sessions (1250)as configured due to the current semmnu setting (100) inyour Unix system. You need to increase semmnu to 3750 andrebuild your Unix kernel.The number of global tables(SHM_GNTBLS) should not be greater than SHMMNI.No enough message queue identifiers. Please make N_TMQ and N_PGQ smaller or enlarge MSGMNI.There's no enough semaphore identifiers in the system. Please decrease NUSERS or enlarge SEMMNI.There's no enough semaphore undo structures in the system. Please decrease NUSERS or enlarge SEMMNU.




18. Choose to Release Disk SpaceThe installation is now complete. UniData prompts you to save or remove the include, lib, work, and demo directories from udtbin, because they are not needed in the udtbin directory for running UniData. If you remove these directories, you free up approximately 10 MB of disk space, but you will have to tar the UniData tape again if you need to reinstall UniData. If you do not remove these directories, you can reinstall UniData without having to tar the tape.







21. Set Environment VariablesBefore you can test the installation by starting UniData and invoking a UniData session, you need to define the environment variables for udthome and udtbin. The following examples show how to do this, by using the default names from a basic installation.












22. Run makeudtIf your application links in C routines with CALLC, you need to relink the new udt by running makeudt now. For information on makeudt, refer to the Administering UniData and Developing UniBasic Applications manuals.


# ./startudUsing UDTBIN=/disk1/ud72/bin



#

You can now run UniData. Change directories using the UNIX cd command to the udthome/demo account. Enter the full path name of the bin directory, followed by the udt command (if you have set your environment variables, the default is udt, as shown in the following example).

# cd ../demo# udt






24. Move Globally Cataloged ProgramsIf you want UniData 7.2 to access globally cataloged programs from a previous release of UniData, you can copy the /sys/CTLG and /sys/CTLGTB directories from a previous release to UniData 7.2.

To copy the CTLG and CTLGTB directories from a previous release of UniData, change to the udthome/sys directory from the previous release of UniData, as shown in the following example:

# cd /disk1/ud71/sys# pwd/disk1/ud71/sys

Next, copy the CTLG directory and the CTLGTB file to UniData 7.2:

# cp -r CTLG /disk1/ud72/sys# cp -r CTLGTB /disk1/ud72/sys

The UniData-supplied programs must be globally cataloged. To accomplish this, start a UniData session in the udthome/sys directory and execute the INSTALLUDT command, as shown in the following example:

# cd /disk1/ud72/sys# udtUniData Release 7.2 Build: (3727)(c) Copyright IBM Corporation 2007, 2008.All rights reserved.

Current UniData home is /disk1/ud72/.Current working directory is /disk1/ud72/sys.

:INSTALLUDT


Installing Using the install.param FileIf you do not want to answer each prompt during the installation, you can customize the install.param file located in udthome/bin, then use this file for the prompt responses. The following example displays the contents of the install.param file before any customization:

# pg install.paramCheckLang YesUdtHome /disk2/srcman/alpha/ud_PEAK_981110WorkDir /disk2/srcman/alpha/ud_PEAK_981110/workLibDir /disk2/srcman/alpha/ud_PEAK_981110/libLogDir /disk2/srcman/alpha/ud_PEAK_981110/logSerial HPUX11Group unisrcStopSys YesRFSflag YesOverWrite NoBackup NoConfProduct NoSaveDir save

Use any UNIX text editor to customize the prompt responses listed in the install.param file, or create your own file with the required responses. In the following example, the paths for UdtHome, WorkDir, LibDir, and LogDir are customized using /disk1/ud72 as udthome. Group is changed to sys:

# pg install.paramCheckLang YesStopSys YesUdtHome /disk1/ud72WorkDir /disk1/ud72/workLibDir /disk1/ud72/libLogDir /disk1/ud72/logUnisharedDir /disk1/unisharedGroup sysSerial serial_numberRFSflag NoREPflag NoBackup NoConfProduct NoOverWrite YesConfirm YesSaveDir save



Syntax:








Using UDTBIN=/disk1/ud72/bin





















Problem:

Installation completes, but UniData will not start. In this case, you won’t see the normal message at the end of the installation.

Cause:


N_PUT


N_TMQ and N_PGQ


Problem:





Cause:


Problem: Message “Warning: As the ‘ranlib’ command is not available for this system, UniData libraries will not be ready for rebuilding udt. The utilities makeudt and makesvr will not work” is displayed during installation.

Cause:



Problem:

Shared memory problems when editing large items with Alternative Editor (AE). An example of a shared memory error is:


Cause:



Step-by-Step Installation on UniData for Windows PlatformsComplete the following steps to install UniData 7.2 products for the first time on your Windows system. If you are upgrading from a previous version of UniData for Windows Platforms, see Chapter 6, “ UniData RDBMS Upgrade Installation.”

1. Log In As an AdministratorYou must log on with Administrator privileges to install UniData. Either log on to the Administrator account on the Windows system, or log on as a member of the local Administrators group.






4. Execute the InstallationFrom the Setup screen, double-click UniData, as shown in the following example:



You will see a message that the system is building an InstallShield wizard. Next the Welcome screen displays, as shown in the following example:






6. Choose Destination Location for UniDataVerify the location to install UniData and the unishared directory. The default direc-tories are \IBM\ud72 and \IBM\unishared, as shown in the following example.

If you do not want to accept the default, click Browse and choose the directory where you want to install UniData.










8. Choose Program Folder NameNext, you will be prompted for the program folder for UniData. The default is IBM\UniData RDBMS 7.2, as shown in the following example.










11. Restart Your Computer You must restart your computer before starting a UniData session. A dialog box similar to the following appears:

Select Yes, I want to restart my computer now, and then click OK to restart your machine. If you want to restart your computer at a later time, click No, I will restart my computer later, and then click OK.










6Chapter

UniData RDBMS Upgrade Installation

Step-by-Step Installation on UniData for UNIX . . . . . . . . . 6-3Updating Multiple UDTHOME Accounts on UniData for UNIX. . . . 6-20Installing Using the install.param File . . . . . . . . . . . . 6-21Troubleshooting Tips . . . . . . . . . . . . . . . . . 6-25Step-by-Step Installation on UniData for Windows Platforms . . . . . 6-27

This chapter is intended for those who are upgrading to UniData Release 7.2 on UNIX or Windows platforms.


You may edit the install.param file to customize your installation, then use the customized file as part of the installation process without having to provide input to the installation prompts. If you want to use this option, proceed to “Installing Using the install.param File” on page 21.

6-2

Step-by-Step Installation on UniData for UNIXFollow the steps in this section for an upgrade installation.

You must log in with root permissions to perform the installation.

1. Save Your make FilesIn UniData, you can link functions written in the C language to UniBasic programs. You can also use CallBasic to access UniData from a C application. UniData uses a group of files in the udtwork directory for these capabilities. The files that are important are: base.mk, callbas.mk, cfuncdef, and, if you are upgrading from Release 3.3.2 or later, cfundef_user.

Release 7.2 provides new base.mk, cfuncdef, and callbas.mk files in the udtwork directory. Additionally, some of the libraries from previous releases of UniData have been renamed. The upgrade installation process installs these new files and libraries, overwriting the files that already exist. Before you upgrade, make backup copies of these three files. If you are using CALLC or CallBasic, you will need to relink your application, using the new make files, after the upgrade process is complete.

Note: If you are upgrading from Release 3.3.2 or later and made your modifications to the cfuncdef_user file, you do not need to make any changes to the cfuncdef file. If you made modifications to the cfuncdef file in the old version of UniData, these changes should be saved to the cfuncdef_user file in the udthome/work directory so you will not have to make the same changes with each upgrade of UniData. See Administering UniData for information about make files and cfuncdef_user.


2, Check Environment VariablesWhen you upgrade to UniData 7.2, you can use the same directories as your old version of UniData, or you can create a new udtbin directory wherever you choose. If you create a new udtbin directory, make sure you change the UDTBIN environment variable to the new udtbin, and make sure that the UDTHOME environment variable is set to the old udthome. To check the environment variables, use the UNIX printenv command, as shown in the following example:

# printenv_=/usr/bin/printenvMANPATH=/usr/share/man/%L:/usr/share/man:/usr/contrib/man/%L:/usr/contrib/man:/usr/local/man/%L:/usr/local/man:/opt/upgrade/share/man/%L:/opt/upgrade/share/man:/usr/dt/share/man:/opt/pd/share/man/%L:/opt/pd/share/man:/opt/ignite/share/man/%L:/opt/ignite/share/manPATH=/disk1/ud72/bin:/usr/bin:/usr/sbin:/sbin...UDTHOME=/disk1/ud71SHELL=/bin/cshUDTBIN=/disk1/ud72/binTERM=vt100PWD=/disk1/ud72/demoTZ=MST7MDT#

If the UDTHOME and UDTBIN environment variables are not set or are set incor-rectly, use the following examples to set them to your existing version of UniData. These examples use /disk1/ud71 as the location of UDTHOME and /disk1/ud72/bin as the location of UDTBIN. Substitute your paths for udthome and udtbin.












3. Change DirectoriesYour current working directory must be the udtbin directory you defined in step 2. Change to this directory and execute the pwd command to check your location.

# cd $UDTBIN# pwd/disk1/ud72/bin#

4. Check for Existing UsersAll current users must log off UniData before you begin the upgrade installation process. Enter the listuser command for your existing version of UniData. If there are users in UniData, have them log off now. If listuser does not list any UniData users, you can proceed with the upgrade installation.

In the following example, no users are logged on, and the installation can safely proceed:

# listuserLicensed/Effective # of Users Udt Sql Total

32 / 32 0 0 0

UDTNO USRNBR UID USRNAME USRTYPE TTY TIME DATE#


5. Stop UniDataStop the existing UniData daemons with the stopud command, then verify that all daemons have been stopped by using the showud command. Be sure to use stopud even if your system seems to be down to make certain all processes and ipc structures are cleaned up. Do not run UniData during the upgrade process; doing so could corrupt your UniData software.

In the following example, stopud is executed followed by showud to verify that all daemons have stopped:

# ./stopudUsing UDTBIN=/disk1/ud71/bin

SM has already been stopped.CLEANUPD stopped successfully.SBCS stopped successfully.SMM stopped successfully.


# ./showud UID PID TIME COMMAND#



Mount the tape on your tape drive. Load the UniData software into the udtbin directory with the UNIX tar command. In the example below, tape.device is the name of the tape drive you are using. For more information on the tar command, see your UNIX documentation.




Your installation media contains a tar file in compressed format. Unload the compressed tar file from disk and uncompress it. Then, extract the UniData files and directories from the tar file. To accomplish these tasks requires roughly twice the amount of disk space required for an ordinary UniData installation. You can complete the unload, uncompress, and extract procedures in the udtbin directory if you have enough disk space at that location. Consider performing the unload and uncompress steps in another location (such as /tmp) if the udtbin directory has less than 250 MB of space available.













Set your current working directory to udtbin. Use the UNIX tar command to extract the UniData files and subdirectories. Make sure you specify the full path name of the tar file. For example, if your udtbin directory is /disk1/ud72/bin, and the tar file (named sco72.tar) is in /tmp, use the following commands:



# rm /tmp/sco72.tar

Proceed to step 3.




7. Enter ./updatesysEnter ./updatesys at the system prompt. This begins the upgrade process.

International Upgrade

The UNIX LANG environment variable affects the behavior of UniData. Before you upgrade UniData, you should be aware of the consequences of using a LANG setting other than “C.” If you use a LANG setting other than “C,” note that certain UniData commands may cause unpredictable results, such as the UniBasic UPCASE and DOWNCASE commands, and the MCU and MCL conversion codes.

If you are upgrading UniData in an environment that does not support ASCII characters 192 and 250 through 255 as internal markers, read UniData Interna-tional before proceeding with the installation.






During the upgrade process, UniData changes the LANG environment variable to “C” for upgrade processing and displays the following message:

# updatesys



WARNING:




If you press ENTER to accept the default answer of “Yes”, UniData continues the upgrade process using the LANG group of “C.” If desired, you can change your LANG environment variable after the upgrade is complete. If you answer “No” to the above prompt, UniData exits the upgrade process.

NonInternational Upgrade

If you are executing a default upgrade, the following screen appears:

# ./updatesys





Press ENTER to accept the default of “Yes” if you want to continue with the upgrade process. If you do not want to proceed at this time, enter “No”.

Note: You must enter “Yes”, “yes”, or “YES” and “No”, “no”, or “NO” rather than “Y” or “N” for all prompts in the installation process.

8. Enter the udtwork Directory The system displays the default work directory where it will load the files to rebuild UniData. The path UniData displays is based on the value of udthome. Press ENTER to accept the default, or enter another path for the work directory:


9. Enter the udtlib DirectoryThis directory contains libraries for all UniData executables. The path UniData displays is based on the value of udthome. Press ENTER to accept the default or enter another path for the lib directory:



10. Enter the Location of the log FilesThis directory contains the location where UniData will build the log files for the Recoverable File System. The path UniData displays is based on the value of udthome. Press ENTER to accept the default, or enter another directory path for the log files:

Enter the full path name of log directory [/disk1/ud71/log]:



12. Enter a Group NameUniData uses the group name associated with the root login as the default. If the group name displayed is correct, press ENTER. If the default is not correct, enter the correct group name:


13. Enter the Serial NumberEnter the serial number found on your IBM Product Configuration sheet in response to the following prompt. This information is not required as part of the installation.

Enter the Serial Number displayed on your "IBM Software Product Configuration" sheet: [serial_number]








16. Back Up Existing DirectoriesIf you answer “Yes” to this prompt, the /usr/ud71/include, udthome/work and udthome/log directories are backed up in a directory called backup in udtbin. If you want to back up these directories, enter “Yes”. If you do not want to back up these directories, press ENTER to accept the default of “No”.



17. Decide When to Authorize UniDataUniData prompts whether you want to configure the product at the end of the instal-lation process or not. If you enter “Yes” at this prompt, UniData automatically runs the confprod utility as part of the installation. If you do not want to configure the product at the end of the installation process, press ENTER to accept the default. UniData will run for 60 days after installation without requiring authorization.


Warning: When licensing UniData, you must be using a terminal supported by vvtermcap. vvtermcap is a special UniData termcap-like file located in the udtbin directory. UniData supports the following terminal types: ANSI, DEC VT100, DEC VT220, VT52 and WYSE 50. If you are installing UniData from a different type of terminal, do not configure the product at the end of the installation process.

18. Enter Old Version Number of UniDataIn order to set the proper language group, UniData prompts for the previous version of UniData from which you are upgrading. Valid responses are 16, 23, 31, 33, 40, or 41, 50, 51, 52, 60, 61, or 71.

Enter the UniData version to be upgraded? [71]: 71




CheckLang No OverWrite Yes Confirm Yes SaveDir save StopSys Yes WorkDir /disk1/ud71/work LibDir /disk1/ud71/lib LogDir /disk1/ud71/log UnisharedDir /usr/unishared Group sys Serial serial_number RFSflag Yes

REPflagNo Backup Yes ConfProduct No PreviousVer 71 Are those values correct? [Yes]:

20. Proceed with the Installation ProcessThe installation process first makes sure that the version of UniData identified by UDTBIN is not running. In an upgrade installation, UniData will stop the version of UniData identified by udtbin.The installation process then changes the file’s ownership to root, and the group name to the name you specified.


Next, the installation process tests the system configuration by running the systest utility, then updates the include, ods, lib, sys, demo, work, sybase, and objcall directories.

Start installing/upgrading UniData RDBMS Release 7.1.Using UDTBIN=/disk1/ud72/bin SM stopped successfully.CLEANUPD stopped successfully.SBCS stopped successfully.SMM stopped successfully.
















22. Choose to Release Disk SpaceThe installation is now complete. UniData prompts you to save or remove the include, lib, work, and demo directories from udtbin, because they are not needed in the udtbin directory for running UniData. If you remove these directories, you free up approximately 10MB of disk space, but you will have to tar the UniData tape again if you need to reinstall UniData. If you do not remove these directories, you can reinstall UniData without having to tar the tape.






24. Check Environment VariablesBefore you can test the installation by starting UniData and invoking a UniData session, you need to ensure that the environment variables for udthome and udtbin are correct. To check your environment variables, use the UNIX printenv command. Since the environment variables were set in step 2, they should still be correct.




# ./startud Using UDTBIN=/disk1/ud72/bin All output and error logs have been saved to ./saved_logs directory.


#

You can now run UniData. Change directories using the UNIX cd command to the demo account located in udthome/demo. Enter the full path of the bin directory, followed by the udt command (if you have set your environment variables, the default is udt, as shown in the following example). If you are using device licensing, enter udtts to start a UniData session.

# cd ../demo# udt




Before users can access UniData, you must set environment variables for all users. Consider using a .login or .profile script. You can include the full UniData paths there. You will also need to make sure each user’s path includes the udtbin path. For detailed information about this, see the Administering UniData manual.

27. Run updatevocRun the updatevoc command to update the VOC files in your UniData accounts with new or changed commands for Release 7.2.


Syntax:

updatevoc [-A] [-C] [-I] [-O] [-N] [-S] [directory]

Description

Run the system-level updatevoc command for each account after you install a new version of UniData. The command adds new VOC entries to the account. UniData reads the new entries from a file called VOCUPGRADE, which the upgrade process places in your udtbin directory.

Parameters

The following table describes each parameter of the updatevoc syntax.

updatevoc Parameters

Parameter Description

[-A] Traverses all subdirectories.

[-C] Records changes made to existing entries in a file named vocupgrade, in the directory from which updatevoc was executed.

[-I] Runs interactively, prompting the user for verification when an entry in VOCUPGRADE will result in changes to an existing entry in the VOC file.

[-O] Updates all VOC entries in VOCUPGRADE, overwriting existing VOC entries without prompting for verification.

[-N] Records changes not made due to conflicts with existing entries in a file named vocupgrade, in the directory updatevoc was run from.

[-S] Suppresses informational messages normally displayed after each change to the VOC file.

[directory] Specifies a directory on which to run updatevoc.


Updating Multiple UDTHOME Accounts on UniData for UNIXIf you have multiple UniData homes, follow the steps below to update each home with Release 7.2 after you have upgraded your primary UniData home:

1. Set UDTHOME Environment VariableSet your UDTHOME environment variable to the UniData home you want to upgrade. Substitute your path for udthome.

From the Bourne or Korn shell:UDTHOME=/disk1/udalt;export UDTHOME

From the C shell:% setenv UDTHOME /disk1/udalt

2. Change DirectoriesYour current working directory must be the directory in which the previous UniData executables are installed. Change to this directory and execute the pwd command to check your location.


3. Begin Upgrade ProcessFollow steps 7 through 23 of the Step-by-Step Installation instructions, or update UniData using the install.param file, described in the following section. Make sure you choose the option to save the include, lib, work, and demo directories in udtbin. If you remove these directories, you will have to tar the UniData tape again to upgrade your UniData homes.

Repeat the preceding three steps for each of the UniData homes you want to upgrade.

Updating Multiple UDTHOME Accounts on UniData for UNIX 6-20

Installing Using the install.param FileIf you do not want to answer each prompt during the upgrade installation, you can customize the install.param file located in udthome/bin, then use this file for the prompt responses. The following example displays the contents of the install.param file before any customization:

# pg install.paramUdtHome /disk2/srcman/alpha/ud_PEAK_981110WorkDir /disk2/srcman/alpha/ud_PEAK_981110/workLibDir /disk2/srcman/alpha/ud_PEAK_981110/libLogDir /disk2/srcman/alpha/ud_PEAK_981110/logSerial HPUX11Group unisrcStopSys YesRFSflag YesOverWrite NoBackup NoConfProduct NoSaveDir save


# pg install.paramCheckLang YesStopSys YesUdtHome /disk1/ud71WorkDir /disk1/ud71/workLibDir /disk1/ud71/libLogDir /disk1/ud71/logUnisharedDir /usr/unisharedGroup sysSerial serial_numberRFSflag NoREPflag NoBackup NoConfProduct NoOverWrite YesConfirm YesSaveDir save



Syntax:



In the following example, updatesys is executed by using the install.param file:
















Update VOC files in /disk1/ud71/sys /disk1/ud71/demo ...







You should now complete steps 24 through 27of the step-by-step installation instructions.



Problem:


Cause:


N_PUT

This UniData configuration parameter, which controls the size of the system buffer for RFS, has a default value of 8192. You may have to decrease it to 4096, depending on the size of shmmax * shmseg. If this result is greater than 8 MB, you will have to adjust N_PUT.

N_TMQ and N_PGQ


Problem:

If the smm.errlog contains a message similar to:




Cause:


Problem:


Cause:



Problem:



Cause:



Step-by-Step Installation on UniData for Windows PlatformsYou can upgrade your UniData installation for two purposes:

Add components you did not previously installInstall a new version of the entire product

1. Review Current ConfigurationWhen you upgrade your UniData product set, you may lose certain configuration information you have defined, because the upgrade overwrites existing values. You may lose:

UDTelnet Configuration settings (but not User Profiles)UDSerial Configuration settingsUniData configuration parameters from the udtconfig file (UDTHOME\include\udtconfig)ODBC server and database definitions

You can preserve the udtconfig changes by making a copy of the udtconfig file before you upgrade. However, at this release of UniData there is no way to preserve the UDTelnet or UDSerial configuration settings.

2. Log On As an AdministratorYou must log on with Administrator privileges to install UniData.

3. Ask Users to Quit UniDataStart a UniData session and use the ECL LISTUSER command to identify current UniData sessions. Contact all users and ask them to exit out of UniData. Use LISTUSER to monitor them. When all users have quit UniData, end your UniData session.


4. Stop UniData with stopud (Optional)Use the stopud command to place UniData in the “nonrunnable” state and prevent users from logging on during the installation process.

5. Stop Current Installed Services

UniData Services

You do not need to stop any UniData services (for instance, the Telnet or Serial Services) before an upgrade installation. The installation routine prompts you whether you wish to upgrade these.

Services From Other Vendors

If you are already using a Telnet service or a serial terminal support service from a vendor other than IBM, and you want to install UniData’s Telnet or serial terminal support services, you must stop your existing services before you proceed with the UniData installation.


Warning: After the installation, you will not be able to run UniData’s Telnet Service or UniData’s Serial Terminal Support Service at the same time as other Telnet or Serial terminal support services. You must stop these whenever you wish to use the ones you installed previously.

6. Load the UniData DiscPlace the UniData disc in your CD-ROM drive. Make certain you have the UniData Product Configuration list that is included with your media. You will need this form when you license the product after installation.


7. Upgrade UniDataFollow the instructions in Chapter 4, “ UniData RDBMS Advanced Installation.” When the installation process prompts for the directory where you want to install UniData, enter the path to the directory installed on your PC that you want to update, as shown in the following example:.

Warning: If you are upgrading your UniData version and you have created indexes on any of the data files that get installed in the UniData demo account (for instance, CLIENTS), you will encounter problems if you select Demo Account when you upgrade. The files and indexes won’t be synchronized, and any attempt to use your indexes will fail. To prevent these problems, either refrain from upgrading the demo database or remove all the indexes (with the DELETE.INDEX command) and re-create them after the upgrade.


8. Update Alternate Global Catalog SpacesAt this point, you may upgrade globally cataloged programs released by UniData in one or more alternate “UDTHOME” directories (created with the newhome command).

If you have one or more UniData home directories and you wish to update the global catalog to reflect changes in the programs released by UniData, from the MS-DOS command prompt, change your current directory to the appropriate alternate UniData home directory, and then execute the updatesys command. Perform this procedure for each alternate UniData home directory you want to update. For information about the updatesys command, see the UniData Commands Reference.

Warning: Do not set your UDTHOME environment variable to the UniData home you want to upgrade.

9. Restart WindowsRestart Windows. Restarting the machine updates your UniData bin directory in the systemwide Path variable.





11. Start UniData with startudIf you stopped UniData in step 4, execute the startud command at the MS-DOS command prompt to set UniData to a runnable state.


12. Start a UniData SessionThe UniData program group contains icons for the components of the UniData product. To execute a component, click the appropriate icon.




7Chapter

UniData RDBMS Patch Installation

Patch Installation Considerations. . . . . . . . . . . . . . 7-3Step-by-Step Installation . . . . . . . . . . . . . . . . 7-5Installing Using the install.param File . . . . . . . . . . . . 7-23Troubleshooting Tips . . . . . . . . . . . . . . . . . 7-26

This chapter is intended for those who are installing a patch release of UniData Release 7.2 on a UNIX platform.

Answers to the prompts in the installation script are kept in the install.param file located in udtbin. This file contains responses that are most likely inappropriate for your installation after it is loaded from tape. You may edit the install.param file to customize your installation, then use the customized file as part of the installation process without having to provide input to the installation prompts. If you want to use this option, proceed to “Installing Using the install.param File” on page 22.

After you complete the installation process, your responses to the installation prompts are written to this file.


Patch Installation ConsiderationsAlthough you can run UniData 7.2 concurrently with previous versions of UniData, such as Release 7.1 and Release 6.1, you cannot run two versions of UniData 7.2 simultaneously. A patch installation overwrites the existing version UniData 7.2 on your system.

Overwritten FilesA patch installation overwrites the following files and/or directories:

The contents of udtbin.The udtconfig file located in /usr/ud72/include.The logconfig file located in /usr/ud72/include.The arch_backup and arch_restore files located in /usr/ud72/include.The contents of the /usr/ud72/ods directory.The base.mk, cfuncdef, and callbas.mk files in udthome/work.The files provided by UniData in the udthome/demo directory (for example, the CLIENTS, ORDERS, and INVENTORY files).The log files, if you are running the Recoverable File System.

During the patch installation process, you have the opportunity to choose whether to back up the /usr/ud72/include, udthome/work and udthome/log directories as part of the upgrade process. If you choose to backup these files, UniData creates a directory called backup in udtbin, which contains the include, log, and work directories as they existed before the upgrade process started. You may want to additionally backup these files in an area outside of the UniData directory structure in case you have to rerun the upgrade process.

If you want to restore a file that was saved in the backup directory, you can copy the file from the udtbin/backup directory to the current file. In the following example, the udtconfig file is copied from the backup directory to /usr/ud72/include using the UNIX cp command:

# pwd/usr/ud72/include# cp /disk1/ud72/bin/backup/include/udtconfig udtconfig#

Patch Installation Considerations 7-3

In addition to the backup directory, a copy of the udtconfig file, called udtconfig.bak, is written to usr/ud72/include directory.

The upgrade process also prompts you to indicate whether or not you want to overwrite the existing udthome/work directory. If you have linked C routines with UniData, do not overwrite the directory during the upgrade process.

Updated FilesA patch installation updates the following files and/or directories:

The VOC file in each UniData account after running updatevoc.The global catalog space located in udthome/sys.

You do not have to recompile or recatalog your globally cataloged programs after a patch installation.


Step-by-Step InstallationFollow the steps in this section for a patch installation.

You must log on with root permissions to perform the installation.

1. Save Your make FilesIn UniData, you can link functions written in the C language to UniBasic programs. You can also use CallBasic to access UniData from a C application. UniData uses a group of files in the udtwork directory for these capabilities. The files that are important are base.mk, new.mk, callbas.mk, cfuncdef, and cfundef_user.

UniData 7.2 provides new base.mk, cfuncdef, and callbas.mk files in the udtwork directory. The patch installation process installs these new files and libraries, overwriting the files that already exist. Either choose the option to backup existing directories during that patch installation, or, before you upgrade, make backup copies of these three files. If you are using CALLC or CallBasic, you will need to relink your application using the new make files after the patch installation is complete.

Note: If you made your modifications to the cfuncdef_user file in your previous version of UniData 7.2, you do not need to make any changes to the cfuncdef file. If you made modifications to the cfuncdef file in the previous version of UniData, these changes should be saved to the cfuncdef_user file in the udthome/work directory so you will not have to make the same changes with each upgrade of UniData. See Administering UniData for information about make files and cfuncdef_user.

Step-by-Step Installation 7-5

2. Check Environment VariablesWhen you install a patch release of UniData 7.2, you use the same directories as your previous version of UniData, since the patch release of UniData 7.2 replaces your previous version of UniData 7.2. Check the environment variables and make sure they are set to the correct paths to the previous version of UniData 7.2. To check the environment variables, use the UNIX printenv command, as shown in the following example:

# printenvMANPATH=/usr/share/man/%L:/usr/share/man:/usr/contrib/man/%L:/usr/contrib/man:/usr/local/man/%L:/usr/local/man:/opt/pd/share/man/%L:/opt/pd/share/man:/opt/hpnp//man:/opt/graphics/starbase/share/man:/opt/audio/share/man:/opt/blinklink/share/man:/opt/ansic/share/man/%L:/opt/ansic/share/man:/opt/langtools/share/man/%L:/opt/langtools/share/man:/opt/video/share/man:/opt/videoout/share/man:/opt/image/share/man:/opt/imake/man:/opt/aCC/share/man:/opt/CC/share/manPATH=/disk1/ud71/bin:/usr/bin:/usr/sbin:/sbinCOLUMNS=80...UDTHOME=/disk1/ud72SHELL=/bin/cshUDTBIN=/disk1/ud72/bin

If the UDTHOME and UDTBIN environment variables are not set or are set incor-rectly, use the following examples to set them to your existing version of UniData. These examples use /disk1/ud72 as the location of UDTHOME and /disk1/ud72/bin as the location of UDTBIN. Substitute your paths for udthome and udtbin.












3. Change DirectoriesYour current working directory must be the directory where the previous UniData executables are installed. Change to this directory and execute the pwd command to check your location.


4. Check for Existing UsersAll current users must log off UniData before you begin the patch installation process. Enter the listuser command to check for users logged on to UniData. If there are users in UniData, have them log off now. If listuser does not list any UniData users, you can proceed with the patch installation.

In the following example, no users are logged on, and the patch installation can safely proceed:

# listuserLicensed/Effective # of Users Udt Sql Total

32 / 32 0 0 0

UDTNO USRNBR UID USRNAME USRTYPE TTY TIME DATE #


5. Stop UniDataStop the existing UniData daemons with the stopud command, then verify that all daemons have been stopped by using the showud command. Be sure to use stopud even if your system seems to be down to make certain all processes and ipc structures are cleaned up. Do not run UniData during the patch installation process; doing so could corrupt your UniData software.

In the following example, stopud is executed followed by showud to verify that all daemons have stopped:

# ./stopud Using UDTBIN=/disk1/ud72/bin

SM stopped successfully. CLEANUPD stopped successfully.SBCS stopped successfully.SMM stopped successfully.Unirpcd has already been stoppedUnidata R7.2 has been shut down. # ./showud UID PID TIME COMMAND#



Mount the tape on your tape drive. Load the UniData software into the udtbin directory with the UNIX tar command. In the example below, tape.device is the name of the tape drive you are using. For more information on the tar command, see your UNIX documentation.




Your installation media contains a tar file in compressed format. Unload the compressed tar file from diskette and then uncompress it. Then, extract the UniData files and directories from the tar file. To accomplish these tasks requires roughly twice the amount of disk space required for an ordinary UniData installation. You can complete the unload, uncompress, and extract procedures in the udtbin directory if you have enough disk space at that location. Consider performing the unload and uncompress steps in another location (such as /tmp) if the udtbin directory has less than 250 MB of space available.








Use the UNIX uncompress command to generate an uncompressed tar file. For example, if the name of the compressed tar file is sco7.2.tar.Z, enter the following command at the UNIX prompt:

# uncompress sco7.2.tar.Z




Set your current working directory to udtbin. Use the UNIX tar command to extract the UniData files and subdirectories. Make sure you specify the full path name of the tar file. For example, if /bin, and the tar file (named sco6.1.tar) is in /tmp, use the following commands:

# cd /disk1/ud72/bin# tar xvf /tmp/sco7.2.tar


# rm /tmp/sco72.tar

Proceed to step 7.




7. Enter ./updatesysEnter ./updatesys at the system prompt. This begins the patch installation process.


The UNIX LANG environment variable affects the behavior of UniData. Before you install UniData, you should be aware of the consequences of using a LANG setting other than “C”. If you use a LANG setting other than “C”, note that certain UniData commands may cause unpredictable results, such as the UniBasic UPCASE and DOWNCASE commands, and the MCU and MCL conversion codes.

If you are installing UniData in an environment that does not support ASCII characters 192 and 250 through 255 as internal markers, read UniData International before proceeding with the installation.







# udtinstall



WARNING:




If you press ENTER to accept the default answer of “Yes,” UniData continues the installation process using the LANG group of “C.” If desired, you can change your LANG environment variable after the installation process is complete. If you answer “No” to the above prompt, UniData exits the installation process.



# ./updatesys





Press ENTER to accept the default of “Yes” if you want to continue with the instal-lation process. If you do not want to proceed at this time, enter “No.”

Note: You must enter “Yes,” “yes,” or “YES” and “No,” “no,” or “NO” rather than “Y” or “N” for all prompts in the installation process.

8. Enter the udtwork Directory The system displays the default work directory where it will load the files to rebuild UniData. The path UniData displays is based on the value of udthome. Press ENTER to accept the default, or enter another path for the work directory:


9. Enter the udtlib DirectoryThis directory contains libraries for all UniData executables. The path UniData displays is based on the value of udthome. Press ENTER to accept the default or enter another path for the lib directory:



10. Enter the Location of the log FilesThis directory contains the location where UniData will build the log files for the Recoverable File System (RFS). The path UniData displays is based on the value of udthome. Press ENTER to accept the default, or enter another directory path for the log files:

Enter the full path name of log directory [/disk1/ud72/log]:



12. Enter a Group NameUniData uses the group name associated with the root log on ID as the default. If the group name displayed is correct, press ENTER. If the default is not correct, enter the correct group name:


13. Enter the Serial Number or Machine NameEnter the serial number found on your Product Configuration sheet in response to the following prompt. This information is not required as part of the installation.









16. Back Up Existing DirectoriesIf you answer “Yes” to this prompt, the /usr/ud72/include, udthome/work and udthome/log directories are backed up in a directory called backup in udtbin. If you want to back up these directories, enter “Yes” or “yes.” If you do not want to back up these directories, press ENTER to accept the default of “No.”

Backup the existing directories? [No]:Yes


17. Decide When to Authorize UniDataUniData prompts whether you want to configure the product at the end of the instal-lation process or not. If you enter “Yes” at this prompt, UniData will automatically run the confprod utility as part of the installation. If you do not want to configure the product at the end of the installation process, press ENTER to accept the default. UniData will run for 30 days after installation without requiring authorization.



18. Back Up work DirectoryIf the work directory you entered in step 8 already exists, UniData prompts whether or not you want to overwrite this directory. If you have already linked your C routines with UniData, do not overwrite the work directory during the patch installation.

/disk1/ud72/work exists, overwrite it? [Yes]:no

19. Enter Old Version Number of UniDataIn order to set the proper language group, UniData prompts for the previous version of UniData from which you are upgrading. For a patch installation, press ENTER to accept the default of 71.

Enter the UniData version to be upgraded? [71]:


20. Review Input DataUniData displays a summary of the information input at each prompt before proceeding with the installation. Review the summary carefully. If all the values are correct, press ENTER to accept the values and proceed with the installation process. If some information is incorrect, enter “No”. UniData exits the installation process. You need to restart the installation and make any corrections to prompt responses.

Summary of your inputs CheckLang No OverWrite Yes Confirm Yes SaveDir save StopSys Yes WorkDir /disk1/ud72/work LibDir /disk1/ud72/lib LogDir /disk1/ud72/log UnisharedDir /usr/unishared Group sys Serial serial_number RFSflag Yes

REPflagNo Backup Yes ConfProduct No PreviousVer 71 Are those values correct? [Yes]:

21. Proceed with the Installation ProcessThe installation process first makes sure that the version of UniData identified by udtbin is not running. In an patch installation, UniData will stop the version of UniData identified by udtbin. The installation process then changes the file’s ownership to root, and the group name to the name you specified.

Next, the patch installation process tests the system configuration by running the systest utility, then updates the include, ods, lib, sys, demo, work, unishared, and objcall directories.








23. Choose to Release Disk SpaceThe patch installation is now complete. UniData prompts you to save or remove the include, lib, work, and demo directories from udtbin, because they are not needed in the udtbin directory for running UniData. If you remove these directories, you free up approximately 10MB of disk space, but you will have to tar the UniData tape again if you need to reinstall UniData. If you do not remove these directories, you can reinstall UniData without having to tar the tape.


24. Installation CompleteThe patch installation process is now complete. If you need to authorize UniData at this time, follow the steps outlined in Chapter 8, “ Licensing UniData Products.” If you licensed UniData in step 22, you can proceed with the next step.


25. Check Environment VariablesBefore you can test the installation by starting UniData and invoking a UniData session, you need to ensure that the environment variables for udthome and udtbin are correct. To check your environment variables, use the UNIX printenv command. Since the environment variables were set in step 2, they should still be correct.



27. Copy Saved FilesIf you want to restore any of the files that were saved in the udtbin/backup directory, copy them using the UNIX cp command. In the following example, the udtconfig file backed up in udtbin/backup is copied to /usr/ud72/include/udtconfig:

# cp /disk1/ud72/bin/backup/include/udtconfig /usr/ud72/include/udtconfig#

28. Run cntl_installIf you are running the Recoverable File System, make sure the logconfig file is adequate to meet your needs. The logconfig file located in /usr/ud72/include is overwritten during a patch installation. Either restore a backup copy of the logconfig file or edit the logconfig file using any UNIX text editor. Then, run cntl_install to reinitialize your log files.

# cntl_install cntl_install utility resets Unidata Systemafter a full database backup (Image Copy).This means, all log (and archive) files willalso be initialized for re-use. Do you want to continue?(y/n) [n] y Installing Logs (and Archives) after cntl_install ........ #

Note: If you are running UniData with archiving enabled, you do not have to restore or edit the archconfig file, since it is not overwritten by the patch installation.



# ./startud Using UDTBIN=/disk1/ud72/bin


SMM is started.SBCS is started.CLEANUPD is started.Unirpcd is started #

You can now run UniData. Change directories using the UNIX cd command to the demo account located in udthome/demo. Enter the full path name of the bin directory, followed by the udt command (if you have set your environment variables, the default is udt, as in the following example).

# cd ../demo# udt



Current UniData home is /usr/ud72/.Current working directory is /usr/ud72/demo.

Note: Before users can access UniData, you must set environment variables for all users. Consider using a .login or .profile script. You can include the full UniData paths there. You will also need to make sure each user’s path includes the udtbin path. For detailed information, see Administering UniData .

30. Run updatevocRun the updatevoc command to update the VOC files in your UniData accounts with new or changed commands for Release 7.2.

Syntax:

updatevoc [-A] [-C] [-I] [-O] [-N] [-S] [directory]


Description

The system-level updatevoc command should be run for each account after you install a new version of UniData. The command adds new VOC entries to the account. The system reads the new entries from a file called VOCUPGRADE, which the upgrade process places in your udtbin directory.

Parameters

The following table describes each parameter of the updatevoc syntax.

updatevoc Parameters

Parameter Description

[-A] Traverses all subdirectories.

[-C] Records changes made to existing entries in a file named vocupgrade, in the directory updatevoc was run from.

[-I] Runs interactively, prompting the user for verification when an entry in VOCUPGRADE will result in changes to an existing entry in the VOC file.

[-O] Updates all VOC entries in VOCUPGRADE, overwriting existing VOC entries without prompting for verification.

[-N] Records changes not made due to conflicts with existing entries in a file named vocupgrade, in the directory updatevoc was run from.

[-S] Suppresses informational messages normally displayed after each change to the VOC file.

[directory] Specifies a directory on which to run updatevoc.


Installing Using the install.param FileIf you do not want to answer each prompt during the patch installation, you can customize the install.param file located in udthome/bin, then use this file for the prompt responses. The following example displays the contents of the install.param file before any customization:

# pg install.paramUdtHome /disk2/srcman/alpha/ud_PEAK_981110WorkDir /disk2/srcman/alpha/ud_PEAK_981110/workLibDir /disk2/srcman/alpha/ud_PEAK_981110/libLogDir /disk2/srcman/alpha/ud_PEAK_981110/logSerial HPUX11Group unisrcStopSys YesRFSflag YesOverWrite NoBackup NoConfProduct NoSaveDir save


# pg install.paramCheckLang YesStopSys YesUdtHome /disk1/ud72WorkDir /disk1/ud72/workLibDir /disk1/ud72/libLogDir /disk1/ud72/logUnisharedDir /disk1/unisharedGroup sysSerial serial_numberRFSflag NoREPflag NoBackup NoConfProduct NoOverWrite YesConfirm YesSaveDir save

Next, execute the updatesys command with the -f option.

Syntax:

updatesys -f filename


In the following example, updatesys is executed by using the install.param file:

# ./updatesys -f install.paramWelcome to the UniData RDBMS.

























Problem:


Cause:


N_PUT

This UniData configuration parameter, which controls the size of the system buffer for RFS, has a default value of 8192. You may have to decrease it to 4096, depending on the size of shmmax * shmseg. If this result is greater than 8 MB, you will have to adjust N_PUT.

N_TMQ and N_PGQ

These UniData configuration parameters are numbers of UNIX message queues created for communication between user processes and the Recoverable File System. By default, each parameter is set to one queue for every four users. Add these to the ten queues for the other UniData daemons, and adjust the UNIX kernel parameter msgmni (number of message queues on your system) accordingly. If you cannot increase msgmni, temporarily reduce N_TMQ and N_PGQ until the kernel can be rebuilt.

Problem:




Cause:


The number of semaphores available systemwide is not adequate for the number of users on your system. Increase the kernel parameter defining the number of semaphores available system wide, normally semmns, to at least NUSERS + 10. If you cannot rebuild the kernel, you must decrease the NUSERS parameter in the udtconfig file, located in /usr/ud72/include, until the kernel can be rebuilt.

Problem:


Cause:


If you answered the last prompt in udtinstall with exit, you need to reload your UniData tape first.

Problem:



Cause:



8Chapter

Licensing UniData Products

About Licensing . . . . . . . . . . . . . . . . . . . 8-3Licensing UniData . . . . . . . . . . . . . . . . . . 8-5Licensing Steps on UniData for UNIX . . . . . . . . . . . . 8-8How UniData Counts Licenses . . . . . . . . . . . . . . 8-18Licensing Steps for UniData for Windows Platforms . . . . . . . 8-19Updating a UniData License . . . . . . . . . . . . . . . 8-22

This chapter covers licensing UniData after you have installed it. This chapter covers the following topics:

Information about licensing.Licensing steps.The confprod program.The udtconf program.


About LicensingThe licensing process allows you to define a software license expiration date based on the license you purchase. UniData begins to issue warnings to the console every hour, beginning 30 days before the expiration date. This warning process and the grace period allow you to get a new authorization before UniData terminates.

Types of UniData LicensesIBM offers the following types of licenses for the UniData product:

The UniData Workstation edition is for a single user license on Windows platforms, and Linux using 1–2 Intel processors. This edition includes device licensing.The UniData Workgroup edition is for 3–24 users on Windows platforms, SCO, or Linux using 1–2 Intel-based processors.The UniData Server edition is for 4 users or more on any platform, Device licensing is not available with the UniData Server edition.The UniData Enterprise edition is for 25 or more users on any platform. This edition includes Device Licensing.

UniData Device LicensingDevice licensing enables you to have multiple UniData sessions from the same device, normally your PC, while consuming only one UniData license. UniData sessions can be connections through client/server middleware, such as UniData ODBC, UniObjects, UniObjects for Java, UniOLEDB, and InterCall, or they can be connections through the wIntegrate and/or SBClient telnet clients. These sessions can be established using one or more user ID and password combinations, but will only consume one UniData license as long as they come from the same physical device. You specify the maximum number of concurrent sessions allowed from a single device when licensing UniData. The number of connections you may specify is 0 -10, depending on the number for which you are licensed. You can connect more than ten times, but each connection over ten consumes a full UniData license.

Device licensing is available on the UniData Workstation, Workgroup, and Enterprise editions.

About Licensing 8-3

Licensing UniDataYou can license UniData products from UniAdmin, or from by entering the confprod command from the command line.


Licensing ProcedureIn order to license UniData, you must complete the following steps. Each step is explained in detail later in this chapter:

1. Determine the number of users and the UniData product set for your system. On UniData for UNIX, your installation media comes preset with a default of eight users, and all layered products set to N. On UniData for Windows platforms, your installation media comes preset with a default of 32 users. You set the number of users and authorized products for your system when you run the confprod program. If the number of users and authorized products on your Product Configuration Sheet differs from what you ordered, contact your UniData software distributor or account manager.

2. Run the confprod program and enter the number of users and the authorized product set into the Configuration and Authorization screen to generate a configuration code.

3. Contact IBM with the generated configuration code to obtain an authorization code.

4. Enter the authorization code into the Configuration and Authorization screen of the confprod program. On UniData for UNIX, the product fields that display Y or N indicate whether you are licensed to use the product. On UniData for Windows Platforms, the check box next to a product indicates whether you are licensed to use that product. The product fields that display numbers show how many users are authorized to use that product.

5. Run udtconf to update the UniData configuration parameters for the number of authorized users.

6. If you are running the Recoverable File System, adjust the log configuration file and reinitialize the log and archive files.

Tip: Refer to the key card sent with the UniData product for information about autho-rizing UniData from the IBM website.

Note: UniData functions for up to 30 days after installation without an authorization code. You should allow sufficient time to contact IBM with your configuration code and receive an authorization code. Any change in the configuration starts the same 30-day countdown. Even if you immediately return your settings to their former values, you must contact IBM for a new authorization code.

Licensing UniData 8-5

Tip: If the configuration provided to you matches what you requested from your UniData supplier, you should consider leaving it the way you received it to avoid any purchasing discrepancies or problems.

On UniData for UNIX, the confprod program requires that you use a terminal supported by vvtermcap. vvtermcap is a special UniData termcap-like file. confprod, and udtconf (the shared memory configuration tool) rely on vvtermcap. UniData expects to find this file in udtbin. If vvtermcap is not located in udtbin, you must set the VVTERMCAP environment variable to the path where vvtermcap resides.

UniData supports the following terminal types:

ANSIDEC VT100DEC VT220VT52WYSE 50

vvtermcap also includes a sample definition that is tunable to your specific terminal requirements. As the system administrator, you should make sure your terminal emulation is listed. If not, you can copy the “Test” terminal definition and modify it to meet your needs.


Licensing Steps on UniData for UNIX

1. Change DirectoriesChange directories to the udtbin directory in which you installed UniData. Change directories using the UNIX cd command and then confirm your location using the pwd command as shown in the following example:

# cd /usr/ud72/bin# pwd/usr/ud72/bin#

2. Run confprodYou must log on as root to run confprod.

The confprod application is used to obtain the configuration code after installing UniData. The following describes how to use confprod:

To start the application, enter the following command from the udtbin directory:

# ./confprod

Licensing Steps on UniData for UNIX 8-7

This displays the Configuration and Authorization screen:

If you have previously set the configuration and obtained authorization, the Authorization field should say “Yes,” indicating that you are authorized until you change the configuration. If you are already authorized and the number of users and UniData products is correct, no further action is required until you make changes.

3. Match Your Product Configuration SheetYou may need to change the current settings on the Configuration and Authorization screen to match your Product Configuration sheet. Change the current settings by using the arrow keys or tab key on your keyboard to move through the choices in the Users/Licensed column. Enter the number of users from the Product Configuration sheet in the first field. Enter the number of Connection Pools from the Product Configuration sheet in the Connection Pooling field. Enter the number of Device Licenses from the Product Configuration sheet in the Device License Field. Enter “Y” (Yes) or “N” (No) in any of the next three fields to indicate whether you are authorized to use the product corresponding to the field. Enter a new expiration date in the Expiration Date field to match the UniData license expiration date on the Product Configuration sheet, if necessary.


4. Save the ChangesIf you changed the configuration and you want to save it, press U (Update). If you were previously authorized and you changed the configuration, UniData automatically changes the Authorization field from “Yes” to “No.” You can skip this step if you did not change the configuration.

Tip: The screen instructions call for CTRL plus the letter on the screen (U, F, A, D, or E); however, the necessity for CTRL depends on your operating system. Try both to see if you need to enter CTRL plus the letter, or just the letter.

5. Generate the Configuration CodeObtain the configuration code from UniData by pressing F (ConFCode). UniData displays the configuration code at the bottom of the screen. You must supply IBM with this code in order to get authorization for a software license.

6. Store the CodeWrite the code down or save it to a file by pressing D (DumpConfig) and entering a file name at the prompt. Saving the code to a file will help to prevent errors, as you can print the file and mail or fax the printout to IBM, or you can e-mail the file to us.

7. Obtain an Authorization CodeFollow the instructions on the key card you received with your UniData product to obtain an authorization code.

8. Enter the Authorization CodeWhen you obtain the authorization code, you must enter the code in the Configuration and Authorization screen. (If you exited the screen, run confprod to reenter the screen. Refer to step 2.) Press CTRL+A (Authorization). At the prompt at the bottom of the screen, enter the authorization code. Your entry is case-sensitive, and you must use dashes in the appropriate places. If the authorization is successful, the screen displays “License Authorized,” and the Authorized field changes from “No” to “Yes.” You are now licensed to run UniData.


9. Exit LicensingPress CTRL+E (Exit) to exit the licensing process.

10. Stop UniDataIf you are licensing UniData immediately after an installation, UniData should not be running. If UniData is running, you must now activate the license. Check to see if UniData is running with the showud command, as shown in the following example:

# showud UID PID TIME COMMAND root 28643 0:00 /disk1/ud72/bin/aimglog 0 18367 root 28644 0:00 /disk1/ud72/bin/aimglog 1 18367 root 28645 0:00 /disk1/ud72/bin/bimglog 2 18367 root 28646 0:00 /disk1/ud72/bin/bimglog 3 18367 root 28656 0:00 /disk1/ud72/bin/cleanupd -m 10 -t 20 root 28640 0:00 /disk1/ud72/bin/cm 18367 root 28652 0:00 /disk1/ud72/bin/repmanager root 28634 0:00 /disk1/ud72/bin/sbcs -r root 28639 0:00 /disk1/ud72/bin/sm 60 1529 root 28627 0:00 /disk1/ud72/bin/smm -t 60 root 22934 0:00 /disk1/unishared/unirpc/unirpcd#

If UniData is running, ask all users to log out of UniData, then stop UniData with the stopud command.

11. Run udtconfThe udtconf utility allows you to automatically set udtconfig parameters for shared memory. Although shared memory requirements are highly application- and platform-dependent, udtconf can provide suggestions for udtconfig parameters and provide information about the actual state of your system.

You do not have log on as root to run udtconf, but the utility reads information from udtconfig parameters and from the UNIX kernel. If you do not log on as root, you may not have sufficient access to the kernel, and the results will be unreliable.

You should run udtconf with UniData users logged off and UniData shut down. The one exception is to assess the impact of the RFS system buffer. In this case, run udtconf from a UNIX prompt while UniData is running.


udtconf Main Display

The following example shows the main screen of the udtconf utility:

To advance to a field displayed on the screen, press TAB. To page down, press CTRL+D. To page up, enter CTRL+U.

The udtconf utility displays warning messages if some of the kernel parameters are not adequate to support the values udtconf calculates. Make sure that the kernel parameter for semaphore undo structures, usually semmnu, is adequate to support the number of authorized users prior to running udtconf.

Settings for the udtconfig parameters NUSERS, SHM_GNTBLS, N_TMQ, and N_PGQ are based on the number of authorized users. Although udtconf displays warning messages if kernel parameters are not adequate to support these settings, the udtconfig file is updated with the values you set if you choose to ignore the warnings. In this case, UniData may not be able to start. For more information about config-uring your UniData system, see Administering UniData.

Update NUSERS for Your Environment

Change the value of NUSERS to correspond to your number of authorized users. The value of NUSERS should be (number of authorized users) + (number of authorized users / 4). If your cursor is not on the NUSERS parameter, press TAB until it is.


Adjust Other Parameters

After you have changed NUSERS, enter CTRL+A to automatically set other udtconfig parameters based on the value of NUSERS. If any of your kernel param-eters will not support the new settings, a warning message appears at the bottom of the screen.

Checking Configuration Parameters

Press CTRL+K to check the UniData configuration parameters against the kernel parameters. If a UniData configuration parameter cannot be supported by a kernel parameter setting, a warning message is displayed at the bottom of the screen for each conflicting parameter, as shown in the following example:

When all configuration parameters have been checked, the system displays the message “Shared memory related configuration values are OK!”

Saving Configuration ParametersPress CTRL+V to save the configuration parameters to the udtconfig file located in /usr/ud72/include. If you do not save the parameters, no changes are made to the udtconfig file.


Recalculating the Size of the CTL

Press CTRL+L from any udtconf screen to recalculate the size of your global control table CTL. This table changes size if you change shared memory parameters such as SHM_GNTBLS, SHM_GPAGESZ, and so forth. If the table size is greater than the kernel parameter shmmax (and the udtconfig parameter SHM_MAX_SIZE), you will not be able to start UniData.

Viewing Current and Suggested Settings

To view current and suggested UNIX kernel settings, press CTRL+P. The following screen shows sample output:

udtconf suggests values assuming that UniData is the only software product on your system. If that is true, as long as the current kernel settings for semaphore undo struc-tures, shared memory segments, and so forth, are at least equal to the suggested values, it should not be necessary to rebuild your kernel. If you have additional appli-cations running, you need to consider the combined effect of UniData and all other applications when evaluating your kernel.


Exit udtconf

To exit the udtconf utility, press CTRL+E. If you have made changes to configuration parameters, make sure to save the changes using CTRL+V before exiting the program.

udtconf and the Recoverable File System

If you are using the Recoverable File System, UniData reserves an amount of shared memory for the system buffer. This memory is reserved when you start UniData, and it is not available to the smm or sbcs daemons. If your system was running close to its limit in terms of memory resources without RFS, allocating the system buffer can be a significant change. For instance, you may see an increase in error messages indicating smm could not create or attach a shared memory segment. For information about configuration parameters for RFS, see Administering the Recoverable File System.

12. Verify logconfig FileIf you are running UniData with the Recoverable File System, the udtconf utility automatically changes the size of the file-level log in /usr/ud61/include/logconfig. The size of the file-level log must be at least NUSERS + 1. Verify that file-level log size is correct.

In the following example, the file level log size appears in bold:

# pg logconfig/disk1/ud72/log/a_0000 021 4096 0 250/disk1/ud72/log/a_0001 021 4096 0 250/disk1/ud72/log/b_0000 022 4096 0 250/disk1/ud72/log/b_0001 022 4096 0 250/disk1/ud72/log/a_0002 021 4096 0 250/disk1/ud72/log/a_0003 021 4096 0 250/disk1/ud72/log/b_0002 022 4096 0 250/disk1/ud72/log/b_0003 022 4096 0 250/disk1/ud72/log/filelog_0 0120 4096 0 126(EOF):


13. Run cntl_install, if NecessaryIf any values in the logconfig file located in /usr/ud72/include change, run cntl_install at this time to reinitialize your log and archive files. You must have root permission to run cntl_install.

The following example shows the output from cntl_install:

# cntl_install cntl_install utility resets Unidata Systemafter a full database backup (Image Copy).This means, all log (and archive) files willalso be initialized for re-use. Do you want to continue?(y/n) [n] y Installing Logs (and Archives) after cntl_install ........ #

14. Complete InstallationIf you are authorizing UniData as part of an installation process, proceed with the step-by-step instructions for your type of installation.

If you are authorizing UniData separately from performing an installation, you may now start UniData with the startud command.


How UniData Counts LicensesEach of the following processes consumes one UniData license:

A UniData session (executing udt).A connection made to UniData through ODBC.A connection made to UniData through ObjectCall.Using bang (!) to execute another UniData session.Interactive phantom processes

Device licensing enables you to have multiple UniData sessions from the same device, normally your PC, while consuming only one UniData license.

Note: Device licensing is not available with the UniData Server edition.

A phantom process does not consume a UniData license, unless the phantom process is interactive.


Licensing Steps for UniData for Windows Platforms

1. Assemble MaterialsYou need the IBM Product Configuration form that was shipped with your instal-lation media. You need to enter information from the LICENSE and SOFTWARE sections of this document.

2. Start UniData AdminAuthorize UniData from the UniAdmin utility, following the steps described below:

Select one of the following methods to access the Configure Product/License dialog box:

From the UniAdmin window, double-click License.From the UniAdmin menu, click Admin, and then click License.

A dialog box similar to the following appears:

Licensing Steps for UniData for Windows Platforms 8-17

3. Verify ConfigurationVerify that the configuration displayed in the Configure Product/License dialog box matches the configuration on the Product Configuration sheet shipped with UniData.

If the number of users, connection pools, or device licenses displayed in the UniData RDBMS, Connection Pooling, and Device Licenses boxes do not agree with your Production Configuration sheet, click the appropriate box and enter the correct number of users or connection pools.

Review the layered products selected in the Configure Product/License dialog box. If you are authorized to use a product that is not selected, select the check box next to the appropriate product. If a product is selected that you are not authorized to use, click the check box next to the appropriate product to clear it.

4. Enter Expiration DateEnter the expiration date from your Product Configuration sheet in the Expiration Date boxes. If you purchased a license that does not expire, select the Never Expire check box.

5. Update the ConfigurationWhen you have made the necessary changes in the Configure Product/License dialog box, click Update to save the changes.

6. Obtain Configuration CodeClick ConfigCode to obtain the configuration code you will need to authorize UniData. The configuration code appears at the bottom of the Configure Product/License dialog box, as shown in the following example:


Authorize UniData

Follow the instructions on the key card you received with your UniData product to obtain an authorization code.

From the Configure Product/License dialog box, click Authorize. The following dialog box appears:

Enter the authorization code, and then click OK. Click Cancel to the exit the program without saving changes.

Note: You must log on as root on UniData for UNIX or Administrator on UniData for Windows Platforms to authorize the product.

Click Exit to exit the Configure Product/License dialog box.

Note: If you do not have your Product Configuration sheet, or if you encounter problems authorizing UniData, contact IBM at 1-800-274-8184, option 3.

Licensing Steps for UniData for Windows Platforms 8-19

Updating a UniData LicenseYou must update your UniData authorization in the following situations:

You upgrade to a later release level of UniData.You purchase an additional UniData product (for instance, the Recoverable File System or NFA Service).You purchase additional user licenses for your UniData RDBMS.You make any change to any of the user-modifiable fields on the confprod screen.


Documents

Installing and Licensing UniData 7.2 Products · 3/8/2010 · Please be aware: Any images or indications reflecting ownership or branding of the product(s) documented herein may