Automatic creation and vary on of the controller description

When APPN support determines that it needs a controller description automatically varied on, it determines if there are any existing controller descriptions that follow the naming convention for automatically created APPC controllers.

Naming convention for controller descriptions:

• The first controller description created has the same name as the CP name of the adjacent system
• Additional controller descriptions created use the following conventions:

CPNAMExx

Where CPNAME is the adjacent system's control-point name and xx is some value from 00-FF.

If the adjacent system does not send a control-point name, then the local system creates a name that is based on the adjacent system's EXCHID value. The format of the name is:

CIIIIIxx

Where C is a constant value, IIIII is the exchange identifier (that is not including the three-digit block number), and xx is some value from '00-FF'.

For an existing controller description to be considered a possible candidate for being automatically varied on, it must:

• Satisfy the naming convention
• Be an APPC controller description
• Be in a varied off status
• Have RMTCPNAME and RMTNETID parameters that match the incoming XID parameter
• Have LINKTYPE parameter specified as *LAN.

If no controllers are found that meet these initial requirements for automatic vary on, then the system creates a new controller. The name of this controller will be the first available name that follows the naming convention for this remote control-point name, and the controller description will indicate that the controller owner is the system (CTLOWN(*SYS)).