Preface

This manual is intended for system administrators, system designers, programmers, and operators of OpenTP1 for Windows.

Readers of this manual must have a basic knowledge of Windows and of online systems. Descriptions in this manual also assume that readers are familiar with the OpenTP1 series manuals listed below. We recommend that you use this manual in conjunction with reading the following manuals, as necessary:

• OpenTP1 Version 7 Description (3000-3-D50(E))
• OpenTP1 Version 7 Programming Guide (3000-3-D51(E))
• OpenTP1 Version 7 System Definition (3000-3-D52(E))
• OpenTP1 Version 7 Operation (3000-3-D53(E))
• OpenTP1 Version 7 Programming Reference C Language (3000-3-D54(E))
• OpenTP1 Version 7 Programming Reference COBOL Language (3000-3-D55(E))
• OpenTP1 Version 7 Messages (3000-3-D56(E))

This manual is organized into the following chapters and appendix:

1. Positioning of This Manual

Chapter 1 describes the relationship of this manual to the other manuals in the OpenTP1 series. It also recommends how you should use this manual.

2. Description of Functions

Chapter 2 describes the differences in program-level functions between OpenTP1 for Windows and OpenTP1 for UNIX, based on a listing of these functions. This chapter also provides detailed explanations of the functions that are specific to OpenTP1 for Windows.

3. Programming

Chapter 3 describes the differences in code-level functions between OpenTP1 for Windows and OpenTP1 for UNIX, based on a listing of these functions. This chapter also explains how to create programs that are specific to OpenTP1 for Windows.

4. Environment Setup

Chapter 4 explains the environment settings specific to OpenTP1 for Windows.

5. System Definitions

Chapter 5 describes the differences in the system definitions between OpenTP1 for Windows and OpenTP1 for UNIX, based on listings of system definitions. This chapter also provides detailed explanations of selected system definitions.

6. Operations

Chapter 6 explains the operation methods that are specific to OpenTP1 for Windows, as well as the graphical user interface (GUI) used by OpenTP1 for Windows.

7. Operation Commands

Chapter 7 describes the differences in the operation commands between OpenTP1 for Windows and OpenTP1 for UNIX, based on a listing of the operation commands. This chapter also provides detailed explanations of selected operation commands.

A. Lists of OpenTP1 Processes

Appendix A provides lists of the system service processes used by OpenTP1 for Windows.

This manual is part of a related set of manuals. The manuals in the set are listed below (with the manual numbers):

OpenTP1 products

• OpenTP1 Version 7 Description (3000-3-D50(E))
• OpenTP1 Version 7 Programming Guide (3000-3-D51(E))
• OpenTP1 Version 7 System Definition (3000-3-D52(E))
• OpenTP1 Version 7 Operation (3000-3-D53(E))
• OpenTP1 Version 7 Programming Reference C Language (3000-3-D54(E))
• OpenTP1 Version 7 Programming Reference COBOL Language (3000-3-D55(E))
• OpenTP1 Version 7 Messages (3000-3-D56(E))
• OpenTP1 Version 7 Tester and UAP Trace User's Guide (3000-3-D57(E))
• OpenTP1 Version 7 TP1/Client User's Guide TP1/Client/W, TP1/Client/P (3000-3-D58(E))
• OpenTP1 Version 7 TP1/Client User's Guide TP1/Client/J (3000-3-D59(E))
• OpenTP1 Version 7 TP1/LiNK User's Guide (3000-3-D60(E))^#
• OpenTP1 Version 7 Protocol TP1/NET/TCP/IP (3000-3-D70(E))
• OpenTP1 Version 7 TP1/Message Queue User's Guide (3000-3-D90(E))^#
• OpenTP1 Version 7 TP1/Message Queue Messages (3000-3-D91(E))^#
• OpenTP1 Version 7 TP1/Message Queue Application Programming Guide (3000-3-D92(E))^#
• OpenTP1 Version 7 TP1/Message Queue Application Programming Reference (3000-3-D93(E))^#

Other OpenTP1 products

• TP1/Web User's Guide and Reference (3000-3-D62(E))^#

Other related products

