TRN1,userdataishere |
It starts the CICS® transaction TRN1 using task control, and passes to it the
data userdataishere in the field CLIENT-IN-DATA. |
TRN2,,IC,000003 |
It starts the CICS transaction TRN2 using interval control, without user data.
There is a 3-second delay between the initiation request from the
listener and the transaction startup in CICS. |
TRN3,userdataishere,TD |
It writes a message to the transient data queue
named TRN3 in the format described by the structure
TCPSOCKET-PARM, described in IBM listener output format.
The data contained in userdataishere is passed to
the field CLIENT-IN-DATA. This queue must be an intrapartition queue
with trigger-level set to 1. It causes the initiation of transaction
TRN3 if it is not already active. This transaction should be written
to read the transient data queue and process requests until the queue
is empty. This mechanism is provided for those server transactions
that are used very frequently and for which the overhead of initiating
a separate CICS transaction
for each server request could be a performance concern.
|
TRN3,,TD |
It causes data to be placed on transient data
queue TRN3, which in turn causes the start or continued processing
of the CICS transaction TRN3,
as described in the TRN3 previous example. There is no user data passed. |
TRN4 |
It starts the CICS transaction TRN4 using task control. There is no user data
passed to the new transaction. |