HP Transact Reference Manual : COPYRIGHT NOTICE [ HP Transact Reference Manual ] MPE/iX 5.0 Documentation
HP Transact Reference Manual
HP 3000 Computer Systems
HP Transact
Reference Manual
HP Part No. 32247-60003
Printed in U.S.A.
Edition Seventh Edition
E0494
________________________________________________________________________
|The information contained in this document is subject to change |
|without notice. |
| |
|HEWLETT-PACKARD MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THIS |
|MATERIAL, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF |
|MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Hewlett-Packard |
|shall not be liable for errors contained herein or use of this |
|material. |
| |
|Hewlett-Packard assumes no responsibility for the use or reliability |
|of its software on equipment that is not furnished by Hewlett-Packard.|
| |
|This document contains proprietary information which is protected by |
|copyright. All rights are reserved. No part of this document may be |
|photocopied, reproduced, or translated to another language without the|
|prior written consent of Hewlett-Packard Company. |
________________________________________________________________________
Copyright (c)1981, 1982-1985, 1986, 1987, 1988, 1990, 1992, 1994 by
Hewlett-Packard Company
Printed September 3, 1997
Printing History
The following table lists the printings of this document, together with
the respective release dates for each edition. The software version
indicates the version of the software product at the time this document
was issued. Many product releases do not require changes to the
document. Therefore, do not expect a one-to-one correspondence between
product releases and document editions.
Edition Date Software Version
--------------------------------------------------------------------------
First Edition December 1981 32247A.00.00
Second Edition December 1982 32247A.00.03
Update #1 June 1983 32247A.01.01
Update #2 February 1985 32247A.02.02
Fourth Edition October 1987 32247A.03.07
Update #1 July 1988 32247A.06.00 &
30138A.00.00
Fifth Edition February 1990 32247A.07.02 &
30138A.02.01
Sixth Edition September 1992 32247A.09.00 &
30138A.04.00
Seventh Edition April 1994 32247A.10.00 &
30138A.05.00
About This Manual
This manual is a reference for programming in the Transact programming
language. It assumes that you have a working knowledge of computer
programming and the HP 3000 computer system, including the subsystems
TurboIMAGE and VPLUS. The manual contains the following chapters and
appendixes:
* Chapter 1, "Introduction to Transact," describes the features and
benefits of Transact.
* Chapter 2, "Program Structure," describes the program structure of
Transact.
* Chapter 3, "Data Items," discusses data item definitions, names,
types, sizes, as well as parent and child items, compound items,
array subscripting, and defining and handling arrays.
* Chapter 4, "Transact Registers," describes registers, the areas of
data storage in Transact, and how they work.
* Chapter 5, "User Interface," describes the three modes of user
interface: command sequence, character mode, and block mode using
VPLUS.
* Chapter 6, "Accessing Databases and Files," describes how to use
databases, KSAM files, and MPE files with Transact.
* Chapter 7, "Error Handling," explains the error handling process
and the effect of the STATUS option on various verbs.
* Chapter 8, "Verbs," provides detailed descriptions of the Transact
verbs.
* Chapter 9, "Running Transact," tells how to compile and execute
Transact programs and control execution at run time.
* Chapter 10, "Transact Test Facility," explains how to use the test
facility, which is a major aid in program testing, integration,
and optimization.
* Chapter 11, "TRANDEBUG," describes Transact/iX's symbolic
debugging facility. It also provides a tutorial introduction to
using the debugger and a dictionary of all TRANDEBUG commands.
* Appendix A, "Flowcharts of File and Database Operations," contains
flowcharts showing the file and database procedures called when
Transact verbs perform file and database operations.
* Appendix B, "Transact/iX Migration Guide," provides guidelines for
migrating Transact/V programs to native mode Transact/iX programs
on an MPE/iX system.
* Appendix C, "Optimizing Transact Applications," provides
guidelines for optimizing the run-time performance and efficiency
of Transact applications.
* Appendix D, "Architected Call Interface," explains how to call
existing Transact/iX subprograms from COBOL or Pascal.
* Appendix E, "Native Language Support," describes how Transact
provides access to MPE native language support at compile time and
run time.
Introducing MPE/iX
MPE/iX, Multiprogramming Executive with Integrated POSIX, is the latest
in a series of forward-compatible operating systems for the HP 3000 line
of computers.
In Hewlett-Packard documentation and in talking with other HP 3000 users,
you will encounter references to MPE XL, the direct predecessor of
MPE/iX. MPE/iX is a supersest of MPE XL. All programs written for MPE XL
will run without change under MPE/iX, and you can continue to use MPE XL
system documentation.
Finally, you may encounter references to MPE V, an HP 3000 operating
system that is not based on the PA-RISC architecture. MPE V software can
be run on the PA-RISC (Series 900) HP 3000s in what is known as
compatibility mode (CM).
Transact Enhancements
This edition of the manual includes descriptions of the enhancements that
have been made to Transact. Here is a list of these enhancements and
where they are located in the manual.
Enhancement Location
-------------------------------------------------------------------------
ALIGN Option for LIST Chapter 8
ASCII Function for LET Chapter 8
CALL, STATUS Chapter 8
CHAR Function for MOVE Chapter 8
COL Function for MOVE Chapter 8
Expand Intrinsic Support of DEFINE(INTRINSIC) Chapter 8
LENGTH Function for LET Chapter 8
LOWER Function for MOVE Chapter 8
POSITION Function for LET Chapter 8
PROPER Function for MOVE Chapter 8
PROPER Modifier for SET and RESET Chapter 8
SPACE Function for MOVE Chapter 8
STRING Function for MOVE Chapter 8
UPPER Function for MOVE Chapter 8
VALUE Function for LET Chapter 8
WORKFILE Option for FIND Chapter 8
CHCK Compiler Option Chapter 9
Where to Find More Information
The following manuals and courses are recommended for additional
reference or to practice using Transact.
Reference Manuals
Title Part Number
-------------------------------------------------------------------------
MPE/V Commands Reference Manual 30000-90009
MPE/V Intrinsics Reference Manual 30000-90010
SPL/V Reference Manual 30000-90024
KSAM/3000 Reference Manual 30000-90079
TurboIMAGE/V Database Management System Reference 32215-90050
Manual
VPLUS/3000 Reference Manual 32209-90001
Dictionary/3000 Reference Manual 32244-90001
HP System Dictionary/V User's Guide 32254-90001
HP System Dictionary/V Utilities Reference Manual 32254-90003
Report/V User's Guide 32245-90001
Inform/V User's Guide 32246-90001
Getting Started with Transact 32247-90007
MPE/iX Commands Reference Manual 32650-90003
MPE/iX Intrinsics Reference Manual 32650-90028
TurboIMAGE/XL Database Management System Reference 30391-90001
Manual
HP System Dictionary/XL General Reference Manual 32256-90004
HP System Dictionary/XL Utilities Reference Manual 32256-90003
Self-Paced Courses
Title Part Number
-------------------------------------------------------------------------
Using Dictionary/V 22843B
Programming in Transact 22842A
Conventions
UPPERCASE Within syntax statements, characters in uppercase
must be entered in exactly the order shown, though
you can enter them in either uppercase or lowercase.
For example:
SHOWJOB
Valid entries: showjob ShowJob
SHOWJOB
Invalid entries: shojwob ShoJob
SHOW_JOB
italics Within syntax statements, a word in italics
represents a formal parameter or argument that you
must replace with an actual value. In the following
example, you must replace filename with the name of
the file you want to release:
RELEASE filename
punctuation Within syntax statements, punctuation characters
(other than brackets, braces, vertical parallel
lines, and ellipses) must be entered exactly as
shown.
{ } Within syntax statements, braces enclose required
elements. When several elements within braces are
stacked, you must select one. In the following
example, you must select ON or OFF:
SETMSG {ON }
{OFF}
[ ] Within syntax statements, brackets enclose optional
elements. In the following example, brackets around
,TEMP indicate that the parameter and its delimiter
are optional:
PURGE {filename} [,TEMP]
When several elements with brackets are stacked, you
can select any one of the elements or none. In the
following example, you can select devicename or
deviceclass or neither:
SHOWDEV [devicename]
[deviceclass]
Conventions (continued)
[...] Within syntax statements, a horizontal ellipsis
enclosed in brackets indicates that you can
repeatedly select elements that appear within the
immediately preceding pair of brackets or braces. In
the following example, you can select itemname and
its delimiter zero or more times. Each instance of
itemname must be preceded by a comma:
[,itemname][...]
If a punctuation character precedes the ellipsis, you
must use that character as a delimiter to separate
repeated elements. However, if you select only one
element, the delimiter is not required. In the
following example, the comma cannot precede the first
instance of itemname:
[itemname][,...]
|...| Within syntax statements, a horizontal ellipsis
enclosed in parallel vertical lines indicates that
you can select more than one element that appears
within the immediately preceding pair of brackets or
braces. However, each element can be selected only
one time. In the following example, you must select
,A or ,B or ,A,B or ,B,A :
{,A}|...|
{,B}
If a punctuation character precedes the ellipsis, you
must use that character as a delimiter to separate
repeated elements. However, if you select only one
element, the delimiter is not required. In the
following example, you must select A or B or AB or
BA. The first element cannot be preceded by a comma:
{A}|,...|
{B}
... Within examples, horizontal or vertical ellipses
indicate where portions of the example are omitted.
_ Within syntax statements, the space symbol _ shows a
required blank. In the following example, you must
separate modifier and variable with a blank:
SET[(modifier)]_(variable);
underlining User input is underlined. For example:
PROMPT? response
In a syntax statement, brackets, braces, or ellipses
are underlined if you must enter them. For example:
COMMAND [[ParameterA]] = ParameterB
Conventions (continued)
shading Within an example of interactive dialog, shaded
characters indicate user input or responses to
prompts. In the following example, OMEGA is the
user's response to the NEW NAME prompt:
NEW NAME? OMEGA
The symbol indicates a key on the terminal's
keyboard. For example, Ctrl indicates the Control
key.
Ctrl char Ctrl char indicates a control character. For
example, Ctrl Y means you have to simultaneously
press the Control key and the Y key on the keyboard.
base prefixes The prefixes %, #, and $ specify the numerical base
of the value that follows:
%num specifies an octal number.
#num specifies a decimal number.
$num specifies a hexadecimal number.
When no base is specified, decimal is assumed.
Bit (bit:length) When a parameter contains more than one piece of data
within its bit field, the different data fields are
described in the format bit (bit:length), where bit
is the first bit in the field and length is the
number of consecutive bits in the field. For
example, Bits (13:3) indicates bits 13, 14, and 15:
most significant least significant
|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|
| 0| | | | | | | | | | | | |13|14|15|
|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|
Bit (0:1) Bits(13:3)
MPE/iX 5.0 Documentation