Preface

This manual explains the system definition of HiRDB Version 8, a scalable database server program product.

Intended readers

This manual is intended for users who will be constructing or operating HiRDB Version 8 ("HiRDB") relational database systems.

It is assumed that readers of this manual have the following:

This manual is based on the following manuals, which should be read before reading this manual:

Organization of this manual

This manual is organized as follows:

Chapter 1. Overview
Explains the organization of the HiRDB system definitions and the syntax rules for specifying the system definitions.
Chapter 2. System Common Definition
Explains the system common definition.
Chapter 3. Unit Control Information Definition
Explains the unit control information definition.
Chapter 4. Server Common Definition
Explains the server common definition.
Chapter 5. Single Server Definition
Explains the single server definition.
Chapter 6. Front-End Server Definition
Explains the front-end server definition.
Chapter 7. Dictionary Server Definition
Explains the dictionary server definition.
Chapter 8. Back-End Server Definition
Explains the back-end server definition.
Chapter 9. UAP Environment Definition
Explains the UAP environment definition.
Chapter 10. Foreign Server Information Definition (When a Foreign Server Is HiRDB)
Explains the foreign server information definition when a foreign server is HiRDB. Create this definition for using the HiRDB External Data Access facility.
Chapter 11. Foreign Server Information Definition (When a Foreign Server Is XDM/RD E2)
Explains the foreign server information definition when a foreign server is XDM/RD E2. Create this definition for using the HiRDB External Data Access facility.
Chapter 12. Foreign Server Information Definition (When a Foreign Server Is ORACLE)
Explains the foreign server information definition when a foreign server is ORACLE. Create this definition for using the HiRDB External Data Access facility.
Chapter 13. Hub Optimization Information Definition
Explains the Hub optimization information definition. Create this definition for using the HiRDB External Data Access facility.
Appendix A. List of Operands
Provides a list of operands and indicates the operands that can be changed during a restart.
Appendix B. Operand Specification Values
Explains the information to be specified in operands (arranged by types of operands).
Appendix C. Examples of Definitions
Provides examples of HiRDB system definitions.
Appendix D. Formulas for Determining Operand Specification Values
Provides and explains formulas that can be used to determine operand specification values.
Appendix E. Determining the Number of Locked Resources
Provides and explains formulas that can be used to determine the numbers of locked resources.
Appendix F. Operands Checked by the pdconfchk Command
Provides a list of operands that can be checked by executing the pdconfchk command.
Appendix G. List of Operands That Can Be Specified When Using the Standby-less System Switchover (Effects Distributed) Facility (Unit Control Information Definition)
Lists the operands that can be specified in the unit control information definition for the standby-less system switchover (effects distributed) facility.

Related publications

This manual is related to the following manuals, which should be read as required.

HiRDB (for Windows)
HiRDB (for UNIX)
HiRDB (for both Windows and UNIX)

*: This manual has been published in Japanese only; it is not available in English.

You must use the UNIX or the Windows manuals, as appropriate to the platform you are using.

Others

Organization of HiRDB manuals

The HiRDB manuals are organized as shown below. For the most efficient use of these manuals, it is suggested that they be read in the order they are shown, going from left to right.

[Figure]

Conventions: Abbreviations

Unless otherwise required, this manual uses the following abbreviations for product and other names.

