In multiple steps BCAM checks whether a partner end system may be created automatically. You can control the type and scope of automatic end system creation using, among other things, the following input files:
Processor file
Socket host file
FQDN file
These files have no direct influence on the BCAM routing tables, but influence only the bahavior of automatic end system creation.
If BCAM cannot determine the end system from the BCAM tables as it is known neither through generation nor through AEC, BCAM checks whether one of the following criteria is satisfied (if this is the case, it is created as a partner end system):
The partner end system is contained in the ISAM file derived from the processor file. Information from both the processor file and from the FQDN file is used to create this ISAM file.
The partner end system is contained in the socket host file.
- The partner end system is known to DNS, is located in the permissible range, and the use of DNS is enabled.
- You define the permissible range, i.e. the namespace or IP address range concerned (for both IPv4 and IPv6) using MODIFY-DNS-ACCESS.
- As the DNS server resides on a partner system, it must either be made known using CREATE commands or be entered in the processor file.
If BCAM was unable to determine the partner system using these checks, it proceeds as follows:
If ACCESS=UPDATE is set for the processor file, the partner end system is always created.
If the server port was permitted using the BCOPTION ... ADD(-REMOTE)-SERVER-PORTS command. access from/to the associated partner system is permitted. Up to 64 server ports can be specified which are granted the option of open, unhindered access to applications.
When the partner end system which begins a communication relationship is within the permissible IP address ranges, it is created.
You define the permissible address ranges using the BCOPTION ... ADD/REMOVE-IP-RANGE command.