Resource definition for non-HTTP requests

Non-HTTP requests require TCPIPSERVICE and TRANSACTION resource definitions. 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.

About this task

Procedure

  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 the ones that can be used with the HTTP protocol. Refer to Creating TCPIPSERVICE resource definitions for CICS web support.
  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 runs the CICS program DFHWBXN. You can use an alternative transaction that runs DFHWBXN, except for 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. Refer to Creating TRANSACTION resource definitions for CICS web support.


dfhtl_nonhresdef.html | Timestamp icon Last updated: Sunday, 4 June 2017