Preface

This manual explains the administration and operation of the OpenTP1 Distributed Transaction Processing Facility.

Products described in this manual, other than those for which the manual is released, may not work with OpenTP1 Version 7 products. You need to confirm that the products you want to use work with OpenTP1 Version 7 products.

Intended readers

This manual is intended for system administrators and system designers.

This manual assumes that the user has already read the manual OpenTP1 Description.

Organization of this manual

This manual is organized into the following parts, chapters, and appendixes:

Part 1: OpenTP1 Environment Setup
1. Environment Setup
This chapter explains OpenTP1 environment setup and the setup procedure.
Part 2: OpenTP1 Operations
2. OpenTP1 Startup and Termination
This chapter explains the OpenTP1 startup and termination procedures.
3. OpenTP1 Online Operation
This chapter explains the normal online operation for OpenTP1.
4. OpenTP1 File Operations
This chapter explains the operations of files used for OpenTP1.
5. Sending and Receiving Messages
This chapter explains sending and receiving messages.
6. OpenTP1 Optional Facility Operation
This chapter explains the OpenTP1 optional facilities.
7. Operations Under the Multi-node Facility
This chapter explains operations required when the multinode facility is used: environment setup, OpenTP1 startup and termination procedures, OpenTP1 node status display, and file operation and recovery.
8. MultiOpenTP1 Operation
This chapter explains the differences between multi OpenTP1 and normal OpenTP1 operation in units of nodes.
9. Operations Under the System Switchover Facility
This chapter explains operations required when the system switchover facility is used, more specifically, the differences in OpenTP1 operation from when the system switchover facility is not used.
Part 3: OpenTP1 Error Handling Procedures
10. Error Handling Procedures
This chapter classifies OpenTP1 errors and explains actions to be taken for different types of errors. It also explains information to be collected when errors occur and information to be inherited during full recovery.
11. Troubleshooting
This chapter explains what information to acquire when an error occurs in OpenTP1, and how to investigate the problem.
Part 4: OpenTP1 Operation Commands
12. Operation Commands
This chapter explains the operation commands used with OpenTP1 in terms of the input, specification, and details of these commands.
13. Details of Operation Commands
This chapter explains the operation commands in alphabetical order.
Appendixes
A. Dump File Format of Input/Output Queues
This appendix explains the dump file format of input/output queues.
B. OpenTP1 Events
This appendix explains the OpenTP1 events that can be registered with the JP1 Event Service.
C. Information Output for Audited Events
This appendix explains the information output for audited events.
D. Journal Information Collected by the Message Control Facility
This appendix explains journal information collected by the message control facility.
E. Details of Statistics
This appendix provides details of each type of statistics.
F. List of Files Output by OpenTP1
This appendix provides tables that list the files output by OpenTP1.
G. Estimating the Size of the Physical File for a Message Queue
This appendix provides formulae for estimating the size of physical files for a message queue.
H. Estimating the Size of OpenTP1 Files
This appendix explains the formulas for estimating the size of OpenTP1 files.
I. Estimating the Number of Record Locks
This appendix explains the formulae for estimating the number of record locks to be registered by OpenTP1.
J. Estimating the Resources Used by UNIX Message Exchange Functions
This appendix explains the formulae for estimating the resources used by the message exchange functions of UNIX.
K. Estimating the Size of an OpenTP1 File System
This appendix explains the formulae for estimating the size of an OpenTP1 file system.
L. Acquiring Performance Verification Traces
This appendix provides the timing to acquire the performance verification trace and describes contents to be acquired.
M. Details About Scenario Templates
This appendix explains the function of scenario templates and the details about scenario templates such as input scenario variables.

Related publications

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

OpenTP1 products

Other OpenTP1 products

Other related products

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

Conventions: Abbreviations for product names

This manual uses the following abbreviations for product names:

AbbreviationFull name or meaning
AIXAIX 5L V5.1
AIX 5L V5.2
AIX 5L V5.3
AIX V6.1
Client .NETTP1/Client for .NET FrameworkuCosminexus TP1/Client for .NET Framework
Connector .NETTP1/Connector for .NET FrameworkuCosminexus TP1/Connector for .NET Framework
DPMJP1/ServerConductor/Deployment Manager
HI-UX/WE2HI-UX/workstation Extended Version 2
HP-UXHP-UX (IPF)HP-UX 11i V2 (IPF)
HP-UX 11i V3 (IPF)
HP-UX (PA-RISC)HP-UX 11i V1 (PA-RISC)
HP-UX 11i V2 (PA-RISC)
IPFItanium(R) Processor Family
JavaJavaTM
JP1JP1/AJS2JP1/AJS2 - AgentJP1/Automatic Job Management System 2 - Agent
JP1/AJS2 - ManagerJP1/Automatic Job Management System 2 - Manager
JP1/AJS2 - ViewJP1/Automatic Job Management System 2 - View
JP1/AJS2 - Scenario OperationJP1/AJS2 - Scenario Operation ManagerJP1/Automatic Job Management System 2 - Scenario Operation Manager
JP1/AJS2 - Scenario Operation ViewJP1/Automatic Job Management System 2 - Scenario Operation View
JP1/NETM/AuditJP1/NETM/Audit - Manager
LinuxLinux(R)
Linux (AMD64/Intel EM64T/x86)Red Hat Enterprise Linux AS 4 (AMD64 & Intel EM64T)
Red Hat Enterprise Linux AS 4 (x86)
Red Hat Enterprise Linux ES 4 (AMD64 & Intel EM64T)
Red Hat Enterprise Linux ES 4 (x86)
Red Hat Enterprise Linux 5 (AMD/Intel 64)
Red Hat Enterprise Linux 5 (x86)
Red Hat Enterprise Linux 5 Advanced Platform (AMD/Intel 64)
Red Hat Enterprise Linux 5 Advanced Platform (x86)
Linux (IPF)Red Hat Enterprise Linux AS 4 (IPF)
Red Hat Enterprise Linux 5 (Intel Itanium)
Red Hat Enterprise Linux 5 Advanced Platform (Intel Itanium)
MS-DOSMicrosoft(R) MS-DOS(R)
NETM/DMJP1/NETM/DM Client
JP1/NETM/DM Manager
JP1/NETM/DM SubManager
OracleOracle 10g
Oracle9i
SolarisSolaris 8
Solaris 9
Solaris 10
TP1/ClientTP1/Client/JuCosminexus TP1/Client/J
TP1/Client/PuCosminexus TP1/Client/P
TP1/Client/WuCosminexus TP1/Client/W
uCosminexus TP1/Client/W(64)
TP1/EEuCosminexus TP1/Server Base Enterprise Option
uCosminexus TP1/Server Base Enterprise Option(64)
TP1/Extension 1uCosminexus TP1/Extension 1
uCosminexus TP1/Extension 1(64)
TP1/FS/Direct AccessuCosminexus TP1/FS/Direct Access
uCosminexus TP1/FS/Direct Access(64)
TP1/FS/Table AccessuCosminexus TP1/FS/Table Access
uCosminexus TP1/FS/Table Access(64)
TP1/High AvailabilityuCosminexus TP1/High Availability
uCosminexus TP1/High Availability(64)
TP1/LiNKuCosminexus TP1/LiNK
TP1/Message ControluCosminexus TP1/Message Control
uCosminexus TP1/Message Control(64)
TP1/Message Control/TesteruCosminexus TP1/Message Control/Tester
TP1/Message QueueuCosminexus TP1/Message Queue
uCosminexus TP1/Message Queue(64)
TP1/Message Queue - AccessuCosminexus TP1/Message Queue - Access
uCosminexus TP1/Message Queue - Access(64)
TP1/MessaginguCosminexus TP1/Messaging
TP1/MultiuCosminexus TP1/Multi
TP1/NET/HDLCuCosminexus TP1/NET/HDLC
TP1/NET/High AvailabilityuCosminexus TP1/NET/High Availability
uCosminexus TP1/NET/High Availability(64)
TP1/NET/HSCuCosminexus TP1/NET/HSC
TP1/NET/LibraryuCosminexus TP1/NET/Library
uCosminexus TP1/NET/Library(64)
TP1/NET/NCSBuCosminexus TP1/NET/NCSB
TP1/NET/OSAS-NIFuCosminexus TP1/NET/OSAS-NIF
TP1/NET/OSI-TPuCosminexus TP1/NET/OSI-TP
TP1/NET/SLU - TypeP2TP1/NET/Secondary Logical Unit - TypeP2uCosminexus TP1/NET/Secondary Logical Unit - TypeP2
TP1/NET/TCP/IPuCosminexus TP1/NET/TCP/IP
uCosminexus TP1/NET/TCP/IP(64)
TP1/NET/UDPuCosminexus TP1/NET/User Datagram Protocol
TP1/NET/User AgentuCosminexus TP1/NET/User Agent
TP1/NET/X25uCosminexus TP1/NET/X25
TP1/NET/X25-ExtendeduCosminexus TP1/NET/X25-Extended
TP1/NET/XMAP3uCosminexus TP1/NET/XMAP3
TP1/Offline TesteruCosminexus TP1/Offline Tester
TP1/Online TesteruCosminexus TP1/Online Tester
TP1/Resource Manager MonitoruCosminexus TP1/Resource Manager Monitor
TP1/Server BaseuCosminexus TP1/Server Base
uCosminexus TP1/Server Base(64)
TP1/Shared Table AccessuCosminexus TP1/Shared Table Access
TP1/WebuCosminexus TP1/Web
Windows 2000Microsoft(R) Windows(R) 2000 Advanced Server Operating System
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
Windows Server 2003Microsoft(R) Windows Server(R) 2003, Datacenter Edition
Microsoft(R) Windows Server(R) 2003, Enterprise Edition
Microsoft(R) Windows Server(R) 2003, Standard Edition
Windows Server 2003 R2Microsoft(R) Windows Server(R) 2003 R2, Enterprise Edition
Microsoft(R) Windows Server(R) 2003 R2, Standard Edition
Windows Server 2003 x64 EditionsMicrosoft(R) Windows Server(R) 2003, Datacenter x64 Edition
Microsoft(R) Windows Server(R) 2003, Enterprise x64 Edition
Microsoft(R) Windows Server(R) 2003, Standard x64 Edition
Windows Server 2003 R2 x64 EditionsMicrosoft(R) Windows Server(R) 2003 R2, Enterprise x64 Edition
Microsoft(R) Windows Server(R) 2003 R2, Standard x64 Edition
Windows Server 2008Microsoft(R) Windows Server(R) 2008 Datacenter (x86)
Microsoft(R) Windows Server(R) 2008 Enterprise (x86)
Microsoft(R) Windows Server(R) 2008 Standard (x86)
Windows Server 2008 x64 EditionsMicrosoft(R) Windows Server(R) 2008 Datacenter (x64)
Microsoft(R) Windows Server(R) 2008 Enterprise (x64)
Microsoft(R) Windows Server(R) 2008 Standard (x64)
Windows VistaMicrosoft(R) Windows Vista(R) Business (x86)
Microsoft(R) Windows Vista(R) Enterprise (x86)
Microsoft(R) Windows Vista(R) Ultimate (x86)
Windows Vista x64 EditionsMicrosoft(R) Windows Vista(R) Business (x64)
Microsoft(R) Windows Vista(R) Enterprise (x64)
Microsoft(R) Windows Vista(R) Ultimate (x64)
Windows XPMicrosoft(R) Windows(R) XP Professional Operating System

