Entries in transaction list table—DFHXLT TYPE=ENTRY

Read syntax diagramSkip visual syntax diagram
>>-DFHXLT--TYPE=ENTRY--+--------------------------------+------->
                       '-,TASKREQ=(kkkk-+-----------+-)-'   
                                        '-,kkkk,...-'       

>--,TRANSID=(xxxx-+-----------+-)------------------------------><
                  '-,xxxx,...-'     

TYPE=ENTRY
Code this if one or more entries are to be generated in the XLT.
TASKREQ=(kkkk[,kkkk],...)
kkkk can be one of the following:
  • PA1 through PA3, and PF1 through PF24 indicates one of the special 3270 keys that can be used to initiate a task.
  • LPA (light pen attention) indicates that a transaction is to be initiated when a light pen detectable field is selected.
  • OPID (operator identification card reader) indicates that a transaction is initiated when the appropriate operator's identity badge has been read in.
  • MSRE indicates that transactions are initiated when the 10/63 character magnetic slot reader is used.

Define each TASKREQ on the CSD file, and install it in the running system. (For further information, see the description of the TASKREQ attribute in TRANSACTION definition attributes.)

TRANSID=(xxxx[,xxxx],...)
Represents a 1- to 4-character transaction code. Define each TRANSID on the CSD file, and install it in the running system. (For further information, see the description of the TRANSACTION attribute in TRANSACTION definition attributes.)

If the TRANSID contains a special character (for example, a comma), the TYPE=ENTRY instruction must contain only one TRANSID with quotation marks as delimiters.

Note: TASKREQ and TRANSID are mutually exclusive parameters.