Name of product or other entityRepresentation
HiRDB/Single Server Version 8HiRDB/Single ServerHiRDB or HiRDB Server
HiRDB/Single Server Version 8(64)
HiRDB/Parallel Server Version 8HiRDB/Parallel Server
HiRDB/Parallel Server Version 8(64)
HiRDB/Developer's Kit Version 8HiRDB/Developer's KitHiRDB Client
HiRDB/Developer's Kit Version 8(64)
HiRDB/Run Time Version 8HiRDB/Run Time
HiRDB/Run Time Version 8(64)
HiRDB Datareplicator Version 8HiRDB Datareplicator
HiRDB Dataextractor Version 8HiRDB Dataextractor
HiRDB Text Search Plug-in Version 7HiRDB Text Search Plug-in
HiRDB Spatial Search Plug-in Version 3HiRDB Spatial Search Plug-in
HiRDB Staticizer Option Version 8HiRDB Staticizer Option
HiRDB LDAP Option Version 8HiRDB LDAP Option
HiRDB Advanced Partitioning Option Version 8HiRDB Advanced Partitioning Option
HiRDB Advanced High Availability Version 8HiRDB Advanced High Availability
HiRDB Non Recover Front End Server Version 8HiRDB Non Recover FES
HiRDB Disaster Recovery Light Edition Version 8HiRDB Disaster Recovery Light Edition
HiRDB External Data Access Version 8HiRDB External Data Access
HiRDB External Data Access Adapter Version 8HiRDB External Data Access Adapter
HiRDB Adapter for XML - Standard EditionHiRDB Adapter for XML
HiRDB Adapter for XML - Enterprise Edition
HiRDB Control ManagerHiRDB CM
HiRDB Control Manager AgentHiRDB CM Agent
Hitachi TrueCopyTrueCopy
Hitachi TrueCopy basic
TrueCopy
TrueCopy remote replicator
JP1/Automatic Job Management System 2JP1/AJS2
JP1/Automatic Job Management System 2 - Scenario OperationJP1/AJS2-SO
JP1/Cm2/Extensible SNMP AgentJP1/ESA
JP1/Cm2/Extensible SNMP Agent for Mib Runtime
JP1/Cm2/Network Node ManagerJP1/NNM
JP1/Integrated Management - ManagerJP1/Integrated Management or JP1/IM
JP1/Integrated Management - View
JP1/Magnetic Tape AccessEasyMT
EasyMT
JP1/Magnetic Tape LibraryMTguide
JP1/NETM/DMJP1/NETM/DM
JP1/NETM/DM Manager
JP1/Performance ManagementJP1/PFM
JP1/Performance Management Agent for HiRDBJP1/PFM-Agent for HiRDB
JP1/Performance Management - Agent for PlatformJP1/PFM-Agent for Platform
JP1/Performance Management/SNMP System ObserverJP1/SSO
JP1/VERITAS NetBackup BS v4.5NetBackup
JP1/VERITAS NetBackup v4.5
JP1/VERITAS NetBackup BS V4.5 Agent for HiRDB LicenseJP1/VERITAS NetBackup Agent for HiRDB License
JP1/VERITAS NetBackup V4.5 Agent for HiRDB License
JP1/VERITAS NetBackup 5 Agent for HiRDB License
OpenTP1/Server Base Enterprise OptionTP1/EE
Virtual-storage Operating System 3/Forefront System ProductVOS3/FSVOS3
Virtual-storage Operating System 3/Leading System ProductVOS3/LS
Extensible Data Manager/Base Extended Version 2
XDM basic program XDM/BASE E2
XDM/BASE E2
XDM/Data Communication and Control Manager 3
XDM Data communication control XDM/DCCM3
XDM/DCCM3
XDM/Relational Database XDM/RDXDM/RDXDM/RD
XDM/Relational Database Extended Version 2
XDM/RD E2
XDM/RD E2
VOS3 Database Connection ServerDB Connection Server
DB2 Universal Database for OS/390 Version 6DB2
DNCWARE ClusterPerfect (Linux Version)ClusterPerfect
Microsoft(R) ExcelMicrosoft Excel or Excel
Microsoft(R) Visual C++(R)Visual C++ or C++
Oracle 8iORACLE
Oracle 9i
Oracle 10g
Sun JavaTM System Directory ServerSun Java System Directory Server or Directory Server
HP-UX 11i V2 (IPF)HP-UX or HP-UX (IPF)
Red Hat LinuxLinux
Red Hat Enterprise Linux
Red Hat Enterprise Linux AS 3 (IPF)Linux (IPF)Linux
Red Hat Enterprise Linux AS 4 (IPF)
Red Hat Enterprise Linux AS 3(AMD64 & Intel EM64T)Linux (EM64T)
Red Hat Enterprise Linux AS 4(AMD64 & Intel EM64T)
Red Hat Enterprise Linux ES 4(AMD64 & Intel EM64T)
turbolinux 7 Server for AP8000Linux for AP8000
Microsoft(R) Windows NT(R) Workstation Operating System Version 4.0Windows NT
Microsoft(R) Windows NT(R) Server Network Operating System Version 4.0
Microsoft(R) Windows(R) 2000 Professional Operating SystemWindows 2000
Microsoft(R) Windows(R) 2000 Server Operating System
Microsoft(R) Windows(R) 2000 Datacenter Server Operating System
Microsoft(R) Windows(R) 2000 Advanced Server Operating SystemWindows 2000 or Windows 2000 Advanced Server
Microsoft(R) Windows ServerTM 2003, Standard EditionWindows Server 2003
Microsoft(R) Windows ServerTM 2003, Enterprise Edition
Microsoft(R) Windows ServerTM 2003 R2, Standard EditionWindows Server 2003 R2 or Windows Server 2003
Microsoft(R) Windows ServerTM 2003 R2, Enterprise Edition
64 bit Version Microsoft(R) Windows ServerTM 2003, Enterprise Edition (IPF)Windows Server 2003 (IPF) or Windows Server 2003
Microsoft(R) Windows ServerTM 2003, Standard x64 EditionWindows Server 2003 or Windows Server 2003 x64 EditionsWindows (x64)
Microsoft(R) Windows ServerTM 2003, Enterprise x64 Edition
Microsoft(R) Windows ServerTM 2003 R2, Standard x64 EditionWindows Server 2003, Windows Server 2003 R2 or Windows Server 2003 x64 Editions
Microsoft(R) Windows ServerTM 2003 R2, Enterprise x64 Edition
Microsoft(R) Windows(R) XP Professional x64 EditionWindows XP or Windows XP x64 Edition
Microsoft(R) Windows(R) XP Professional Operating SystemWindows XP ProfessionalWindows XP
Microsoft(R) Windows(R) XP Home Edition Operating SystemWindows XP Home Edition
Single serverSDS
System managerMGR
Front-end serverFES
Dictionary serverDS
Back-end serverBES

