IBM listener input format

The standard listener requires the following input format from the client in its first transmission. The client should then wait for a response before sending any subsequent transmissions. Input can be in uppercase or lowercase. The commas are required.

Note: Because the listener cannot distinguish between a comma used as a delimiter in the listener's initial message and a comma that is part of the client-in-data format, the client-in-data format should not contain a comma. In text such as x'2C' in ASCII data or such as '6B' in EBCDIC data, the single quote can be interpreted as a comma.


>>-tran--+-----------------------------------------+-----------><
         |                        .-,kc--+---+---. |   
         |                        |      '-,-'   | |   
         '-,--+----------------+--+--------------+-'   
              '-client-in-data-'  +-,ic,--hhmmss-+     
                                  '-,td--+---+---'     
                                         '-,-'

tran: The CICS® transaction ID (in uppercase) that the listener is going to start. This field can be one to four characters.
client-in-data: Optional. Application data, used by the optional security exit ¹ or the server transaction. The maximum length of this field is a 40-byte character (35 bytes, plus 1 byte filler and 4 bytes for startup type).
/ic/td/kc: Optional. The startup type that can be either KC for CICS task control, IC for CICS interval control or TD for CICS transient data. These can also be entered in lowercase (kc,ic, or td). If this field is left blank, startup is immediate using CICS task control (KC). KC or kc can be specified to indicate that the child server task is started using EXEC CICS START with no delay interval. This is the same as specifying IC,000000.
hhmmss: Optional. Hours, minutes, and seconds for interval time if the transaction is started using interval control. All six digits must be given.
Note: TD ignores the timefield.