Configuring CICS Web support base components

The base components of CICS® Web support are needed for all CICS Web support tasks. You need to configure these before starting to work with CICS Web support.

Start of change Components of CICS Web support lists all the components. The base components that you need to set up are:

If you want to use an analyzer program that you coded in an earlier CICS release to reference the code page conversion table DFHCNV, you might need to set up some DFHCNV entries. Code page conversion table entries are not required for new CICS Web support development.

When you have set up these base components, you can verify the operation of CICS Web support using the supplied sample programs.

End of change
  1. Enable TCP/IP support for the CICS region, following the instructions in "Using TCP/IP in a CICS region" in the CICS Installation Guide. This process includes setting up Communications Server and establishing access to a DNS, or domain name, server through z/OS.
  2. Enable CICS to access z/OS UNIX System Services by including an OMVS segment in the user profile of the CICS region user ID, following the instructions in "Authorizing CICS region userids to z/OS UNIX System Services" in the CICS Installation Guide.
  3. Set up SSL support, following the instructions in the CICS RACF® Security Guide. The CICS RACF Security Guide explains the facilities that SSL provides.
  4. Create one or more TSMODEL definitions for temporary storage queues to store CICS Web support data from Web transactions. The CICS Resource Definition Guide tells you how to do this. Temporary storage queues are used to store request lines, status lines, and HTTP headers for inbound and outbound messages. (They are not used for message bodies.) The prefix for a temporary storage queue is specified on TCPIPSERVICE definitions for ports on which requests are received.
    Note: Do not specify a TSMODEL that specifies the POOLNAME attribute: CICS Web support does not support the use of shared temporary storage queues. Also, the use of recoverable temporary storage queues is not recommended for CICS Web support, because this can cause locking issues and reduce throughput.
  5. Specify appropriate system initialization parameters, following the steps in Specifying system initialization parameters for CICS Web support. Some of the system initialization parameters are optional at this stage.
  6. Reserve as many ports belonging to z/OS Communications Server as you need for CICS Web support. Reserving ports for CICS Web support has more information about this.
  7. Optional: If you have existing request processing structures in CICS Web support that include an analyzer program which references entries in the conversion table (DFHCNV), and you want to continue using these request processing structures unchanged, Migrating entries in the code page conversion table (DFHCNV) tells you what to do. You do not need a code page conversion table for any other CICS Web support tasks.
  8. Verify the operation of CICS Web support using the supplied samples. Verifying the operation of CICS Web support tells you how to do this.