This manual also uses the following abbreviations:

AbbreviationFull name or meaning
ACKAcknowledgement
ADMAdaptable Data Manager
ADOActiveX Data Objects
ADTAbstract Data Type
APApplication Program
APIApplication Programming Interface
ASN.1Abstract Syntax Notation One
BESBack End Server
BLOBBinary Large Object
BOMByte Order Mark
CD-ROMCompact Disc - Read Only Memory
CGICommon Gateway Interface
CLOBCharacter Large Object
CMTCassette Magnetic Tape
COBOLCommon Business Oriented Language
CORBA(R)Common ORB Architecture
CPUCentral Processing Unit
CSVComma Separated Values
DAOData Access Object
DATDigital Audio Taperecorder
DBDatabase
DBMDatabase Module
DBMSDatabase Management System
DDLData Definition Language
DF for Windows NTDistributing Facility for Windows NT
DF/UXDistributing Facility/for UNIX
DICDictionary Server
DLTDigital Linear Tape
DMLData Manipulate Language
DNSDomain Name System
DOMDocument Object Model
DSDictionary Server
DTDDocument Type Definition
DTPDistributed Transaction Processing
DWHData Warehouse
EUCExtended UNIX Code
EXExclusive
FATFile Allocation Table
FDFloppy Disk
FESFront End Server
FQDNFully Qualified Domain Name
FTPFile Transfer Protocol
GUIGraphical User Interface
HBAHost Bus Adapter
HDHard Disk
HTMLHyper Text Markup Language
IDIdentification number
IPInternet Protocol
IPFItanium(R) Processor Family
JARJava Archive File
Java VMJava Virtual Machine
JDBCJava Database Connectivity
JDKJava Developer's Kit
JFSJournaled File System
JFS2Enhanced Journaled File System
JISJapanese Industrial Standard code
JP1Job Management Partner 1
JREJava Runtime Environment
JTAJava Transaction API
JTSJava Transaction Service
KEISKanji processing Extended Information System
LANLocal Area Network
LDAPLightweight Directory Access Protocol
LIPloop initialization process
LOBLarge Object
LRULeast Recently Used
LTOLinear Tape-Open
LULogical Unit
LUNLogical Unit Number
LVMLogical Volume Manager
MGRSystem Manager
MIBManagement Information Base
MRCFMultiple RAID Coupling Feature
MSCSMicrosoft Cluster Server
NAFONetwork Adapter Fail Over
NAPTNetwork Address Port Translation
NATNetwork Address Translation
NICNetwork Interface Card
NISNetwork Information Service
NTFSNew Technology File System
ODBCOpen Database Connectivity
OLAPOnline Analytical Processing
OLEObject Linking and Embedding
OLTPOn-Line Transaction Processing
OOCOBOLObject Oriented COBOL
ORBObject Request Broker
OSOperating System
OSIOpen Systems Interconnection
OTSObject Transaction Service
PCPersonal Computer
PDM II E2Practical Data Manager II Extended Version 2
PICPlug-in Code
PNMPublic Network Management
POSIXPortable Operating System Interface for UNIX
PPProgram Product
PRProtected Retrieve
PUProtected Update
RAIDRedundant Arrays of Inexpensive Disk
RDRelational Database
RDBRelational Database
RDB1Relational Database Manager 1
RDB1 E2Relational Database Manager 1 Extended Version 2
RDORemote Data Objects
RiSeReal time SAN replication
RMResource Manager
RMMResource Manager Monitor
RPCRemote Procedure Call
SAXSimple API for XML
SDSSingle Database Server
SGMLStandard Generalized Markup Language
SJISShift JIS
SNMPSimple Network Management Protocol
SQLStructured Query Language
SQL/KStructured Query Language / VOS K
SRShared Retrieve
SUShared Update
TCP/IPTransmission Control Protocol / Internet Protocol
TMTransaction Manager
TMS-4V/SPTransaction Management System - 4V / System Product
UAPUser Application Program
UOCUser Own Coding
VOS KVirtual-storage Operating System Kindness
VOS1Virtual-storage Operating System 1
VOS3Virtual-storage Operating System 3
WSWorkstation
WWWWorld Wide Web
XDM/BASE E2Extensible Data Manager / Base Extended Version 2
XDM/DFExtensible Data Manager / Distributing Facility
XDM/DSExtensible Data Manager / Data Spreader
XDM/RD E2Extensible Data Manager / Relational Database Extended Version 2
XDM/SD E2Extensible Data Manager / Structured Database Extended Version 2
XDM/XTExtensible Data Manager / Data Extract
XFITExtended File Transmission program
XMLExtensible Markup Language

