z/OS Communications Server: IP IMS Sockets Guide
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Transaction-request message segment (client to Listener)

z/OS Communications Server: IP IMS Sockets Guide
SC27-3653-00

To initiate a connection with an IMS™ server, the client first issues a transaction-request message segment (TRM), which tells the Listener which transaction to schedule.

The format of the transaction-request message segment (TRM) is:

Field Format Meaning
TRMLen H Length of the segment (in binary) including this field. This field is sent in network byte order.
TRMRsv CL2 Reserved
TRMId CL8 Identifying string. Always *TRNREQ*. If the client data stream will be sent in ASCII, the TRMId field should also be transmitted in ASCII because the Listener uses this field to determine whether ASCII to EBCDIC translation is required.
TRMTrnCod CL8 The transaction code (TRANCODE) of the IMS transaction to be started. It must not begin with a / character; it must follow the naming rules for IMS transactions. If the Listener has determined that data will be transmitted in ASCII, it translates the transaction code to EBCDIC before any further processing is done.
TRMUsrDat XLn This variable-length field contains client data that is passed directly to the security exit without translation.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014