Maintain local and remote definitions separately

Maintaining local and remote definitions separately

To migrate your TCT definitions to one or more CSD files, do the following:
  1. Assemble the TCT for the terminal-owning system.
  2. Assemble the TCT for the application-owning system. If you have more than one application-owning system, they may be able to share remote definitions, so you may not need to assemble more than one application-owning TCT.
  3. Allocate definitions for different systems to different groups, if sharing a CSD file between systems.

    In the copy book example, if you use TYPE=GROUP macros to delimit groups within COMTERMS, edit COMTERMS after assembling DFHTCTLA and before assembling DFHTCTRB to change the TYPE=GROUP macros to name a different set of groups. (This does not apply if the tables are to be migrated to different CSD files.)

  4. Use DFHCSDUP to migrate all the TCTs. The commands look like this:
         MIGRATE TABLE(DFHTCTLA) TYPESGROUP(TTS)
         MIGRATE TABLE(DFHTCTRB) TYPESGROUP(TTS)

    Migration of the remote terminals normally creates definitions that use the same TYPETERMs created for the corresponding local definitions.

  5. Include the groups containing the local definitions in the GRPLIST for the terminal-owning system.
  6. Include the groups containing the remote definitions in the GRPLIST for each application-owning system.

If there are only a small number of terminals that need more than one definition, it is probably best to migrate all the definitions in the terminal-owning TCT and then to use RDO to create the corresponding remote definitions with the required REMOTESYSTEM attribute. You can use the COPY and ALTER commands to do this.