The processor file contains the assignments between the processor names and IP, IPv6 or ISO Internet addresses for partner end systems that were or can be added automatically.
A processor can be assigned multiple IP, IPV6 or ISO internet addresses. These addresses can be entered in the processor file.
The ISO internet, IP and IPV6 addresses must be unique. Their uniqueness must be guaranteed by the network administrator.
Own IP addresses must be defined if the BS2000 system has more than one line connection to an IP (sub)network. In this special case the own address is specified with the additional entry OWN-ADR/OWN-ADDR.
The processor name identifies the processor and gives the first route to this processor its name. If required, additional routes to this processor can also be generated automatically. These are then assigned an artificial name (see also section "Identifying automatically created end systems").
Note
DNS servers should always be entered in the FQDN file and not in the processor file, see section "FQDN file".
Handling multihoming problems
In configurations in which multiple lines are connected to one IP subnetwork then, in the case of client mode operation with local partner systems, no unique assignment of the BS2000 IP address that is to be used is possible on the basis of the partner IP address. In this case, the BS2000 system selects the first available local IP address.
This addressing problem, which is referred to as multihoming in the IP environment, can lead to problems if the affected partner systems do not know all the IP addresses.
These multihoming problems can be avoided by defining which IP address is to be used for the connection by additionally specifying the "OWN-ADR" parameter and the local IP address in the corresponding processor file entry (see definition of partner "PGTR3815“ in the "Example").
If a local IP address is specified by means of the "OWN-ADR" parameter then BCAM does not extend the configuration unless the specified local IP address is defined in BCAM.
Similar problems can occur with IPv6. In IPv6 it is therefore also possible to specify the local IPv6 address.
Name and content of the processor file
The name of the processor file is specified using the PROCESSOR-TABLE parameter of the DCOPT, DCSTART, or BCMOD command.
(Default name: $TSOS.SYSDAT.BCAM.PROCESSORS)
The following syntax rules apply to the file entries:
Comment lines:
1st. character = *
A comment line is not evaluated further.Structure of all other lines (read from left to right)
processor name (max. 8 characters)
at least one blank
type of address: “IP”, "IPV6" or “INTF”
at least one blank
alternatively:
IP address if "IP" is set (in "dotted decimal notation")
or
- IPv6 address if "IPV6" is set (in ": notation")
ISO Internet address, if “INTF” is set,
the contents of the address are interpreted as a string of hexadecimal characters (max. 40 characters).
at least one blank
"OWN-ADR/OWN-ADDR",
(optional if the own IP address is also specified, only evaluated if "IP" and "IPV6" set)
at least one blank
alternatively:
local IP address if "OWN-ADR/OWN-ADDR" and "IP"
(in "dotted decimal notation")
or
local IPv6 address if "OWN-ADR/OWN-ADDR" and "IPV6"
(in ": notation")
As of #, the remainder of the line is interpreted as a comment
Example
* Example for PROCESSOR-TABLE D055ZE30 IP 129.25.17.9 PGTR3815 IP 139.22.16.35 OWN-ADR 139.22.16.1 BCAMSR03 IPV6 FE80::A00:6FF:FE0D:5C4F # testhost1 IPv6 MIGRPC15 IPV6 ::139.25.17.9 BCAMVM03 IPV6 FE80::A00:6FF:FE08:9A62 OWN-ADR FE80:0:0:0:A00:6FF:FE08:9A6D D088P1 INTF 4465178819 # testhost1 ISO SOLARIS IP 139.25.226.106 SOLARIS IP 139.25.226.138 OWN-ADR 139.25.82.128 SOLARIS IPV6 3FFE:1:1000:6000:A00:20FF:FEB2:2859
The ISO Internet and IP and IPV6 addresses must be unique. The uniqueness must be ensured by the network administrator.