Relative performance of CICS web support response methods

Application-generated responses use more resources than static responses. Application-generated responses require a user transaction to be attached. An analyzer program, converter program, or more than one user-written application program might be involved in processing the request and producing the response. Typically, greater elapsed time and processor time is required to produce the response.

Static responses involve only the web attach task, a URIMAP definition, and the source document for the response body. Performance for a static response is better than for an application-generated response, so if you are using an architecture with an application program and analyzer program to deliver a simple response document, consider converting this to a static response. For those application-generated responses, the requests that are targeting a URIMAP with ANALYZER(NO) specified might qualify for being processed by directly attached user transactions, and bypassing the web attach task. For more information, see HTTP requests are processed by directly attached user transactions.

For UNIX files only, the HTTP If-Unmodified-Since header is respected. If the UNIX file is unmodified since the time selected in this header, the file is not returned, and an HTTP 304 (Not Modified) response with no message body is returned instead. This can considerably reduce the amount of data transmitted.

Within this category, performance is further influenced by the choice of source document used for the response body, which can be:
  • A z/OS® UNIX System Services file, called directly from the URIMAP definition using the HFSFILE option.
  • A z/OS UNIX System Services file, defined as a CICS® document template, and called from the URIMAP definition using the DOCTEMPLATE option.
  • A document template stored in a z/OS partitioned data set or PDSE.
  • A document template stored in a transient data queue.
  • A document template stored in a temporary storage queue.
  • A document template stored in a CICS file (ESDS, RRDS or another type of data set).
  • A document template contained in a CICS program.
  • A document template generated by an exit program. The content of the document template could be loaded from a location such as DB2® or another database manager. Document templates generated by an exit program are classed with static responses when they operate through a URIMAP definition and not through a web-aware application program. However, they do involve an application program, so in terms of resource and performance, they can be similar to an application-generated response.

Introduction to documents and document templates has more information about the different types of CICS document template, and how to set them up. If you are using a CICS document template to provide a static response, ensure that the definition is installed before you use it.

To improve performance, the CICS document handler caches a copy of most document templates when they are installed. Subsequent references to the template use the cached copy. This means that the relative speed of access for the document template type is not important after the first retrieval from the source. Caching does not take place for document templates retrieved from CICS programs, because programs are already managed by the CICS loader, and have fast retrieval times. For document templates generated by exit programs, you can specify whether or not a copy is to be cached.

When storage is constrained, the performance of document templates can be impacted. Programs containing document templates are managed like other CICS loaded programs, and may be flushed out by program compression. Document templates cached by the document handler may be released, and on the next reference of these document templates, they will need to be retrieved from the source.



dfht3np.html | Timestamp icon Last updated: Monday, 5 June 2017