unidata - rocket software · 9/3/2010 · this software and the associated documentation are...

C:\Program Files\Adobe\FrameMaker8\UniData 7.2\7.2rebranded\UNIADMIN\Front.fmMarch 9, 2010 2:46 pm

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

UniData

Using UniAdmin

UDT-720-UADM-1

ii Using UniAdmin

C:\Program Files\Adobe\FrameMaker8\UniData 7.2\7.2rebranded\UNIADMIN\Front.fmMarch 9, 2010 2:46 pm

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

Notices

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

Copyright© Rocket Software, Inc. 1998-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

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

Using UniAdmin 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

PrefaceOrganization of This Manual . . . . . . . . . . . . . . . ixElements of Syntax Statements . . . . . . . . . . . . . . . x

Chapter 1 Installing and Administering UniAdminInstallation Process . . . . . . . . . . . . . . . . . . 1-3Administering Servers . . . . . . . . . . . . . . . . . 1-11

Registering Servers . . . . . . . . . . . . . . . . . 1-11Unregistering a Server . . . . . . . . . . . . . . . . 1-13Editing Server Information . . . . . . . . . . . . . . 1-13

Managing Server Connections . . . . . . . . . . . . . . . 1-15Connecting to a Server . . . . . . . . . . . . . . . . 1-15Disconnecting from a Server . . . . . . . . . . . . . . 1-16

Chapter 2 Administering AccountsAccessing Accounts Admin . . . . . . . . . . . . . . . . 2-3

Adding a New Account. . . . . . . . . . . . . . . . 2-4Viewing a UniData Account . . . . . . . . . . . . . . 2-5

Chapter 3 Configuring UniData through UniAdminChanging Parameter Values . . . . . . . . . . . . . . 3-3Checking Parameter Values . . . . . . . . . . . . . . 3-4

UniData Configuration Parameters. . . . . . . . . . . . . . 3-5

Chapter 4 Administering Devices through UniAdminAdministering Tape Devices. . . . . . . . . . . . . . . . 4-3

Modifying Tape Device Information . . . . . . . . . . . 4-4Deleting a Tape Device. . . . . . . . . . . . . . . . 4-4Tape Devices on Windows Platforms . . . . . . . . . . . 4-4Saving the Configuration . . . . . . . . . . . . . . . 4-4

ram Files\Adobe\FrameMaker8\UniData 7.2\7.2rebranded\UNIADMIN\uniadminTOC.fm (bookTOC.template)9 2010 2:47 pm

Administering Line Devices . . . . . . . . . . . . . . . . 4-5Creating a New Line Device Definition. . . . . . . . . . . 4-6Modifying Line Device Information . . . . . . . . . . . . 4-6Deleting a Line Device Definition . . . . . . . . . . . . 4-6Saving the Line Device Information . . . . . . . . . . . . 4-7

Chapter 5 Viewing Disk Space Usage

Chapter 6 Using UniData File ToolsFile Checking Tools . . . . . . . . . . . . . . . . . . 6-3

The guide Utility . . . . . . . . . . . . . . . . . . 6-3The filever Utility . . . . . . . . . . . . . . . . . 6-7The checkover Utility . . . . . . . . . . . . . . . . 6-9

File Repair Tools . . . . . . . . . . . . . . . . . . . 6-12The fixfile Utility. . . . . . . . . . . . . . . . . . 6-12The dumpgroup Utility . . . . . . . . . . . . . . . . 6-16The fixgroup Utility . . . . . . . . . . . . . . . . . 6-18

File Conversion Tools . . . . . . . . . . . . . . . . . . 6-21The memresize Utility . . . . . . . . . . . . . . . . 6-21The convdata Utility . . . . . . . . . . . . . . . . . 6-24The convcode Utility . . . . . . . . . . . . . . . . 6-25The convmark Utility . . . . . . . . . . . . . . . . 6-26The convidx Utility . . . . . . . . . . . . . . . . . 6-29The udfile Utility . . . . . . . . . . . . . . . . . . 6-30The shfbuild Utility . . . . . . . . . . . . . . . . . 6-32

Chapter 7 Licensing UniDataLicensing UniData . . . . . . . . . . . . . . . . . . . 7-3

Types of UniData Licenses. . . . . . . . . . . . . . . 7-3Obtaining an Authorization Code . . . . . . . . . . . . . . 7-4

Chapter 8 Monitoring UniData LocksDisplaying File/Record Locks . . . . . . . . . . . . . . . 8-3

File/Record Locks Display . . . . . . . . . . . . . . . 8-3Clearing a Lock . . . . . . . . . . . . . . . . . . 8-4

Displaying System Resource Locks . . . . . . . . . . . . . 8-5Clearing a Lock . . . . . . . . . . . . . . . . . . 8-6

Displaying the Lock Waiting Queue . . . . . . . . . . . . . 8-7

Table of Contents v

vi Usin

Chapter 9 Administering Network ServicesAdministering Databases . . . . . . . . . . . . . . . . 9-3

Adding a Database . . . . . . . . . . . . . . . . . 9-4Updating a Database . . . . . . . . . . . . . . . . 9-5Deleting a Database . . . . . . . . . . . . . . . . 9-5Viewing a Database . . . . . . . . . . . . . . . . 9-6

Administering NFA Servers . . . . . . . . . . . . . . . 9-7Administering the UDSerial Server . . . . . . . . . . . . . 9-15

Service Option . . . . . . . . . . . . . . . . . . 9-16Starting, Stopping, and Pausing the Telnet Server . . . . . . . 9-17Port Configuration . . . . . . . . . . . . . . . . . 9-17Control Keys . . . . . . . . . . . . . . . . . . 9-21Modem Options. . . . . . . . . . . . . . . . . . 9-22Logon Script. . . . . . . . . . . . . . . . . . . 9-24Auto Connection . . . . . . . . . . . . . . . . . 9-25

Administering the UDTelnet Service . . . . . . . . . . . . . 9-27Service Options . . . . . . . . . . . . . . . . . . 9-29User Profiles. . . . . . . . . . . . . . . . . . . 9-32Customizing User Profiles . . . . . . . . . . . . . . 9-35Generated Profiles . . . . . . . . . . . . . . . . . 9-39Starting, Stopping and Pausing UDTelnet. . . . . . . . . . 9-40

Monitoring UniData Services . . . . . . . . . . . . . . . 9-42Starting UniData Services . . . . . . . . . . . . . . 9-42Stopping UniData Services . . . . . . . . . . . . . . 9-42

Chapter 10 UniData Data ReplicationDefining Publishing Groups . . . . . . . . . . . . . . . 10-3Defining Replication on a Subscribing System . . . . . . . . . 10-14Changing Replication Group Definition . . . . . . . . . . . . 10-22Administering Replication through UniAdmin. . . . . . . . . . 10-24Replication Recovery Log . . . . . . . . . . . . . . . . 10-27

REP_RECV_LOG . . . . . . . . . . . . . . . . . 10-27Diagnosis Utility . . . . . . . . . . . . . . . . . . . 10-29Monitoring Replication . . . . . . . . . . . . . . . . . 10-30

Starting the Replication Monitor . . . . . . . . . . . . 10-32Replication Group Status Table . . . . . . . . . . . . . 10-35

Chapter 11 Configuring Log Files for RFSConfiguring Log Files . . . . . . . . . . . . . . . . . 11-3Configuring Archive Files . . . . . . . . . . . . . . . . 11-7

g UniAdmin

Chapter 12 Displaying Programs in Shared Memory

Chapter 13 Configuring SSLConfiguring SSL Through UniAdmin . . . . . . . . . . . . . 13-2Accessing UniData SSL Configuration Dialog Box . . . . . . . . 13-3Creating a Certificate Request . . . . . . . . . . . . . . . 13-4Creating a Certificate . . . . . . . . . . . . . . . . . . 13-11Creating a Security Context . . . . . . . . . . . . . . . . 13-19Configuring SSL for UniObjects for Java or Telnet. . . . . . . . . 13-34

Chapter 14 Administering UsersView Number of Users . . . . . . . . . . . . . . . . 14-2Logging a User Out of UniData . . . . . . . . . . . . . 14-3

Table of Contents vii

PrefaceThis manual describes UniAdmin. This tool enables you to perform the following tasks:

Administer AccountsCreate a new accountView details of an existing accountDelete an Account

Set UniData configuration parametersAdminister tape and line devicesView disk usageUniData File Tools

Check the integrity of UniData FilesRepair damaged filesResize UniData filesConvert UniData files

License UniDataLicense UniVerse or UV/NetMonitor UniData locks

Monitor locksClear file locksClear record locksClear group locks

Administer network servicesAdminister telnet servicesAdminister other services

Administer ReplicationAdminister The Recoverable File SystemManage shared programsConfigure SSL

vii Using UniAdmin

Administer UniData users

viii

Organization of This ManualThis manual is organized as follows:

Chapter 1, “Installing and Administering UniAdmin,” describes how to install and administer UniAdmin.

Chapter 2, “Administering Accounts,” describes how to create and administer UniData accounts.

Chapter 3, “Configuring UniData through UniAdmin,” describes how to set UniData configuration parameters through UniAdmin.

Chapter 4, “Administering Devices through UniAdmin,” describes how to use administer tape devices and line devices through UniAdmin.

Chapter 5, “Viewing Disk Space Usage,” describes how to view disk space usage on your system through UniAdmin.

Chapter 6, “Using UniData File Tools,” describes how to execute UniData file tools against directories or individual files through UniAdmin.

Chapter 7, “Licensing UniData,” describes how to license UniData products through UniAdmin.

Chapter 8, “Monitoring UniData Locks,” describes how to administer locks through UniAdmin.

Chapter 9, “Administering Network Services,” describes how to administer network services through UniAdmin, including configuring UniRpc services, administering databases, administering NFA, UDSerial, and UDTelnet Servers, and administering UniData services.

Chapter 10, “UniData Data Replication,” describes how to setup and configure UniData Data Replication.

Chapter 11, “Configuring Log Files for RFS,” describes how to set up before image and after image log files for the UniData Recoverable File System through UniAdmin.

Chapter 12, “Displaying Programs in Shared Memory,” describes how to view the number of users running cataloged UniBasic programs through UniAdmin.

Chapter 13, “Configuring SSL,” describes how configure SSL through UniAdmin.

Chapter 14, “Administering Users,” describes how to view or terminate UniData processes through UniAdmin.

ix Using UniAdmin

Elements of Syntax StatementsThis reference manual uses a common method to present syntax for UniData commands. The syntax statement includes the command name, required arguments, and options you can use with the command. Italics represents a variable you can replace with any valid option. The following figure illustrates the elements of a syntax statement.

COMMAND required [option] [option1 | option2]{option1 | option2} required... "string"

command names

no brackets or bracesindicates a required

argument

square brackets indicatean optional argument

a vertical line indicates thatyou can choose between

the given arguments

braces indicate that youmust choose betweenthe given arguments

an ellipsis indicates thatyou can enter more than

one argument

quotation marks

appear in boldface

must enclose aliteral string

Elements of Syntax Statements x

1Chapter

Installing and Administering UniAdmin

Installation Process . . . . . . . . . . . . . . . . . . 1-3Administering Servers . . . . . . . . . . . . . . . . . 1-11 Registering Servers . . . . . . . . . . . . . . . . 1-11 Unregistering a Server. . . . . . . . . . . . . . . . 1-13 Editing Server Information . . . . . . . . . . . . . . 1-14Managing Server Connections . . . . . . . . . . . . . . 1-15 Connecting to a Server . . . . . . . . . . . . . . . 1-15 Disconnecting from a Server. . . . . . . . . . . . . . 1-16

This chapter describes how to install and administer UniAdmin.

1-2

Installation Process

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

2. Exit Other ApplicationsBefore proceeding, exit any other Windows applications you may have open.

3. Load the UniData Client CDPlace the UniData Client 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.

1-3 Using UniAdmin

4. Execute the InstallationFrom the Setup screen, click UniAdmin, as shown in the following example:

Installation Process 1-4

5. Proceed With InstallationFrom the UniAdmin Setup window, click Next to continue with the installation, or click Cancel to exit the installation process.

1-5 Using UniAdmin

6. Review License AgreementThe License Agreement dialog box appears, as shown in the following example:

Review the license agreement. If you agree with the terms, click I accept the terms of the license agreement. If you do not agree, click I do not accept the terms of the license agreement to exit the installation process.


7. Choose Destination FolderDetermine where you want to install UniAdmin. By default, it is installed in \IBM\UniAdmin. If you want to select a different directory, click Browse. The following example illustrates the Choose Destination Location dialog box:

Click Back to return to the previous screen, Next to continue with the installation, or Cancel to exit the installation without saving changes.

1-7 Using UniAdmin

8. Select Program FolderDetermine the name of the program folder where you want to install UniAdmin. The following example illustrates the Select Program Folder dialog box:

By default, the installation process installs UniAdmin in the IBM U2\UniAdmin folder. If you want to install it in a different folder, enter the name of the folder in the Program Folders box, or select the folder from the Existing Folders list.

Click Back to return to the previous screen, Next to continue with the installation, or Cancel to exit the installation without saving changes.


9. Copy FilesUniAdmin now has enough information to begin copying files. A dialog box similar to the following appears:

If you want to change any of the settings, click Back. Click Next to continue with the installation process, or click Cancel to exit the installation program.

1-9 Using UniAdmin

9. Complete the InstallationAfter UniData copies the program files, the following dialog box appears:

Click Finish to complete the installation.

10. Reboot Your ComputerBefore proceeding, reboot your computer to properly initialize all components of UniAdmin.


Administering ServersYou must register each server that you want to access through UniAdmin. The server must be running UniData 6.0 or later.

Registering ServersComplete the following steps to register servers for UniAdmin.

1. Start UniAdmin

From the Start menu, select Programs, then select the folder where UniAdmin resides, and then click UniAdmin. A window similar to the following example appears:

2. Define Server to Register

You can access the Server Register dialog box in any of the following ways:

1-11 Using UniAdmin

Using the right mouse button (right-click) U2Servers, and then click Register Servers. Click the server icon on the toolbar, as shown in the following example:

Server Icon

From the UniAdmin menu, click Connect, and then click New.

A dialog box similar to the following appears:

Enter the name of the server you want to register in the Server Name box.

3. Choose DatabaseSelect the database against which you are using UniAdmin. The database is either UniData or UniVerse.

4. Choose the Transport Type

From the Transport Type box, choose the type of communication you are using to the server. You can choose Default, TCP/IP, or Lan Manager. The default is TCP/IP.

5. Register the Server

Click Register to register the server, or Cancel to exit the program without saving changes. The registered servers appear in the UniAdmin window,

Administering Servers 1-12

Unregistering a ServerComplete the steps described in this section to unregister a server.

From the UniAdmin window, right-click on the server you want to unregister, and then click Un-Register. A dialog box similar to the following appears:

If the server information in the dialog box is accurate, click Un-Register to unreg-ister the server, or click Cancel to exit the program without saving changes.

After you unregister a server, it no longer appears on the UniAdmin window.

Editing Server InformationIf you want to change information you previously entered about a registered server, right-click on the server for which you want to edit information, and then click Properties. A dialog box similar to the following appears:

1-13 Using UniAdmin

Edit the information you want to change. Click Save to save the changes, or click Cancel to exit the dialog box without saving changes.

Administering Servers 1-14

Managing Server ConnectionsThis section describes how to connect and disconnect from a UniData server.

Connecting to a ServerTo connect to a server, double-click the server to which you want to connect, or right-click the server and then click Connect, or select Connect from the menu, and click the server to which you want to connect. A login dialog box similar to the following appears:

Enter the login name of the user you are connecting as in the Login ID box. Tab to the Password box and enter the password for the user.

Note: You must log on as root on UniData for UNIX, or Administrator on UniData for Windows platforms for many of the administration options available from UniAdmin. The necessary privileges associated with administrative processes are described in Administering UniData on UNIX and Administering UniData on Windows Platforms.

1-15 Using UniAdmin

Administration Options

After you connect to the server, a window similar to the following appears:

Double-click the server folder to display a list of processes available, or review the options from the menu. Each option is described in detail in later chapters.

Disconnecting from a ServerTo disconnect from a server, right-click on the server from which you want to disconnect, and then click Disconnect.

Managing Server Connections 1-16

2Chapter

Administering Accounts

Accessing Accounts Admin . . . . . . . . . . . . . . . 2-3 Adding a New Account . . . . . . . . . . . . . . . 2-4 Viewing a UniData Account . . . . . . . . . . . . . . 2-5

This chapter describes how to create and administer UniData accounts.

2-2

Accessing Accounts AdminYou can access the Accounts Admin dialog box in any of the following ways:

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

Regardless of the manner in which you administer accounts, a dialog box similar to the following appears:

2-3 Using UniAdmin

Adding a New AccountTo create a new account, click the New. A dialog box similar to the following example appears:

To create a new account, complete the following steps:

1. Choose Account NameIn the Account Name box, enter the name the new account.

2. Define PathIn the Pathname box, enter the location of the new account, or click Browse to select the path.

Accessing Accounts Admin 2-4

UniAdmin displays the following information when the account is created:

Viewing a UniData AccountTo view information about a UniData account, select the account from the UniData Accounts Admin window, and then click Detail. A dialog box similar to the following example appears:

2-5 Using UniAdmin

This dialog box displays the account name, the path, the owner, and the group owner for the account.

Accessing Accounts Admin 2-6

3Chapter

Configuring UniData through UniAdmin

Changing Parameter Values . . . . . . . . . . . . . . 3-3 Checking Parameter Values . . . . . . . . . . . . . . 3-4UniData Configuration Parameters . . . . . . . . . . . . . 3-5

This chapter describes how to use UniAdmin to view and change UniData configu-ration parameters.

Select one of the following methods to access the Configure UniData dialog box:

Right-click on the server where you want to configure UniData, and then click Configuration Editor. From the UniAdmin window, click Admin, and then click Config Editor.

Regardless of the method you chose to configure the server, a dialog box similar to the following appears:

If you want to view the configuration parameters in ascending order, double-click Parameter. If you want to view the configuration parameters in descending order, double-click Parameter while holding down the SHIFT key.

3-2

Changing Parameter ValuesClick the parameter for which you want information or you want to change. A short description of the parameter appears in the Parameter Description box, as shown in the following example:

