SeeView Manual

SeeView Directives
HP NonStop SeeView Manual—526355-004
8-3
SECTION
Use the PARM declaration within a procedure to reference string and integer
parameters passed by the CALL statement. String Intrinsics provide additional
information regarding the current calling environment. (See also HELP #, #MENU..
#TASK...intrinsics, and WITH statements.)
You can invoke procedures from menus, sills, other procedures, or another shell
environment such as SEECSTM. A procedure can display a menu, which can invoke a
procedure, which in turn can display a menu, and so on. This technique helps to
formalize and externalize the calling interface between procedures and menus and
promotes user control of complex functions.
For an example of a procedure called from a menu, see Example 8-1 on page 8-2.
SECTION
The ?SECT interpreter directive identifies groups of SeeView statements that are
automatically executed when you invoke a script file or cache with the INVOKE
statement or SF15, or when you first start a SeeView program.
The ?SECT section-name directive indicates the beginning of a section starting in
column one of a line. When you first start the SeeView program, all sections in the
current shell file are executed. After the SeeView program is running, sections
contained in source files are executed in one of two ways:
•
An INVOKE statement executed from either a menu production or a section
executes all sections in the specified file or cache. In this way, a menu invokes
external user menus and sections (for example, SEECSTM).
•
When you press SF15, sections are executed in the shell file or cache defined by
the ALTER SHELL statement. Press SF15 to reinvoke the shell setup (for example,
SeeShell).
Sections provide a way to externally initialize an environment (for example, declare
additional menus and procedures). See also the INVOKE statement on page 9-60.
SEEVIEW
The ?SEEVIEW interpreter directive identifies the version of the SeeView interpreter
needed to execute the script containing this directive. If the version of a SeeView
program is older than the directive specifies, the old version of SeeView does not
execute the script and issues a warning message. You can protect new scripts that use
new SeeView syntax from accidentally being executed by older versions of the
SeeView interpreter.
?SECT section-name
?SEEVIEW version