When definitions of remote server programs aren't required

There are some circumstances in which you may not need to install a static definition of a remote server program.

  • The server program is to be autoinstalled.

    As an alternative to being statically defined in the client system, the remote server program can be autoinstalled when a DPL request for it is first issued. If you use this method, you need to write an autoinstall user program to supply the name of the remote system. (For details of the CICS autoinstall facility for programs, see Autoinstalling programs, map sets, and partition sets. For programming information about writing program-autoinstall user programs, see Writing a program to control autoinstall of APPC connections.)

    When the autoinstall user program is invoked, it can install:
    A local definition of the server program
    CICS runs the server program on the local region.
    A definition that specifies REMOTESYSTEM(remote_region) and DYNAMIC(NO)
    CICS ships the LINK request to the remote region.
    A definition that specifies DYNAMIC(YES)
    CICS invokes the dynamic routing program to route the LINK request.
    Note: The DYNAMIC attribute takes precedence over the REMOTESYSTEM attribute. Thus, a definition that specifies both REMOTESYSTEM(remote_region) and DYNAMIC(YES) defines the program as dynamic, rather than as residing on a particular remote region. (In this case, the REMOTESYSTEM attribute names the default server region passed to the dynamic routing program.)
    No definition of the server program
    CICS invokes the dynamic routing program to route the LINK request.
    Note: This assumes that the autoinstall control program chooses not to install a definition. If no definition is installed because autoinstall fails, the dynamic routing program is not invoked.
  • The client program names the target region explicitly, by specifying the SYSID option on the EXEC CICS LINK command.
    Note:
    1. If there is no installed definition of the program named on the LINK command, the dynamic routing program is invoked but cannot route the request, which is shipped to the remote region named on the SYSID option.
    2. If the SYSID option names the local CICS region, the dynamic routing program is able to route the request.
  • DPL calls for the server program are to be routed dynamically.

    If there is no installed definition of the program named on the LINK command, the dynamic routing program is invoked and (provided that the SYSID option is not specified) can route the request.

    Note: Although in some cases a remote definition of the server program may not be necessary, in others a definition will be required—to set the program's REMOTENAME or TRANSID attribute, for example. In these cases, you should install a definition that specifies DYNAMIC(YES).