Log representations

The application log that is displayed by Windows Event Viewer is referred to as the event log. The following procedure is used to view the event log.

To view the event log:
1. Choose Start, Programs, Administrative Tools (Common), and then Event Viewer.
2. Choose Log, and then Application.
3. The application log is displayed. Messages with HiRDBSingleServer or HiRDBParallelServer displayed in the Source column were issued by HiRDB.
If you specified a setup identifier when you installed HiRDB, the specified setup identifier follows HiRDBSingleServer or HiRDBParallelServer.

Conventions: Diagrams

This manual uses the following conventions in diagrams:

[Figure]

Conventions: Fonts and symbols

Font and symbol conventions are classified as:

These conventions are described below.

General font conventions

The following table lists the general font conventions:

FontConvention
BoldBold type indicates text on a window, other than the window title. Such text includes menus, menu options, buttons, radio box options, or explanatory labels. For example, bold is used in sentences such as the following:
  • From the File menu, choose Open.
  • Click the Cancel button.
  • In the Enter name entry box, type your name.
ItalicsItalics are used to indicate a placeholder for some actual text provided by the user or system. Italics are also used for emphasis. For example:
  • Write the command as follows:
    copy source-file target-file
  • Do not delete the configuration file.
Code fontA code font indicates text that the user enters without change, or text (such as messages) output by the system. For example:
  • At the prompt, enter dir.
  • Use the send command to send mail.
  • The following message is displayed:
    The password is incorrect.

Examples of coding and messages appear as follows (although there may be some exceptions, such as when coding is included in a diagram):

MakeDatabase
...
StoreDatabase temp DB32

In examples of coding, an ellipsis (...) indicates that one or more lines of coding are not shown for purposes of brevity.

Conventions in syntax explanations

Syntax definitions appear as follows:

StoreDatabase [temp|perm] (database-name ...)

The following table lists and explains the symbols used in syntax definitions and explanations. When typing an actual command or definition, omit any syntax symbols listed here.

