| Home : Databases : IMS |
| Click "Subscribe" if you want to be notified of new or updated links in this category. | Subscribe |
|
|
IMS Listings
|
|
Total:
3 | Displaying: 1 - 3 |
|
|
|
This article provides a high-level overview of IMS database concepts, terminology, and database design considerations. It covers the following topics:
Overview
Hierarchical versus Relational Databases
Design Considerations
Updated: 05/24/2006
|
|
|
IMS is a large application that runs on z/OS. There is a symbiotic relationship between IMS and z/OS. Both are tailored to provide the most efficient use of the hardware and software components.
IMS runs as a z/OS subsystem and uses several address spaces: one controlling address space, several separate address spaces that provide IMS services, and several address spaces that run IMS application programs. z/OS address spaces are sometimes called regions,1 as in the IMS control region. The term region is synonymous with a z/OS address space.
The various components of an IMS system are explained in more detail in “Structure of IMS Subsystems.”
Updated: 05/24/2006
|
|
|
The IMS system definition process:
+ Describes the IMS resources to IMS:
* At installation time
* When maintenance is applied
* When standard application definition changes are required
+ Assumes a working knowledge of the z/OS system modification program/extended (SMP/E). SMP/E is required for installation and is used as part of the IMS system definition process.
+ Is evolving to be more dynamic (versus static) over time.
Updated: 05/24/2006
|
|
