Browse Prior Art Database

Local PSM in MVS

IP.com Disclosure Number: IPCOM000102494D
Original Publication Date: 1990-Nov-01
Included in the Prior Art Database: 2005-Mar-17
Document File: 1 page(s) / 38K

Publishing Venue

IBM

Related People

Cox, D: AUTHOR [+3]

Abstract

This article describes the ability to support Local Persistent Storage Mechanism (PSM) in MVS within the same address space. Persistent Storage Mechanism is a memory management system for transaction programs. In OfficeVision/2 (OV/2) threads within the same process can share data though Local PSM. This enables a process to keep data intact across the creation and destruction of threads within the process. Persistent Storage also allows data to be kept by key rather than by address pointer. This capability is needed within OfficeVision/MVS to enable code from OV/2 to be ported to MVS.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 87% of the total text.

Local PSM in MVS

       This article describes the ability to support Local
Persistent Storage Mechanism (PSM) in MVS within the same address
space. Persistent Storage Mechanism is a memory management system for
transaction programs.  In OfficeVision/2 (OV/2) threads within the
same process can share data though Local PSM. This enables a process
to keep data intact across the creation and destruction of threads
within the process. Persistent Storage also allows data to be kept by
key rather than by address pointer. This capability is needed within
OfficeVision/MVS to enable code from OV/2 to be ported to MVS.

      The solution is to provide a Local Persistent Storage Mechanism
for an address space in MVS.  The Local PSM structure duplicates the
structure used by OV/2. The key concept which has to be recreated
within MVS is that in OS/2* there are named shared segments of
memory. OV/2 assigns a name to the segment which is the local PSM
area. The method to accomplish this in MVS is to anchor the local PSM
within a address space control block.  The ASXB or Address Space
Auxiliary Block is used to anchor the local PSM. As every task within
the address space can locate and access the ASXB, every task can now
locate and access the Local PSM.

      The advantage to this solution is that local memory management
is done for OfficeVision the same way in OS/2 and MVS. Memory can be
allocated by OV applications without regard to the environment. In
addition, the enh...