Selecting files for use as data tables

It is not possible to lay down any exact rules about whether a file will benefit from conversion to a shared data table. The checklist in this topic gives some general guidance.

There are many considerations, and an analysis of the potential uses of shared data tables support should be undertaken by someone who understands how the files are used by the various applications and the configuration of the CICS® regions.

Additional sources of information that could help you to select the files include:
  • File statistics. Using statistics to select data tables describes how you can use statistics information as one of the inputs to the selection task.
  • The LSR pool statistics.
  • Trace entries.
  • Monitoring data.

However, the most beneficial input to the selection process is a thorough understanding of the applications and the way in which they use the files.

If your installation is using data tables for the first time, the following checklist gives some general principles to help you select files for defining as data tables.
  • You should consider using CICS-maintained data tables first, as these are easier to implement. If you use a CICS-maintained data table, no changes are required to the applications. If you use a user-maintained data table, some changes might be required.
  • Use a CICS-maintained data table if you need to ensure the integrity of the data table across a CICS restart.
  • Use a CICS-maintained data table if you require journaling of updates. If you require journaling of all access requests, the file is not suitable as a data table.
  • The exec interface user exits XEIIN and XEIOUT, and the file control user exits XFCREQ and XFCREQC, are not invoked in the file-owning region if a request to access a data table is satisfied by cross-memory services. When selecting a file, you should ensure that successful operation of your application does not depend on any activity performed at these user exits.
  • You should be aware of the security implications of sharing a data table, as described in Security checking for data tables.
  • If a file is frequently accessed from another region, or if it is accessed by many other regions, or if the accesses are predominantly read requests, the benefits of making it a data table can be very large. Remember that the performance gain for a remote file is greater than for a local file.
  • For a CICS-maintained data table, select files that have a reasonably high proportion of requests that only access the data table (see Application programming for data tables). From among those, select the files with the highest usage of these requests in order to maximize the performance gains.

    Information on file usage can be found in File control statistics in DFHSTUP reports. Not all read requests can take advantage of the data table, so you should check the data table information in the CICS statistics report afterward to verify that the data table is being used effectively. See Monitoring data tables for more information.

  • For a user-maintained data table, select files that have a large proportion of update activity but do not require the updates to be recovered across a CICS restart (see Data integrity).
  • Use performance measurements to estimate the approximate CPU savings, bearing in mind any forecasts for future usage.
  • Select one or two files with the best estimates. Give preference to a small file over a large file when the estimated savings are similar, because a small file will probably use less real storage.
  • Monitor your real storage consumption. If your system is already real-storage constrained, using a large data table could increase your page-in rates. This in turn could adversely affect CICS system performance. Use your normal performance tools, such as RMF™(Version 5), to look at real-storage usage and paging rates.
  • Consider reducing the number of buffers in the LSR pool because the use of data tables could reduce the number of times that the LSR pool is used.
  • You can use the user exit XDTRD to select the records included in the data table. In addition, for a user-maintained data table, you can use the user exit XDTRD to modify the records. You can thus optimize the use of virtual and real storage by storing in the data table only the data that you need.
  • A very large data table might require more data space storage than your usual region limit set by the MVS IEFUSI exit. In this case, you can either increase the limit by modifying the IEFUSI exit or use a CICS XDTRD global user exit program to suppress some records. The IEFUSI exit is described in the z/OS MVS Installation Exits manual (SA22-7593).


dfhf10a.html | Timestamp icon Last updated: Sunday, 4 June 2017