You may have to define remote server programs if you are using CICS® DPL. A remote server program is a program that resides on another CICS system. CICS program-control LINK requests that are made against a remote program are shipped to the remote system by means of CICS DPL.
A remote server program can be defined using the CEDA transaction. Figure 57 shows the program attributes that you need to specify. How you specify the attributes depends on whether DPL requests for the program are to be routed to the remote region statically or dynamically.
DEFINE
PROGRAM(name)
GROUP(.....)
DESCRIPTION(......)
Remote Attributes
REMOTESYSTEM(name)
REMOTENAME(name)
TRANSID(name)
DYNAMIC(NO|YES)
To route DPL requests for the program statically:
An EXEC CICS LINK command that names the program is shipped to the server region named on the REMOTESYSTEM option.
To route DPL requests for the program dynamically:
An EXEC CICS LINK command that names the program causes the dynamic routing program to be invoked. The routing program can select the server region to which the request is shipped.
The name by which the server program is known on the local CICS system is specified in the PROGRAM option. This is the name that is used in LINK requests by client programs in the local system.
The name by which the server program is known on the remote CICS system is specified in the REMOTENAME option. This is the name that is used in LINK requests that are shipped by CICS to the remote system.
If the name of the server program is to be the same on both the local and the remote systems, the REMOTENAME option need not be specified.
It is possible to use the program resource definition to specify the name of the mirror transaction under which the program, when used as a DPL server, is to run. The TRANSID option is used for this purpose.
For dynamic requests that are routed using the CICSPlex® System Manager (CICSPlex SM), the TRANSID option takes on a special significance, because CICSPlex SM’s routing logic is transaction-based. CICSPlex SM routes each DPL request according to the rules specified for its associated transaction.
For introductory information about CICSPlex SM, see the CICSPlex SM Concepts and Planning manual.
There are some circumstances in which you may not need to install a static definition of a remote server program:
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 the CICS Resource Definition Guide. For programming information about writing program-autoinstall user programs, see the CICS Customization Guide.)
When the autoinstall user program is invoked, it can install:
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.