If you want to change the value for a parameter, click the parameter you want to change, then enter the new value in the Value box, and then click Set.

To save the configuration, click Save. The file is written to /usr/ud72/include/udtconfig on UniData for UNIX, or to udthome\include\udtconfig on UniData for Windows Platforms. Click Cancel to exit the program without saving changes.

Note: Changes you make to the configuration file do not take effect until you stop and restart UniData.

3-3 Using UniAdmin

Checking Parameter ValuesTo check that the configuration parameters have valid values, click Check. A dialog box similar to the following appears:

If you want to view any of the logs associated with the UniData daemons, click View Logs. For a description of these logs, see Administering UniData on UNIX or Admin-istering UniData on Windows Platforms.

If you want to view any of the error logs associated with UniData daemons, click View Errors.

To return to the Server Manager window, click Done.

3-4

UniData Configuration ParametersThe following tables describe the configuration parameters that are placed in the udtconfig file located in /usr/ud72/include on UniData for UNIX, or udthome\include on UniData for Windows Platforms at the time of installation.

The following parameters are available on UniData for Windows Platforms only.

udtconfig File Parameters for Windows NT Only

Parameter Name Description

MSGMNI The maximum number of message queues available for UniData system-wide.

MSGMAX The maximum size of a message.

MSGTQL The maximum number of messages allowed systemwide.

MSGTX The default text size of a message per node.

The following parameters are system-dependent and should not be changed.

udtconfig File Parameters That Should Not be Changed


LOCKFIFO The locking sequence of processes in the system. This parameter should not be changed.

SYS_PV Type of P/V operations used for the Recoverable File System (RFS) only. Determined at installation; platform dependent. Do not change unless instructed by IBM Technical Support.

3-5 Using UniAdmin

The following parameters may be changed to suit your environment:


NFILES Number of physical files that can be opened at the operating system level at one time in a UniData session. This limit is for both udt and tm processes; the name of the corresponding kernel parameter varies among UNIX versions.

NUSERS Limit for number of UniData user processes (such as udt and PHANTOM) that can run at the same time. This parameter replaces the parameter called SHM_LNTBLS.

WRITE_TO_CONSOLE Switch for turning on and off messaging to your console. Must be greater than zero for messages to display at console.

TMP Path of a UNIX directory for storing intermediate work files. Default is /tmp/. If modifying this parameter, make sure the path contains a trailing /.

NVLMARK Specifies a character to print to represent the null value. The ASCII character that represents the null value is nonprinting.

FCNTL_ON Used with UniData Physical Lock Manager. If a UNIX platform supports test-n-set instruction, SYS_PV is set to 3 and FCNTL_ON is set to 0. If a UNIX platform does not support test-n-set instruction, SYS_PV is set to 2 and FCNTL_ON is set to 1. Do not change this parameter unless instructed to do so by IBM Technical Support.

TOGGLE_NAP_TIME If FCNTL_ON is set to 0, the length of time (in milliseconds) that a process waits to access a shared memory address held by another process. This parameter has no effect if FCNTL_ON is set to 1. Do not change unless instructed to do so by IBM Technical Support.

NULL_FLAG Toggles null value handling on and off. If 0, null value handling is off. Must be greater than 0 for null value handling to be in effect.

udtconfig File Parameters That Can Be Changed

UniData Configuration Parameters 3-6

N_FILESYS Maximum number of UNIX file systems allowed. If you have more than 200 UNIX file systems, increase to your number of file systems.

N_GLM_GLOBAL_BUCKET The number of hash buckets systemwide, used to hold the lock names in shared memory. This setting directly affects performance. Normally, the default value of this parameter should not be changed. However, if you notice significant degradation in performance, or your application intensively accesses specific files, you can increase this parameter. The default value is the closest prime number to NUSERS * 3.

N_GLM_SELF_BUCKET The number of hash buckets for the per-process locking table. This parameter is highly application dependent. If the application requires a large number of locks in one transaction (more than 20), you should increase this setting to the closest prime number to the maximum number of locks per transaction.

GLM_MEM_ALLOC The number of lock nodes allocated for each memory request. This parameter is highly application dependent. If your application requires a large number of locks in one transaction, this setting should be increased to the maximum number of locks per transaction * 2.

GLM_MEM_SEGSZ The segment size for each shared memory segment required for the lock manager. The maximum number of segments is 16. Large application environments require a larger size. Each udt will register the lock names it is locking in its per-process locking table. This table is also organized as a hashed table.


udtconfig File Parameters That Can Be Changed (continued)

3-7 Using UniAdmin

The following parameter is related to internationalization.

Internationaliza tion udtconfig File Parameter


UDT_LANGGRP The language group ID used to distinguish language groups that use similar special characters. UDT_LANGGRP is composed of the record mark, escape sequence mark, and the null value mark. The default is 255/192/129.

ZERO_CHAR The character you want to use to represent CHAR(0). See OSREAD, OSBREAD, READT in the UniBasic Commands Reference for more information.

BGINPUTTIMEOUT The number of seconds a background or phantom process waits before timing out. Before the timeout expires, a process may use the UNIX tandem or the UniData for Windows NT TANDEM command to attach to the process.

LB_FLAG For nonrecoverable files, turn Transaction Processing on or off by changing the value of this parameter. If you set the value of to 0, Transaction Processing is off for nonrecoverable files and TP semantics are ignored. If you set the value to 1, Transaction Processing is on. Note: If RFS in on, the LB_FLAG has no effect on recoverable files. You cannot turn off transaction processing for recoverable files if RFS is enabled

USE_DF The USE_DF parameter enables you to choose how UniData loads the shared memory table. Beginning in UniData 7.2, the smm daemon no longer forked a df process to create the entries in the shared memory table, as it had in prior releases. Now, UniData loads the shared memory table by reading the mount table.If you set the value of USE_DF to 0, UniData loads the shared memory table by reading the mount table. This is the default setting.If you set the value of USE_DF to 1, the smm process forks a df process to load the shared memory table.


udtconfig File Parameters That Can Be Changed (continued)


The following table describes shared memory related parameters. These parameters may be changed to suit your environment.


SBCS_SHM_SIZE Size, in bytes, of shared memory segments created by sbcs to store globally cataloged programs. sbcs can attach a maximum of 20 segments system-wide. Run-time errors result if a user attempts to load a new global program that exceeds this limit.

SHM_MAX_SIZE Current kernel setting for maximum size (in bytes) of a shared memory segment. This parameter is set at installation; if you increase the kernel parameter shmmax, you need to increase SHM_MAX_SIZE to the same value as well.

SHM_ATT_ADD Starting address for shared memory attachment. Set at installation; do not change this unless instructed by IBM Technical Support.

SHM_LBA Alignment size, in bytes, for shared memory attachment. Set at installation; do not change.

SHM_MIN_NATT The minimum number of shared memory segments that should be kept attached to a process.

SHM_GNTBLS Number of GCTs (global control tables) in CTL. Each shared memory segment is associated with a GCT. The GCT registers the use of global pages in its associated shared memory segment. Cannot exceed the kernel parameter shmmni.

SHM_GNPAGES Number of global pages in a shared memory segment.

SHM_GPAGESZ Size of each global page, in 512-byte units.

SHM_LPINENTS Number of entries in the PI table of a LCT, which is the number of processes allowed in a process group. It is set to 10 within the system, regardless of the udtconfig setting.

SHM_LMINENTS Number of entries in the MI table of a LCT, which means the number of global pages or self-created dynamic segments that can be attached by a process. Cannot exceed 255.

SHM_LCINENTS The number of entries in the CI table of each LCT, which is the number of local pages that can be attached by a process.

Shared Memory udtconfig File Parameters

3-9 Using UniAdmin

The following table describes size limitation parameters.

SHM_LPAGESZ Size, in 512-byte blocks, of each local page in a global page. A global page is divided into local pages, so SHM_GPAGESZ must be a multiple of SHM_LPAGESZ.

SHM_FREEPCT Percentage of freed global pages in an active global shared memory segment that UniData keeps in the global shared memory pool. smm checks the current percentage; if the percentage is less than SHM_FREEPCT, smm creates a new shared segment.

SHM_NFREES The number of inactive shared memory segments that UniData keeps in the system. smm checks the current number of inactive segments; if the number is larger than SHM_NFREES, smm returns some inactive global shared segments to UNIX.


AVG_TUPLE_LEN Number of local pages that matches the average length of records in your applications. Specifies the length of a buffer kept by udt for holding a record. Should not exceed the number of local pages in a global page.

EXPBLKSIZE Number of local pages used for expression buffers. udt keeps a buffer of this size for intermediate results. IBM recommends you set this parameter so the buffer is one-quarter to one-half the size of a global page.

MAX_OBJ_SIZE Maximum size, in bytes, of object programs that can be loaded into shared memory. Object programs larger than this size are loaded into the user’s address space instead of shared memory.

MIN_MEMORY_TEMP The minimum number of local pages that should be kept for temporary buffers in a process group. Determined at installation.

Size Limitation udtconfig File Parameters


Shared Memory udtconfig File Parameters (continued)


The following table describes parameters related to dynamic files.

STATIC_GROWTH_ WARN_TABLE_SIZE

The number of table elements in the Static Growth Warn table. UniData uses this table to track the last time a warning was issued indicating a file was larger than the threshold. When no unused elements are present in the table, UniData uses the oldest element for a new static file.

STATIC_GROWTH_ WARN_SIZE

The threshold value for the static file size, expressed in bytes.

STATIC_GROWTH_ WARN_INTERVAL

The time interval, expressed in seconds, to warn when a static file is larger than the threshold.


GRP_FREE_BLK Pertains to dynamic files only; the number of free blocks kept in the free block list at the group level. If more blocks are freed, they are kept at the file level.

SHM_FIL_CNT Maximum number of dynamic files that can be open concurrently, systemwide.

SPLIT_LOAD Default loading factor option (percent) at which a group in a dynamic file using the KEYONLY option splits. Splitting occurs when the percentage of space in a group occupied by keys and pointers reaches the split load. The ECL CONFIGURE.FILE command overrides this for individual files.

MERGE_LOAD Default loading factor (percent) at which a group pair in a dynamic file using the KEYONLY option merges. A group pair is eligible for merging when the sum of the percentages of space occupied by keys and pointers in both groups is less than MERGE_LOAD. The CONFIGURE.FILE command lets users override this for individual files.

Dynamic File udtconfig File Parameters


Size Limitation udtconfig File Parameters (continued)

3-11 Using UniAdmin

The following parameter is for NFA server.

NFA udtconfig File Parameters


EFS_LCKTIME Used by the NFA server to specify the maximum time to wait for a lock.

TSTIMEOUT Used by the udtts executable to specify the maximum number of seconds to wait for input from client about device information. If the information is not provided, UniData starts without the device information.

NFA_CONVERT_CHAR If this value is set to 1, UniData converts marks in a stream of data to host-specific marks.

KEYDATA_SPLIT_LOAD Default loading factor (percent) at which a group in a dynamic file using the KEYDATA option splits. Splitting occurs when the percentage of space in a group occupied by keys and pointers reaches the split load. The ECL CONFIGURE.FILE command overrides this for individual files.

KEYDATA_MERGE_LOAD Default loading factor (percent) at which a group pair in a dynamic file using the KEYDATA option merges. A group pair is eligible for merging when the sum of the percentages of space occupied by keys and pointers in both groups is less than KEYDATA_MERGE_LOAD. The CONFIGURE.FILE command overrides this for individual files.

MAX_FLENGTH Upper size limit, in bytes, of each partition file (dat00x) of a dynamic file. When a part file reaches this size, UniData does not add further blocks to it, but creates another part file using the part table. The default value is 1073741824 bytes (1 GB). Must be greater than 32768 bytes (32 KB) and less than 2147467264 bytes (2 GB-16KB).

PART_TBL Path of a text file that directs UniData where to create dynamic file part files.


Dynamic File udtconfig File Parameters (continued)


The following table describes parameters related to Journaling:

Journaling udtconfig File Parameters


JRNL_MAX_PROCS Maximum number of journal processes per journal path.

JRNL_MAX_FILES Maximum number of journal files allowed per journal process.

The following table describes UniBasic file-related parameters.

UniBasic File-Related udtconfig File Parameters


MAX_OPEN_FILE Maximum number of hashed files that can be opened by UniBasic OPEN statements, per udt process. Includes RFS and non-RFS, static, dynamic, and sequentially hashed files; each dynamic file counts as one file.

MAX_OPEN_SEQF Maximum number of sequential files that can be opened at one time by UniBasic OPENSEQ statements, per udt process.

MAX_OPEN_OSF Maximum number of UNIX sequential files that can be opened at one time by UniBasic OSOPEN statements, per udt process.

MAX_DSFILES Maximum number of nonrecoverable dynamic part files (dat00x, over00x) a UniData process can open with UniBasic OPEN statements or ECL commands. Each dynamic file has at least two part files.

3-13 Using UniAdmin

The following table describes parameters related to UniBasic.

UniBasic udtconfig File Parameters


MAX_CAPT_LEVEL Number of levels allowed for nested UniBasic EXECUTE WITH CAPTURING or MDPERFORM WITH CAPTURING clauses. Individual users can set an environment variable that overrides the configuration parameter.

MAX_RETN_LEVEL Number of levels allowed for nested UniBasic EXECUTE WITH RETURNING or MDPERFORM WITH RETURNING clauses. Individual users can set an environment variable that overrides the configuration parameter.

COMPACTOR_POLICY Used to guide BASIC memory compactor to do compaction for BASIC strings. 0 — compact when program is finished 1 — compact when EXECUTE (another BASIC pgm) is completed2 — compact when EXECUTE (another BASIC program) or CALL is completed

VARMEM_PCT The percentage of free memory that should be kept in the first global page for UniBasic variables after compacting. If the actual percentage is less than this value, UniData keeps one free global page. Otherwise, UniData returns all free global pages to UNIX.

The following parameter is used in semaphore operations.

Semaphore udtconfig File Parameters


NSEM_PSET Number of semaphores per semaphore set.


The following table describes index-related parameters.

Index udtconfig File Parameters


SETINDEX_BUFFER_ KEYS Controls whether READFWD and READBCK state-ments use a buffering mechanism. Default value is 0 (buffering off). Individual environment variable overrides udtconfig setting; BUFFER.KEYS keyword in the SETINDEX statement overrides either.

SETINDEX_VALIDATE_KEY Controls whether READFWD and READBCK state-ments validate a key value just read. Default value is 0 (no validation). Individual environment variable overrides udtconfig setting. VALIDATE.KEY keyword in the SETINDEX statement overrides either.

The following parameter is used with the UniData Physical Lock Manager.

Physical Lock Manager udtconfig File Parameters

Parameter name Description

MGLM_BUCKET_SIZE Number of nodes per bucket. If this parameter is inadequate for an application, an out of memory message is displayed.

UPL_LOGGING Determines if UPL performs logging. If this parameter is set to 0, UPL does not perform any logging. If this value is set to 1, UPL performs logging.

The following parameters affect the UniData _HOLD_ file.

Index udtconfig File Parameters


MAX_NEXT_HOLD_DIGITS Enables you to specify the number of digits used for the next _HOLD_ file number, found in the NEXT.HOLD record of D__HOLD.

CHECK_HOLD_EXIST Determines if UniData checks for the existence of a _HOLD_ file prior to unconditionally removing it when you specify the BANNER UNIQUE option with the SETPTR command.

3-15 Using UniAdmin

The following parameter is used to turn the Recoverable File System off and on.

Recoverable File System on/off udtconfig Parameter


SB_FLAG Toggles system buffer on and off. If zero, system buffer is off. Must be greater than zero for RFS.

The following parameters are related to open files with the Recoverable File System.

Recoverable File System udtconfig Parameters


BPF_NFILES Per-process logical limit for total number of RFS files that can be opened with UniBasic OPEN statements at one time. If more RFS files are opened, UniData closes files and then reopens them, causing heavy overhead. This parameter cannot exceed N_AFT.

N_PARTFILE Systemwide total number of recoverable dynamic part files that can be open at one time. This limit includes files opened by ECL and UniBasic. Each dynamic file has at least two part files, so opening a dynamic file means opening at least two part files. Even if more than one user opens the same dynamic file, each part file is counted once toward the total.

The following parameters are related to the active file table (AFT) used with the RFS.


N_AFT Systemwide limit on the number of recoverable files and indexes that can be open at one time. This is the number of slots in the system buffer AFT. Parameter is like MAX_OPEN_FILES but pertains only to recoverable files. A dynamic file counts as one file. Even if more than one user opens the same file, it is only counted once.

N_AFT_SECTION Number of sections in the AFT. Used for RFS only.

Active File Table udtconfig Parameters


The following table describes parameters related to the archiving feature of RFS.

Archiving udtconfig Parameters


ARCH_FLAG Toggles archiving function on and off for RFS. Must be greater than 0 for archiving.

N_ARCH The number of archive files.

ARCHIVE_TO_TAPE Switch for turning on automatic save of archive files to backup. Changing the value to 1 turns on this feature.

ARCH_WRITE_SZ Size, in bytes, of blocks for the archive process to write from the log files to the archive files. Default is zero, meaning each write is one block. If set to a non-zero value, must be a multiple of the log/archive block size.

The following parameters are used for the system buffer in the RFS.

System Buffer udtconfig File Parameters


N_BIG Number of block index groups. This parameter determines the size of an index table for accessing the RFS system buffer. If you enlarge N_PUT, you should enlarge N_BIG as well. Must be a prime number.

N_PUT Number of 1024-byte pages in the system buffer. The size of the buffer cannot exceed SHMMAX. Sometimes the default value of N_PUT must be decreased in order to complete a UniData installation.

N_AFT_BUCKET Number of hash buckets in the AFT. Used for RFS only.

N_AFT_MLF_BUCKET Number of hash buckets in the AFT for tracking multilevel files. Used for RFS only.

N_TMAFT_BUCKET Number of hash buckets in the active file table (TMAFT) for each tm process. Used for RFS only.


Active File Table udtconfig Parameters (continued)

3-17 Using UniAdmin

The following table describes parameters used for message queues with the Recov-erable File System.

Message Queue udtconfig File Parameters


