Sequence of conversion processing

This is the sequence of conversion processing.

  1. Unless USREXIT=NO is specified in the DFHCNV TYPE=ENTRY macro that defines the conversion template for the resource, DFHCCNV links to DFHUCNV, passing the parameter list described in Parameter list (DFHUVNDS).
    Note:
    1. If you have not defined a template, DFHUCNV is invoked, on the assumption that the user program is to handle all conversions for the resource.
    2. DFHUCNV must be present in your system unless all DFHCNV TYPE=ENTRY macros specify USREXIT=NO.
  2. If a conversion template is defined for the resource, DFHUCNV is responsible for converting any fields with a type in the user-data range.

    If no conversion template is defined for the resource, DFHUCNV is responsible for determining the format of the data, and for converting all appropriate fields.

  3. On return from DFHUCNV, DFHCCNV carries out any standard conversions specified in the conversion template for fields that are not subject to user-defined conversion.
  4. The shipped request is executed.
Figure 1 illustrates the conversion process.
Figure 1. The data conversion process
Illustration showing the sequence of data conversion processing described in the text.