• Indexed Sequential Access Method ISAM (3000-3-046(E))
• XP/W (3000-3-047(E))
• Extended Mapping Service 2/Workstation XMAP2/W DESCRIPTION/USER'S GUIDE (3000-7-421(E))
• SEWB 3 General Information (3000-7-450(E))
• Job Management Partner 1/Base User's Guide (3020-3-K06(E))
• Job Management Partner 1/Base Messages (3020-3-K07(E))
• Job Management Partner 1/Base Software Developer's Guide (3020-3-K08(E))

For OpenTP1 protocol manuals, please check whether English versions are available.

#

If you want to use this manual, confirm that it has been published. (Some of these manuals might not have been published yet.)

This manual abbreviates manual titles. The following table lists the full name of each manual together with its abbreviated name as used in this manual:

Full name	Name used in this manual
OpenTP1 Programming Reference C Language	OpenTP1 Programming Reference
OpenTP1 Programming Reference COBOL Language
Scalable Database Server HiRDB Version 7 Installation and Design Guide, for Windows(R) systems	Scalable Database Server HiRDB Installation and Design Guide
Scalable Database Server HiRDB Version 8 Installation and Design Guide, for Windows(R) systems
Scalable Database Server HiRDB Version 7 UAP Development Guide	Scalable Database Server HiRDB UAP Development Guide
Scalable Database Server HiRDB Version 7 UAP Development Guide, for Windows(R) systems
Scalable Database Server HiRDB Version 8 UAP Development Guide

(1) Conventions: Attribute notation symbols

Attribute notation symbols are used to indicate conventions such as the scope of user-specified values:

Attribute notation symbol	Convention
~	A swung dash indicates that a user-specified attribute value must follow.
<< >>	Double paired angle brackets indicate the default for a user-specified value.
< >	Paired angle brackets indicate the syntax element for a user-specified value.
(( ))	Double paired parentheses indicate the scope of a user-specified value.

(2) Conventions: Fonts

The following table explains the fonts used in this manual:

Font	Convention
Bold	Bold 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: From the File menu, choose Open. Click the Cancel button. In the Enter name entry box, type your name.
Italics	Italics are used to indicate a placeholder for some actual text to be provided by the user or system. For example: Write the command as follows: copy source-file target-file The following message appears: A file was not found. (file = file-name) Italics are also used for emphasis. For example: Do not delete the configuration file.
Code font	A 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.

(3) Conventions: Syntax description symbols

The following table explains the syntax description symbols used in this manual:

Symbol	Convention
|	In syntax explanations, a vertical bar separates multiple items, and has the meaning of OR. For example: abcdefg -h iii|jjj means that, following the -h option, you can specify either iii or jjj.
{ }	In syntax explanations, curly brackets indicate that only one of the enclosed items is to be selected. For example: abcdefg {-h|-i} means that you can specify either the -h option or the -i option.
[ ]	In syntax explanations, square brackets indicate that the enclosed item or items are optional. For example: abcdefg [-h|-i] means that you can specify abcdefg, abcdefg -h, or abcdefg -i.
...	In syntax explanations, an ellipsis (...) indicates that the immediately preceding item can be repeated as many times as necessary. For example: abcdefg -h user-server-name[, user-server-name] ... means that you can specify as many user server names in the -h option as necessary.
	In syntax explanations, underlined text indicates the value that the system assumes when the relevant operand or command parameter is omitted. For example: abcdefg [-h {iii|jjj}] means that, if omitted, iii is assumed to be the value specified for the -h option.
	In syntax explanations, an upper-case delta character indicates a space. For example: logical-file-namephysical-file-name means that a space separates the logical file name and the physical file name.

(4) Conventions: Syntax elements

The following characters are used for explaining syntax elements in user-specified values:

Syntax element	Characters
Alphabetic characters	Alphabetic characters (A to Z, a to z) and the underscore (_)
Alphabetic characters and symbols	Alphabetic characters (A to Z, a to z), hash mark (#), at sign (@), and backslash (\)
Alphanumeric characters	Alphabetic characters and numeric characters (A to Z, a to z, 0 to 9)
Alphabetic characters, symbols, and numeric characters	Alphabetic characters, symbols, and numeric characters
Special characters	Asterisk (*)
Unsigned integer	Numeric characters
Hexadecimal number	Numeric characters, A to F, and a to f (However, upper-case characters A to F are not permitted when numeric characters and lower-case characters a to f are expressly permitted.)
Identifier	An alphanumeric character string that begins with an alphabetic character
Symbolic name	A string consisting of a combination of alphanumeric characters and symbols that begins with an alphabetic character or symbol
Character string	An array of alphabetic characters
Path name	A string consisting of symbolic names, forward slashes (/), and periods (.) that conforms to the path name conventions of the operating system being used.
OpenTP1 file name	A character string of 14 or fewer characters consisting of a combination of alphabetic characters, numeric characters, periods (.), underscores (_), and at marks (@).

(1) Conventions: Abbreviations for product names

This manual uses the following abbreviations for product names:

Full name or meaning	Abbreviation
COBOL2002 Net Client Suite	COBOL2002
COBOL2002 Net Client Runtime
COBOL2002 Net Developer
COBOL2002 Net Server Suite
COBOL2002 Net Server Runtime
HiRDB/Parallel Server Version 7	HiRDB
HiRDB/Single Server Version 7
HiRDB/Parallel Server Version 8
HiRDB/Single Server Version 8
JavaTM	Java
Job Management Partner 1/Automatic Job Management System 2 - Agent	JP1/AJS2 - Agent	JP1/AJS2	JP1
Job Management Partner 1/Automatic Job Management System 2 - Manager	JP1/AJS2 - Manager
Job Management Partner 1/Automatic Job Management System 2 - View	JP1/AJS2 - View
Job Management Partner 1/Automatic Job Management System 2 - Scenario Operation Manager	JP1/AJS2 - Scenario Operation Manager	JP1/AJS2 - Scenario Operation
Job Management Partner 1/Automatic Job Management System 2 - Scenario Operation View	JP1/AJS2 - Scenario Operation View
Job Management Partner 1/Base
Job Management Partner 1/Cm2/Operations Assist Agent	JP1/Cm2
Job Management Partner 1/NETM/Audit - Manager	JP1/NETM/Audit
Job Management Partner 1/NETM/DM Client	JP1/NETM/DM
Job Management Partner 1/NETM/DM Manager
Job Management Partner 1/NETM/DM SubManager
Microsoft(R) MS-DOS(R)	MS-DOS
Micro Focus Net Express(R)	Net Express
Oracle Database 10g	Oracle
Oracle Database 11g
Oracle9i
Microsoft(R) SQL Server 2005	SQL Server
Microsoft(R) SQL Server 2008
uCosminexus TP1/Client/J	TP1/Client/J	TP1/Client
uCosminexus TP1/Client/P	TP1/Client/P
uCosminexus TP1/Client/W	TP1/Client/W
uCosminexus TP1/Client/W(64)
uCosminexus TP1/Client for .NET Framework	TP1/Client for .NET Framework
uCosminexus TP1/Connector for .NET Framework	TP1/Connector for .NET Framework
uCosminexus TP1/Server Base Enterprise Option	TP1/EE
uCosminexus TP1/Server Base Enterprise Option(64)
uCosminexus TP1/Extension 1	TP1/Extension 1
uCosminexus TP1/Extension 1(64)
uCosminexus TP1/FS/Direct Access	TP1/FS/Direct Access
uCosminexus TP1/FS/Direct Access(64)
uCosminexus TP1/FS/Table Access	TP1/FS/Table Access
uCosminexus TP1/FS/Table Access(64)
uCosminexus TP1/High Availability	TP1/High Availability
uCosminexus TP1/High Availability(64)
uCosminexus TP1/LiNK	TP1/LiNK
uCosminexus TP1/Message Control	TP1/Message Control
uCosminexus TP1/Message Control(64)
uCosminexus TP1/Message Control/Tester	TP1/Message Control/Tester
uCosminexus TP1/Message Queue	TP1/Message Queue
uCosminexus TP1/Message Queue(64)
uCosminexus TP1/Message Queue - Access	TP1/Message Queue - Access
uCosminexus TP1/Message Queue - Access(64)
uCosminexus TP1/Messaging	TP1/Messaging
uCosminexus TP1/Multi	TP1/Multi
uCosminexus TP1/NET/HDLC	TP1/NET/HDLC
uCosminexus TP1/NET/High Availability	TP1/NET/High Availability
uCosminexus TP1/NET/High Availability(64)
uCosminexus TP1/NET/HSC	TP1/NET/HSC
uCosminexus TP1/NET/Library	TP1/NET/Library
uCosminexus TP1/NET/Library(64)
uCosminexus TP1/NET/NCSB	TP1/NET/NCSB
uCosminexus TP1/NET/OSAS-NIF	TP1/NET/OSAS-NIF
uCosminexus TP1/NET/OSI-TP	TP1/NET/OSI-TP
uCosminexus TP1/NET/Secondary Logical Unit - TypeP2	TP1/NET/Secondary Logical Unit - TypeP2
	TP1/NET/SLU - TypeP2
uCosminexus TP1/NET/TCP/IP	TP1/NET/TCP/IP
uCosminexus TP1/NET/TCP/IP(64)
uCosminexus TP1/NET/User Datagram Protocol	TP1/NET/UDP
uCosminexus TP1/NET/User Agent	TP1/NET/User Agent
uCosminexus TP1/NET/X25	TP1/NET/X25
uCosminexus TP1/NET/X25-Extended	TP1/NET/X25-Extended
uCosminexus TP1/NET/XMAP3	TP1/NET/XMAP3
uCosminexus TP1/Offline Tester	TP1/Offline Tester
uCosminexus TP1/Online Tester	TP1/Online Tester
uCosminexus TP1/Resource Manager Monitor	TP1/Resource Manager Monitor
uCosminexus TP1/Server Base	TP1/Server Base
uCosminexus TP1/Server Base(64)
uCosminexus TP1/Shared Table Access	TP1/Shared Table Access
uCosminexus TP1/Web	TP1/Web
UNIX(R)	UNIX
Microsoft(R) Visual Studio(R) 2005 Professional Edition	Visual Studio
Microsoft(R) Visual Studio(R) 2005 Standard Edition
Microsoft(R) Visual Studio(R) 2005 Team Edition for Software Architects
Microsoft(R) Visual Studio(R) 2005 Team Edition for Software Developers
Microsoft(R) Visual Studio(R) 2005 Team Edition for Software Testers
Microsoft(R) Visual Studio(R) 2005 Team Suite
Microsoft(R) Visual Studio(R) 2008 Professional Edition
Microsoft(R) Visual Studio(R) 2008 Standard Edition
Microsoft(R) Visual Studio(R) Team System 2008 Architecture Edition
Microsoft(R) Visual Studio(R) Team System 2008 Development Edition
Microsoft(R) Visual Studio(R) Team System 2008 Database Edition
Microsoft(R) Visual Studio(R) Team System 2008 Team Suite
Microsoft(R) Visual Studio(R) Team System 2008 Test Edition
Microsoft(R) Windows(R) 2000 Advanced Server Operating System	Windows 2000		Windows
Microsoft(R) Windows(R) 2000 Datacenter Server Operating System
Microsoft(R) Windows(R) 2000 Professional Operating System
Microsoft(R) Windows(R) 2000 Server Operating System
Microsoft(R) Windows(R) 7 Enterprise	Windows 7
Microsoft(R) Windows(R) 7 Professional
Microsoft(R) Windows(R) 7 Ultimate
Microsoft(R) Windows Server(R) 2003, Datacenter Edition	Windows Server 2003	Windows Server 2003
Microsoft(R) Windows Server(R) 2003, Enterprise Edition
Microsoft(R) Windows Server(R) 2003, Standard Edition
Microsoft(R) Windows Server(R) 2003 R2, Enterprise Edition	Windows Server 2003 R2
Microsoft(R) Windows Server(R) 2003 R2, Standard Edition
Microsoft(R) Windows Server(R) 2003 R2, Enterprise x64 Edition	Windows Server 2003 R2 x64 Editions
Microsoft(R) Windows Server(R) 2003 R2, Standard x64 Edition
Microsoft(R) Windows Server(R) 2003, Datacenter x64 Edition	Windows Server 2003 x64 Editions
Microsoft(R) Windows Server(R) 2003, Enterprise x64 Edition
Microsoft(R) Windows Server(R) 2003, Standard x64 Edition
Microsoft(R) Windows Server(R) 2008 Datacenter (x86)	Windows Server 2008	Windows Server 2008
Microsoft(R) Windows Server(R) 2008 Enterprise (x86)
Microsoft(R) Windows Server(R) 2008 Standard (x86)
Microsoft(R) Windows Server(R) 2008 R2, Datacenter Edition	Windows Server 2008 R2
Microsoft(R) Windows Server(R) 2008 R2, Enterprise Edition
Microsoft(R) Windows Server(R) 2008 R2, Standard Edition
Microsoft(R) Windows Server(R) 2008 Datacenter (x64)	Windows Server 2008 x64 Editions
Microsoft(R) Windows Server(R) 2008 Enterprise (x64)
Microsoft(R) Windows Server(R) 2008 Standard (x64)
Microsoft(R) Windows Vista(R) Business (x86)	Windows Vista	Windows Vista
Microsoft(R) Windows Vista(R) Enterprise (x86)
Microsoft(R) Windows Vista(R) Ultimate (x86)
Microsoft(R) Windows Vista(R) Business (x64)	Windows Vista x64 Editions
Microsoft(R) Windows Vista(R) Enterprise (x64)
Microsoft(R) Windows Vista(R) Ultimate (x64)
Microsoft(R) Windows(R) XP Professional Operating System	Windows XP

(2) Conventions: Acronyms

This manual also uses the following acronyms:

Acronym	Full name or meaning
API	Application Programming Interface
CPU	Central Processing Unit
CUP	Client User Program
DAM	Direct Access Method
DB	Database
DBA	Database Administrator
DBMS	Database Management System
DLL	Dynamic Link Library
EOF	End of File
GUI	Graphical User Interface
HA	High Availability
I/O	Input/Output
ID	Identifier
IP	Internet Protocol
ISAM	Indexed Sequential Access Method
IST	Internode Shared Table
J2EE	Java 2 Enterprise Edition
MCF	Message Control Facility
MHP	Message Handling Program
MQI	Message Queue Interface
MSCS	Microsoft Cluster Service
MSDTC	Microsoft Distributed Transaction Coordinator
NIC	Network Interface Card
NTFS	New Technology File System
ODBC	Open DataBase Connectivity
OS	Operating System
OSI	Open Systems Interconnection
OSI TP	Open Systems Interconnection Transaction Processing
PRF	Performance
RM	Resource Manager
RPC	Remote Procedure Call
RTS	Real Time Statistic
SPP	Service Providing Program
SUP	Service Using Program
TAM	Table Access Method
TCP/IP	Transmission Control Protocol/Internet Protocol
TP	Transaction Processing
UAP	User Application Program
UOC	User Own Coding
WER	Windows Error Reporting
XA	Extended Architecture
XAR	Extended Architecture Resource

(3) Conventions: Differences between JIS and ASCII keyboards

The JIS and ASCII code maps assign different input characters to the codes shown below. The characters used in the code input examples in this manual (code examples) are based on the JIS code map (Japanese keyboard).

Code	JIS keyboard	ASCII keyboard
(5c)16	(yen sign)	\ (backslash)
(7e)16	(overscore)	~ (swung dash)

(4) Conventions: Differences between upper-case and lower-case characters

OpenTP1 distinguishes between upper-case and lower-case characters (case sensitive). Make sure that you keep this distinction in mind when you specify command options or when you use character strings for command parameters in definition files. For example, the -a option is not the same as the -A option.

(5) Conventions: Descriptions of C language functions and COBOL UAPs

If there are no significant differences in a description with respect to C language functions and COBOL UAP creation programs, the C language functions are used in the description.

(6) Conventions: Environment variables

Windows environment variables are written as %DCDIR%. To use a Windows environment variable value, make sure that you type %DCDIR%, not $DCDIR.

(7) Conventions: KB, MB, GB, and TB

This manual uses the following conventions:

• 1 KB (kilobyte) is 1,024 bytes.
• 1 MB (megabyte) is 1,024² bytes.
• 1 GB (gigabyte) is 1,024³ bytes.
• 1 TB (terabyte) is 1,024⁴ bytes.

(8) Conventions: Path name specifications

You must always include the drive letter when you specify an absolute path name. In a Windows environment, the colon (:) is used to separate the drive name from the folder names. Do not specify a colon in a path name anywhere other than following the drive letter.

Use a semicolon (;) to separate multiple path names.

(9) 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:

• Version 1.00 (or 1.0) is written as 01-00.
• Version 2.05 is written as 02-05.
• Version 2.50 (or 2.5) is written as 02-50.
• Version 12.25 is written as 12-25.

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.