N_PGQ Number of message queues for tm processes to send messages to udt processes. Calculated by installation; one queue for every four licenses.

N_TMQ Number of message queues for udt processes to send messages to tm processes. Calculated by installation; one queue for every four licenses.

On UniData for UNIX, the udt and tm processes communicate using message queues. Since message queues are not available on Windows platforms, UniData provides three options for the communication between the udt and tm processes. The following table describes these options:

UDT_TM_IPC udtconfig Parameter


UDT_TM_IPC ? UDT_TM_IPC=1 – UniData uses its own message queues to communicate between the udt and tm processes. If you change the value of the N_PGQ or N_TMQ udtconfig parameters, you must also change the value of the MSGMNI configuration parameter. The value of MSGMNI should be 12+N_PGQ+N_TMQ.

? UDT_TM_IPC=2 – UniData uses named pipes as the commu-nication mechanism between the udt and tm processes. Each udt process creates two named pipes, one for the udt process to write and the tm process to read, and one for the tm process to write and the udt process to read.

? UDT_TM_IPC=3 – UniData uses memory-mapped files and events to communicate between the udt and tm processes. Each udt process creates 2K memory-mapped files when it starts.


The following table describes parameters related to the before image and after image log files used with RFS.


N_AIMG Number of after image log files in each log set.

N_BIMG Number of before image log files in each log set.

AIMG_BUFSZ The size of the after image buffer, in bytes.

BIMG_BUFSZ The size of the before image buffer, in bytes.

AIMG_MIN_BLKS Minimum number of blocks required in the after image buffer before the system flushes the blocks to the after image logs. Block size is set in the log configuration table.

BIMG_MIN_BLKS Minimum number of blocks required in the before image buffer before the system flushes the blocks to the before image logs. Block size is set in the log configuration table.

AIMG_FLUSH_BLKS Number of blocks that are flushed to the after image logs from the after image buffer at one time.

Before Image/After Image udtconfig File Parameters

3-19 Using UniAdmin

The following table describes the parameters that determine flushing intervals for RFS.

Flushing Interval udtconfig File Parameters


CHKPNT_TIME Checkpoint interval: number of seconds between flushes of the system buffer to disk.

GRPCMT_TIME Interval, in seconds, between flushes to the after image log set.

LOG_OVRFLO Path to the directory where log overflow files are created.

BIMG_FLUSH_BLKS Number of blocks that are flushed to the before image logs from the before image buffer at one time.

RFS_DUMP_DIR Defines where UniData stores the rfs.dump file when you execute the s_stat -s command. The default value is an empty string, with UniData storing the rfs.dump file in the $UDTBIN directory. If the path you specify a path that is invalid when UniData starts, UniData writes the rfs.dump file to the $UDTBIN directory, and prints a message to the sm.log.

RFS_DUMP_HISTORY Specifies how many rfs.dump files to preserve when you execute the s_stat -s command.The default value is 1. With this value, UniData creates the rfs.dump file in the directory you specify with the RFS_DUMP_DIR parameter.If this value is set to a positive integer, for example 4, the rfs.dump files will be named rfs.dump1, rfs.dump2, rfs.dump3, and rfs.dump4. The s_stat -s command uses the first available rfs.dump file. If all rfs.dump files are full, s_stat -s reuses the oldest rfs.dump.file.If this value is set to 0, all rfs.dump files are preserved and named rfs.dump1, rfs.dump2, and so forth.


Before Image/After Image udtconfig File Parameters (continued)


The following table describes the parameters related to the sync daemon.

Sync Daemon udtconfig File Parameters


N_SYNC Determines how many sync daemons UniData should start.

SYNC_TIME Defines the number of seconds the sync daemon should wait before scanning the Block Index Group to flush dirty pages.

The following table describes the parameter related to the Century Pivot date.

Century Pivot udtconfig File Parameters


CENTURY_PIVOT Determines the century pivot date. Default is 1930.

The following table describes the parameters related to replication.


REP_FLAG Turns UniData Data Replication on or off. If this value is 0, UniData Data Replication is off. If this value is a positive integer, it is on.

TCA_SIZE The maximum number of entries in the Transaction Control Area. The default value is 2048.

MAX_LRF_FILESIZE The maximum Log Reserve File size, in bytes. The default value is 134217728 (128 MB). The maximum value is 2147483136.

N_REP_OPEN_FILE The maximum number of open replication log files for a udt or tm process. The default value is 8.

MAX_REP_DISTRIB Reserved for internal use.

MAX_REP_SHMSZ The maximum shared memory buffer segment size. The default value is 67108864 (64 MB).

udtconfig Parameters for Replication

3-21 Using UniAdmin

The following table describes the parameters related to Euro processing.

udtconfig Parameters for Euro Processing


CONVERT_EURO Turns Euro conversion on or off. If this flag is set to 0, UniData does not perform conversion. If this flag is set to 1, UniData performs conversion.

SYSTEM_EURO The configurable system Euro encoding. On UNIX systems, the default is CHAR(164). On Windows Platforms, the default is CHAR(128).

TERM_EURO Sets the terminal system Euro Code. On UNIX systems, the default is CHAR(164). On Windows Platforms, the default is CHAR(128).

REP_LOG_PATH The full path to the Replication log files..

UDR_CONVERT_CHAR When this value is set to 1, if the publishing system and the subscribing system have a different I18N group, UniData converts marks and SQLNULL marks to those on the local machine on the data passed between the two systems. The default value is 0.

REP_CP_TIMEOUT Specifies the cm daemon timeout interval for replication. The default value is 300 seconds. If this value is set to 0, the cm daemon will not time out.


udtconfig Parameters for Replication (continued)


4Chapter

Administering Devices through UniAdmin

Administering Tape Devices . . . . . . . . . . . . . . . 4-3 Modifying Tape Device Information . . . . . . . . . . . 4-4 Deleting a Tape Device . . . . . . . . . . . . . . . 4-4 Tape Devices on Windows Platforms . . . . . . . . . . . 4-4 Saving the Configuration . . . . . . . . . . . . . . . 4-4Administering Line Devices . . . . . . . . . . . . . . . 4-5 Creating a New Line Device Definition . . . . . . . . . . 4-6 Modifying Line Device Information . . . . . . . . . . . 4-6 Deleting a Line Device Definition . . . . . . . . . . . . 4-6 Saving the Line Device Information . . . . . . . . . . . 4-7

This chapter describes how to configure and administer tape and line devices through UniAdmin.

Select one of the following methods to access the Maintain UniData Devices dialog box:

From the UniAdmin window, double-click Devices then select Tapes in the Device Type area.From the UniAdmin menu, click Admin, then click Devices, then select Tapes in the Device Type area.

A dialog box similar to the following example appears:

4-2

Administering Tape DevicesTo enter a new tape device, click New. The New tape device dialog box appears, as shown in the following example.

You can define up to 10 tape units for the UniData environment. The tape unit number must be within the range 0-9.

In the ID box, enter the ID of the tape device you are defining.

In the DevicePath box, enter the path and device name of the “no rewind” device drive for the tape unit, or click Browse to search for the device. If you are defining the device on UniData for Windows Platforms, you must specify the drive in the UNC format if the device is a tape drive.

In the RewindPath box, enter the path and name of the “rewind” device driver for the unit you are defining, or click Browse to search for the device. If you are defining the device on UniData for Windows Platforms, you must specify the drive in the UNC format if the device is a tape drive. If you are using a disk file, you may identify it by its path and file name. The disk file must already exist.

In the Block Size box, select or enter the block size in bytes. The block size must be a multiple of 512.

Note: When defining tape units, be certain to define unit 0. Some of the UniData tape handling commands require unit 0 to be defined so that it can be used as a default.

4-3 Using UniAdmin

Modifying Tape Device InformationIf you want to modify information for a tape device already appearing in the list, click the device that you want to modify, then click Detail. Make appropriate changes, and then click OK to save your changes, or Cancel to exit without saving changes.

Deleting a Tape DeviceIf you want to delete a tape device definition from the list, click the device definition you want to delete, and then click Delete.

Tape Devices on Windows PlatformsOn UniData for Windows Platforms, setting tape devices through the Maintain UniData Devices dialog box establishes a link between a UniData internal tape unit number and an NTFS tape device. You can use SETTAPE to relate unit number to tape devices, or to NTFS or FAT disk files.

Saving the ConfigurationSaving the tape configuration creates an editable ASCII file located in udthome/sys/tapeinfo on UniData for UNIX and udthome\sys\tapeinfo on UniData for Windows Platforms.

Note: To initialize or update a pointer to a tape unit, you must log on as root on UniData for UNIX or as Administrator on UniData for Windows Platforms.

Administering Tape Devices 4-4

Administering Line DevicesUniAdmin enables you to initialize a communication line for use during the current UniData session.

Note: To initialize a line, you must log on as root on UniData for UNIX or Administrator on UniData for Windows Platforms.

Select one of the following methods to access the Line Device Config dialog box:

From the UniAdmin window, double-click Devices, and then select Lines in the Device Type area.From the UniData Admin menu, click Manage, then select Devices, and then click Line.

The Line Device Config dialog box appears, as shown in the following example:

4-5 Using UniAdmin

Creating a New Line Device DefinitionTo define a new line device, select Lines, then click New. The New line device dialog box appears, as shown in the following example:

In the ID box, enter a line number from 0 to 499 of a device to be initialized.

In the DevicePath box, enter one of the following:

On UniData for UNIX, path and name for the physical device, for instance, /dev/tty01. On UniData for Windows Platforms, identifier for a serial device, for instance, COM1.

Click OK to add the line device definition, or click Cancel to exit without saving changes.

Modifying Line Device InformationIf you want to modify information for a line device already appearing in the list, click the line device that you want to change, then click Detail. Make appropriate changes, then click OK to save your changes, or click Cancel to exit.

Deleting a Line Device DefinitionIf you want to delete a line device definition from the list, click the device definition you want to delete, and then click Delete.

Administering Line Devices 4-6

Saving the Line Device InformationSaving the line configuration creates an editable ASCII file located in udthome/sys/lineinfo on UniData for UNIX and udthome\sys\lineinfo on UniData for Windows Platforms.

4-7 Using UniAdmin

5Chapter

Viewing Disk Space Usage

This chapter describes how to display file system disk usage through UniAdmin.

Select one of the following methods to access the File System Usage dialog box:

From the UniData Admin window, double-click Disk Space.From the UniAdmin menu, click Admin, then click Disk Space.From the UniAdmin toolbar, click the Show Disk Space Information icon, as shown in the following example.

Show Disk Space Information

The File System Usage dialog box appears, as shown in the following example:

5-2 Using UniAdmin

6Chapter

Using UniData File Tools

File Checking Tools . . . . . . . . . . . . . . . . . . 6-3 The guide Utility . . . . . . . . . . . . . . . . . 6-3 The verify2 Utility . . . . . . . . . . . . . . . . . 6-7 The filever Utility . . . . . . . . . . . . . . . . . 6-9 The checkover Utility . . . . . . . . . . . . . . . . 6-11File Repair Tools . . . . . . . . . . . . . . . . . . . 6-14 The fixfile Utility . . . . . . . . . . . . . . . . . 6-14 The dumpgroup Utility . . . . . . . . . . . . . . . 6-18 The fixgroup Utility . . . . . . . . . . . . . . . . 6-20File Conversion Tools . . . . . . . . . . . . . . . . . 6-23 The memresize Utility. . . . . . . . . . . . . . . . 6-23 The convdata Utility . . . . . . . . . . . . . . . . 6-26 The convcode Utility . . . . . . . . . . . . . . . . 6-27 The convmark Utility . . . . . . . . . . . . . . . . 6-28 The convidx Utility . . . . . . . . . . . . . . . . 6-31 The udfile Utility . . . . . . . . . . . . . . . . . 6-32 The shfbuild Utility . . . . . . . . . . . . . . . . 6-34

The chapter describes how to use UniData file tools from UniAdmin. The following file tools are available:

File Checking Toolsguide – analyzes hashed files, generates statistics, and provides sugges-tions for optimizing file sizes and ensuring data integrity.filever – displays whether a file is high-byte or low-byte, recoverable or nonrecoverable, static or dynamic.checkover – list files in the current account that are in level 2 overflow, and reports the number of groups that have overflowed.

File Repair Toolsfixfile – repairs a damaged group in a UniData file by extracting and reloading readable records.fixgroup – reloads a single hashed file group from the output file generated by dumpgroupdumpgroup – extracts readable records from a specified group in a UniData file.

File Conversion Toolsmemresize – resizes a hashed file in size, modulo, block size, or hashing algorithm. memresize also converts between static and dynamic hashed files and changes the split/merge type and the part table for dynamic files.convdata – converts UniData hashed data files from Motorola 68000 internal integer format to Intel 386 internal integer format.convcode – converts UniData object files from Motorola 68000 internal integer format to Intel 386 internal integer format.convmark – searches for and converts ASCII values in UniData files.convidx – converts UniData index files from Motorola 68000 internal integer format to Intel 386 internal integer format.udfile – converts a UniData file to or from recoverable.shfbuild – creates a sequentially hashed file by converting an existing dynamic or static file.

6-2

File Checking ToolsYou can access the file checking tools in one of the following ways:

From the UniAdmin window, double-click File Tools. From the UniAdmin menu, click Admin, then click File Tool.From the UniData Admin toolbar, click the File Tools icon, as shown in the following example:

File Tools Icon

The guide UtilityThe guide utility analyzes hashed files, generates statistics, and provides suggestions for optimizing file sizes and ensuring data integrity. UniData must be running when you execute guide.

By default, the guide utility produces the following reports:

Management adviceFile errorsDetailed statisticsDamaged groups

6-3 Using UniAdmin

To access the guide utility, double-click the account where you want to run guide, then click the file you want to run guide against, then select Guide from the File menu, or use the right mouse button (right-click) and select Guide. A dialog box similar to the following example appears:

To begin running guide, click Start. A dialog box similar to the following example appears:

File Checking Tools 6-4

guide Options

By default, guide creates the GUIDE_ADVICE.LIS, GUIDE_ERRORS.LIS, and GUIDE_STATS.LIS. If you want to change the files that guide produces by default, select or clear the appropriate option from the guide Options dialog box.

The following section describes each guide option:

Advice file – Provides advice for improving file sizing or cleanup. The default name for this file is GUIDE_ADVICE.LIS.Brief summary – Summarizes record counts, total size, used size, and modulo.Error file – Reports statistical errors in the file name you specify. Default output file name is GUIDE_ERRORS.LIS.Fixup file – Reports damaged groups in the file name you specify. Default output file name is GUIDE_FIXUP.DAT.Input file – Analyzes all files listed in a file that you create on the server. Default file name is GUIDE_INPUT.DAT. In this file, list one file name per line. UniData ignores blank lines and lines beginning with !.Stat level – Reports on file size. 1 summarizes file size information. 2 reports file size information. 3 adds information about distribution of data sizes.Hash Type – Evaluates hashing algorithms for hash types 0 or 1. Select “a” to evaluate both hash types. Use in conjunction with Modulo check.# large rec – Displays keys of the largest records.Modulo check – Analyzes the effects a different modulo would have on the filename you specify. Must be used with Hash type.Output file – Combines output in filename, rather than placing it in separate files. If you do not specify a file name, sends combined output to the File Tools window. Report file – Directs output to a system-level file name you specify. The file must already exist. Copy the dictionary for the file name you specify from udthome/sys/D_UDT_GUIDE on UniData for UNIX or udthome\sys\D_UDTGUIDE on UniData for Windows Platforms. Later, you can execute UniQuery commands against the file name.# small rec – Displays keys of the smallest records in the file.Stats file – Displays detailed statistics about the file.

6-5 Using UniAdmin

Suppress – Suppresses output based on the parameter you chose.a – No management advice is reported.b – No summary report is generated.e – No detailed error report is generatedp – Scrolls output with no pagination.s – No detailed statistical report is generated.

Click OK to return to the guide window, or click Cancel to exit without saving changes.

For detailed information about using guide to assess file damage and to manage file integrity, see Administering UniData on UNIX or Administering UniData on Windows Platforms.

Note: You must have read and write permissions on the files guide analyzes.

Output Reports

Depending on the parameter you include, guide may create any or all of the following reports. If any of these output files exist when you execute guide, UniData changes all output file names by appending a six-digit time stamp to each file name. This way, only the most current output files have no time stamp; and if a particular output file is not created during this execution, no file of that name exists.

However, if you run multiple iterations of guide from the same directory when using the default output file names, each iteration will overwrite each other’s output files. You must use the guide options to create unique file names, or only run one instance of guide per directory at one time to avoid this behavior.

Report Default File NameParameter Description

File management advice

GUIDE_ADVICE.LIS -a Provides advice for improving file sizing or cleanup.

File errors GUIDE_ERRORS.LIS -e Lists structural errors.

guide Output Files


For examples of the reports described in the previous table, see the UniData Commands Reference.

The filever UtilityThe filever utility displays the following information about UniData files:

high-byte or low-byte (also provided by the system-level filever command) recoverable or nonrecoverable static or dynamic

Detail GUIDE_STATS.LIS -s Details statistics on filename.

Summary GUIDE_BRIEF.LIS -b Summarizes record counts, total size, used size, and modulo.

Damaged groups

GUIDE_FIXUP.DAT -f Lists damaged groups. This file can be used as input for ECL commands, fixfile, dumpgroup, and fixgroup.

Report Default File NameParameter Description

guide Output Files (continued)

6-7 Using UniAdmin

To access the filever utility, double-click the account where you want to run filever, then click the file you want to run filever against, then select Filever from the File menu, or right-click and select Filever. A dialog box similar to the following example appears:

To begin running the filever utility, click Start.


The following example illustrates output from the filever utility:

The checkover UtilityThe checkover utility lists files in the account you specify that are in level 2 overflow. This utility also reports the number of groups that have overflowed.

Static hashed files are divided into a specific number of groups (the file modulo). When you first write data to the file, UniData stores IDs and data in the same file block. When the block becomes full of data, level 1 overflow occurs and data is written to a second block. If enough records are written to the same block, the primary keys also overflow — this is level 2 overflow.

Tip: Your system administrator should run this command for each UniData account and periodically resize files for optimal system performance.

6-9 Using UniAdmin

