Start of change

Migrating entries in the code page conversion table (DFHCNV)

In this release, a code page conversion table is not normally required for CICS® Web support. However, if you have existing request processing structures that include an analyzer program which references entries in the conversion table, and you do not want to change the analyzer program, you can continue to provide DFHCNV entries.

In releases of CICS before CICS Transaction Server for z/OS®, Version 3 Release 1, the code page conversion table (DFHCNV) was used to define code page conversions between the code pages used within CICS, and the ASCII code pages used by Web clients. For CICS Web support in CICS Transaction Server for z/OS, Version 3 Release 1, you do not need to create any new entries in the code page conversion table. CICS Web support handles code page conversion using z/OS conversion services.

However, if you want to continue to use an analyzer program that you coded in an earlier CICS release to reference DFHCNV, you must either continue to supply the entries in the code page conversion table, or change the analyzer program. Changing the analyzer program involves coding two new output parameters to specify the client and server code pages, in place of the output parameter that specified the name of a DFHCNV entry. If you do this, you do not need to migrate your DFHCNV entries. Writing an analyzer program tells you how to code your output parameters in this way.
Note: As supplied, the CICS-supplied sample analyzer DFHWBADX specifies an entry defined in the sample code page conversion table DFHCNVW$. The sample conversion table can be used without any configuration, but you might prefer to modify DFHWBADX to use the new output parameters, to provide greater control and avoid the use of the sample conversion table.

If you prefer to continue using DFHCNV, follow these steps:

  1. Locate your source for the DFHCNV resource definition macros that you used to define the conversion table in an earlier CICS release. The sequence of macros should include a DFHCNV TYPE=ENTRY macro for each pair of code pages.
  2. Use the macros to set up a DFHCNV conversion table, following the process described in CICS Family: Communicating from CICS on System/390®. You need to define, assemble and link-edit the table.
End of change