Allocation of real storage when using transaction isolation

When transaction isolation is active, there is a cost in terms of real storage. If insufficient real storage is allocated, paging problems can result, which then affect performance. The cost depends on the number of subspaces in use in the system, and the size of the EDSALIM parameter.

Because the page size of the EUDSA is 1 MB, the value of EDSALIM is likely to be very large for a CICS® system that has transaction isolation active. This virtual storage needs to be mapped with page and segment tables using real storage, so an increase in the real storage usage can occur. In addition to the real storage used to map the virtual storage for the EDSALIM value, subspaces also require real storage. For example:
  • Each subspace requires 2.5 pages, where a page means a 4 KB page of real storage.
  • Assuming that each transaction in the system requires a unique subspace, (transaction definition TASKDATAKEY(USER) and ISOLATE(YES)), real storage required is the MXT value x 2.5 pages.
  • If each transaction in the system requires a page of storage in the EUDSA (1 MB page), a page table is required to map the storage. Real storage is the MXT value x 1 page.
  • A further three pages are required, so the total of real storage is the MXT value x (1 + 2.5 pages) + 3 pages.
  • All of this real storage is allocated from the ELSQA.

The figures for the real storage usage is in addition to that required for a CICS system that does not have transaction isolation active. The CICS requirement for real storage varies depending on the transaction load at any one time. As a guideline, each task in the system requires 9 KB of real storage. Multiply this number by the number of concurrent tasks that can be in the system at any one time (governed by the MXT system initialization parameter).



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