2.3. Data Management

In order to minimize memory requirements and enhance computational performance, the SAS4A/SASSYS-1 data management scheme maintains a framework for optional data storage. Accordingly, users have the ability to control data allocation for specific modules via the storage allocation record. These storage flags affect the creation of module-specific data structures that are utilized for management of dynamically allocated memory and common block data.

Flag IADEFC on the storage allocation record affects channel-specific data allocation for DEFORM-4, DEFORM-5, and FPIN2 data, meaning allocation of these data structures is necessary if any of these modules are to be utilized. Flag IAPLUC controls allocation of memory for data related to PINACLE, LEVITATE, or PLUTO2; similar to IADEFC, allocation using IAPLUC is necessary if any the related modules are utilized during a simulation. It should be noted that problems that initiate either PINACLE, LEVITATE, or PLUTO2 must have either DEFORM‑4 or DEFORM‑5 also running, but the DEFORM modules may operate without PINACLE, LEVITATE, or PLUTO2.

Two additional storage areas are allocated for the control system module (CNTLSYS) and the balance-of-plant module (BOP). These areas need not be allocated if the corresponding module is not to be executed. Allocation of the CNTLSYS storage is controlled with variable IACNTL on the storage allocation record, and the BOP module storage area allocation option is controlled with variable IALBOP in the same record.

If the optional SAS4A/SASSYS-1 interface to the DIF3D code is used, the DIF3D modules allocates two storage areas under the control of the BPOINTR package. These storage areas are used only on the DIF3D side of the interface.