Configuration Section

Unless otherwise indicated the following are CASE INSENSITIVE:

• Keys
• Section
• Values

The following are CASE SENSITIVE:

• File Names

Section identifiers help organize the configuration file into relevant parts that may be re-used for alternate configurations and tests.

Explore other sections:

• Machine Configuration Section (this article)
• Deadstart Section
• Equipment Section
• Helpers Section
• NPU Connections Section
• Operator Section

REQUIRED Identifies the Section Name in the .INI file containing the representation of the deadstart panel.

REQUIRED Identifies the Section Name in the .INI file containing the equipment definitions.

Identifies the Section Name in the .INI file containing a list of pathnames of helper program start/stop scripts. This statement is optional. If not specified, then no helper programs are indicated, and none are started.

DEFAULT: “” (null string)

Identifies the Section Name in the .INI file containing definitions of data communication features to be used by the emulated NPU or MDI. This is optional. If it is not specified, then no NPU/MDI data communication features are defined (e.g., interactive terminals, remote batch stations, trunks, etc.).

DEFAULT: “” (null string)

Identifies the Section Name in the .INI file containing the list of operator commands to be executed during startup. This is optional. If it is not specified, no operator commands are executed automatically during startup.

DEFAULT: “” (null string)

Enables or disables the CPU exchange jump feature. This simulates the physical CEJ/MEJ switch that was found on the deadstart panels of most CDC mainframe models.

DEFAULT: 1

Defines the number of central processor units to be emulated by this configuration.

DEFAULT: 1

Sets the real-time clock increment value. When specified as 0, DtCyber uses the host computer's hardware clock to emulate the CDC mainframe's real-time clock. Normally, 0 is the recommended value. However, if the host computer does not have a hardware clock (not typical), the value should specify the number of 1-microsecond mainframe clock ticks per emulator execution cycle.

DEFAULT: 0

Sets the label that will be displayed in the DtCyber operator prompt and host computer system window title.

DEFAULT: 0

Specifies the number of banks of ECS memory that the machine has. An ECS bank contains ~126K 60-bit words.

DEFAULT: 0

Specifies the number of banks of ESM memory that the machine has. An ESM bank contains ~131K 60-bit words.

DEFAULT: 0

Enables or disables CPU and NPU/MDI idle detection.

DEFAULT: OFF

Specifies the number of consecutive emulator cycles where the mainframe CPU is detected to be in its idle loop before the host system CPU is idled.

LINUX/UNIX DEFAULT: 50 WINDOWS DEFAULT: 7000

Specifies the amount of time that the host CPU will be idled per idle cycle when mainframe idle has been detected. For Linux/Unix, the value is specified in microseconds. For Windows, it is specified in milliseconds.

LINUX/UNIX DEFAULT: 60 WINDOWS DEFAULT: 1

Specifies the source IP address to which DtCyber will bind all of the sockets it creates. When an IP address other than 0.0.0.0 is specified, sockets will be associated implicitly with a specific network interface. Thus, this statement can condition DtCyber to bind its sockets to a specific hardware interface, or to a virtual interface such as a TAP interface, enabling multiple instances of DtCyber to run on the same physical host without having UDP/TCP port conflicts. Specifying 0.0.0.0 (the default) causes sockets to be bound effectively to all available interfaces.

DEFAULT: 0.0.0.0

Defines the size of the machine's central memory, in 60-bit words. The value is expressed in octal. For mainframe model CYBER865, the value must be one of 1000000, 2000000, 3000000, or 4000000. For mainframe model CYBER875, the value must be one of 4000000, 10000000, 14000000, or 20000000. For other models, the value must be at least 40000.

DEFAULT: 1000000 (octal)

Defines the mainframe model that DtCyber will emulate.

DEFAULT: 6400

Requests DtCyber to start/stop a network interface automatically when it starts up and shuts down, respectively. This can be used, for example, to start/stop a TAP interface automatically.

device is the name of the interface device to start/stop, e.g., tap0. scriptpath is the pathname of the script that will be called to start/stop the interface. The default is ./ifcmgr. Three parameters are passed to the script: 1) the device name, 2) the IP address specified by the ipAddress statement, above, 3) the keyword start or stop, depending upon whether DtCyber is starting or shutting down.

Defines the type of operating system that will run on the mainframe for this configuration. This affects various features of the emulation, including how CPU idle is detected, how end of output jobs is detected, etc.

DEFAULT: NONE

DEFAULT: “” (nullstring)

This value must point to a pre-existing directory which will contain the persistent shadow objects used by dtCyber containing information to be used between restarts.

Specifies the maximum number of concurrent connections accepted by the PLATO NIU.

DEFAULT: 4

Defines the TCP port number on which the PLATO NIU will listen for connections from PLATO terminals.

DEFAULT: 5004

Defines the octal number of peripheral processor units to be emulated by this configuration.

DEFAULT: 12 (octal)

Sets the cycle counter frequency in MHz.

DEFAULT: 0

Specifies the maximum number of concurrent connections accepted by the 6676 multiplexor.

DEFAULT: 4

Defines the TCP port number on which the 6676 multiplexor will listen for Telnet connections.

DEFAULT: 5000

Establishes the debug trace mask used by DtCyber. The trace mask is an integer value where each bit enables/disables a trace feature, as defined below:

DEFAULT: 0