Remote destinations—DFHDCT TYPE=REMOTE

The DFHDCT TYPE=REMOTE macro defines a transient data destination that is owned by another CICS® system or region. The destination must also have a complete definition in the system or region in which it resides.

Note: If a transient data request includes the SYSID operand, CICS does not refer to the DCT but identifies the specified destination as remote.
Read syntax diagramSkip visual syntax diagram
>>-DFHDCT--TYPE=REMOTE--,DESTID=name--,SYSIDENT=name------------>

>--+----------------+--+---------------+-----------------------><
   '-,LENGTH=length-'  '-,RMTNAME=name-'   

TYPE=REMOTE
Indicates that this DCT entry identifies a remote transient data destination.
DESTID=name
Code this with a 4-character name by which the destination is known to application programs in the local system or region. For further information, see the RMTNAME operand below.

Do not use special characters, lower case, or mixed case characters in a DESTID name. The DESTID name should not start with a 'C' unless the name is known to CICS.

SYSIDNT=name
Code this with the 4-character alphanumeric name of the system or region in which the remote transient data destination resides. The name specified must be the same as that given in the CONNECTION name of the RDO definition. (For more guidance information about the CONNECTION option, see CONNECTION definition attributes.)
LENGTH=length
Code this with the length in bytes of fixed records for a remote destination. The value specified must correspond to that specified for the DCT in the system or region in which the destination resides. If a value is not specified for the LENGTH operand, code the LENGTH parameter in READQ or WRITEQ requests in the application program.
RMTNAME=name
Code this with the 4-character name by which the destination is known in the system or region in which that destination resides. If this operand is omitted (the normal case), the name specified in the DESTID operand is used.

If more than one system or region has a destination with the same name, the DESTID operand allows the definition of an alias that routes a transient data request to a specific system or region. RMTNAME defines the common name, SYSIDNT defines the system or region, and DESTID defines the unique alias. A transient data request using the alias identifies the remote name and the system or region to which the request is shipped.

Examples:

1. Destination A001 is owned by system A.

SYSTEM DESTID RMTNAME
A A001 A001
B B001 A001
D D001 A001
E E001 A001
In system A, both RMTNAME and DESTID are A001. In systems B, D, and E, RMTNAME is A001, but DESTID must be different.

2. Four systems A, B, D, and E each own a different destination, but each destination has the same name X001.

Each system has a definition for its local destination and each of the three remote destinations.

SYSTEM DESTID SYSIDNT RMTNAME
A A002 A X001
A B002 B X001
A D002 D X001
A E002 E X001
Each remote definition in system A:
  • Has the RMTNAME X001
  • Defines the remote system with the SYSIDNT parameter B, D, or E
  • Uses the DESTID parameter to define a unique alias for use by application programs in the local region