Control section—DFHTCT TYPE=INITIAL

You code one DFHTCT TYPE=INITIAL macro before all the macros that define your resources. The TYPE=INITIAL macro has two purposes:
  1. To establish the area of storage into which the TCT is assembled.
  2. To specify information that applies to the whole TCT, or to the individual non-VTAM entries (and any VTAM-LDC definitions).
Read syntax diagramSkip visual syntax diagram
                         .-,ACCMETH=VTAM----.   
>>-DFHTCT--TYPE=INITIAL--+------------------+------------------->
                         '-,ACCMETH=NONVTAM-'   

   .-,ERRAT=NO-------------------------------------------------------.   
>--+-----------------------------------------------------------------+-->
   '-,ERRAT=LASTLINE--+------------+--+------------+--+------------+-'   
                      '-,INTENSIFY-'  +-,BLUE------+  +-,BLINK-----+     
                                      +-,RED-------+  +-,REVERSE---+     
                                      +-,PINK------+  '-,UNDERLINE-'     
                                      +-,GREEN-----+                     
                                      +-,TURQUOISE-+                     
                                      +-,YELLOW----+                     
                                      '-,NEUTRAL---'                     

   .-,MIGRATE=YES------.                                       
>--+-------------------+--+------------+--+----------------+---><
   '-,MIGRATE=COMPLETE-'  '-,SUFFIX=xx-'  '-,SYSIDENT=name-'   

Note: SYSIDNT is Intercommunication only
Note: For general information about TYPE=INITIAL macros, see TYPE=INITIAL (control section).
ACCMETH=([VTAM,]NONVTAM)
This specifies the access methods required in the running CICS system.
VTAM
Specify this if you are using VTAM as an access method. (You can define VTAM devices only with the CEDA transaction, however.)
NONVTAM
Specify this if you are using telecommunications access methods other than VTAM. These access methods include BSAM (for sequential devices) and TCAM Start of change(for remote TCAM terminals)End of change.
Note: The default is to assume both VTAM and NONVTAM.
ERRATT={NO∨([LASTLINE][, INTENSIFY] [,{BLUE∨RED∨PINK∨GREEN∨TURQUOISE∨YELLOW∨ NEUTRAL}][,{BLINK∨REVERSE∨ UNDERLINE}])}
Indicates the way error messages are displayed on all 3270 display screens. You can either let it default to NO, or specify any combination of LASTLINE, INTENSIFY, one of the colors, and one of the highlights. Specifying INTENSIFY, one of the colors, or one of the highlights forces LASTLINE.

Any attributes that are not valid for a particular device are ignored.

NO
Any error message is displayed at the current cursor position and without any additional attributes.
LASTLINE
Any error message is displayed starting at the beginning of the line nearest the bottom of the screen, such that the message fits on the screen.

Attention: If messages are received in quick succession, they overlay one another. The earlier messages may disappear before the operator has read them.

INTENSIFY
Error messages are intensified, and placed on the last line of the screen.
BLUE∨RED∨PINK∨GREEN∨TURQUOISE∨YELLOW∨ NEUTRAL
Error messages are shown in the color specified, and placed on the last line of the screen.
BLINK∨REVERSE∨UNDERLINE
Error messages are highlighted, and placed on the last line of the screen.
MIGRATE={YES∨COMPLETE}
This operand controls the building of TCT entries for VTAM devices that are eligible for resource definition online (RDO). The only way RDO-eligible resources may be moved to the CSD file from the macro source is to use DFHCSDUP, as described under YES below.
YES
YES indicates that you want to generate the necessary data to migrate your RDO-eligible resources. The records generated from the macro source are designed to be used as input to the DFHCSDUP utility program. An MNOTE attention message is issued for each RDO-eligible resource. The DFHCSDUP MIGRATE command converts them into resource definitions on the CSD file. These can then be managed using RDO.
COMPLETE
Use of COMPLETE means that TCT entries are not generated from the macro source for any RDO-eligible devices. For each one, the assembly produces an MNOTE. This means that you can keep your TCT macro source code after you have migrated your definitions.

If you continue to assemble a TCT for resources that are not eligible for RDO, continue to use MIGRATE=COMPLETE.

SYSIDNT={CICS∨name}
This 1- to 4-character name is a private name that the CICS system uses to identify itself. If you use DFHTCT TYPE=REGION macros to define remote terminals, you must code this operand. It is used to determine whether a remote or a local TCT terminal entry is generated from each TYPE=TERMINAL macro following the TYPE=REGION macro. If the SYSIDNT on the TYPE=REGION macro is the same as the SYSIDNT on the TYPE=INITIAL macro, a local definition is generated; otherwise a remote definition is generated.

The value you code for this operand is used to define the name of the local region during assembly of the TCT only. You must also define the name of the local region, for execution purposes, using the SYSIDNT system initialization parameter.