SNAX/APN Application Programming Manual

The ITI Interface
SNAX/APN Application Programming Manual—420111-001
3-5
Setting BREAK Key Ownership
(SETMODE Function 11)
Setting BREAK Key Ownership (SETMODE Function 11)
The file system lets a terminal user signal a running application by pressing the BREAK
key if the application performs its own BREAK handling. (If the application does not
performs its own BREAK handling, pressing the BREAK key while the application is
running returns you to the command interpreter where you started the application.)
Because 3270 terminals do not have the BREAK key, this function is simulated by
another key or key combination. Table 3-1 lists the various keys used for various types
of terminals.
A process that is enabled for BREAK is called the owner of BREAK. Only one process
can own BREAK for a specific terminal at any time. A process does not automatically
become the owner of BREAK when it is started; it becomes the owner of BREAK by
using SETMODE function 11.
param1
0 Disables BREAK key (default).
> 0 Enables BREAK key.
< 0 Gives BREAK ownership back to previous owner.
param2
Terminal access mode after BREAK is pressed.
0 Normal mode (any application that has the terminal open can access the
terminal).
1 BREAK mode (only applications with BREAK access can access the
terminal).
For information on how to establish BREAK access, see Setting Terminal Access
Mode and File Access Type (SETMODE Function 12) on page 3-7.
You can also fetch the current settings of the BREAK handling parameters; see Setting
and Fetching BREAK Parameters (SETPARAM Function 3) on page 3-6 later in the this
subsection. BREAK and BREAK handling are described in greater detail in the
Guardian Programmer’s Guide.
Table 3-1. Simulated BREAK Keys in 3270-Type Terminals
Terminal Key Used as BREAK
Non-SNA channel-attached PA1
SNA link-attached ATTN
CALL SETMODE ( filenum , 11 , param1 , param2 ) ;