Conventions: Acronyms

This manual also uses the following acronyms:

AcronymFull name or meaning
ANSIAmerican National Standards Institute
APApplication Program
CPUCentral Processing Unit
CUPClient User Program
DAMDirect Access Method
DAM FRCDAM File Recovery
DHCPDynamic Host Configuration Protocol
DIDDistributed Identifier
DMLData Manipulation Language
DNSDomain Name System
HAHigh Availability
I/OInput/Output
IPInternet Protocol
ISAMIndexed Sequential Access Method
ISTInternode Shared Table
LANLocal Area Network
MCFMessage Control Facility
MHPMessage Handling Program
MQAMessage Queue Access
MSDTCMicrosoft Distributed Transaction Coordinator
NISNetwork Information Service
OSOperating System
OSIOpen Systems Interconnection
OSI TPOpen Systems Interconnection Transaction Processing
PRFPerformance
RIRecovery Information
RMMResource Manager Monitor
RPCRemote Procedure Call
RTSReal Time Statistic
SPPService Providing Program
TAMTable Access Method
TAM FRCTAM File Recovery
UAPUser Application Program
UID/GIDUser Identifier/Group Identifier
UOCUser Own Coding
UTCCoordinated Universal Time
VMVirtual Machine
XAExtended Architecture
XARExtended Architecture Resource

