Devices with LDC lists

For 3600, 3770 batch, 3770 and 3790 batch data interchange, and LUTYPE4 logical units, you can specify the name of an LDC list (Logical Device Code list). In RDO this information is held on the TYPETERM definition.

You cannot define the LDC list itself using RDO. The LDC list and its contents must still be defined by the macro method. The TERMINAL and TYPETERM using the LDC list can be created in RDO, and the LDC list defined by using the macro is named by the LDCLIST attribute on the TYPETERM definition.

You cannot define a list of LDC codes explicitly on the TYPETERM definition.1 This simplifies the interface to these facilities and allows tables to be migrated to the CSD file. If you have a DFHTCT TYPE=TERMINAL macro with an LDC= specification of the form:
LDC=(aa=nnn,bb=nnn,...)
the assembly produces a level 8 MNOTE. This tells you to recode the list either as a local LDC list or as an extended local LDC list. (See TYPETERM definition attributes.)
Then recode the terminal entry in this form:
DFHTCT TYPE=TERMINAL,TRMIDNT=tttt,TRMTYPE=uuuuu,
       ACCMETH=VTAM,LDC=nnnnnnnn
where nnnnnnnn is the name you gave your LDC list when you defined it.
DFHCSDUP MIGRATE always produces a TERMINAL-TYPETERM pair of definitions:
DEFINE TERMINAL(tttt) TYPETERM(xxxxxxxx)
DEFINE TYPETERM(xxxxxxxx) DEVICE(dddddddd) LDCLIST(nnnnnnnn)
1 This also applies to the DFHTCT TYPE=TERMINAL macro, although in earlier CICS® releases you could define of a list of LDC codes explicitly.