HP 3000 Manuals HP 3000 Manuals
Chapter 6 CUSTOMIZING EDIT/3000
6-1. USER INTERFACE PROCEDURES
To satisfy a number of needs for Customizing EDIT/3000 in specific
applications, three logical procedures can be written. These procedures
are HP32201 'USERINIT, HP32201'USERADD, and HP32201'USER- COMMAND. They
are designed to allow you to tailor some of the externals of EDIT/3000 to
your specific requirements.
A user may write one, two, or all three logical procedures in SPL/3000,
FORTRAN/3000, or any other programming language which accepts parameters
as specified, produces a logical result, and is stored in an MPE/3000
Segmented Library (see the MPE Segmenter Reference Manual for a
description of segmented libraries), When EDIT/3000 is to be customized
for use by everyone on the system, these user written procedures should
be installed in the system segmented library (SL.PUB.SYS). If, however,
EDIT/3000 is to be customized for those users of a particular account,
they should be installed in the segmented library of the public group of
that account (SL.PUB.account). Lastly, if EDIT/3000 is being customized
for those users of an account who are logged on in a particular group,
the procedures should be installed in the seg- mented library of the
log-on group of that account (SL.group.account).
In all cases, in order for EDIT/3000 to call the procedures, it must be
initiated with the book MPE command
:RUN EDITOR.PUB.SYS; PARM=16
This is the only way to activate the procedures, even if they are in the
system segmented library. At run time, the segmented libraries are then
searched for the procedures in the following order: first the SL of the
log-on group of the log-on account, next the SL of the public group of
the log-on account, and last the SL of the public group of the system
account.
Note that a simple User Defined Command could be written to facilitate
initiating EDIT/3000 as described above. For example:
MYEDIT
OPTION LIST
RUN EDITOR.PUB.SYS; PARM=16
See Section IX of the MPE Commands Reference Manual for an explanation of
creating and using User Defined Commands.
Each procedure includes the following four parameters, in the order
shown: STRING, LENGTH, USER- SPACE, PROCSPACE. For example, written in
SPL/3000, the header for such a procedure is:
LOGICAL PROCEDURE HP32201'procname
(STRING,LENGTH,USERSPACE,PROCSPACE)
BYTE ARRAY STRING;
INTEGER LENGTH;
ARRAY USERSPACE;
ARRAY PROCSPACE;
where procname is either USERINIT, USERCOMMAND, or USERADD.
The parameters are defined as follows (additional requirements are given
in the descriptions of each procedure):
STRING is a byte array containing the characters of one line, which
may consist of up to 255 characters.
LENGTH is an integer value specifying the number of characters in
the current line being passed by STRING.
USERSPACE is a 10 word array that is available for user "global"
storage. This space is shared with the other user procedures. The
first two words contain the EDIT/3000 command input and output book
MPE file numbers, in that order. These file numbers could, for
example, be used for diagnostic messages by the three procedures.
The rest of the array is initialized to binary zeros when EDIT/3000
is invoked and will not be changed by EDIT/3000 between calls to the
procedures.
PROCSPACE is a 20 word array maintained by EDIT/3000 for the
procedure's use. It is shared with the EDIT/3000 PROCEDURE command
(see the description of the array SPACE, along with the PROCEDURE
command, in paragraph 4-31) and is initialized to binary zeros.
Descriptions of each procedure follow.