The <handler> pipeline configuration element

Specifies the attributes of a message handler program.

Some CICS®-supplied handler programs do not use the <handler> element. For example, the CICS-supplied SOAP message handler programs are defined using the <cics_soap_1.1_handler>, <cics_soap_1.2_handler>, <cics_soap_1.1_handler_java>, and <cics_soap_1.2_handler_java> elements.

Used in:

Service provider
Service requester

Contained by:

<default_transport_handler_list> element
<transport_handler_list> element
<service_handler_list> element
<terminal_handler> element
<default_http_transport_handler_list> element
<default_mq_transport_handler_list> element

Contains:

<program> element, containing the name of the handler program
<handler_parameter_list> element, containing XML elements that are made available to the message handlers in container DFH-HANDLERPLIST.

The configuration elements must be used in the sequential order that they are listed.

Example

<?xml version="1.0"?>
<provider_pipeline>
        xmlns="http://www.ibm.com/software/htp/cics/pipeline">
 <service>
  <service_handler_list>
   <handler>
     <program>MYPROG</program>
     <handler_parameter_list><output print="yes"/></handler_parameter_list>
   </handler>
  </service_handler_list>
  <terminal_handler>
   <cics_soap_1.1_handler>
    ...
   </cics_soap_1.1_handler>
  </terminal_handler>
 </service>
 <apphandler>DFHPITP</apphandler>
</provider_pipeline>

In this example, the handler program is MYPROG. The handler parameter list consists of a single <output> element; the contents of the parameter list are known to MYPROG.