To access the checkover utility, double-click the account where you want to run checkover, then click the file you want to run checkover against, then select Checkover from the File menu, or right-click and select Checkover. A dialog box similar to the following example appears:


To begin running the checkover utility, click Start. The following example illustrates output from the checkover utility:

6-11 Using UniAdmin

File Repair ToolsYou can access the file checking tools in one of the following ways:

From the UniAdmin window, double-click File Tools. From the UniAdmin menu, click File Tools.From the UniData Admin toolbar, click the File Tools icon, as shown in the following example:

File Tools Icon

The fixfile UtilityThe fixfile utility repairs a damaged group in a UniData file by extracting and reloading readable records. You can specify as input a file created by the guide utility.

UniData operates differently depending on whether the file is static or dynamic, and whether one group is damaged or multiple groups are damaged. For detailed infor-mation about using fixfile to repair damaged groups, see Administering UniData on UNIX or Administering UniData on Windows Platforms.

To repair files, you must include the Dump info file and Fix corruption options.

Warning: Do not let users access UniData files when fixfile is fixing them — you could lose records.

File Repair Tools 6-12

To access the fixfile utility, double-click the account where you want to run fixfile, then click the account or file you want to run fixfile against, then select Fixfile from the File menu, or right-click and select Fixfile. A dialog box similar to the following example appears:

6-13 Using UniAdmin

fixfile Options

This section describes the options available with the fixfile utility. To specify an option, click Options. The following dialog box appears:

Output file – For each readable record, UniData creates an ASCII file in a directory in the current UniData account. UniData also takes the following actions for static and dynamic files:

Static files – Stores readable records in (uneditable) outputfile.Dynamic files – Stores readable records in (uneditable) outputfile and in a subdirectory in the /tmp directory named filename_groupno on UniData for UNIX, or in the \TEMP directory on UniData for Windows Platforms.


Input dump file – The file containing names of files and groups to be repaired. inputfile is produced by the guide command. If you did not designate inputfile with guide, fixfile reads damaged file and group names from the GUIDE_FIXUP.DAT file in the directory you specify. For infor-mation about the format of this file, see the UniData Commands Reference.

Message file – Writes error messages and statistics to the messagefile instead of the terminal.Working directory – Specifies directory for storing work files.Fix corruption – Clears damaged groups. You must combine this option with the Dump info file or the Display only options.Do not clear group – Does not clear records before reloading them, so that damaged records are retained in the file. You must combine this option with the Output file or Fix corruption options. To copy readable records to another file, include the Do not clear group and the Output file options. To copy readable records to another file and return them to the file, include the Do not clear group, the Output file, and the Fix corruption options.Display only – Record key and the record length are reported for each readable record. Directs output to the terminal only. All attributes in the record are listed, indented by two spaces. In the display, UniData delim-iters and nonprinting characters are represented as follows:Attribute mark – New lineValue mark – “}”Subvalue mark – “|”Text mark – “{“Nonprinting – “.”Convert non-printable – Combine with the Output file option to convert UniData delimiters and nonprinting characters in the ASCII files as follows:Attribute mark – New lineValue mark – “}”Subvalue mark – “|”Text mark – “{“Nonprinting – “.”

6-15 Using UniAdmin

Select the check box for the options you want, then click OK to return to the fixfile dialog box, or click Cancel to exit the fixfile Options dialog box without saving changes.

Executing fixfile

In the Directory box, enter the full path of the directory where you want to execute fixfile, or click Browse to choose the account.

If you want to execute fixfile against a specific file and group, enter the name of the file in the File box, and then enter the group number in the Group box.

Note: If you specify a file name, you must also specify a group number.

Click Run to execute fixfile, or Exit to exit the program without saving changes. When fixfile is running, you can click Cancel to stop the program.

The dumpgroup UtilityThe dumpgroup utility extracts readable records from a specified group in a UniData file. If the file is corrupt, dumpgroup unloads only the complete, valid records, leaving behind any information it cannot read.

If you execute dumpgroup without specifying an output file, the output simply displays on the screen. You will not be able to use that output to verify records or repair the damaged group. If you do specify an output file, dumpgroup extracts readable records in uneditable form, suitable for reloading. The dumpgroup utility also creates a directory in the /tmp directory on UniData for UNIX or the \TEMP directory on UniData for Windows Platforms for each dumped group. The directory is named FILE_GROUP, where FILE and GROUP are the filename and group number you specified. This directory contains an ASCII file for each record, so that you can check them for consistency before reloading the damaged file.


From the File Tools window, click dumpgroup. A window similar to the following appears:

dumpgroup OptionsTwo options are available with the dumpgroup utility. To select an option, click Start. The following dialog box appears:

6-17 Using UniAdmin

If you want to direct the output from the dumpgroup utility to an output file, select the Dump info file option. The output file that contains the readable records from the dumped group. You cannot edit this file. If you do not select this option, the dumpgroup utility displays readable records on the display screen. The output file is the input file for the fixgroup utility.

Warning: Make sure outputfile is not the name of another item in your account. If it is, UniData will overwrite it.

If you want to convert nonprinting field markers to printable characters in outputfile, select the Convert non-printable check box. This option makes outputfile editable. You must also select the Dump info file check box if you want to use this option.

Click Run to execute dumpgroup, or Cancel to exit the program without saving changes.

The fixgroup UtilityThe fixgroup utility reloads a single hashed file group from the output file generated by the dumpgroup utility.


From the File Tools window, click fixgroup. A dialog box similar to the following appears:

Enter the group number you want to fix in the Group box.

fixgroup OptionsTwo options are available with the fixgroup utility. To select an option, click Start. The following dialog box appears:

6-19 Using UniAdmin

If you want to use the inputfile generated by the dumpgroup utility, select the Input dump file check box. If you do not select this option, UniData clears the group you specify without reloading it.

If you want to reload damaged records from inputfile without clearing the group first, select the Do not clear group check box. This option may be useful if the group has updated since dumpgroup was executed.

Select the check boxes for the options you want, and then click OK to execute fixgroup, or Cancel to exit the program without saving changes.

Warning: If you run fixgroup without including an input file (using the -i parameter), UniData clears the damaged group and leaves it empty. Be sure that you have previ-ously saved the readable records with the dumpgroup command. If you clear the damaged group and you have not saved the readable records, the data in that group is lost.


File Conversion ToolsYou can access the file conversion tools in one of the following ways:

From the UniData Admin window, double-click File Tools, and then double-click File Repair Tools. From the UniData Admin menu, click Tools, select File Repair, and then click the tool you want to run.From the UniData Admin toolbar, click the File Tools icon, as shown in the following example:

File Tools Icon

The memresize UtilityThe memresize utility resizes a hashed file in size, modulo, block size, or hashing algorithm. You can also use this utility to convert between static and dynamic hashed files and change the split/merge type and the part table for dynamic files. The memresize utility operates in an internal memory buffer and writes to disk only when the buffer becomes full or when the memresize operation completes.

6-21 Using UniAdmin

Select the file you want to resize, then click Memresize from the File menu, or right-click the file and select Memresize. A dialog box similar to the following appears:

memresize Options

To access the options available with the memresize utility, click Start. A dialog box similar to the following appears:

File Conversion Tools 6-22

The following section describes each memresize option:

Modulo – The new modulo number to be assigned to the file you specify.Temp file path – The path where UniData locates a working copy of the file during resizing. The default is /tmp on UniData for UNIX or \TEMP on UniData for Platforms. This option has no effect if the resulting file is a dynamic file.Memory – Size in kilobytes of memory buffer used for the operation. memresize may perform faster with a larger memory allocation. The minimum size is 256 K. The default on most systems is 8000 K (8 MB). You can assign as much memory as is available on your system. For example, 12000 assigns 12 MB of memory to the memresize process.Block factor – An integer between 0 and 16 that UniData uses to determine file size. Hash type – Hash type for the resized file. Click the Hash type arrow to select the hash type to be assigned to the file you specify.Part file – If the file is a dynamic file after resizing, part_tbl is the path and filename of a previously established part table. memresize copies part_tbl into the dynamic file directory. The copy of part_tbl in the dynamic file directory serves as the “per-file” part table for the dynamic file. The option is supported on UniData for UNIX only.Dictionary – Select this check box if you want to resize the dictionary portion of the file name you specify.Restore – Select this check box if you want to skip over file corruption that cannot be fixed, but continue resizing the file. Use this option when a file must be restored regardless of corruption.Dynamic – If you select this option, the filename you specify will be a dynamic file after resizing.Static – If you select this option, the filename you specify will be a static hashed file after resizing.Key only – After resizing, the file is dynamic and the split/merge type is KEYONLY.Key and data – After resizing, the file is dynamic and the split/merge type is KEYDATA.

Select the options you want to use with the memresize utility, and then click OK to run memresize, or Cancel to exit.

6-23 Using UniAdmin

The convdata UtilityThe convdata utility converts UniData hashed data files from Motorola 68000 internal integer format to Intel 386 internal integer format. Format information is embedded within the file header. This command automatically determines if files match the present machine integer format. If files do not need to be converted, UniData displays a message that no data files were converted.

Select the file you want to convert, then click Convdata from the File menu, or right-click the file and select Convdata. A dialog box similar to the following appears:


convdata Options

To access the options available with the convdata utility, click Start. A dialog box similar to the following appears:

If you want to process subdirectories recursively, select the Convert sub-directories check box. Click OK to return to the convdata dialog box. Click Cancel to exit the dialog box without saving changes.

Click Run to execute convdata, or Cancel to exit the program without saving changes.

The convcode UtilityThe convcode utility converts UniData object files from Motorola 68000 internal integer format to Intel 386 internal integer format. Format information is embedded within the file header. This command automatically determines if object files match the present machine integer format. If files do not need to be converted, UniData displays a message that no files were converted.

You can run convcode more than once on a UniData file to convert between the two formats.

6-25 Using UniAdmin

Select the file you want to convert, then click Convcode from the File menu, or right-click the file and select Convcode. A dialog box similar to the following appears:

Click Start to execute convcode, or Close to exit the program without saving changes.

The convmark UtilityThe convmark utility searches for and converts ASCII values in UniData files.The new value must be one that is not contained in the file to be converted.

Based on the option selected, UniData does one of the following:

Displays the number of occurrences of a particular ASCII value.Counts the number of UniData delimiters in files.Converts a single ASCII character (ASCII values 128 – 255 only).Converts the UniData delimiters for your language group. (Be sure you have changed the language group with the udtlangconfig command. For instruc-tions, see UniData International.)


convmark Constraints

You cannot use the convmark command to convert in the following conditions:

If your source file contains the new ASCII values — the ones to which you are attempting to convert — no data in the file is converted. UniData instead returns a message indicating that the data already contains the new mark. This does not mean that the file has been converted or that it does not require conversion. You must review and change the records manually.On UniData for UNIX, directories indicated by path1, and so forth, cannot contain any UNIX links (created with the UNIX ln command). If they do, convmark produces an error message and aborts.

Select the file you want to convert, then click Convmark from the File menu, or right-click the file and select Convmark. A dialog box similar to the following appears:

6-27 Using UniAdmin

convmark Options

To access the options available with the convmark utility, click Options. A dialog box similar to the following appears:

Test only – For use in test mode. Returns the number of files in the directory you specify that need to be converted, but does not convert them. You can combine this option with any other options.Language group ID – The language group ID is made up of the ASCII values that represent the record mark, the cursor control escape sequence, and the null value for that language group:

159/130/129 French, Japanese, and English255/192/129 English

Old value – Used without the new value option, counts the occurrences of new_value. Used with the new value option, converts from old_value. Must be a single ASCII value from 128 through 255.New value – Replacement value. Must be a single ASCII value from 128 through 255.

Select the options you want to use with the convmark utility, and then click OK to return to run convmark. Click Cancel to exit the dialog box without saving changes.


The convidx UtilityThe convidx utility converts UniData index files from Motorola 68000 internal integer format to Intel 386 internal integer format. Format information is embedded within the file header. This command automatically determines if files match the present machine integer format. If files do not need to be converted, UniData displays a message to that effect.

You can run convidx more than once on a UniData file.

Static index files have a prefix of X_. Dynamic index files are named “idx001, idx002...”. See Using UniData for more information about working with index files and alternate key indexes.

Select the file you want to convert, then click Convidx from the File menu, or right-click the file and select Convidx. A dialog box similar to the following example appears:

6-29 Using UniAdmin

convidx Options

To access the options available with the convidx utility, click Options. A dialog box similar to the following appears:

If you want to process subdirectories recursively, select the Convert sub-directories check box. Click OK to return to the convidx dialog box. Click Cancel to exit the dialog box without saving changes.

Click Run to execute convidx, or Exit to exit the program without saving changes.

The udfile UtilityThe udfile utility converts a UniData file to or from recoverable. If you enter this udfile without options, UniData displays the type of file (recoverable or nonrecov-erable). You cannot convert the file type while UniData is running.

You must have root permission the change a file to or from recoverable.

The udfile command will not convert files that were created in 1/2-K blocks. If you attempt to do so, UniData generates an error message indicating that the file cannot be converted to recoverable. You must resize the file to at least a 1-K block size using the RESIZE command or the memresize command. Or, you can create a new file with at least a 1K block size, then copy the contents of the old file into the new one using the ECL COPY command. For details about converting files to recoverable with udfile, see Administering the Recoverable File System.


Select the file you want to convert, then click Udfile from the File menu, or right-click the file and select Udfile. A dialog box similar to the following appears:

udfile Options

To access the options available with the udfile utility, click Start. A dialog box similar to the following appears:

If you want to change a nonrecoverable file to a recoverable file, click Change to recoverable file.If you want to change a recoverable file to a nonrecoverable file, click Change to non-recoverable file.

6-31 Using UniAdmin

If you want to display whether a file is recoverable or nonrecoverable, click Display current file status.

Select the options you want to use with the udfile utility, and then click OK to run udfile. Click Cancel to exit the dialog box without saving changes.

The shfbuild UtilityThe shfbuild utility converts an existing UniData static or dynamic file to a sequen-tially hashed file.

A sequentially hashed file has the same structure as a dynamic file, but all records are stored sequentially based on the primary key. The modulo (number of groups) for a sequentially hashed file is fixed, it does not grow and shrink as records are added or deleted.

Sequentially hashed files are created by converting from existing UniData static or dynamic files. You specify a percentage of the file that you want to remain empty to allow for growth. Although the structure for a sequentially hashed file is the same as a dynamic file, the modulo is fixed.

A sequentially hashed file is used for files where the majority of access is based on the primary key.

For more information about sequentially hashed files, see Administering UniData.


Select the file you want to convert, then click Shfbuild from the File menu, or right-click the file and select Shfbuild. A dialog box similar to the following appears:

6-33 Using UniAdmin

shfbuild Options

To access the options available with the shfbuild utility, click Start. A dialog box similar to the following appears:

The following table describes the shfbuild options.

Parameter Description

-a Only rebuild the last group of the sequentially hashed file. UniData splits the last group into groups according to the records in the group. If you use this option, the outfile should be the name of the sequentially hashed file. Do not specify infile.

-k Build the gmekey file only. If you use this option, outfile should be the name of the sequentially hashed file. Do not specify infile. UniData rebuilds the gmekey file according to the keys in each group of outfile.

-n/-t Force the outfile to be in numeric or alphabetic order. By default, the order of outfile is determined by the infile primary key type. If infile is a sequen-tially hashed file, UniData uses the same order in outfile. If infile is not a sequentially hashed file, the order of outfile is determined by the justifi-cation of the @ID of the infile dictionary record. If it is right justified, it is numeric. Otherwise, it is alphabetic. If you use the -a or the -k option, these options have no effect.

-f Force outfile to truncate before being built.

shfbuild Parameters


-m Specifies the new modulo of outfile.

-e Empty percent. This is a number between 0 and 99 which indicates how much space in the rebuilt groups to reserve. UniData calculates the new modulo of the file from empty_percent and the number of records in the rebuilt groups. If you do not specify -e or -m, UniData rebuilds the sequen-tially hashed file according to the default empty percent of 20.

-b Specifies the block size of the sequentially hashed file in kilobytes.

-i infile Load the contents from infile instead of outfile. infile can be any type of UniData file.

outfile The name of the output file.


shfbuild Parameters (continued)

6-35 Using UniAdmin

7Chapter

Licensing UniData

Licensing UniData . . . . . . . . . . . . . . . . . . 7-3 Types of UniData Licenses . . . . . . . . . . . . . . 7-3Obtaining an Authorization Code . . . . . . . . . . . . . 7-4

This chapter describes the configuration options available through UniAdmin, including:

Licensing UniData and layered products.Setting udtconfig parameters.Configuring UniRPC ServicesAdministering databases.Configuring ObjectCall servers.Administering ObjectCall databases.

7-2 Using UniAdmin

Licensing UniDataThe 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. The maximum number of concurrent sessions allowed from a single device is ten. After connecting ten sessions, you can start another session, but it will consume a full UniData license.

Device licensing is available on the UniData Workstation, Workgroup, and Enter-prise editions.

Licensing UniData 7-3

Obtaining an Authorization CodeSelect 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 License.


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

If the number of users displayed in the UniData RDBMS box does not agree with your Product Configuration sheet, click this box and enter the correct number of users.

In the Connection Pooling box, enter the number of connections from the client to the server for which you are licensed.

In the Device License box, enter the number of device licenses for which you are authorized. The maximum value is 10.

7-4 Using UniAdmin

Review the layered products selected in the Configure UniData 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 autho-rized to use, click the check box next to the appropriate product to clear it.

Enter Expiration Date

Enter 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.

Update the Configuration

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

Obtain Configuration Code

Click ConfigCode to obtain the configuration code you will need to authorize UniData. A window similar to the following appears:

Authorize UniDataObtain an authorization code from the IBM website at http://www-306.ibm.com/software/data/u2/unidata/support/. Click Register Your Product, then follow the instructions on the screen.

Obtaining an Authorization Code 7-5

8Chapter

Monitoring UniData Locks

Displaying File/Record Locks. . . . . . . . . . . . . . . 8-3 File/Record Locks Display . . . . . . . . . . . . . . 8-3 Clearing a Lock . . . . . . . . . . . . . . . . . . 8-4Displaying System Resource Locks . . . . . . . . . . . . . 8-5 Clearing a Lock . . . . . . . . . . . . . . . . . . 8-6Displaying the Lock Waiting Queue . . . . . . . . . . . . . 8-7

This chapter describes the tools available from UniAdmin to monitor locks.

You can access the locking tools in one of the following ways:

From the UniAdmin window, double-click Locks. From the UniAdmin menu, click Admin, and then click Locks.From the UniAdmin toolbar, click the Lock icon, as shown in the following example:

Lock Icon

8-2

Displaying File/Record LocksWhen you click the File/Record Locks tab, a window similar to the following appears:

The Lock Administration window displays a list of file and record locks on the server.

File/Record Locks DisplayThe following table describes the column headings of the File/Record Locks window.

8-3 Using UniData Admin

Tip: To increase or decrease the size of a column, place the cursor on the line to the right of the column heading you want to change until the cursor becomes a double-headed arrow, then click the mouse button and drag to the proper size.

File/Record Lock Column Headings

Column Heading Description

UNO The sequential number UniData assigns to the udt process that set the lock.

UNBR The process ID of the user who set the lock.

UID The user ID of the user who set the lock.

UNAME The log on name of the user who set the lock.

TTY The terminal device of the user who set the lock.

FILENAME The file name in which the record is locked.

INBRH The high integer of the inode of the file holding the lock, on UniData for Windows Platforms only.

INBR The inode of the locked file. On UniData for Windows Platforms, this is the low integer of the inode of the file holding the lock.

DNBR Used in conjunction with INBR to define the file at the operating system level.

RECORD ID The record ID of the locked record.

M The type of lock. X indicates an exclusive lock. S indicates a shared lock.

TIME The time at which the lock was set.

DATE The date on which the lock was set.

To refresh the display, click Refresh.

Clearing a LockTo clear a lock displayed in the window, select the lock you want to clear, and then click Clear Lock.

Displaying File/Record Locks 8-4

Displaying System Resource LocksThe System Resource Locks window displays semaphore-type locks that reserve system resources for exclusive use. These locks can be set individually with the LOCK command. They are also set by other UniData commands, including T.ATT.

Click the System Resource Locks tab from the Lock Administration window. A window similar to the following appears:

The following table describes the column headings of the System Resource Locks window.



System Resource Locks Column Headings


UNO Sequential number UniData assigns to the UniData session.

UNBR Process group ID (pid) of the user setting the lock.

UID User ID of the user setting the lock.

UNAME Login name of the user setting the lock.

FILENAME File name in which the record is locked.

INBR I-node of the locked file on UniData for UNIX only.

DNBR Used in conjunction with INBR to define the file at the operating system level on UniData for UNIX only.

TTY Terminal device of the user setting the lock.

RECORD ID Record ID of the locked record.

M Record lock mode.

TIME The time at which the lock was set.

DATE The date on which the lock was set.


Clearing a LockTo clear a lock displayed in the window, select the lock you want to clear, and then click Clear Lock.

Displaying System Resource Locks 8-6

Displaying the Lock Waiting QueueThe Lock Waiting Queue window lists processes that currently waiting for locks. If a process is waiting for a lock, this window displays information about the holder of the lock and processes waiting for the lock. Locks are set by each udt process through the General Lock Manager (GLM) module.

UniBasic commands that check for locks, such as READU and READVU, cause processes to wait for locks to be released before proceeding.

Click the Lock Waiting Queue tab from the Lock Administration window. A window similar to the following appears:

Information about the owner of the lock is listed above the line. Information about processes waiting for the lock is listed below the line, sorted by the date and time the process requested the lock.


The following table describes the column headings that display in the output for the Lock Waiting Queue window for the owner of the lock.


Lock Waiting Queue Owner Display


FILENAME The name of the file holding the lock.

RECORD ID The record ID holding the lock.

M The type of lock held. X is an exclusive lock, S is a shared lock.

OWNER The user name of the owner of the lock.

UNBR The process group ID (pid) of the user who set the lock.

UNO The sequential number UniData assigns to the udt process for the owner of the lock.

TTY The Terminal device of the user owning the lock.

TIME The time the lock was set.

DATE The date the lock was set.

The next table describes the Lock Waiting Queue window column headings for the processes waiting for locks.


FILENAME The name of the file for which a lock is requested.

RECORD ID The record ID of the record for which a lock is requested.

M The type of lock held. X is an exclusive lock, S is a shared lock.

OWNER The user name of the process waiting for a lock.

UNBR The process group ID (pid) of the user who waiting for the lock.

UNO The sequential number UniData assigns to the udt process waiting for the lock.

Lock Waiting Queue Waiting Display

Displaying the Lock Waiting Queue 8-8


TTY The terminal device of the user waiting for the lock.

TIME The time the lock was requested.

DATE The date the lock was requested.


Lock Waiting Queue Waiting Display (continued)


9Chapter

Administering Network Services

Administering Databases . . . . . . . . . . . . . . . . 9-3 Adding a Database . . . . . . . . . . . . . . . . . 9-4 Updating a Database . . . . . . . . . . . . . . . . 9-5 Deleting a Database . . . . . . . . . . . . . . . . 9-5 Viewing a Database . . . . . . . . . . . . . . . . 9-6Administering NFA Servers . . . . . . . . . . . . . . . 9-7Administering the UDSerial Server . . . . . . . . . . . . . 9-15 Service Option . . . . . . . . . . . . . . . . . . 9-16 Starting, Stopping, and Pausing the Telnet Server . . . . . . . 9-17 Port Configuration . . . . . . . . . . . . . . . . . 9-17 Control Keys . . . . . . . . . . . . . . . . . . 9-21 Modem Options. . . . . . . . . . . . . . . . . . 9-22 Logon Script. . . . . . . . . . . . . . . . . . . 9-24 Auto Connection . . . . . . . . . . . . . . . . . 9-25Administering the UDTelnet Service . . . . . . . . . . . . 9-27 Service Options . . . . . . . . . . . . . . . . . . 9-29 User Profiles. . . . . . . . . . . . . . . . . . . 9-32 Customizing User Profiles . . . . . . . . . . . . . . 9-35 Generated Profiles . . . . . . . . . . . . . . . . . 9-39 Starting, Stopping and Pausing UDTelnet. . . . . . . . . . 9-40Monitoring UniData Services . . . . . . . . . . . . . . . 9-42 Starting UniData Services . . . . . . . . . . . . . . 9-42 Stopping UniData Services . . . . . . . . . . . . . . 9-42

This chapter describes the network services that you can administer through UniAdmin, including:

Configuring UniRPC ServicesAdministering databasesAdministering NFA serversAdministering UDSerial serversAdministering UDTelnet serversAdministering UniData Services

9-2 Using UniAdmin

Administering DatabasesThe UniData ODBC, UniOLEDB, VSG, UniObjects, UniObjects for Java, and UniObjects for .NET products access databases defined in the ud_database file. You can modify this file through Database Admin.

Select one of the following methods to access Database Admin.

From the UniAdmin window, double-click Network Services, and then double-click Database Admin.From the UniAdmin menu, click Admin, select Network Services, and then click Database Admin.


Administering Databases 9-3

Adding a DatabaseTo add a database, click Add. The Add Database dialog box appears, as shown in the following example:

Enter the name of the database in the Database Name box. Enter the UDTHOME on the server in the UDTHOME box, or click Browse to select the location. Enter the full path to the UniData account in the UDTAccount box, or click Browse to select the location. Enter the trace level in the Trace Level box. For information about trace levels, see the documentation for the appropriate product connecting to the database.

Click OK to save your changes, or click Cancel to exit the program without saving changes.

9-4 Using UniAdmin

Updating a DatabaseTo modify an existing entry in the ud_database file, from the Database Configu-ration dialog box, click Update. The Update Database dialog box appears, as shown in the following example:

Change any necessary information, then click OK to save your changes, or click Cancel to exit the program without saving changes.

Deleting a DatabaseTo delete a database, click the database you want to remove, and then click Delete. The Delete Database dialog box appears, as shown in the following example:

If you want to delete the database shown, click OK. Click Cancel to the exit the program without saving changes.

Administering Databases 9-5

Viewing a DatabaseTo view information about a database, click the database for which you want to view information, then click View. The View Database dialog box appears, as shown in the following example:

Click OK to return to the Database Configuration window.

Click Cancel to exit Database Admin.

9-6 Using UniAdmin

Administering NFA ServersNote: This subsection applies to UniData for Windows Platforms only.

The UniAdmin utility controls the NFA server process on the server machine on which the remote files reside. You can add, update, view, or delete NFA server defini-tions. The server definitions are written to the registry. They are read when the NFA Service is started.

You can access the NFA Server Configuration dialog box in one of the following ways:

From the UniAdmin window, double-click Network Services, and then double-click NFA Server.From the UniAdmin menu, click Admin, select Network Services, and then click NFA Server.

Administering NFA Servers 9-7

The NFA Server Configuration dialog box appears, as shown in the following example:

9-8 Using UniAdmin

Adding an NFA Server Definition

To add an NFA server definition, in the NFA Server Configuration dialog box, click Add. A dialog box similar to the following example appears.

The following table describes each parameter that appears in the Add NFA Server dialog box.


Server Name Specifies the name of the NFA server you want to add.

Port Number Specifies the port number you want to use. IBM has registered 1155 as the NFA port number.

UDTHOME The path and file name of the UniData home directory on the NFA server.NFA does not validate this field when you enter it. If you specify an invalid path and filename, subsequent NFA connections fail.

NFA Server Parameters


UDTBIN Specifies the path and file name of the UniData bin directory on the NFA server.NFA does not validate this field when you enter it. If you specify an invalid path and file name, subsequent NFA connections fail.

Program Name Specifies the name of the UniData program that executes UniBasic statements against NFA files. You must accept the default, which is “nfa.server”.NFA processes fail if you change this field.

Basic Type Specifies the BASICTYPE to use for running the NFA server. You can specify P or U. The default value is U, which executes all ECL SELECT statements in ECLTYPE U. To execute ECL SELECT state-ments in ECLTYPE P, specify P.

Log Level Specifies the level of NFA server logging. You must specify a level in the range from 0 through 10. 10 represents the most detailed level of logging. The default is 0, which logs fatal errors only.

Log Dir Specifies the directory in which NFA creates the server log files. The default directory is \TEMP. NFA creates the log files with the naming convention UDTsvr_xxx.log where xxx is the process ID of the server process.

Security Enables/Disables network security checking. The default is Disable. For more information, see “Developing OFS/NFA Applications” later in this section.

Allow UNIX Client

If you select this option, NFA treats connections without a password as valid connections from a UNIX client. By default, the option is not selected.


NFA Server Parameters (continued)

9-10 Using UniAdmin

After you complete the Add NFA Server dialog box, click OK. The new server definition is added to the registry. The following message appears.

To restart the NFA Service, click OK. This makes the new server definition available immediately. To store the server information and make it available the next time NFA Server Service is stopped and restarted, click Cancel.


Updating an NFA Server Definition

To update an existing NFA server definition, in the NFA Server Configuration dialog box, highlight the server you want to update, and then click Update. A dialog box similar to the following appears.

Notice that the Server Name and Port Number appear dimmed. You can update any item except Server Name and Port Number. After you complete the Update NFA Server dialog box, click OK. UniData updates the server definition in the registry.

9-12 Using UniAdmin

To restart the NFA service, click OK. This makes the new server definition effective immediately. If you click Cancel, the updated server definition becomes effective the next time the NFA Service is restarted.

Deleting an NFA Server Definition

To delete an NFA server definition, in the NFA Server Configuration dialog box, highlight the server you want to delete, and then click Delete. A dialog box similar to the following example appears.


To delete the server definition, click OK. To return to the NFA Server Configuration dialog box, click Cancel. If you click OK, UniData removes the server definition from the registry, and a dialog box similar to the following example appears:

To restart the service, click OK. This deletes the server definition immediately. To delete the server information the next time NFA Service is restarted, click Cancel.

9-14 Using UniAdmin

Administering the UDSerial ServerThe UniData Terminal Server (also called UDSerial) is a software product that enables you to connect serial devices to your network. If you have UDSerial running on a Windows system, any serial device connected to the Windows system through UDSerial can have complete Telnet capabilities throughout the Windows network.

Functionally, UDSerial simply connects a device to Telnet. To run UniData through UDSerial, you must have both UDSerial and UDTelnet installed and running.

Tip: IBM recommends you install UDSerial even if your immediate plans do not include accessing UniData via asynchronous terminal. UDSerial occupies a minimal amount of disk space. By default, the service is disabled on all ports when you install it, so it uses no system resources. By installing UDSerial, you are building in flexibility for future needs.

Note: You need to log on as a member of your local Administrators group (or as the Administrator) to modify the configuration settings for the UniData Terminal Server.

You configure the UniData Terminal Server through UniAdmin. Select one of the following methods to access the Terminal Server dialog box from UniAdmin:

From the UniAdmin menu, click Admin, then select Network Settings, and then click UDSerial Server.From the UniAdmin window, double-click Network Services, and then double-click UDSerial Server.From the UniAdmin toolbar, click the UDTelnet Server icon, as shown in the following example:

UdSerial ServerIcon

Administering the UDSerial Server 9-15

Regardless of the method you choose, the Terminal Server dialog box appears, as shown in the following example:

The following table describes the dialog tabs for Terminal Server dialog box.

Terminal Server Dialog Box Tabs

Dialog Tab Description

Service Settings for escape sequence, terminal type, event logging level, and logon banner.

Ports Configuration settings for each serial port used by UDSerial.

Service OptionThe Service dialog box enables you to configure your terminal service.

Set Escape Sequence

The Escape Sequence is the hexadecimal equivalent of the character string used as an escape from a remote system. The default 1d (hex equivalent of Ctrl-]). This option is not applicable for UniData.

