# Compaq ACMS for OpenVMS
Concepts and Design Guidelines

Previous | Contents | Index

Q
Queues
See Task queue
Queuing
See Task queue
R
Records
locks
contention
duration and performance
effect of retaining server context on
use of reusable server processes
Relationship
defined
types of entity
Remote
access to data
choosing method for
Request
I/O
access to presentation service
Request Interface
and Systems Interface
for user-written presentation service
Requirements analysis
for ACMS design
Requirements Specification
additional requirements
for ACMS design #1
for ACMS design #2
to meet a business problem
Resource manager
determined from Requirements Specification
single or multiple
Return
status
to ACMS
S
SCA
See Source Code Analyzer
Scrolled regions
Security
specified in requirements analysis
using task for
Server context
and locking
Servers
advantages of reusable
context
advantage of releasing
record locks in
retaining
retaining and releasing
meeting task processing requirements
processes
reusable procedure servers #1
reusable procedure servers #2
reusable servers #1
reusable servers #2
setting number of
See also DCL, servers
See also Procedures, servers
types
using procedure servers
Software design
relationship to database design
Source Code Analyzer
application development tool
Step exception
type of exception
Steps
procedures
servers for
sequencing
controlling task flow through
Stream I/O
access to presentation service
limitations
Systems Interface
and Request Interface
and user-written presentation service
use instead of DECforms
T
Task-call-task
customized menus
for security
for task flow control #1
for task flow control #2
Task groups
and form-related syntax
deciding number of
design issues
performance issues
Task queue
ACMS tasks
for deferred processing #1
for deferred processing #2
for high application availability
for transaction persistence
Tasks
and exchange step syntax
as logical transactions
coordinating distributed transaction from
definitions
testing status values
design
performance considerations #1
performance considerations #2
trade-offs in
designing for modularity
flow control in
independence of using Request Interface
multiple-step
performance considerations
relationship to business functions
single-step
performance considerations
step sequencing in
task-call-task and common library tasks
workspaces
types #1
types #2
types #3
TDMS
See Terminal Data Management System
Terminal
I/O
and procedures
use from processing steps
Terminal Data Management System
ACMS default request presentation service
field validation
performance considerations
performance issues
runtime support
using ADU syntax
using DCL commands
Tools
for application development
Transaction exceptions
type of exception
Transactions
defined by business activities
duration
for each business function
identifying within each business function
in exchange steps
lock contention #1
lock contention #2
logical
mapped to AVERTZ tasks
U
Update tasks
RMS
locking records
User
interface
alternatives
design of
for ACMS
major design considerations
performance considerations #1
performance considerations #2
performance considerations #3
specified in requirements analysis
workspace type #1
workspace type #2
V
Validation
in form or procedure
VR_CHECKIN_TASK
AVERTZ application task #1
AVERTZ application task #2
VR_CHECKOUT_TASK
AVERTZ application task #1
AVERTZ application task #2
VR_COMPLETE_CHECKOUT_TASK
AVERTZ application task #1
AVERTZ application task #2
VR_GETRESV_TASK
AVERTZ application task #1
AVERTZ application task #2
VR_RESERVE_TASK
AVERTZ application task #1
AVERTZ application task #2
W
Workspaces
declaring and referring to #1
declaring and referring to #2
declaring and referring to #3
defining
group type
passing
status values
size of
structure
task type #1
task type #2
user type
using