Conventions: Diagrams

This manual uses the following conventions in diagrams:

[Figure]

Conventions: Differences between JIS and ASCII keyboards

The JIS code and ASCII code keyboards are different in the input characters represented by the following codes. In this manual, the use of a JIS keyboard is assumed for these characters.

CodeJIS keyboardASCII keyboard
(5c)16[Figure](yen symbol)\ (backslash)
(7e)16[Figure](overline)~ (tilde)

Conventions: Fonts and symbols

The following table explains the fonts used in this manual:

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:
  • 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 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 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.

The following table explains the symbols used in this manual:

SymbolConvention
|In syntax explanations, a vertical bar separates multiple items, and has the meaning of OR. For example:
A|B|C means A, or B, or C.
{ }In syntax explanations, curly brackets indicate that only one of the enclosed items is to be selected. For example:
{A|B|C} means only one of A, or B, or C.
[ ]In syntax explanations, square brackets indicate that the enclosed item or items are optional. For example:
[A] means that you can specify A or nothing.
[B|C] means that you can specify B, or C, or nothing.
...In coding, an ellipsis (...) indicates that one or more lines of coding are not shown for purposes of brevity.
In syntax explanations, an ellipsis indicates that the immediately preceding item can be repeated as many times as necessary. For example:
A, B, B, ... means that, after you specify A, B, you can specify B as many times as necessary.
~The value for the preceding item must be specified in accordance with the attributes listed immediately following the swung dash.
<< >>Default value assumed when specification is omitted.
< >Syntax element (see below).
(( ))Range of specifiable values.

Conventions for permitted characters

In most cases, only the following characters are permitted as syntax elements (if other characters are permitted, the manual will state this explicitly):

TypeDefinition
Upper-case alphabetic charactersA to Z and underscore (_)
Lower-case alphabetic charactersa to z
Alphabetic charactersA to Z, a to z
Alphabetic symbolsAlphabetic characters (A to Z, a to z), #, @, and $
Numeric characters0 to 9
Alphanumeric charactersA to Z, a to z, 0 to 9
Special characters*
Unsigned integersNumeric values (0 to 9)
HexadecimalsNumeric values (0 to 9), A to F, and a to f
(However, if the manual specifies numeric characters (0 to 9) and alphabetic characters a to f, the hexadecimal value you specify cannot include the characters A to F.)
IdentifiersAlphanumeric character string beginning with an alphabetic character (A to Z, a to z)
Symbolic namesString of alphanumeric symbols beginning with an alphabetic symbol
Character stringsArray of any characters
Path namesSymbolic name, slash (/), and period (.)
(The path name depends on the OS being used.)
OpenTP1 file namesCharacter string consisting of alphabetic characters (A to Z, a to z), numeric characters (0 to 9), period (.), underscore (_), and @ (maximum length of 14 characters)

Conventions: KB, MB, GB, and TB

This manual uses the following conventions:

Conventions: Platform-specific notational differences

For the Windows version of OpenTP1, there are some notational differences from the description in the manual. The following table describes these differences.

ItemDescription in the manualChange to:
Environment variable$aaaaaa
Example: $DCDIR
%aaaaaa%
Example: %DCDIR%
Path name separatorColon (:)Semicolon (;)
Directory name separatorSlash (/)Backslash (\)
Absolute path nameA path from the root directory
Example: /tmp
A path name from a drive letter and the root directory
Example: C:\tmp
Executable file nameFile name only (without an extension)
Example: mcfmngrd
File name with an extension
Example: mcfmngrd.exe
make commandmakenmake

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 note

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