9-16 Using UniAdmin

Set Terminal Type

In the Terminal Type box, enter the terminal type used by a remote system. This option is not applicable for UniData.

Specify Logon Banner

In the Logon Banner box, enter a message to display when a user successfully connects to UDSerial.

Starting, Stopping, and Pausing the Telnet ServerClick Start to start the UDSerial Service. The Start button appears dimmed unless the service is paused or stopped.

Click Stop to stop the UDSerial Service. The Stop button appears dimmed unless the service is running.

Click Pause to pause the UDSerial Service. The Pause button appears dimmed unless the service is running.

Click OK to save the new settings and exit the Terminal Server dialog box. Click Apply to save the new settings and keep the Terminal Server dialog box open. Changed settings do not affect UDSerial sessions that are already started. New sessions started after you change the service parameters use the new parameters. Click Cancel to exit the Terminal Server dialog box without saving change

Warning: Do not stop the terminal server if UDSerial users are logged on to the system. You could cause file corruption by disrupting writes in progress.

Port ConfigurationConfiguring a port depends on the serial device to which you are attaching. You need to know about the characteristics of your terminal device to select the appropriate settings.


Click the Ports tab. A dialog box similar to the following appears:

9-18 Using UniAdmin

To modify the configuration information for a port, either double-click the port name, or select the port name and click Properties. The Port Properties dialog box appears, similar to the following example:

By default this dialog box displays with the Settings tab selected. Notice that the dialog box offers additional dialog tabs for Modem Options, Logon Script, Auto Connection, and Control Keys.

Note: You can choose which ports to use with UDSerial. If you have COM ports that are reserved for other uses (for instance, serial printers or other software), you can leave those ports disabled in UDSerial configuration. Even if ports share the same serial card, they do not all have to be managed by UDSerial.

Select Baud Rate

The baud rate is the Transmission speed of the port in bits per second (BPS). Refer to the vendor documentation for the hardware you are attaching to the port and select the appropriate value from the list.


Select Data Bits

Data bits are the number of data bits per character. Valid settings are be 5, 6, 7, or 8. The most common setting is 8. Refer to your vendor documentation and select the appropriate value from the list.

Select Parity

Parity determines the method of marking boundaries of characters. Parity can be none, even, odd, or mark. Consult your vendor documentation and select the appro-priate value from the list.

Select Stop Bits

Stop bits determine the method of marking the end of characters. Valid settings are 1, 1.5, or 2. The most common setting is 1. Refer to your vendor documentation and select the appropriate value from the list.

Set Flow Control

Flow Control determines the method for controlling data transmission between sending and receiving devices. Valid settings are Xon/Xoff, DTR/DSR, RTS/CTS, hardware, or none. Refer to your vendor documentation and select the appropriate value from the list.

Set Terminal Type

Set the terminal type to vt100. If the port is only used for direct access to UniData, you can set it to a valid entry in udtermcap.

9-20 Using UniAdmin

Control KeysIf you select the Control Keys tab on the Port Properties dialog box, a dialog box similar to the following example appears:

Determine Escape Character

The value in the Escape Character box determines the character sequence to disconnect a session with a remote system and return your serial device to the Telnet prompt. You must enter this value as the hexadecimal equivalent of the actual sequence. The default is 1d (hex equivalent of Ctrl-]).

Set X on

X on is required if Flow Control in the Settings dialog box is Xon/Xoff. You must enter the value in hexadecimal. The default is 11 (hex equivalent of Ctrl-Q).


Set X off

X off is required if Flow Control in the Settings dialog box is Xon/Xoff. You must enter the value in hexadecimal. The default is 13 (hex equivalent of Ctrl-S).

Tip: If your terminal supports Xon/Xoff flow control, you probably do not need to modify the Control Keys.

Modem OptionsIf you have connected a modem to your COM port, and you want the modem to be managed by UDSerial, select the Modem Options tab from the Port Properties dialog box. A dialog box similar to the following example appears:

Enter Modem Initialization String

Enter the initialization commands for the modem, one command per line (for instance, auto answer and echo off) in the Modem Initialization String box.

9-22 Using UniAdmin

The Modem Initialization string contains commands for the modem. Insert one command per line. For example, the following initialization string is proper if you are using a US Robotics Courier V modem and are using hardware flow control:

+++ Force modem back to Command mode ATH0 Hang up modem AT &R1 &I0 Disable flow control entirely AT &B0 & N0 Makes the serial port and connect rates equal AT &H1 &R2 Sets hardware flow control AT S0=1 Enables auto answer

The following example illustrates the Modem Options box using the initialization commands above:

Set Modem DelayThe value in the Modem Delay box determines the delay, in milliseconds, between each line in the initialization string. The default is 1000 milliseconds. Valid values are between 1000 and 5000.


Logon ScriptIf you select the Logon Script tab, a dialog box similar to the following example appears:

Enter Logon Script

In the Script window, enter a logon script, one input per line. The window is scrol-lable. The default is blank, meaning no string is sent to the remote computer.

Enter Delay

Enter the delay, in milliseconds, between each line of the logon script in the Delay box.

Determine Output Suppress

Check the Output Suppress check box to prevent the end user of the serial device from seeing the input string as it is passed to the remote computer.

9-24 Using UniAdmin

Warning: Configuring a logon script (userid, password) is generally unwise for a terminal. Automatically passing an ID and password can compromise your security. If you are configuring a device such as a bar code reader, where a user cannot directly access your system, passing a preset user ID and password may be desirable. In either case, consider selecting Auto Connection.

Auto ConnectionSelect the Auto Connection tab if you want the device attached to your port to connect to a particular remote host.

Tip: Auto Connection is extremely useful for devices that do not accept direct user input, like printers or bar code readers. Auto Connection can also simplify the interface for users of terminal devices.

When you select the Auto Connection tab, a dialog box similar the following example appears:

Determine Auto Connect

Select the Auto Connect check box to enable Computer Name and Type.


Enter Computer Name

In the Computer Name box, enter the name or IP address of the computer to which you want to connect. The computer name must be resolvable by your Windows system.

Determine How to Activate Remote Connection

The Type box determines the method for activating the remote connection. The default is None. The following table describes valid Types.

Auto Connection: Valid Types

Type Description

None Auto Connection is disabled.

CTS Connect/disconnect when CTS signal is raised/dropped. Will not work if Flow Control for this port is RTS/CTS.

DSR Connect/disconnect when DSR signal is raised/dropped. Will not work if Flow Control for this port is DTR/DSR.

Carrier Connect/disconnect when carrier is detected (RLSD) or dropped.

Always Connect/disconnect when UDSerial is started/stopped. Make sure there is a receiving host if you pick this Type.

9-26 Using UniAdmin

Administering the UDTelnet ServiceThe UniData Telnet Service (UDTelnet) enables multiple users to log on to a single Windows platform to run UniData. With the UniData Telnet Service installed and started, your Windows platform exports a logon prompt to its network so that network users can log on and run UniData.

Note: You need to log on to the Administrator account or log on as a member of the local Administrators group to configure the UDTelnet Service.

Select one of the following methods to access the Telnet Server dialog box from UniAdmin:

From the UniAdmin menu, click Admin, then select Network Services, and then click UDTelnet Server.From the UniAdmin window, double-click Network Services, and then double-click UDTelnet Server.From the UniAdmin toolbar, click the UDTelnet Server icon, as shown in the following example:

UDTelnet ServerIcon

Administering the UDTelnet Service 9-27

Regardless of the method you choose, the UDTelnet Server dialog box appears, as shown in the following example:

The following table describes the dialog tabs for Telnet Server.

Telnet Server Dialog Tabs

Dialog Tab Use

Service Settings for maximum login attempts, logon pause, logon timeout, termi-nation pause, telnet port number, SSL port number, keep alive, and logon banner.

Users Allows you to specify a list of users that are allowed to connect to your Windows platform through UDTelnet.

9-28 Using UniAdmin

Service OptionsSelect the Service tab from the Telnet Server dialog box to view and edit parameters that govern the operation of the UDTelnet Service. A dialog box similar to the following example appears:

Set Telnet Port Number

Set the telnet port number that the UDTelnet service should monitor for client connections.

The default value for the Telnet Port Number is 23. IBM recommends that you not change this unless you have another service that requires socket 23.


Tip: In the TCP/IP protocol stack, certain sockets are reserved for specific services. The file %systemroot%\system32\drivers\etc\services on your Windows platform contains a partial listing of reserved sockets, excerpted from Internet RFC1060. Use the listing as an aid to identify available sockets.

Set SSL Port Number

Set the SSL port number that the UDTelnet service should monitor for client connections.

The default value for the Telnet Port Number is 992. IBM recommends that you not change this unless you have another service that requires socket 992.

Set Connection Parameters

You can set the connection parameters described below through UniAdmin.

Set Maximum Logon Attempts

In the Maximum Logon Attempt box, enter the maximum number of attempts a user is allowed to enter a login and password. Use the Maximum Logon Attempt arrows to choose the number of times. The default is 5.

Set Logon Pause Value

The number of seconds UniData pauses between logon attempts if a logon attempt fails. The default value is 4.

Set Logon Timeout Value

The number of seconds UniData waits for a response to a logon prompt. As soon UniData reaches this limit, it drops the telnet connection. The default value is 30.

Set Termination Pause Value

The number of seconds UniData pauses after the final failed logon attempt before it drops the telnet connection. The default value is 4.

9-30 Using UniAdmin

Set Keep Alive Parameters

You can set the keep alive parameters described below through UniAdmin.

Keep Alive Interval

The interval separating keep alive transmissions until a response is received. The default value is 1000 (1 second).

Keep Alive Time

The parameter controls how often TCP attempts to verify that an idle connection is still intact by sending a keep alive packet. The default value is 7,200,000 (2 hours).

Maximum Data Retransmissions

This parameter controls the number of times TCP retransmits an individual data segment before ending the connection. The default value is 5.

Set Backlog Queue Value

The maximum length of the queue of pending telnet connections. The default value is 14.

Select Detach ProcessIf you select this option, the UniData Telnet Service creates the UniData process (ud_tl_server.exe) as a detached process.

Select Create Desktop

If you select this option, the UniData Telnet Service creates its own WinStation/Desktop and assigns it to the UniData process.

Specify Logon Banner

In the Logon Banner box, enter a message to display when a user successfully connects to UDTelnet.


Starting, Stopping, and Pausing the Telnet Server

Click Start to start the Telnet Server. The Start button appears dimmed unless the service is paused or stopped.

Click Stop to stop the Telnet Server. The Stop button appears dimmed unless the service is running.

Click Pause to pause the Telnet Server. The Pause button appears dimmed unless the service is running.

Click OK to save the new settings and exit the Telnet Server dialog box. Click Apply to save the new settings and keep the Telnet Server dialog box open. Changed settings do not affect Telnet sessions that are already started. New sessions started after the service parameters were changed use the new parameters. Click Cancel to exit the Telnet Server dialog box without saving changes.

User ProfilesSelect the Users tab to specify which users are allowed to connect to your system through UDTelnet, and to create custom user profiles.

9-32 Using UniAdmin

A dialog box similar to the following example appears when you click the Users tab:

This dialog box enables you to specify a list of users that are allowed to connect to your Windows system via UDTelnet. At installation, UDTelnet is started with a default configuration that allows any user who can access your Windows system from the network to access the system through UDTelnet as well. This default behavior is acceptable in many instances. However, administrators may wish to grant only certain users Telnet access, or to create individual user profiles. The Users dialog box allows this flexibility.

Warning: If you remove the Default profile, no user can log in through UDTelnet unless you have created a specific profile for the user.


Default User Profile

When you first display the Users dialog box, you see an entry for DEFAULT in the User box. Highlight DEFAULT and click Edit to display the default profile. The following example illustrates a sample default profile.

Specify Default ShellIn the Default Shell box, enter the full path of an executable. In the default profile, this is set to udtbin\udt.exe, which starts a UniData session.

Specify Startup Directory

Enter the full path of the working directory to which you want to connect at login in the Startup Directory box. In the default profile, this is set to the UniData demo account.

Specify Arguments

In the Command Line box, enter any arguments you want to pass to the default shell. In the default configuration, this is blank.

9-34 Using UniAdmin

Determine ANSI Version

Select the ANSI Version 3.x check box if you want to enable faster screen refreshes for terminals that support ANSI 3.x color. By default, this check box is not selected.

Determine How to Map Characters

Select the Use Redirection Chars check box if you want to map unprintable characters to printable characters. By default, this check box is selected.

Prompt for Working Directory

Select the Prompt Directory check box if you want the user to select a working directory at logon time. By default, this check box is not selected.

Note: If you want one or more users to see the MS-DOS prompt when they log on, edit the user profile or profiles so that the default shell is %systemroot%\system32\cmd.exe.

Click OK to return to the Telnet Server dialog box, or click Cancel to exit without saving changes.

Customizing User ProfilesComplete the following steps to create a customized profile for a user.


1. Add a ProfileClick New to add a user profile. The following dialog box appears:

Enter the logon name of the user, then click OK. Enter the logon name only (for instance, user01). Do not enter the domain name (for instance, do not enter ACCOUNTING\user01). When you click OK, a dialog box similar to the following appears:

UniData populates the dialog elements with the values from the Default Configuration. Click OK to accept those values, or edit one or more fields to customize the profile.

Note: If you deleted the Default profile, UniData displays a message when you attempt to add new user profiles. You must enter all the configuration settings manually, since UniData cannot copy them from the default profile.

9-36 Using UniAdmin

2. Customize a ProfileTo edit a profile, highlight the user name in the User box, then click Edit. Consider the following points when customizing a user profile:

Specify a full path in the Default Shell box. You can use either drive letters or the Universal Naming Convention (UNC) to specify the path.By specifying the Startup Directory, you can direct different users to different startup directories, even if they are using the same default shell.You can allow users to choose their directory when they log on by selecting the Prompt Directory check box.If you do not know whether a particular terminal supports Version 3 Color, select the ANSI Version 3.x check box. Test the terminal; if screen colors are not displayed correctly, modify the user profile to clear the ANSI Version 3.x check box.


The following example shows a sample configuration that allows a user to log in through UDTelnet, select a starting directory, and access the MS-DOS command prompt. The default startup directory is C:\IBM\ud72\demo:

Changes to a user’s configuration are visible the next time the user logs in through UDTelnet.

9-38 Using UniAdmin

Generated ProfilesIf you selected Prompt Directory in your Default Profile, UniData creates a profile for each user who would normally receive the default user profile. UniData creates the individual profiles the first time a user chooses a startup directory different from the default. The generated profile uses the same configuration settings as the default profile, with the exception of Startup Directory, which is set to the directory chosen by the user when they log on. The following examples show the effect of the Prompt Directory option. In the first example, the default user profile has Prompt Directory selected:

The following example shows the appearance of the screen when a user logs in:

Path (C:\IBM\ud72\demo) : \IBM\ud72\claireg


Notice that the default path is C:\IBM\ud72\demo, and the user is selecting an alternate startup directory, \IBM\ud72\claireg. Pressing ENTER starts a UniData session in \IBM\ud72\claireg. This login session also creates a profile for the user, which you can view or edit from the Telnet Server dialog box. The generated profile is shown in the following example:

The next time the user logs in via Telnet, the default path is changed, as shown in the following example:

Path (\IBM\ud72\claireg) :

Starting, Stopping and Pausing UDTelnetNote: Pause and Stop have the same functionality. Once a user logs on through Telnet, their process is not affected by Pause or Stop. Pause and Stop both prevent additional users to log on through Telnet.

You can start, stop, or pause the UDTelnet Server Service from the Service tab in the Telnet Server dialog box.

9-40 Using UniAdmin

Click Stop to stop the UDTelnet Service. Users already logged on can continue to work, but no additional users can log on through UDTelnet until you Start the service.Click Start to start the UDTelnet service (if it is stopped) or continue the service (if it is paused).Click Pause to pause the UDTelnet service. Users already loggedoin can continue to work, but no additional users can log on through UDTelnet until you Start the service.


Monitoring UniData ServicesYou can start or stop UniData services from UniAdmin.

Select one of the following methods to access the UniData Services dialog box from UniAdmin:

From the UniAdmin menu, click Admin, then select Network Services, and then click UniData Services.From the UniAdmin window, double-click Network Services, and then double-click UDTelnet Server.


Starting UniData ServicesTo start a UniData service, click service you want to start, then click Start. You can start all services by clicking Start All.

Stopping UniData ServicesTo stop a UniData service click the service you want to stop, then click Stop. You can stop all UniData services by clicking Stop All.

9-42 Using UniAdmin

10Chapter

UniData Data Replication

Defining Publishing Groups . . . . . . . . . . . . . . . 10-3Defining Replication on a Subscribing System . . . . . . . . . 10-14Changing Replication Group Definition . . . . . . . . . . . 10-22Administering Replication through UniAdmin . . . . . . . . . 10-24Replication Recovery Log . . . . . . . . . . . . . . . . 10-27 REP_RECV_LOG . . . . . . . . . . . . . . . . . 10-27Diagnosis Utility . . . . . . . . . . . . . . . . . . . 10-29Monitoring Replication . . . . . . . . . . . . . . . . . 10-30 Starting the Replication Monitor . . . . . . . . . . . . 10-32 Replication Group Status Table . . . . . . . . . . . . . 10-35

UniData replication provides an automatic way to deliver read-only copies of UniData files to other UniData systems. You can use the replicated data as a standby system in case of system failure, or as a reporting system.

For detailed information, see “UniData Data Replication.”

After you install and configure UniData Replication, you can use UniAdmin to administer replication processes.

10-2 Using UniAdmin

Defining Publishing Groups You must define each of the replication groups on the publishing system before you can start UniData Data Replication.

Complete the following steps to define a publishing replication group from UniAdmin.

Select one of the following methods to access the UniData Replication Admin dialog box:

From the UniAdmin window, double-click Replication.From the UniAdmin menu, click Admin, then click ReplicationFrom the UniAdmin toolbar, click the Replication icon, as shown in the following example:

Replication Admin Icon

Defining Publishing Groups 10-3


10-4 Using UniAdmin

Define Subscribing Systems

To define remote replication systems, from the UniData Replication Admin dialog box, click System Definition. A dialog box similar to the following example appears:

To add a subscribing system location, click Add. A dialog box similar to the following example appears:


Enter System ID

In the System ID box, enter the name of the subscribing system. The name of the subscribing system is the name given when you installed UniData Data Replication on your system. By default, this name is <hostname>_version.

Enter Host Name

In the Host Name box, enter the host network name or network address of the repli-cation system.

Enter UniData Version

In the Version box, enter the UniData version running on the system. The version must be 60 or higher.

Define DHCP System

Select the DHCP check box if the remote system has a dynamic IP address.

Choose to Auto Resume

Auto Resume determines if replication to the system you specify will be synchro-nized and resume automatically when UniData starts, or after a reconfiguration. Select Yes if you want UniData to automatically resume processing, or No if you want to manually synchronize data and resume processing.

Define Sync Interval

In the Sync Interval box, select the time interval, in minutes, in which the replication system automatically synchronizes replication.

UniData Data Replication automatically synchronizes subscribing systems with their publisher every period defined by sync_interval. A sync_interval of 0 indicates a manual synchronization system, where UniData does not automatically synchronize the systems.

The synchronization interval is only valid when using deferred replication.

10-6 Using UniAdmin

Choose Connect Authorization

If you select the Connect Authorization check box for a subscribing system, UniData Data Replication verifies the login name and password when the subscribing system issues a SYNC request.

Define Timeout Interval

The timeout interval defines the number of seconds to wait if no packets are received before suspending replication.

The publishing system sends a packet to the subscribing system approximately every 4 seconds when replication is idle. The subscribing system then sends a packet back to the publishing system. If you define a timeout interval on the subscribing system, the publistener process counts the time that has elapsed between packets being received. If the amount exceeds the timeout interval, replication is suspended.

If you set the timeout value to 0, UniData Data Replication does not time out.

IBM recommends that you not set the timeout interval to less than 2 minutes.

Define Exception Action

The Exception Action is a shell script on UNIX platforms, or a batch program on Windows platforms. Enter the full path to the trigger in the EXCEPTION_ACTION box. For example, if you define an exception action trigger as UDRepExceptionAction.sh in the /usr/ud72 directory, set the full path as:

EXCEPTION_ACTION=/usr/ud72/UDRepExceptionAction.sh

If you define an Exception Action on a subscribing system, whenever an exception occurs and suspends replication, UniData Data Replication invokes the Exception Action script.

When you finish defining the subscribing system requirements, click OK to return to the UniData Replication Admin dialog box.


Adding a Publishing Group

To add a publishing group, in the Publishing Groups area of the UniData Repli-cation Admin dialog box, click Add. A dialog box similar to the following example appears:

10-8 Using UniAdmin

If you select ACCOUNT in the Level box, the following dialog box appears:

Defining Group Name

In the Group ID box, enter a unique name for the publishing group.


Defining Replication Level

In the Level box, select the level of replication. Valid values are FILE or ACCOUNT.

Specifying Publishing Account

In the Account box, select the local account where the replication group resides. UniAdmin automatically populates the Account Path box.

Select Files to Publish

In the Files area of the Publishing Group Details dialog box, click Add to select the files you want to publish. A dialog box similar to the following example appears:

Click the file you want to publish. You can select multiple files by clicking the file while holding down the CTRL key.

10-10 Using UniAdmin

When you have selected all the files you want to publish, click OK, or click Cancel to exit without saving changes. A dialog box similar to the following example appears:

By default, both the data portion and the dictionary portion of the file are selected. If you do not want to publish the data portion of the file, clear the Data check box. If you do not want to pu blish the dictionary portion of the file, clear the Dict check box. If you to be able to update the file on the subscribing system, select the Sub Writable check box.

When you finish selecting all the files you want to publish, click OK to return to the UniData Replication Admin dialog box.


Select Files to Exclude

If you are using account-level replication, you can select files to exclude fromU-niData Data Replication. In the Excluded Files area of the Publishing Group Details dialog box, click Add. A dialog box similar to the following example appears:

Click the file you want to exclude. You can select multiple files by clicking the file while holding down the CTRL key.

When you finish selecting all the files you want to exclude, click OK to return to the Publishing Group Details dialog box.

Enter RFS Failover System

If you want this publishing group to automatically failover to a standby system, select the standby system in the RFS Failover System box.


Set Configuration Parameters

Set any of the configuration parameters necessary for your environment in the Configuration area of the Publishing Group Details dialog box, as shown in the following example:


Defining Replication on a Subscribing SystemYou must define the publishing system location and import the replication group definitions from that location. If the subscribing system you are defining is a standby system, you also need to define other subscribing systems, if any.

