Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Execute Multiple Knowledge-Based System Products in an MSV Subsystem

IP.com Disclosure Number: IPCOM000114895D
Original Publication Date: 1995-Feb-01
Included in the Prior Art Database: 2005-Mar-30
Document File: 2 page(s) / 75K

Publishing Venue

IBM

Related People

Moh, CC: AUTHOR

Abstract

MVS subsystems are typically implemented to provide services for a single product, such as ESE, to execute in that address space and utilize cross memory services to communicate with its client address spaces. It is possible to generalize the required task initiation and management services provided by the subsystem to enable several Knowledge-Based System (KBS) products to coexist in one subsystem address space.

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

Execute Multiple Knowledge-Based System Products in an MSV Subsystem

      MVS subsystems are typically implemented to provide services
for a single product, such as ESE, to execute in that address space
and utilize cross memory services to communicate with its client
address spaces.  It is possible to generalize the required task
initiation and management services provided by the subsystem to
enable several Knowledge-Based System (KBS) products to coexist in
one subsystem address space.

Several changes may be required for the code to provide the multiple
product support:
  1.  Addition of a Subsystem Product Table and associated ISPF
       maintenance panels
  2.  Addition of Product Control Block data structure
  3.  Modification of the subsystem API
  4.  Modification of task management services
  5.  Modification of various other subsystem components

      A KBS subsystem may require a Subsystem Product Table during
startup to configure the address space for the desired products.  A
record for each product to be included in the address space exists in
the Subsystem Product Table.  Each product can be identified by a
unique eight character product code, which is used during subsystem
operation to direct commands to that product.

      The Product Control Block data structure is a null terminated
linked list of data areas in the subsystem address space.  During
initialization, one control block is allocated and formatted, based
upon information in the Subsystem Product Table, for each product.
These data structures contain a number of fields which describe the
operating characteristics of the product, such as how many subtasks
are allowed, etc.  Various components of the subsystem access this
data during subsystem operation.

      The subsystem API's INIT call, which makes a connection between
a client address space and t...