Preface

This manual is intended for system designers, programmers, and operators, as well as system administrators.

This manual consists of the following chapters and an appendix:

1. Overview

Chapter 1 provides a functional overview of TP1/Client/J and describes its features.

2. Functionality

Chapter 2 describes the functionality of TP1/Client/J.

3. Program Interface

Chapter 3 describes the program interface for using TP1/Client/J.

4. Classes Used with TP1/Client/J

Chapter 4 describes the classes that are used with TP1/Client/J.

5. Definitions

Chapter 5 describes the TP1/Client/J environment definitions.

6. Error Handling

Chapter 6 describes the procedures for handling errors.

Appendix A. Changes During Upgrading

Appendix A describes the changes to APIs, definitions, and commands from version to version.

This manual is part of a related set of manuals. The manuals in the set, including this manual, 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))^#1
• 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))^#1
• OpenTP1 Version 7 TP1/Message Queue Messages (3000-3-D91(E))^#1
• OpenTP1 Version 7 TP1/Message Queue Application Programming Guide (3000-3-D92(E))^#1
• OpenTP1 Version 7 TP1/Message Queue Application Programming Reference (3000-3-D93(E))^#1

Other OpenTP1 products

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

Other related products

• VOS3 Data Management System XDM Description (6190-6-620(E))
• VOS3 Data Management System XDM E2 System Definition (6190-6-625(E))

Note

You must check and confirm that the products described in these manuals will run on your operating system.

#1: 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 uses the following abbreviations for product names:

Full name or meaning	Abbreviation
uCosminexus Application Server Enterprise	Cosminexus Application Server
uCosminexus Application Server Standard
VOS1 DCCM3	DCCM3
VOS3 XDM/DCCM3
Java(TM)	Java
Java(TM)2 Software Development Kit, Standard Edition	JDK
uCosminexus TP1/Client/J	TP1/Client/J
uCosminexus TP1/Client/P	TP1/Client/P
uCosminexus TP1/Client/W	TP1/Client/W
uCosminexus TP1/NET/TCP/IP	TP1/NET/TCP/IP
uCosminexus TP1/LiNK	TP1/LiNK	TP1/Server
uCosminexus TP1/Server Base	TP1/Server Base
uCosminexus TP1/Web	TP1/Web
Microsoft(R) Windows(R) 2000 Advanced Server Operating System	Windows 2000
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) Software Development Kit	Windows SDK
Microsoft(R) Windows Server(R) 2003, Datacenter Edition	Windows Server 2003 (32bit)	Windows Server 2003
Microsoft(R) Windows Server(R) 2003, Datacenter x64 Edition
Microsoft(R) Windows Server(R) 2003, Enterprise Edition
Microsoft(R) Windows Server(R) 2003, Enterprise x64 Edition
Microsoft(R) Windows Server(R) 2003 R2, Enterprise Edition
Microsoft(R) Windows Server(R) 2003 R2, Enterprise x64 Edition
Microsoft(R) Windows Server(R) 2003 R2, Standard Edition
Microsoft(R) Windows Server(R) 2003 R2, Standard x64 Edition
Microsoft(R) Windows Server(R) 2003, Standard Edition
Microsoft(R) Windows Server(R) 2003, Standard x64 Edition
Microsoft(R) Windows Server(R) 2003, Enterprise Edition for Itanium-based systems	Windows Server 2003 (64bit)
Microsoft(R) Windows Vista(R) Business (x86)	Windows Vista(32bit)	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(64bit)
Microsoft(R) Windows Vista(R) Enterprise (x64)
Microsoft(R) Windows Vista(R) Ultimate (x64)
Microsoft(R) Windows(R) XP Professional Operating System	Windows XP

• Unless functional differences exist, Windows Server 2003, Windows XP and Windows Vista are referred to collectively as Windows.

This manual also uses the following abbreviations:

Abbreviation	Full name or meaning
API	Application Programming Interface
CGI	Common Gateway Interface
CUP	Client User Program
DCE	Distributed Computing Environment
EJB	Enterprise Java Beans(TM)
FD	Floppy Disk
HTTP	Hyper Text Transfer Protocol
J2EE	Java 2 Enterprise Edition
JDK	Java(TM) Development Kit
JSP	JavaServer Pages(TM)
MHP	Message Handling Program
OLTP	Online Transaction Processing
OS	Operating System
PC	Personal Computer
PRF	PeRFormance
RAP	Remote Application Programming Interface
RPC	Remote Procedure Call
SPP	Service Providing Program
TCP/IP	Transmission Control Protocol / Internet Protocol
TMS-4V/SP	Transaction Management System-4V/System Product
UAP	User Application Program
VM	Virtual Machine
WS	Workstation
WWW	World Wide Web

This manual uses the following conventions in diagrams:

Font and symbol conventions are classified as:

• General font conventions
• Conventions in syntax explanations

These conventions are described below.

General font conventions

The following table lists the general font conventions:

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, 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.
Italics	Italics 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 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.

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 the conventions used in syntax explanations:

Example font or symbol	Convention
StoreDatabase	Code-font characters must be entered exactly as shown.
database-name	This font style marks a placeholder that indicates where appropriate characters are to be entered in an actual command.
SD	Bold code-font characters indicate the abbreviation for a command.
perm	Underlined characters indicate the default value.
[ ]	Square brackets enclose an item or set of items whose specification is optional.
|	Only one of the options separated by a vertical bar can be specified at the same time.
...	An ellipsis (...) indicates that the item or items enclosed in ( ) or [ ] immediately preceding the ellipsis may be specified as many times as necessary.
()	Parentheses indicate the range of items to which the vertical bar (|) or ellipsis (...) is applicable.

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.

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.

Please check the availability of the products and manuals for HAmonitor, ServerConductor/DeploymentManager, Cosminexus, and Job Management Partner 1/Automatic Job Management System 2.