The automatic end system creation function and the processor file are connected to each other. The connection is established using the ACCESS parameter in the PROCESSOR-TABLE operand of the DCOPT, DCSTART and BCMOD commands.
With ACCESS you define the mode for server operation:
ACCESS=READ
Controlled server operation with restricted access to the host.
The partner end systems with the specified processor names which are described in the processor file can be created.
Further end systems may be created only when at least one of the following conditions is satisfied:
Creation of the socket host file is permitted
An entry exists for the end system in DNS and the use of DNS is enabled
The end system is permitted via a permitted server port
The IP address is entered in an IP range using a BCOPTION command
ACCESS=UPDATE
Open server operation with unrestricted access to the host.
Any partner end system may be created.
If the name of the partner end system is not contained in the processor file (or in the sources which are mentioned in the description for ACCESS=READ), it is permitted nevertheless and entered in the .AUT, .LOG and ISAM files. Furthermore, IP, IPv6 and ISO internet partners are entered retroactively in the .AUT and .LOG files.
ACCESS=ALLOW
Open server operation with unrestricted access to the host.
Any partner end system may be created, but is not entered in the.AUT, .LOG and ISAM files, i.e.:
If the name of the partner end system is not contained in the processor file (or in the sources which are mentioned in the description for ACCESS=READ), it is permitted nevertheless. In contrast to ACCESS=UPDATE, no creation takes place in the .AUT, .LOG and ISAM files. Furthermore, IP, IPv6 and ISO internet partners are not entered retroactively by means of dynamic generation.
Note
The partner end systems whose IPv6 Interface Identifiers are temporarily randomly generated and not, as suggested in the IPv6 Basis RFC, derived from the MAC address lead to non-unique entries in the .AUT, .LOG and ISAM files in the case of pure ACCESS=UPDATE. Precisely this is avoided with the setting ACCESS=ALLOW.
Switching to controlled server operation
Proceed as follows to switch from open to controlled server operation:
> | Use the BCMOD command to switch from ACCESS=UPDATE or ACCESS=ALLOW to ACCESS=READ. When switching from ACCESS=ALLOW to ACCESS=READ, no further steps are required. |
> | With the help of the .LOG file also include the processors which are still to have access in the original processor file. |
> | Replace the artificial processor names by the processor names you wish to use. |
> | In order to remove the artificial processor names in the .IS1 and .IS2 files, too, use the BCMOD command to temporarily specify a processor file which is identical to the original. |
> | Delete the derived .IS1 and .IS2 files of the original processor file. |
> | Delete the .AUT and .LOG files of the original processor file. |
> | Use the BCMOD command to specify the original processor file again. |
Details on .IS1, .IS2, .AUT and .LOG files are provided on "BCAM control files".