Installing shipped terminals and connections

Because your autoinstall control program is invoked for shipped terminals and connections, you can use it to reset the TERMINAL (or CONNECTION) attribute of a shipped definition to an alias, thereby avoiding conflicts with names of remote terminals, local terminals, sessions and connections already installed in the applications-owning region (AOR).

There is no need to reset the REMOTENAME attribute, which remains set to the name by which the terminal is known in the TOR; and autoinstall model names are not applicable to shipped definitions.

If the autoinstall control program selects a terminal name that clashes with the name of a local terminal, then the request is rejected and the autoinstall control program is not invoked again.

For more information about using aliases on remote definitions, see Local and remote names for terminals.