NPU Connections Section

Explore other sections:

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

An NPU connections section defines all of the data communication features supported by an NPU (Network Processing Unit), MDI (Mainframe Device Interface), or HCP (Host Communication Processor). This includes interactive terminals, remote batch devices, links between mainframes, and other networking features. If an NPU, MDI, or HCP equipment is defined, but an NPU connections section is not defined, the default configuration is as if an NPU connections section was defined with the following statement:

terminals=6610,0x01,10,raw

Thus, the default NPU/MDI/HCP configuration is that DtCyber will listen for interactive terminal connections on TCP port 6610, the connections will be associated with CLA ports starting with CLA port 01, as many as 10 concurrent connections will be accepted, and the connections will be handled as raw connections, i.e., Telnet protocol negotiations will not be recognized.

A CDC data communication network consists of a collection of mainframes and NPU's or MDI's. Each such mainframe, NPU, or MDI is a node in the network, and each one is assigned a unique number to identify it. Node numbers are in the range 1 to 255.

When a network includes at least one MDI, the MDI makes features of CDCNet accessible to mainframes running NOS 2 and the NAM subsystem. CDCNet as a whole is assigned a unique node number. This makes CDCNet appear to NAM as an individually addressable element of the network (like a mainframe, NPU, or MDI), thus enabling NAM to route service requests and data to “applications” in CDCNet (e.g., the CDCNet TCP/IP gateway).

DEFAULT: 255

cdcnetNode=<node_number>

Optional privileged TCP port offset for CDCNet TCP/IP passive connections. When a NAM applications requests to listen for TCP connections on a port number less then 1024, this offset is automatically added before requesting the host on which DtCyber is running to post the listen request. This can prevent the host system from rejecting the request when DtCyber is not running as a privileged application.

DEFAULT: 6600

cdcnetPrivilegedTcpPortOffset=<offset>

Optional privileged UDP port offsets for CDCNet TCP/IP passive connections. When a NAM applications requests to listen for UDP connections on a port number less then 1024, this offset is automatically added before requesting the host on which DtCyber is running to post the listen request. This can prevent the host system from rejecting the request when DtCyber is not running as a privileged application.

DEFAULT: 6600

cdcnetPrivilegedUdpPortOffset=<offset>

A CDC data communication network consists of a collection of mainframes and NPU's or MDI's. Each such mainframe, NPU, or MDI is a node in the network, and each one is assigned a unique number to identify it. Node numbers are in the range 1 to 255.

A unique node number assigned to a mainframe is known as a coupler node number. The coupler node number associated with a mainframe uniquely identifies the mainframe in the network.

DEFAULT: 1

couplerNode=<node_number>

Uniquely identifies the name of the host associated with this NPU/MDI configuration. When this DtCyber instance is configured to connect to others using LIP (Link Interface Protocol) or NJE (Network Job Entry) protocol, this identifier is sent to the other hosts during connection negotiation, and other hosts will send their unique identifiers to this host to identify themselves.

hostID=<string>

Defines the IPv4 address of the DtCyber instance associated with this configuration. Certain protocols such as NJE (Network Job Entry) use this value during connection negotiations with other hosts to help uniquely identify the local host.

DEFAULT: “127.0.0.1” (localhost)

hostIP=<ipv4_address>

Defines the allocated buffer threshold below which the NPU/MDI is considered to be idle. Asynchronous terminal connections tend to have buffers allocated to them briefly and on demand, as keystrokes are entered or output is being sent to them. HASP connections tend to have at least one buffer allocated to them while they are connected. Consequently, the value chosen for this parameter should be at least 2 greater than the number of HASP connections expected to be active concurrently under normal conditions.

Note that this configuration parameter is meaningful when the value of the idle parameter in the Machine Configuration Section is on. Otherwise, this parameter is ignored. When idle is on and the number of buffers allocated to network connections is greater than or equal to the value of idleNetBufs, the system as a whole is considered to be busy.

DEFAULT: 4

idleNetBufs=<buffer_count>

A CDC data communication network consists of a collection of mainframes and NPU's or MDI's. Each such mainframe, NPU, or MDI is a node in the network, and each one is assigned a unique number to identify it. Node numbers are in the range 1 to 255.

A unique node number assigned to an NPU or MDI is known as an NPU node number. The node number associated with an NPU or MDI uniquely identifies it in the network.

DEFAULT: 2

npuNode=<node_number>

HASP

terminals=<local-port>,<cla-port>,<connections>,hasp[,B<block-size>]

NJE

terminals=<local-port>,<cla-port>,<connections>,nje,<remote-ip>:<remote-port>,<remote-name>[,<local-ip>][,B<block-size>][,P<ping-interval>]

PTERM

terminals=<local-port>,<cla-port>,<connections>,pterm[,auto|xauto]

RAW

terminals=<local-port>,<cla-port>,<connections>,raw[,auto|xauto]

RHASP

terminals=<local-port>,<cla-port>,<connections>,rhasp,<remote-ip>:<remote-port>[,B<block-size>]

RS232

terminals=<local-port>,<cla-port>,<connections>,rs232[,auto|xauto]

TELNET

terminals=<local-port>,<cla-port>,<connections>,telnet[,auto|xauto]

TRUNK

terminals=<local-port>,<cla-port>,<connections>,trunk,<remote-ip>:<remote-port>,<remote-name>,<coupler-node>

Port numbers are divided into ranges as follows:

• Port numbers 0-1023 – Well known ports. These are allocated to server services by the Internet Assigned Numbers Authority (IANA). e.g Web servers normally use port 80 and SMTP servers use port 25 (see diagram above).

• Ports 1024-49151 - Registered Port -These can be registered for services with the IANA and should be treated as semi-reserved. User written programs should not use these ports.

• Ports 49152-65535 – These are used by client programs and you are free to use these in client programs. When a Web browser connects to a web server the browser will allocate itself a port in this range. Also known as ephemeral ports.

npuConnections.example.txt

[npu.nos287]
;----------------------------------------------------------------------
; Networking definitions for NOS 2.8.7
;----------------------------------------------------------------------
;
; Coupler node, NPU/MDI node, and CDCNet node numbers must match
; values defined in the NDL file and equipment deck.
;
couplerNode=1
npuNode=2
cdcnetNode=255
;
; Listen for TCP and UDP connections on actual, unbiased port numbers.
; These values are added to privileged port numbers to produce the
; port numbers on which DtCyber will listen for TCP and UDP services.
;
cdcnetPrivilegedTcpPortOffset=0
cdcnetPrivilegedUdpPortOffset=0
;
; Define the host identifier used in establishing trunk connections
; over TCP.
;
hostID=NCCM01
;
; CLA port 0x01 and 0x02 are reserved for trunks in an environment
; with multiple NOS hosts.
;
; Listen for trunk connection requests on TCP port 2550, and attempt
; to make connection requests to another NOS system running on the
; local host at port 2551, with host ID NCCM02 and coupler node 3.
;
terminals=2550,0x01,1,trunk,127.0.0.1:2551,NCCM02,3
;
; CLA port 0x03 is used for a PSU printer.
;
terminals=2552,0x03,1,raw
;
; CLA ports 0x04 - 0x13 are used for interactive terminal
; connections using the Telnet protocol.
;
terminals=23,0x04,16,telnet
;
; CLA ports 0x14 - 0x15 are used for remote batch terminal
; connections using the HASP/BSC/TCP protocol
;
terminals=2553,0x14,1,hasp,B400
terminals=2554,0x15,1,hasp,B400