Complete the following steps to define a subscribing replication group from UniAdmin.

Select one of the following methods to access the UniData Replication Admin dialog box on the subscribing system:





Defining Replication on a Subscribing System 10-15

Define the Publishing System Location on Subscribing System

To define remote publishing system on the subscribing system, from the UniData Replication Admin dialog box, click System Definition. A dialog box similar to the following example appears:

To add another system, click Add. A dialog box similar to the following example appears:


Enter System ID

In the System ID box, enter the publishing system name.

Enter Host Name

In the Host Name box, enter the host network name or network address of the publishing system.

Enter UniData Version

In the Version box, enter the UniData version running on the system. The version must be 60 or higher.

Choose to Auto Resume

Auto Resume determines if replication from the publishing system you specify will be synchronized and resume automatically when UniData starts, or after a reconfig-uration. Select Yes if you want UniData to automatically resume processing, or No if you want to manually synchronize data and resume processing.

Define Sync Interval

In the Sync Interval box, select the time interval, in minutes, in which the replication system automatically synchronizes replication.

UniData Data Replication automatically issues a SYNC request to the publishing system every period defined by sync_interval. A sync_interval of 0 indicates a manual synchronization system, where UniData does not automatically synchronize the systems.

Define Timeout Interval

The timeout interval defines the number of seconds to wait if no packets are received before suspending replication.

The publishing system sends a packet to the subscribing system approximately every 4 seconds when replication is idle. If the publishing system has the a timeout interval defined, the udsub process counts the time that has elapsed between packets being received. If the amount exceeds the timeout interval, replication is suspended.


IBM recommends that you not set the timeout interval to less than 2 minutes.

Define Exception Action

The Exception Action is a shell script on UNIX platforms, or a batch program on Windows platforms. Enter the full path to the trigger in the EXCEPTION_ACTION box. For example, if you define an exception action trigger as UDRepExceptionAction.sh in the /usr/ud72 directory, set the full path as:

EXCEPTION_ACTION=/usr/ud72/UDRepExceptionAction.sh

Define Connection User Name and Password to Publishing System

If you select Connect Authorization on the subscribing system location definition on the publishing system, you must define the connection user name and password to the publishing system location. To define the connection user name and password to the publishing system, select the publishing system in the Replication System Definition dialog box, then click Set Connection. The Set Rep System Connection dialog box appears, as shown in the following example:

Enter the login name and the corresponding password. Re-enter the password. Click OK to return to the Replication System Definition dialog box.


Define Subscribing GroupsIn the Subscribing Groups area of the UniData Replication Admin dialog box, click Add. The Subscribe Group Details dialog box appears, as shown in the following example:


Select Publishing System

In the From System box, select the publishing system from which this subscribing system is receiving data.

Select Group ID

Select the Group ID from the publishing system in the Group ID list.

When you select the Group ID, UniAdmin populates the file list and configuration parameters from the same Group ID on the publisher.

Select Into Account

Select the account to which you want to replicate data in the Into Account dialog box. UniAdmin automatically populates the Account Path box.

Define Type of Replication

In the Distributions area of the Subscription Group Details dialog box, click the value in the Type box. The following list of replication types appears:

Select the type of replication you want for the subscriber.

Select Hot Standby

If the subscribing system will be used as a standby system, select the Hot Standby check box.


The following example illustrates a completed definition for a subscribing system:

Click OK to save the subscribing group definition, or click Cancel to exit without saving changes.

Verify Distribution Information

In the UniData Replication Admin dialog box, select a subscribed group, then click Detail.

UniAdmin displays the distribution information for the publishing group in the Distributions area of the Publishing Group Details dialog box, as shown in the following example:


Changing Replication Group Definition To change a replication group definition, from the UniData Replication Admin menu, click the publishing group you want to update, then click Detail. A dialog box similar to the following example appears:

Make the appropriate changes, then click Update.


You must synchronize the reconfigured group from its publisher or to its subscriber after making your changes.

Changing Replication Group Definition 10-23

Administering Replication through UniAdminComplete the following steps to access the Replication Admin Tool dialog box from UniAdmin.

Select one of the following methods to access the dialog box:



From the UniData Replication Admin dialog box, click Replication Tool. A dialog box similar to the following example appears:


You can execute the following administration options from the Replication Admin Tool:

Report – Reports the current status of a replication. This command is useful after a failure or failover occurs. For detailed information about this command, see “UniData Replication.”Sync – Synchronizes subscribing systems to their publishing systems. The publishing system establishes a connection to the subscribing system and invokes the subscribing process. UniData reads and transfers replication logs from the publishing system to the subscribing system. The subscribing system then applies the updates to the database. For detailed information about this commands, see “UniData Replication.”Reconfig – Reconfigures the replication configuration while UniData is running. For detailed information about this command, see “UniData Replication.”Suspend – Suspends a live replication. In a suspended mode, UniData inter-rupts the connection between the publisher and the subscriber. The publishing system saves the replication log files to the Replication Logs rather than transferring them to the subscribing systems. The subscribing system and all replication writer processes stop after they finish updating existing logs in the replication buffer. For detailed information about this command, see “UniData Replication.”Failover – Changes the replication direction on a local system, either from the local system to the publishing system or subscribing system, or changes the subscribing source distribution. For detailed information about this command, see “UniData Replication.”Reset – The reset command clears saved replication logs in the Replication Log Reserve File. Use the reset command after you copy or store database files, since the remaining replication logs are no longer useful. For detailed information about this command, see “UniData Replication.”

Select Targets

A target is a replication, a replication group, or a distribution of a replication group. A replication is all data replicated from a remote system to the local system, or from a local system to a remote system. A target definition of ALL represents all replica-tions on the system. One command can have multiple targets.

Administering Replication through UniAdmin 10-25

If you want to execute the command against all targets, select All in the Targets area of the Replication Admin Tool dialog box.

If you want to select the replication to execute the command against, select the Selected option in the Targets area of the Replication Admin Tool dialog box, then click Add. A dialog box similar to the following example appears:

Enter the target information, then click OK, or click Cancel to exit without saving changes.

To execute a command, click the command you want to run, then click Execute. Any output from the command appears in the Status box.


Replication Recovery LogThe replication recovery log is a UniData file located in $UDTHOME/sys. This file records replication recovery. The resynchronization of a publishing group on a system running RFS generates a record in the Replication Recovery Log that records the publishing group recovery. UniData also writes the logs representing missing transactions during recovery when resyncronizing after failing over to a system running immediate replication to this file.

The Replication Recovery Log has two associated files:

REP_RECV_LOG – records the recovery of publishing groups and the keys of missing transaction.REP_RECV_REC – records the records and virtual attribute values of the missing transaction.

REP_RECV_LOGThe REP_RECV_LOG contains the following information:

Replication group name that was recoveredTimestamp of the recoveryMissing logs:

Insert/Delete/UpdateReplication accountReplication object nameKey of the record@ID of the record in REP_RECV_REC representing the old record of the missing log.@ID of the record in REP_RECV_REC representing the new record of the missing log. @ID of the record in REP_RECV_REC representing virtual attribute values of the old record.@ID of the record in REP_RECV_REC representing virtual attribute values of the new record.

Replication Recovery Log 10-27

You can execute any UniData commands against these files to query the information they contain.

To view the logs from UniAdmin, from the UniData Replication Admin dialog box, click Recovery Logs. A dialog box similar to the following example appears:

Select the time stamp for which you want to view the logs in the Time Stamp box, then select the replication group in the Group ID box. UniAdmin displays the recovery status.

If you want to use this log to apply the update, select the system to which you want to resynchronize in the System box of the Re-synchronize to area of the dialog box, then select the appropriate account in the Account box. If you want to ignore errors that occur during the synchronization process, select Ignore Error. Click Re-Sync to begin the synchronization process.


Diagnosis UtilityThe Diagnosis Utility available from UniAdmin is used by IBM Engineering for diagnosing problems encountered with UniData Replication.

Diagnosis Utility 10-29

Monitoring ReplicationUniData provides a tool to monitor UniData Data Replication.

The Replication Monitoring tool monitors connection status, data transferring, and whether or not the publisher and subscriber systems are synchronized.

To access the Replication Monitoring tool, from UniAdmin, double-click Repli-cation, then click Monitor Replications. The Replication Monitoring window appears, as shown in the following example:


The Replication Monitor can monitor two types of replications:

Publishing Replication – the data replication from the local system to a remote subscribing system, including all replication groups involved. A publishing system can have more than one Publishing Replication defined. Subscribing Replication – the data replication from a remote publishing system to the local system, including all replication groups involved. A subscribing system can have more than one Subscribing Replication defined.

Replication Name

Each UniData Replication is assigned a unique name on one system, consisting of the replication type and the remote system name. A replication type can be one of the following:

ImmediateStandby ImmediateRealtimeStandby RealtimeDeferred

Choose the name of the replication you want to monitor from the Replications box.

Note: If a replication has failed over, it still belongs to the same Replication as it did before the failover, but the name changes.

Refreshing IntervalYou can define how often to refresh the Replication Monitor. The defaul interval is 3 seconds. Choose the number of seconds to refresh the monitor in the Interval in seconds box.

Monitoring Replication 10-31

Starting the Replication MonitorTo start the Replication Monitor, click Start. A window similar to the following example appears:

Replication Status

The Replication Status indicates whether the publisher and subscriber are connected. The status can be one of the following:

Green – The Publisher and subscriber are connected for all groups involved in the Replication.Yellow – At least one of the replication groups has been suspended by an administrator.Red – At least one the replication groups has terminated abnormally.


Sync Status

The Sync status indicates whether the subscribing database is synchronized with the publishing database. The status can be one of the following:

Green – The pubishing and subscribing databases are synchronized.Yellow – There are pending updates that have not been applied to the subscribing database.

Packet Received

The number of packets received from the other party of the Replication. Types of packets include data packets, confirmation packets, heartbeat packets and other control packets. Monitoring this information indicates whether the physical connection between the publishing database and the subscribing database is satisfactory. This number is cumulative from the last time UniData was started or UniData Replication was reconfigured.

Packet Sent

The number of packets that have been sent to the other party of the Replication. Types of packets include data packets, confirmation packets, heartbeat packets and other control packets. Monitoring this information indicates whether the physical connection between the publishing database and the subscribing database is satis-factory. This number is cumulative from the last time UniData was started or UniData Replication was reconfigured.

Subscriber Received

The number of data records that have been received from the other party of the repli-cation. This number is cumulative from the last time UniData was started or UniData Replication was reconfigured.

Note: When monitoring a publishing replication this number may be out of date if the Replication Status is not green.


Subscriber Committed

The number of data records that have been committed on the subscribing database. This number is cumulative from the last time UniData was started or UniData Repli-cation was reconfigured.

Note: When monitoring a publishing replication this number may be out of date if the Replication Status is not green.

Publisher Committed

The number of data records that have been committed on the publishing database. This number is cumulative from the last time UniData was started or UniData Replication was reconfigured.

TP Total

The sum of all transactions committed in the replication groups on the local system. This number is cumulative from the last time UniData was started or UniData Replication was reconfigured.

CGTPs Resolved

The sum of all transactions committed across more than one replication group on the local system. This number is cumulative from the last time UniData was started or UniData Replication was reconfigured.


Replication Group Status TableThe Replication Group Status table displays the current status of each

replication group belonging to the Replication you specify.

The following information is displayed in the Replication Group Status table:

Group Name – The name of the replication group.Conn. Status – The connection status between the publishing system and the subscribing system in the group. The status can be one of the following:

Green – The publisher and subscriber are connected in this group.Yellow – The Replication group has been suspended by an administrator.Red – The Replication group has terminated abnormally.


In-Sync – Inicates whether the subscribing files are synchronized with the publishing files in the group. The In-Sync status can be one of the following:

Green – The publishing and subscribing databases are synchronized.Yellow – There are pending updates in this Replication Group that have not been applied to the subscribing database.

Rep. Status – The current Replication Group status. The status can be one of the following on the publishing system:

REP_RUNNING – The replication is running.REP_SYNCING – The replication is performing synchronization.REP_SUSPENDED – The replication is suspended.REP_DO_SUSPEND – The replication is in the process of suspending.REP_EXIT – The replication is suspended due to an abnormal termination.

The status can be one of the following on the subscribing system:SUB_STOP – The replication is stopped.SUB_EXIT – The subscribing system has exited abnormally.SUB_SHUTDOWN – Replication on the subscribing system has been shut down.SUB_RUNNING – Replication on the subscribing system is running.SUB_DO_RECONFIG – A reconfiguration process is occurring on the subscribing system.SUB_DO_SUSPEND – Replication is suspended on the subscribing system.SUB_SYNCING – Replication is performing synchronization on the subscribing system.SUB_RESYNCING – Replication is performing resynchronization on the subscribing system.SUB_DO_FAILOVER – The subscribing system is performing a failover.


Changed By – The event or reason that caused the Replication status to change. If the status changed due to an exception, this column displays the error category and error code. A detailed error string is available in the tooltips. The following list describes the valid events or reasons can cause a change in the Replication status:

PUB_STARTUP – The publishing system started.SYS_STARTUP – The UniData system started.AUTO_SYNC – Replication is automatically resuming.PUB_REQUEST – A request was sent from the publishing system, or an event occurred on the publishing system resulting in a change of status. SUB_REQUEST – A request was sent from the subscribing system, or an event occurred on the subscribing system resulting in a change of status.DBA_ORDER – The system administrator issued a request resulting in a change of status.RECONFIG – Replication is reconfiguring. FAILOVER – A failover has occurred.CM_REQUEST – When running the Recoverable File System, the CM daemon is unable to finish a checkpoint until all standby subscribing systems have received the replication log generated before a checkpoint begins. If this does not happen in the configurable timeframe, the CM daemon requests the repmanager process to suspend the replication.SCHEDULED – The repmanager process can only schedule a SYNC command for DEFERRED replication.SYNCDONE – A sychronization process succeeded.REMOTE_REQ – A subsribing system can request to execute a SYNC command on the publishing system. CGTP_SUSPEND – Cross-group transaction processing is suspended.

#Recv’d – The number of packets received in the group. Monitoring this number indicates if the physical connection between the publishing system and subscribing system is satisfactory.


#Sent – The number of packets sent in the group. Monitoring this number indicates if the physical connection between the publishing system and subscribing system is satisfactory. This number is cumulative from the last time UniData was started or UniData Replication was reconfigured.Data Replicated – The total amount of data, in bytes, replicated in the group. On a publishing system this field represents the total amount of data sent out. On a subscribing system, this field represents the total amount of data received from the publishing system.This number is cumulative from the last time UniData was started or UniData Replication was reconfigured. SubGot – The Log Sequential Number of the latest replication log received by the subscribing system. This number is cumulative from the last time UniData was started or UniData Replication was reconfigured.SubDone – The Log Sequential Number of the latest replication log committed to the subscribing database. This number is cumulative from the last time UniData was started or UniData Replication was reconfigured.PubDone – The Log Sequential Number of the latest replication log committed to the publishing database. This number is cumulative from the last time UniData was started or UniData Replication was reconfigured.#TP – The number of transactions resolved in this group, including cross-group transactions. This number is cumulative from the last time UniData was started or UniData Replication was reconfigured.


11Chapter

Configuring Log Files for RFS

Configuring Log Files . . . . . . . . . . . . . . . . . 11-3Configuring Archive Files . . . . . . . . . . . . . . . . 11-7

This chapter describes how to define log files for the Recoverable File System.

For detailed information about RFS, see “Administering the Recoverable File System.”

11-2 Using UniAdmin

Configuring Log FilesSelect one of the following methods to access the Logging Config dialog box:

From the UniData Admin window, double-click RFS Configuration, then click Logging Configuration.From the UniAdmin menu, click Admin, then select RFS Configuration, then click Logging Configuration.


The types of log files are:

Before image log filesAfter image log filesFile-level log files

Configuring Log Files 11-3

Before Image Log Files

When you update database files that you define as recoverable, UniData first writes a copy of the unaltered file blocks to a before image log file. If your system crashes, UniData can restore the database by first reading the before image log files and writing them back into the recoverable files. The Recoverable File System then updates the files with information from the after image log files.

After Image Log Files

When you update database files that you define as recoverable, UniData does not write the changes directly to your database files. Instead, UniData records the changes in an after image log file and to the system buffer. Periodically, UniData flushes the system buffer pages to update your database. If your system crashes, UniData can recover your files to a state that existed before the crash by first reading the before image log files and writing them back into the recoverable files, then reading the after image log files and writing the changes recorded in them back into the recoverable files.

File-Level Log Files

A file-level log file stores a record of operations that affect an entire file rather than affecting the contents of a file. Commands that produce entries in a file-level log file include CREATE.FILE, DELETE.FILE, CLEAR.FILE, CNAME, CREATE.INDEX, DELETE.INDEX, BUILD.INDEX, ENABLE.INDEX, and DISABLE.INDEX. During crash recovery, UniData uses the file-level log file to recover certain of these actions, and prompts you to redo the ones it cannot restore.

Crash recovery attempts to recover CLEAR.FILE and any completed file-level operations automatically, except for index operation. If a file-level operation is incomplete, UniData prints a message in the FileInfo file located in udthome. Media recovery attempts to recover all file-level operations except for index operations.

11-4 Using UniAdmin

Each line in the logconfig file represents a log file. You must define five attributes for each log file that must appear in the logconfig file.

Before and After Image Log File Fields

Field Description

Filename The full path and file name of the log file. You can use any file name.

Flag Select the appropriate flag:021 describes an after image log022 describes a before image log0120 describes a file-level log

Blocksize The block size of the log file. A UNIX block size should be a multiple of the file system block size. A raw disk file should be a multiple of the disk sector size. IBM recommends a 4096-byte block size for both UNIX file system and raw disk logs. The block size cannot exceed 16384.

Start Block The start block offset in the log file.

Log Length The log file size as specified by the number of blocks in the log file.

Make entries in the in this order:

1. First group of after image logs. 2. First group of before image logs. 3. Second group of after image logs.4. Second group of before image logs.5. File-level log file.

In the Parameters area of the Logging Config dialog box, enter the following information:

FilenameFlagBlocksizeStart blockLog length

Highlight a log file definition in the upper part of the Logging Config dialog box.

