4.4 Coding Rules

There are only a few rules for creating configuration files. The file must be an ASCII text file. Blank lines,
or lines beginning with a hash (“#”) sign or an asterisk (“*”), are treated as comments and are not
checked.

The system parameters may appear in any order but must precede all device definitions. Each system
parameter must be specified on a separate line.

The device records may also appear in any order but must follow the system parameters. There must be
one device definition for each I/O device or for each group of identical I/O devices.

4.5 Record Format

The following sections describe the format of the Hercules configuration file records. The format is slightly
different between system parameters and device definitions.

4.5.1 Format of the system parameters

The record format of the system parameters is as follows:

system-parameter argument

where:

system-parameter is the name of the system parameter.

argument is the value assigned to the system parameter.

Examples:

CPUMODEL 3090

ENGINES 4*CP,2*AP,2*IP,2*IL

HTTP ROOT /usr/local/share/hercules/

PANRATE FAST

4.5.2 Format of the device definitions

The format of device definition is as follows:

devnum(s) devtype [argument(s)]

where:

devnum(s) is either: a single devnum (see details below), a range of devnums separated by a dash (“-“),
a count of devnums seperated by a dot (“.”), or a comma (“,”) separated list of devnums.

Examples include:

0200-0210 0300.10
0400,0410 0100,0110-011F

If devnums specifies more than one device then all devices will have identical characteristics. All devices
defined as a group must be defined on a single channel. A channel is defined as a continuous group of
256 (or hexadecimal 100) devices. For example devices 0010 and 0020 are on the same channel,
whereas devices 0100 and 0210 are not on the same channel.

The devnum itself is either a 1 to 4 digit hexadecimal number in the range 0000 to FFFF for ESA/390 or
0000 to 0FFF for S/370. The device number uniquely identifies each device to the operating system.

devtype is the device type.

argument(s) is a list of parameters depending on the device type. These parameters are explained in the
sections that describe each device type.

Examples:

0120 3380 mvsv5r.120

0230.16 3270 GROUP1 192.168.100.0 255.255.255.0

0583-0587 3420 * maxsizeM=170 eotmargin=131072

4.6 Sample Configuration File

The following figure shows a real example of a Hercules configuration file, used for running the MVS 3.8J
operating system. Please note, that not all possible parameter and definitions are contained in this
sample.

# **********************************************************************************************

# Hercules V4.00.0 Emulator Control file

# MVS V3.8J

# **********************************************************************************************

# ==============================================================================================

# System parameters

# ==============================================================================================

ARCHLVL S/370 # Initial architecture mode

CAPPING 25 # CPU capping (MIPS)

CNSLPORT 3270 # Telnet client port

CODEPAGE DEFAULT # Codepage conversion table

CPUMODEL 7060 # CPU model

CPUSERIAL 001963 # CPU serial number

DEFSYM DASDPATH D:/MVS/DASD # Define symbol for CCKD DASD device path

DEFSYM READERPATH D:/MVS/READER # Define symbol for READER device path

DEFSYM PRINTPATH D:/MVS/PRINTER # Define symbol for PRINTER device path

DEFSYM PUNCHPATH D:/MVS/PUNCH # Define symbol for PUNCH device path

DEVTMAX 0 # Maximum number of device threads

ENGINES CP # Processor engine types

HERCLOGO HERCLOGO.TXT # Hercules 3270 logo file

HTTP PORT 8089 NOAUTH # HTTP server port / authorization data

Previous Page Next Page