Caution: On Windows, the value you choose for your process priority has a direct impact on how your
thread priorities are interpreted! You should never modify one without understanding what impact you are
doing so might have on the other!

5.82.2 Thread Priorities

On Linux/Unix hosts Hercules needs to be a setuid root program to allow it to reset its dispatching priority
to a high (negative) value (i.e. “chown root.root hercules; chmod +s hercules”).

For Windows the following conversions are used for translating Linux/Unix thread priorities to Windows
thread priorities:

Unix
Thread Priority

Windows
Thread Priority

Meaning

-20 to -16

Time Critical

Base priority of 15 for Idle, Below Normal, Normal, Above Normal,
or High class processes, and a base priority of 31 for Realtime
class processes.

-15 to -9

Highest

Priority 2 points above the priority class.

-8 to -1

Above Normal

Priority 1 point above the priority class.

0 to 7

Normal

Normal priority for the priority class.

8 to 15

Below Normal

Priority 1 point below the priority class.

16 to 19

Lowest

Priority 2 points below the priority class.

20

Idle

Base priority of 1 for Idle, Below Normal, Normal, Above Normal,
or High class processes, and a base priority of 16 for Realtime
class processes.

Table 9: Thread Priority Conversions

Caution: On Windows, your Thread Priority is interpreted differently based on your chosen Process Prio-
rity setting! You should never modify your Thread Priority settings without first reviewing your chosen Pro-
cess Priority setting!

6. Device Definition Descriptions

6.1 Local non-SNA 3270 Devices

6.1.1 Function

The local non-SNA 3270 device statements are used to define terminals to the Hercules configuration.
There are no required arguments for this particular device type but there are several optional arguments
that may be specified.

To use this device a tn3270 client must connect to the host machine via the port number specified on the
CNSLPORT statement. A valid tn3270 device type such as IBM-3278 must be used.

If the tn3270 client software allows it to specify a device type suffix (e.g. IBM-3278@GROUPNAME) then
the suffix can be used to connect to that specific device number, if defined. If no suffix is used then the
tn3270 client will be connected to the first available and defined 3270 device.

If a specific terminal device address is specified via the device type suffix of the tn3270 client software
then it must be eligible to connect at that device address or the connection is immediately rejected. An
alternative terminal device for which the tn3270 client might be eligible will not be automatically selected.

6.1.2 Syntax

Descriptive

[groupname [ipaddr [mask]]]

Diagram

Êʬ¬¬ ¬¬¬ ¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬Ê






ʬ¬¬§¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬§¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬ÊÍ


¬¬¬¬¬ * ¬¬¬¬¬¬¬§¬¬¬§¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬«


groupname ¬¬¬ ipaddr ¬¬¬§¬¬¬¬¬¬¬¬¬¬¬¬«








¬¬
mask ¬¬

6.1.3 Parameter

devaddr

This is the device address.

devtype

This is the device type. Valid terminal device types are 3270 and 3278.

groupname

If a terminal group name is given on the device statement then a device type suffix
with this group name can be used to indicate that a device in this group is to be

Previous Page Next Page