Configuring Log Files 11-5

If you click Insert, UniData inserts the log file definition above the highlighted log file. If you click Append, UniData inserts the log file definition below the highlighted log file.

Click Change to change information about the highlighted log file.

Click Remove to remove the highlighted log file.

Click Save to save your changes, or Close to exit the program without saving changes.

11-6 Using UniAdmin

Configuring Archive FilesSelect one of the following methods to access the Archive Config dialog box:

From the UniData Admin window, double-click RFS Configuration, then click Archive Configuration.From the UniAdmin menu, click Admin, then select RFS Configuration, then click Archive Configuration.


Configuring Archive Files 11-7

Each line in the archive table represents an archive file. There are four attributes for each archive file that must appear in the archconfig file.

Archive File Fields

Field Description

Filename The full path and file name of the archive file. You can use any file name.

Blocksize The block size of the archive file. A UNIX file size should be a multiple of the file system block size. A raw disk file should be a multiple of the disk sector size. IBM recommends a 4096-byte block size for both UNIX file system and raw disk archives. The block size cannot exceed 16,384.

Start Block The start block offset in the archive file.

Log Length The archive file size as specified by the number of blocks in the archive file.

In the Parameter Editor area of the Archive Configuration dialog box, enter the following information for each archive file:

File nameBlock sizeStart blockLog length

Highlight a log file definition in the upper part of the Archive Configuration dialog box.

If you click Insert, UniData inserts the log file definition above the highlighted log file. If you click Append, UniData inserts the log file definition below the highlighted log file.

Click Change to change information about the highlighted log file.

Click Remove to remove the highlighted log file.

Click Save to save your changes, or Close to exit the program without saving changes.

11-8 Using UniAdmin

12Chapter

Displaying Programs in Shared Memory

12-2 Using UniAdmin

This chapter describes how to view the number of users sharing globally cataloged UniBasic programs.

Select one of the following methods to access the UniData Catalog Shared Memory dialog box:

From the UniAdmin window, double-click Shared Programs.From the UniAdmin menu, click Admin, then click Shared Programs.From the UniAdmin toolbar, click the Shared Programs icon, as shown in the following example:

Shared Programs Icon


Ref Count indicates the number of users currently sharing the program. To update this count, click Refresh.

13Chapter

Configuring SSL

Configuring SSL Through UniAdmin . . . . . . . . . . . . 13-2Accessing UniData SSL Configuration Dialog Box . . . . . . . . 13-3Creating a Certificate Request . . . . . . . . . . . . . . 13-4Creating a Certificate . . . . . . . . . . . . . . . . . 13-11Creating a Security Context . . . . . . . . . . . . . . . 13-19Configuring SSL for UniObjects for Java or Telnet . . . . . . . . 13-35

C:\Program Files\Adobe\FrameMaker8\UniData 7.2\7.2rebranded\UNIADMIN\uniadminCH13.fm3/9/10

Configuring SSL Through UniAdminSecure Sockets Layer (SSL) is a transport layer protocol that provides a secure channel between two communicating programs over which you can send arbitrary application data securely. It is by far the most widely deployed security protocol used on the World Wide Web.

SSL provides server authentication, encryption, and message integrity. It can also support client authentication.

UniData currently supports CallHTTP and the Sockets API. SSL support is important for both of these protocols in order to deploy commercial applications and securely process sensitive data, such as credit card transactions.

This chapter assumes that users who want to use SSL have a basic knowledge of public key cryptography.

13-2 Using UniAdmin

C:\Program Files\Adobe\FrameMaker8\UniData

Accessing UniData SSL Configuration Dialog BoxUse the UniData SSL Configuration dialog box to administer SSL.

Select one of the following methods to access the UniData SSL Configuration dialog box:

From the UniAdmin window, double-click SSL Configure.From the UniAdmin menu, select Admin, then click SSL Configure.


13-3


Creating a Certificate RequestComplete the following steps to generate an X.509 certificate request, which you can send to a third-party CA to obtain a certificate, or use as input to the Generate Certif-icate wizard.

1. Click Generate a Certificate Request. A dialog box similar to the following example appears:

Click Next.

13-4 Using UniAdmin


2. The Certficate Request file dialog box appears, as shown in the following example:

In the Certficate Request File box, enter the full path of the operating sys-tem-level file to hold the certificate request, or click Browse to search for the location.Click the type of Digest Algorithm for the certificate request. The following types of algorithms are available:

MD5 – MD5 hash functionSHA1 – SHA1 hash function

Click Next.

13-5


3. Next, choose the properties for the certificate from the Request Properties dialog box, as shown in the following example:

The available properties are:C – Country CodeST – State or ProvinceL – Locality (city)O – OrganizationOU – Organization UnitCN – Common NameEmail – Email address

You must define the Country Code, Organization, and Common Name.Click Next.

13-6 Using UniAdmin


4. From the Key Pair Selection dialog box, select the type of Key Pair.

If you are using a previously generated key pair for the certificate request, select Using existing key pair. If you are creating a new key pair, select Generating new key pair.Click Next to continue.

13-7


5. The Key Pair Info dialog box appears, as shown in the following example:

Specify the Key Algorithm. Select RSA if you want to use an RSA key algorithm, or DSA if you want to use a DSA key algorithm.Select the key length from the Key Length list. Valid values range from 512 to 2048.Select the Key File Format. Select PEM for a Privacy Enhanced Mail for-mat, or DER for a Distinguished Encoding Rules format.If you selected a Key File Format of DER, enter the patch to the parameter file in the Parameter File box. UniData uses this file to generate a new key pair. If you leave this box empty, UniData uses the default.In the Private Key File box, enter the name of the file in which you want to store the generated private key, or click Browse to search for the existing key if you selected Use Existing Key Pair.In the Public Key File box, enter the name of the file in which you want to store the generated public key, or click Browse to search for the existing key if you selected Use Existing Key Pair.Click Next to continue.

13-8 Using UniAdmin


6. Next, define a password for the private key from the Password dialog box, as shown in the following example:

In the Password for Private Key box, enter a password for the private key. Confirm the password by reentering it in the Confirm Password box.

13-9


7. Click Create to generate the certificate request file. The following dialog box appears after the certificate request is successfully generated:

Click OK. The following dialog box appears:

Click Finish to return to the UniData SSL Configuration wizard.



Creating a CertificateYou can create two types of certificates from UniAdmin:

Self-signed certificates as a root CA that can be used later to sign other certificates.CA signed certificates.

To create a certificate, from the UniData SSL Configuration dialog box,click Certificate. A dialog box similar to the following example appears:

13-11


To begin generating an X.509 certificate, or to view details of an existing certificate, click Generate a Certificate. A dialog box similar to the following example appears:

Click Next, then complete the following steps to create a certificate:



1. The Certificate File dialog box appears, as shown in the following example:

In the Certificate Request File box, enter the certificate request file name, or click Browse search for the file. Click Next.

13-13


2. The Certificate Request File dialog box appears, as shown in the following example:

In the Certficate Request File box, enter the name of the file to write the generated certificate, or click Browse to search for the file. Click Next.



3. The Validity Period dialog box appears, as shown in the following example:

Select the number of days for which certificate is valid from the Validity Period list. The certificate is valid starting from the current date until the number of days you specify expires. The default value is 365 days.Click Next.

13-15


4. The Certificate Type dialog box appears, as shown in the following example:

Select the type of certificate. The following types of certificates are available:

Self SignCA SignLeaf CA Sign

Click Next to continue.



5. If the type of certficate is CA or Leaf CA, you must specify a private key file associated with the signing CA certificate. Define the private key file from Private Key File dialog box, as shown in the following example:

Enter the name of the private key file in the Private Key File box, or click Browse to search for this file, then click Next.

13-17


6. Enter the password for the private key file in the Password dialog box, as shown in the following example:

7. Click Create to create the certificate.



Creating a Security ContextA security context is a data structure that holds all aspects of security characteristics that the application intends to associate with a secured connection.

To create a security context, from the UniData SSL Configuration dialog box, click the Security Context Record tab. A dialog box similar to the following example appears:

Complete the following steps to create a Security Context Record:

1. Select the account where you want to create or view the security context record (SCR) from the SCR Database list. UniAdmin populates the Path box with the full path of the database.

13-19


2. To add an SCR record, click Add. A dialog box similar to the following example appears:

Make sure you have generated the necessary keys and certificates needed before proceeding.Click Next to continue.



3. The Security Context Record ID dialog box appears, as shown in the following example:

Enter an ID for the SCR in the Security Context Record ID box.Select the appropriate version for the SCR record in the Version box. Valid versions are:

SSLv2SSLv3TLSv1

Note: IBM recommends that you only use SSLv3 or TLSv1.Click Next to continue.

13-21


4. Next, define if the SCR for the server or client from the SCR for Server or Client dialog box, as shown in the following example:

If the SCR is for use by a server, select SCR for Server. If the SCR is for use by a client, select SCR for Client.Click Next to continue.



5. When you select Client Authentication, during the initial SSL handshake, the server sends the client authentication request to the client. It also receives the client certificate and performs authentication according to the issuer’s certificate (or certificate chain) set in the security context.Set authentication parameters from the Server Authenticate dialog box, as shown in the following example:

If you want to set authentication, select the Client Authentication check box.The Authentication Depth value determines how deeply UniData verifies before determining that a certificate is not valid.Depth is the maximum number of intermediate issue certificates, or CA cer-tificates, UniData must examine while verifying an incoming certificate. A depth of 0 indicates that the certificate must be self-signed. A depth of 1 means that the incoming certificate can be either self-signed, or signed by a CA known to the security context.You can set Authentication Depth on the server and the client. The default value for both is 1.

13-23


You can add an authentication rule to a security context. UniData uses the rules during SSL negotiation to determine whether or not to trust the peer. UniData supports the following rules:

Verification Strength rule – This rule governes the SSL negotiation and determines whether or not an authentication process is considered successful. There are two levels of security, generous and strict. If you specify generous, the certificate need only contain the subject name (common name) that matches one specified by “PeerName” to be considered valid. If you specify strict, the incoming certificate must pass a number of checks, including signature check, expiry check, purpose check, and issuer check.

Note: IBM recommends setting the rule to generous only for development or testing purposes.

PeerName rule – By specifying the PeerName rule and attribute mark separated common names in ruleString, trust server/client names will be stored in the context.During the SSL handshake negotiations, the server sends its certificate to the client. By specifying trust server names, the client can control with which server or servers it should communicate. During the hand-shake, once the server certificate has been authenticated by way of the issuer (CA) certificate(s). UniData compares the subject name con-tained in the certificate against the trusted server names set in the context. If the server subject name matches one of the trusted names, communication continues, otherwise UniData does not establish the connection.

If no trusted peer name is set, any peer is considered legitimate.To add an authentication rule, click Add. A dialog box similar to the follow-ing example appears:

Enter the information for the new rule, then click OK. Select the Authentication Strength, then click Next.



6. The Certificate Path Rule enables you to specify locations to search for certificates. Define the Certificate Path Rule from the Certificate Path Rule dialog box, as shown in the following example:

When you add a certificate to an SCR, the full path for that certificate is reg-istered in the SCR. This path is derived from the current directory where UniData is running. When the certificate is loaded into memory to establish the SSL connection, UniDara uses this registered full path to retrieve the certificate. You can change the path in one of the following ways:

Relative – If you select Relative, UniData looks in the current directory where UniData is running for the certificate. Note: Some of the UniData processes, such as the telnet server processes, run from the system directory.Path – If you select Path, UniData uses the path you specify for loading the certificate added to this SCR. You can specify either an absolute path or a relative path.Env – If you select Env, enter an environment variable name in the Env box. If you specify this option, the UniData process first obtains the

13-25


value of the environment variable you specify and uses that value as the path to load the certificates.Note: UniData only evaluates the environment variable when the first SSL connection is made. The value is cached for later reference.

7. You can load a certificate, or multiple certificates, into a security context for use as a UniData server certificate or client certificate. Alternatively, you can specify a directory that contains the certificates to use as a Certificate Authority (CA) certificate to authenticate incoming certificates or act as a revocation list, checking for expired or revoked certificates.The purpose of a certificate is to bind the name of an entity with its public key. It is basically a means of distributing public keys. A certificate always contains the following three pieces of information:

NamePublic KeyDigital signature signed by a trusted third party called a Certificate Authority (CA) with its private key.

If you have the public key of the CA, you can verify that the certificate is authentic.SSL protocol specifies that when two parties start a handshake, the server must always send its certificate to the client for authentication. It may also require the client to send its certificate to the server for authentication. Uni-Data servers that act as HTTP clients are not required to maintain a client certificate. UniData applications that act as SSL socket servers must install a server certificate. UniObjects for Java servers and telnet servers also require server certificates.There can be only one server/client certificate per specific security context. Adding a new certificate automatically replaces an existing certificate. However, for issuer certificates, UniData chains a new one with existing certificates so UniData applications can perform chained authentication.If the issuer certificate is in PEM format, it can contain multiple certificates generated by concatenating certificates together.Note: All certificates that form an issuer chain must be of the same type.



Select the self certificate file from the Self Certificate dialog box, as shown in the following example:

In the Self Certificate File box, enter the path to the file containing the self certificate, or click Browse to search for the file.Next, select the format for the certificate. Select PEM for Base64 encoded format, or DER for ASN.1 binary format.Click Next to continue.

13-27


8. If you are defining an SCR record intended to be used by a server, you must install a private key. If you are defining an SRC record intended to be used by a client and you do not install a self-certificate, you do not need to install a private key.You can load a private key into a security context so it can be used by SSL functions. Setting a private key replaces an existing private key.UniData uses a private key to digitally sign a message or encrypt a symmet-ric secret key to use for data encryption.Select the private key associated with self certificate from the Private Key dialog box, as shown in the following example:

In the Private Key File box, enter the file that contains the private key, or click Browse to search for the file.In the Password for Private Key box, enter the password for the private key.Next, select the format for the private key. Click PEM for Base64 encoded format, or DER for ASN.1 binary format.



Click Next to continue.9. To define a CA certificate, in the CA Certificate dialog box, click Add. A

dialog box similar to the following example appears:

In the Certificate File box, enter the path to the file containing the certifi-cate, or click Browse to search for the file.Next, select the format for the certificate. Click PEM for Base64 encoded format, or DER for ASN.1 binary format.Click OK to add the certificate, or Cancel to exit.Click Next to continue.

10. You can generate a random file from a series of source files and set that file as the default random file for the SCR record.The strength of cryptographic functions depends on the true randomness of the keys. Be default, UniData uses the .rnd file in the current account. You can override the default by adding a random seed file.Note: IBM recommends you use the default .rnd file.To select a random seed file other than the default, click Browse to search for the file, as shown in the following example:

13-29


To create a new random seed file, click New Random File. A dialog box similar to the following example appears:

Enter the path to random file, or click Browse to select the random source file.In the File Length list, choose the file length. In the Random Seed Source Files box, enter the random seed source files.Click OK.



11. You can define ciphers from the Ciphers dialog box, as shown in the following example:

Ciphers enable you to identify which cipher suites should be supported for the specified context. It affects the cipher suites and public key algorithms supported during the SSL/TLS handshake and subsequent data exchanges.When a context is created, its cipher suites will be set to SSLv3 suites sup-ported by the SSL version you selected.In the Ciphers box, enter the Cipher Suite for this SCR record.The CipherSpecs parameter is a string containing cipher-spec separated by colons. An SSL cipher specification in cipher-spec is composed of 4 major attributes as well as several, less significant attributes. For detailed informa-tion about Cipher Suites, see “UniData BASIC Extensions.”

13-31


12. From the Certificate Revocation List dialog box, click Add to add a CRL file as part of a revocation list, as shown in the following example:


In the Certificate File box, enter the path to the file containing the CRL, or click Browse to search for the file.Next, select the format for the CRL file. Click PEM for Base64 encoded format, or DER for ASN.1 binary format.,Click OK to create the SCR record, or click Cancel to exit.Click Next to continue.




In the Password for SCR Record box, enter a password to access the record. Reenter the password in the Confirm Password for SCR Record box.Click Create to create the SCR record, or click Cancel to exit.

13-33


Configuring SSL for UniObjects for Java or TelnetAfter you create an SCR record, you need to configure SSL for UniObjects for Java or SSL for Telnet.

An SCR record contains all SSL-related properties necessary for the server to establish a secured connection with an SSL client. The properties include the server’s private key certificate, client authentication flag and strength, and trusted entities. For more information, see “UniData BASIC Extensions.”

From the UniData SSL Configuration dialog box, select the Configure tab. A dialog box similar to the following example appears:

Complete the following steps to configure SSL:



1. Click New. A dialog box similar to the following example appears:

From the Service Name list, select a service name.From the SCR Database list, select the database for this configuration entry. UniAdmin automatically populates the Path box.Select the SCR record from the SCR Record list, then enter the password for this record in the Password Seed box.

13-35

14Chapter

Administering Users

View Number of Users . . . . . . . . . . . . . . . 14-3 Logging a User Out of UniData . . . . . . . . . . . . . 14-3

You can view the user currently logged into the UniData system, or logout an existing user from UniAdmin.

Select one of the following methods to access the User Administration dialog box:

From the UniAdmin window, double-click Users.From the UniAdmin menu, select Admin, then click Users.From the UniAdmin toolbar, click the Users icon, as shown in the following example.

Users icon

The following example illustrates the Users Administration dialog box:

View Number of UsersThe Number of Users area of the dialog box displays the number of users for which you are licensed in the Licensed box.

The Current # of Users area of the dialog box displays the number of Udt and Sql users currently using UniData.

14-2

Viewing User Information

The following table describes the column headings in the User Administration window.

User Administration Column Headings


UDTNO Sequential number UniData assigns to each user.

USRNBR System-level process ID (pid) assigned to a UniData session.

UID System-level ID assigned to a user.

USRNAME Login name of the user.

USRTYPE Type of process the user is running.

TTY Device ID.

Login Time Time and date the user process started.

Logging a User Out of UniDataTo log a user out of UniData, highlight the user, then click Logout. A dialog box prompting for confirmation appears before the selected user is logged out of UniData.

14-3 Using UniAdmin

unidata - rocket software · 9/3/2010 · this software and the associated documentation are...

Documents