Activation Group

From MidrangeWiki
Revision as of 15:57, 2 October 2020 by David (talk | contribs) (Created page with "Activation groups use either single-level storage or teraspace for supplying storage for static program variables. For more information, see Teraspace and Single-Level Sto...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Activation groups use either single-level storage or teraspace for supplying storage for static program variables. For more information, see Teraspace and Single-Level Storage. When single-level storage is used, the static program variables and dynamic storage are assigned separate address spaces for each activation group, which provides some degree of program isolation and protection from accidental access. When teraspace is used, the static program variables and dynamic storage may be assigned separate address ranges within teraspace, which provides a lesser degree of program isolation and protection from accidental access.

The temporary data management resources include the following:

  • Open files (open data path or ODP)
  • Commitment definitions
  • Local SQL cursors
  • Remote SQL cursors
  • Hierarchical file system (HFS)
  • User interface manager
  • Query management instances
  • Open communications links
  • Common Programming Interface (CPI) communications


This article is a stub. You can help by editing it.