Installing the HTML templates

Attention: This topic contains Product-sensitive Programming Interface and Associated Guidance Information.

The procedure is as follows:

  1. Review your CICS® application programs and their use of BMS to see if customization is necessary.
  2. For the applications that need customized HTML pages, create a customization macro definition, and store it in a library in the concatenation of macro libraries specified in the SYSLIB DD statement for the assembler. Write appropriate DFHWBOUT macro invocations, and put them in the appropriate places in your map definitions.
  3. Assemble the existing map definitions with TYPE=TEMPLATE on the DFHMSD macro, or SYSPARM=TEMPLATE in the parameters passed to the assembler. Note that the label on the DFHMSD macro is used to name the HTML templates produced for each map in the map set being processed. The HTML template names consist of the label from the DFHMSD macro, followed by a one- or two-character suffix generated with the characters A-Z and 0–9. The two-character suffix is used when there are more than 36 maps in the mapset, and in this case the mapset name must be six characters or less. For the bridge exit to match the HTML template with the BMS map when a BMS SEND or RECEIVE is issued by a program, the HTML template members must match the name of the map set value used on the SEND and RECEIVE statements. If you are using a customizing macro, you must add the name of the customizing macro to the TYPE. The assembler produces IEBUPDTE source statements that set up one template for each map in a map set.
  4. Use IEBUPDTE to store the templates in the template library. If the record format of the template library is not fixed blocked, you will need to store them in another partitioned data set, and then convert them to the record format of the template library using, for instance, ISPF COPY.

  5. If you want to put your templates in a partitioned data set other than the one specified in the DFHHTML DDname, you must define DOCTEMPLATE definitions for your templates, and specify an alternate DDname. The alternate DDname must also be specified in your CICS JCL.
    To allocate a partitioned data set containing templates to a specific DD name in order to install templates from it, you can use the ADYN sample transaction. First install the DFH$UTIL group, which contains ADYN and its related programs, then run ADYN:
    ADYN
    ALLOC DDNAME(ddname) DATASET('template-pds') STATUS(SHR)
    where ddname is the DDname specified in the DOCTEMPLATE definition, and template-pds is the name of the partitioned data set containing the template to be installed. For further information on installing and using ADYN, see the CICS Customization Guide.