Resource definition for non-HTTP requests

TCPIPSERVICE and TRANSACTION resource definitions are needed for non-HTTP requests. TCPIPSERVICE resource definitions for non-HTTP requests must specify the USER (user-defined) protocol, which is associated with the CICS-supplied transaction CWXU. URIMAP resource definitions are not used when requests are received through the USER protocol.

  1. Create a TCPIPSERVICE resource definition, with the USER protocol, for each port that you use for non-HTTP requests. The attributes that can be used with the USER protocol are the same as those which can be used with the HTTP protocol. Creating TCPIPSERVICE resource definitions for CICS Web support tells you how to do this.
  2. For each TCPIPSERVICE resource definition, decide whether to use the CICS-supplied transaction CWXU, the CICS Web user-defined protocol attach transaction, or an alternative. The DFHCURDI sample includes a sample definition for CWXU. CWXU executes the CICS program DFHWBXN. An alternative transaction that executes DFHWBXN may be used, with the exception of the other default transactions that are defined for protocols on the TCPIPSERVICE resource definition.
  3. Optional: Create TRANSACTION resource definitions for any alias transactions that you want to use for request processing. Creating TRANSACTION resource definitions for CICS Web support tells you how to do this.