Asynchronous Terminals and Printer Processes Programming Manual

TERMINAL PROGRAMMING CONSIDERATIONS
Break Handling
Any process that runs on the same terminal as the command
interpreter or any other process that uses BREAK must perform
error recovery for the two errors associated with BREAK, errors
110 and 111.
CSSASYNC and TERMPROCESS delay for five seconds before responding
to a process that does not own break and is looping on the
BREAKONLY error. The delay prevents CPU usage from reaching
100 percent. Errors 118, 119, and 120 are still logged on the
console to notify the operator of the problem.
Using Break (Single Process per Terminal)
To use the break feature, you must indicate in your application
process the terminals to be monitored for a break signal and the
process ID of the process that is supposed to receive the break
message.
The SETMODE operation that enables this type of break monitoring
is:
operation = 11, set break ownership and terminal access
type
parameter-1 = cpu,pin , enable BREAK for process cpu,pin
parameter-2 = 0, specify normal terminal access type
The SETMODE operation that disables this type of break monitoring
is:
operation = 11, set break ownership and terminal access
type
parameter-1 = 0, disable BREAK
parameter-2 = 0, specify normal terminal access type
Example
To arm BREAK, you could place the following in your application
program:
LITERAL SET^BREAK^OWNER = 11,
NORMAL^MODE = 0;
.
November 1987 4-15