From a systems point of view, modularity is generally improved, program
implementation is uniform, documentation and on-line help generation are
automated and the user interface can be modified without affecting the
application programs.
The end user benefits from a single, consistent interface (regardless of the
computer or operating system) coupled with an ability to tailor and automate
the application environment.
From a conceptual point of view, tasks written under the IMP system are
treated like powerful "subroutines". Each task is passed a set of parameter
values, executes its function and returns. Where and how these parameter
values were determined is not the concern of the invoked applications task.
Central to the IMP system is the "Parameter File", in which all parameter
data values are stored before a subset of values is "passed" to an invoked
task. It is a permanent, sequentially-organized, random access disk data
file which can handle any number of parameters. Normally, IMP is used with
EASI, a user interface which handles all user I/0, examines and sets
parameter values and invokes tasks as subroutines. Other user interface
systems could be provided to perform this function without any changes to IMP
or to the applications programs.
A typical IMP system configuration is shown in Figure 3.
USER
1
USER INTERFACE (EAST)
IMP
|
PARAMETER FILE
[ | | ]
IMP IMP IMP IMP
TASK CODE [TASK CODH [TASK CODH [TASK CODE
Figure 3: One Possible IMP System Configuration.
The IMP library features include:
° automatic generation of program requirements
* automatic loading of control data into programs for execution
* automatic checking for missing parameters
consistent error handling
passing of control data between programs and procedures
596
Ther
PCI
the
the
whol
prog
enha
and
PCI'
lang
lear
and
effo
comp
comp
for
edit
blen
to u
prog
EASI
user
dict
lang
or a
The
All
appe
cons
cont
from
appl
days
dire
imme
para
valu
(STA
to c
