Joined: 06 Jun 2008 Posts: 8280 Location: Dubuque, Iowa, USA
From the CICS Resource Definition manual:
6.4.5 Indirect destinations--DFHDCT TYPE=INDIRECT
An indirect destination is specified by the DFHDCT TYPE=INDIRECT macro. The indirect destination does not point to an actual data set, but to another destination. This may be extrapartition, intrapartition, or remote. It may even be another indirect destination.
For example, you can give a different symbolic name (DESTID) to each of several different message types. You can then send all these message types either to the same physical destination (INDDEST), or to different physical destinations.
The DFH$TDWT sample program demonstrates how you can use indirect destinations to send different categories of message to the same terminal. For programming information about DFH$TDWT, see the CICS Customization Guide .
If you use EXEC CICS INQUIRE TDQUEUE, information is always returned about an indirect queue. (This does not, however, guarantee that the inquiry transaction is able to use EXEC CICS INQUIRE TDQUEUE for the ultimate target queue.)
If the QUEUE operand of an EXEC CICS WRITEQ TD (or READQ or DELETEQ) command specifies an indirect queue, access is determined by the security setting of the ultimate target queue.
Code this with the 1-through 4-character symbolic name of the indirect destination. The symbolic name is used when writing to the destination.
You must not use special characters, lower case, or mixed case characters in a DESTID name.
Code this with the name (DESTID) of a transient data destination. The destination can be intrapartition, extrapartition, remote, or indirect. If there is no DCT entry for the destination with this name, an assembly error results.