Browse Prior Art Database

Office Global Control Block in ECSA

IP.com Disclosure Number: IPCOM000119551D
Original Publication Date: 1991-Feb-01
Included in the Prior Art Database: 2005-Apr-01
Document File: 1 page(s) / 40K

Publishing Venue

IBM

Related People

Cox, D: AUTHOR [+3]

Abstract

This article describes how to allow components in OfficeVision*/MVS (OV/MVS) to locate and gain access to global resources in the Office Environment. There is a need for a Global Office Control Block which is accessible and locatable by all Office components. This control block should be able to indicate the current status of the Office Environment. It should be able to provide the information needed to access Office Resources. This information should include the PC number needed to invoke Office Platform Components, such as Global Persistent Storage Mechanism (PSM), through Cross Memory Services. In addition, this control block should be flexible to adapt to the installation-specific configuration.

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

Office Global Control Block in ECSA

      This article describes how to allow components in
OfficeVision*/MVS (OV/MVS) to locate and gain access to global
resources in the Office Environment. There is a need for a Global
Office Control Block which is accessible and locatable by all Office
components. This control block should be able to indicate the current
status of the Office Environment.  It should be able to provide the
information needed to access Office Resources. This information
should include the PC number needed to invoke Office Platform
Components, such as Global Persistent Storage Mechanism (PSM),
through Cross Memory Services. In addition, this control block should
be flexible to adapt to the installation-specific configuration.

      The solution to the Global Office Control Block is to have it
created during Office environment initialization and place it in
Extended Common Storage Area (ECSA). ECSA is located in at the same
virtual address in every address space, so this means the control
block is available to every address space. The control block needs to
contain the essential information and anchors need for the Office
Platform.  A reasonable performance requires that all Office address
spaces must be able to quickly locate and address the global Office
Platform. As ECSA is a limited system resource, the control block
must be kept small with anchors to point to resources kept within the
extended private area of the Environment Facility (EF). The...