# Compaq ACMS for OpenVMS
Concepts and Design Guidelines

## Index

Previous | Contents

Master Alphabetic Index
A | B | C | D | E | F | G | H | L | M | N | O | P | Q | R | S | T | U | V | W

A
Access Control List
and task-call-task
ACMS$LOCAL_TDMS_IN_AGENT logical
ACMS$PROCESSING_STATUS workspace
contains status values
Agent program
ACMS-supplied
coordinating distributed transaction from
Application
deciding number of
design
business objectives in
design issues
development cycle #1
development cycle #2
form design for
guidelines for programming
performance #1
performance #2
Application Execution Controller
APPLICATION LOGICAL NAME clause
Application programming
suggestions
Atomic units
of work
Attributes
defined
Availability
specified in requirements analysis
B
Block steps
coordinating distributed transaction from
Business activities
and transactions
defining
effect on task design
Business areas
defining
Business functions
defining
identifying transactions within
mapped to AVERTZ tasks
relationship to tasks
C
Cancel actions
performance considerations
CMS
See Code Management System
Code Management System
application development tool
Command Process
alternatives
Conditional
processing
for task flow control
work
complex processing
D
Data
remote
choosing access for
Data Manipulation Language
use of precompiled statements
Data type
conversion #1
conversion #2
Database
design
relationship to application design
Database transaction
defined
Databases
attributes
binding and opening
entities
relationships
DCL
commands
for TDMS
servers
See also Servers
DEC/Code Management System
See Code Management System
DEC/Module Management System
See Module Management System
DEC Software Engineering Tools
for application development
DEC/Test Manager
application development tool
DECforms
ACMS default form presentation service
and ACMS
choosing number of forms
field validation
performance
considerations
issues
structure and design
DECset
See DEC Software Engineering Tools
DECtp Implementation Toolkit
application development tool
Design
documents
modular
of database
of software
user interface
Development cycle
for ACMS
Distributed forms processing
and task queues
benefits of
Distributed transactions
choosing remote access
coordinating
from agent
from block step
from processing step
from step procedure
from tasks
defined
for multiple databases
tracking #1
tracking #2
where coordinated from
DTM
See DEC/Test Manager
E
Entities
defined
relationships between
EXC
See Application Execution Controller
Exception handling
in ACMS
types of exceptions
Exchange steps
defined by business activities
in transactions
F
Fields
validation
performance considerations #1
performance considerations #2
Flow control
in tasks
Forms
design
data type conversion #1
data type conversion #2
performance considerations
scrolled regions
trade-offs in
use of data types other than text #1
use of data types other than text #2
use of forms product other than DECforms
I/O
access to presentation service
Functional analysis
for ACMS design
requirements for TP system
Functional Specification
for ACMS design #1
for ACMS design #2
for identifying transactions
G
Group
workspace type #1
workspace type #2
H
Handling errors
passing status in workspaces
L
Language-Sensitive Editor
application development tool
Locks
See Records, locks
LSE
See Language-Sensitive Editor
M
Memory
usage
Menu
customizing
MMS
See Module Management System
Modular design
of ACMS applications
of tasks
Module Management System
application development tool
Multiple-step tasks
design of user interface
memory usage
performance considerations
processing by ACMS run-time
N
Naming
procedures
guidelines
Nested blocks
for task flow control
Nonrecoverable exceptions
type of exception
O
Oracle Trace
logging performance events
tracking distributed transactions #1
tracking distributed transactions #2
P
PCA
See Performance and Coverage Analyzer
Performance
application design
form design #1
form design #2
form design #3
multiple-step tasks #1
multiple-step tasks #2
releasing server context
reusable procedure servers
reusable servers
workspace design
application design issues
DECforms issues
logging performance events with Oracle Trace
releasing server context #1
releasing server context #2
Request Interface issues
specified in requirements analysis
Systems Interface issues
task group
TDMS issues
with distributed forms processing
Performance and Coverage Analyzer
application development tool
PEU
use of I/O within
Presentation services
for ACMS
Procedures
coordinating distributed transaction from
designing
grouping in servers
guidelines for writing #1
guidelines for writing #2
initialization
advantages of
servers
See also Servers
uses of
Processing
deferred
of ACMS tasks
with task queue
Processing immediacy
for each business function
specified in requirements analysis
Processing steps
coordinating distributed transaction from
locking records for RMS update tasks
performance considerations
Programming
considerations
Programming Specification
for ACMS design #1
for ACMS design #2
identifying ACMS components in

Previous | Next | Contents | Index