Example font or symbolConvention
StoreDatabaseCode-font characters must be entered exactly as shown.
database-nameThis font style marks a placeholder that indicates where appropriate characters are to be entered in an actual command.
SDBold code-font characters indicate the abbreviation for a command.
permUnderlined characters indicate the default value.
[ ]Square brackets enclose an item or set of items whose specification is optional.
Example: pdbuffer [-p]
This example indicates that you can specify either pdbuffer or pdbuffer -p.
|Only one of the options separated by a vertical bar can be specified at the same time.
Example: pdlogadfg -d sys | spd
This example indicates that you can specify either sys or spd for the -d option.
...An ellipsis (...) indicates that the item or items enclosed in ( ) or [ ] immediately preceding the ellipsis may be specified as many times as necessary.
Example: pdbuffer -r RDAREA-name [, RDAREA-name] ...
This example indicates that you can specify RDAREA-name after -r as many times as you wish.
()Parentheses indicate the range of items to which the vertical bar (|) or ellipsis (...) is applicable.
{ }A single pair of curly brackets encloses multiple items, one of which you must specify.
Example: pdbuffer [{-r RDAREA-name |
-i authorization-identifier.index-identifier | -o}]
This example indicates that you must specify any one of the three options enclosed by the curly brackets: -r RDAREA-name, -i authorization-identifier.index-identifier, or -o.
{{ }}A double pair of curly brackets encloses multiple items, all of which you can specify multiple times as a single unit.
Example: {{pdbuffer -a option-name}}
This example indicates that you can specify these multiple times as follows:
pdbuffer -a option-name
pdbuffer -a option-name
_An underlined value specifies a default.
Example: [pd_rpc_trace = Y | N]
If the operand is not specified, the default value (N) is used.
[Figure]A swung dash precedes the attributes of a user-specified value.
<< >>Double angle brackets enclose the default value assumed by the system when the specification is omitted.
< >Angle brackets enclose the syntax element notation for a user-specified value.
(( ))Double parentheses enclose the permitted range of values that can be specified.

Syntax element conventions

The following syntactical element symbols are used in this manual:

Syntactical element symbolMeaning
<alphabetics>The alphabetic characters (A-Z and a-z) and the underline (_)
<alphabetics and special characters>The alphabetic characters (A-Z and a-z) and the special characters #, @, and \
<alphanumerics>Alphabetics and the numeric digits (0-9)
<alphanumerics and special characters>Alphabetics, special characters, and numeric digits
<unsigned integer>Numeric value
<unsigned decimal>1Numeric value (0-9), period (.), numeric value (0-9)
<hexadecimal>Numeric digits and A-F (or a-f)
<identifier>2Alphanumeric character string beginning with an alphabetic character
<symbolic name>Alphanumeric character string beginning with an alphabetic character or a special character
<character string>Any string of characters
<pathname>3Alphanumeric characters, \, parentheses, spaces, and periods (.)
<host-name>Character string composed of alphabetic characters (A-Z, a-z), numeric characters, periods (.), hyphens (-), or underscores (_)
Note: All alphabetic characters must be single-byte characters. The syntactical element symbols are case sensitive.
1 If the numeric value preceding the period is 0, it can be omitted. Similarly, if the numeric value following the period is 0, both the period and the 0 can be omitted.
2 A space may also be included in RDAREA names. However, when an RDAREA name includes a space, the entire name must be enclosed in quotation marks (").
3 Path names depend on the OS being used. Do not use a backslash (\) in HiRDB file system area names. If you use a parenthesis or a space in a pathname, you must enclose the entire pathname in double quotation marks (").

Notations used in formulas

The following notations are used in computational expressions:

SymbolMeaning
[Figure][Figure]Round up the result to the next integer.
Example: The result of [Figure]34 [Figure] 3[Figure] is 12.
[Figure][Figure]Discard digits following the decimal point.
Example: The result of [Figure]34 [Figure] 3[Figure] is 11.
MAXSelect the largest value as the result.
Example: The result of Max(10, 2 [Figure] 4, 3 + 8) is 11.
MINSelect the smallest value as the result.
Example: The result of Min(10, 2 [Figure] 4, 3 + 8) is 8.

Notes on Windows path names

Example: C:\win32app\hitachi\hirdb_s\spool\tmp

Example: pdinit -d "C:\Program Files(x86)\hitachi\hirdb_s\conf\mkinit"

However, double quotation marks are not necessary when you use the set command in a batch file or at the command prompt to set an environment variable or when you specify the installation directory. If you do use double quotation marks in such a case, the double quotation marks become part of the value assigned to the environment variable.

Example: set PDCLTPATH=C:\Program Files\hitachi\hirdb_s\spool

Conventions: KB, MB, GB, and TB

This manual uses the following conventions:

Conventions: Version numbers

The version numbers of Hitachi program products are usually written as two sets of two digits each, separated by a hyphen. For example:

The version number might be shown on the spine of a manual as Ver. 2.00, but the same version number would be written in the program as 02-00.

Important notes on this manual

The following facilities are explained, but they are not supported:

The following products and option program products are explained, but they are not supported: