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

Control of Development of an Application System

IP.com Disclosure Number: IPCOM000038495D
Original Publication Date: 1987-Jan-01
Included in the Prior Art Database: 2005-Jan-31
Document File: 1 page(s) / 11K

Publishing Venue

IBM

Related People

Velez, C: AUTHOR

Abstract

An Information Development System Application Development Facility (IMSADF) groups fields and drivers into a system. However, only load modules have been grouped in this way and the source information that builds the load modules has not been organized as a system. To manage and control source information, it is converted to Interactive System Productivity Facility (ISPF) tables and stored under a common system definition. This allows a program developer to easily migrate the complete source system to other environments if the need arises. This organization also allows the program developer to obtain at any moment lists of all the elements for a given category, e.g., segments, and to update any particular element if so desired.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 100% of the total text.

Page 1 of 1

Control of Development of an Application System

An Information Development System Application Development Facility (IMSADF) groups fields and drivers into a system. However, only load modules have been grouped in this way and the source information that builds the load modules has not been organized as a system. To manage and control source information, it is converted to Interactive System Productivity Facility (ISPF) tables and stored under a common system definition. This allows a program developer to easily migrate the complete source system to other environments if the need arises. This organization also allows the program developer to obtain at any moment lists of all the elements for a given category, e.g., segments, and to update any particular element if so desired. Libraries containing the source and load modules are also organized in this way, thereby providing a better way of moving source and load modules from test to production. This organization allows the specification of types of users with different types of access to a particular system, e.g., read-only users, update users and delete users. This classification allows a better change control of all the elements of that system.

1