Showing papers in "Ibm Systems Journal in 1988"

An architecture for a business and information system

Abstract: The transaction-processing environment in which companies maintain their operational databases was the original target for computerization and is now well understood. On the other hand, access to company information on a large scale by an end user for reporting and data analysis is relatively new. Within IBM, the computerization of informational systems is progressing, driven by business needs and by the availability of improved tools for accessing the company data. It is now apparent that an architecture is needed to draw together the various strands of informational system activity within the company. IBM Europe, Middle East, and Africa (E/ME/A) has adopted an architecture called the E/ME/A Business Information System (EBIS) architecture as the strategic direction for informational systems. EBIS proposes an integrated warehouse of company data based firmly in the relational database environment. End-user access to this warehouse is simplified by a consistent set of tools provided by an end-user interface and supported by a business data directory that describes the information available in user terms. This paper describes the background and components of the architecture of EBIS.

IBM parallel FORTRAN

Abstract: IBM Parallel FORTRAN is a compiler and library for writing and executing parallel programs. It provides language extensions for explicitly programming in parallel, and it also provides compiler enhancements for automatically generating both parallel and vector code. Parallel FORTRAN offers a language for parallel programming that is independent of the machine configuration and the operating system. The combination of Parallel FORTRAN and IBM 3090 multiprocessors can provide a significant reduction in turnaround time for applications.

Introduction to systems application architecture

Abstract: Systems Application Architecture is a framework in which applications are developed so that they run consis-tently on major IBM computing systems. This paper presents the motivation and requirements for this framework and describes the main elements of its structure. It also discusses the effect on current processing technologies and on application development.

Common user access—a consistent and usable human-computer interface for the SAA environments

Abstract: Systems Application Architecture (SAA) will allow customers to apply their investments in their computer operations across IBM's three major computing environments that exhibit unique characteristics in terms of architecture, workstations, operating systems, and system services. User experience is one of these investments. The Common User Access (CUA) establishes a degree of standardization that is compatible with the differences in the three environments and that supports transfer of users' experiences. CUA is based on a user-interface architecture that identifies fundamental elements of structure. The intent is to provide a transfer of users' conceptual-level learning across different and evolving technologies. CUA specifies user-interface components and guidelines to be used by application designers, and it provides a basis for programming development tool specifications.

OS/2 EE database manager overview and technical highlights

Abstract: Structured Query Language (SQL) has become an industry standard. It is supported by mainframe products. This paper describes the OS/2 EE Database Manager, which is based on the relational database model of E. F. Codd and on the SQL query language. A functional overview of the OS/2 EE Database Manager and OS/2 EE is provided; technology applied to different areas is highlighted.

SNA network management directions

Abstract: Network management is the process of monitoring and controlling the components of a communication-oriented network of information systems in the areas of configuration management, operational control, problem management, change management, and performance and accounting management. This paper discusses the evolution of the SNA network management architecture and products that implement that architecture, and describes their likely future direction.

Distributed files for SAA

Abstract: Files are still a major way of storing data in computer systems, and they are a significant part of the information to be handled by the distributed processing networks that are developing. Systems Application Architecture is supporting distributed files. In this paper, the goals, benefits, and problems of providing this support are discussed, along with the role of Distributed Data Management architecture.

ICAP/3090: parallel processing for large-scale scientific and engineering problems

Abstract: Described is the lCAP/3090 (for loosely coupled array of processors) parallel processing system. General parallel processing performance issues that determine the success of all multiple-instruction/multiple-data-stream parallel computing systems are examined in the context of large-scale scientific and engineering problems. Experiments with previous lCAP parallel pro-cessing systems that have made possible the present design of lCAP/3090 are also described.

Distributed databases for SAA

Abstract: This paper describes, in general terms, distributed database and its relationship to Systems Application Architecture (SAA). It shows the importance to effective distribution of IBM's Structured Query Language (SQL), the database element of the Systems Application Architecture Common Programming Interface (SAA CPI). The paper defines five levels of distribution, showing how each fits real-world application requirements. Finally, it outlines the magnitude of the task.

VGA—design choices for a new video subsystem

Abstract: The VGA (Video Graphics Array) video subsystem is provided as standard on the system boards of the IBM Personal System/2® Models 50 and above. VGA was designed to meet the objectives set for these new systems and to support compatibility with older IBM offerings, while at the same time providing greater performance and increased function. The IBM Enhanced Graphics Adapter (EGA) was chosen as the compatibility base for VGA, since EGA had become the video standard for IBM-compatible computer systems. Six new modes of operation were designed to meet the needs of new business and consumer applications and to improve the ergonomics of the systems. Higher-performance video presents several design problems, including electromagnetic interference, physical design size, and cost. These design problems were contained by implementing the VGA function in a single-gate array and by using an analog display interface. The use of a video digital-to-analog converter (DAC) allows the VGA subsystem to show any color from a choice of 256K colors when a color display is used, or 64 gray shades when a monochrome display is used. The VGA subsystem was designed to provide a uniform interface for color and monochrome that allows a color mode to be selected when a monochrome display is used, or a monochrome mode to be used on a color display. A color-summing algorithm was designed and implemented in the BIOS (Basic Input/Output System) software that will allow colors to be shown as shades of gray on the monochrome display.

Common communications support in systems application architecture

Abstract: Application execution in a Systems Application Architecture (SAA) network depends on the underlying capability of the network to obtain reliable connectivity and orderly data exchange among its system components. The objectives of SAA are distributed applications, distributed processing, and distributed data, which are achieved through interconnected SAA systems supporting appropriate interfaces and architectures. The Common Communications Support of SAA affords this capability by utilizing a number of Systems Network Architecture communication architectures and international standards. These architectures provide useful data interchange within SAA components by providing services ranging from managing data links to specifying data streams for user applications. This paper discusses the role of Common Communications Support and the means for SAA users to access this support, and provides an overview of the functions and roles of various component architectures of Common Communications Support, along with their interrelationships.

SAA distributed processing

Abstract: Discussed are motivations for distributed versus centralized data processing, the relative advantages of each, and the trade-offs involved as they relate to Systems Application Architecture (SAA). Presented is a taxonomy of the various approaches to designing applications to operate in a distributed manner. SAA support for these modes is described. The management of an enterprise-wide network of systems is discussed.

Architectures of advanced function printing

Abstract: Discussed is the use of the capabilities of all-points-addressable laser (page) printers in applications involving pages composed of text, image, and vector data in a device-independent way. Also presented is the ability to describe and print complex documents composed of multiples of such pages. Provision is made for the migration of current line-printer applications to print using these new page printers. Three architectures are described that—along with an Advanced Function Printing (AFP) model—support these capabilities. Each of these architectures is described in the context of the current implementation of the Advanced Function Printing software.

The design of Operating System/2

Abstract: The design of Operating System/2™ (OS/2™) is a result of matching the requirements of IBM and its customers for a new operating system for various models of the Personal System/2® with the need for continuity with a very large body of established DOS applications. The design of OS/2 represented a significant challenge both in meeting these requirements and in making efficient use of the hardware. In this paper, the design characteristics of OS/2 are discussed.

Enabling the user interface

Abstract: Presenting a consistent interface to the user is one of the objectives of Systems Application Architecture (SAA). The development of SAA applications is simplified by providing enabling interfaces which help an application developer support the SAA user interface. Rather than providing a single-level en-abling interface, SAA offers a spectrum of levels spread over two interfaces: the SAA Presentation Interface and the SAA Dialog Interface. This gives the application developer the freedom to choose the appropriate level of interface for the application.

Seismic computations on the IBM 3090 vector multiprocessor

Abstract: Computerized seismic prospecting is an echo-ranging technique usually targeted at accurate mapping of oil and gas reservoirs. In seismic surveys an impulsive source, often an explosive charge, located at the earths surface generates elastic waves which propagate in the subsurface; these waves are scattered by the earths geological discontinuities back to the surface, where an array of receivers registers the reflected signals. The data recorded are then processed in a complex sequence of steps. Among them, seismic migration and stacking velocity estimation represent two characteristic components of the process solving the inverse problem of recovering the structure and the physical parameters of the earths geologic layers from echo measurements. A complementary tool in relating seismic data to the earth's inhomogeneities is provided by seismic numerical models, which assume a subsurface structure and compute the seismic data which would be collected in a field survey, by solving the direct problem of exploration geophysics. This paper describes a vectorized and parallelized implementation of a two-dimensional seismic elastic model on the IBM 3090 VF Vector Multiprocessor. An implementation of a parallel seismic migration algorithm is then described. The paper also reports performance data for a vector/parallel implementation on the IBM 3090 of some typical seismic velocity estimation algorithms. The three problems chosen are representative of a wide class of geophysical computations, and the results summarized in this paper show their suitability for efficient implementation on the IBM 3090 Vector Multiprocessor; combined vector/parallel speedups in the range 15–25 are in fact observed.

Engineering and scientific subroutine library for the IBM 3090 vector facility

Abstract: The Engineering and Scientific Subroutine Library (ESSL) provides FORTRAN, Assembler, and APL2 application programmers with a high-performance set of mathematical subroutines which take advantage of the performance gains offered by the IBM 3090 Vector Facility. This paper describes the contents of ESSL and presents some of the techniques that were used to develop high-performance vector subroutines. Other key design considerations such as accuracy, ease of use, and error handling are also discussed. This information should be useful to anyone developing programs for the IBM 3090 Vector Facility.

Program locality of vectorized applications running on the IBM 3090 with vector facility

Abstract: An instruction-level simulator is used to study the program locality of large scientific applications. The simulator, which models an IBM 3090 processor with Vector Facility and a cache, was developed to help a programmer improve the performance of an application through better understanding and use of the Vector Facility and the memory hierarchy of the IBM 3090 system. Our main observations on a set of scientific applications are as follows: (1) although the applications have different characteristics of memory accesses and vectorization , their program locality is high enough to take advantage of conventional cache structures; (2) the cache hit ratio of the vector execution can be quite different from (but not significantly lower than) that of the scalar execution of the same application; and (3) the application programs that are written to optimize the use of the memory hierarchy in the system generally result in higher cache hit ratios than the others. The cache performance of these applications with respect to various cache parameters is also presented. In particular, our study finds that the cache structure of the IBM 3090 is well suited for large scientific applications.

Programming style on the IBM 3090 vector facility considering both performance ad flexibility

Abstract: To obtain high performance from the IBM 3090 Vector Facility, we must investigate vector instruction constructs in terms of the loop context of the application algorithm. We exemplify the method by linear algebra subroutines for basic matrix operations and a linear equation solver. In these examples, we clarify the mathematical meaning that each loop is computed by analyzing the loops in terms of a generic algorithm. This analysis helps us to achieve optimal loop selection. We then obtain additional performance gain by considering cache capacity. These procedures suggest that there are three levels of performance classification. They also show that program structure yields great benefits in terms of performance and generality of the program.

Integrating applications with SAA

Abstract: Advances in computing technology and reductions in development cost have greatly increased the number of people who use computers, and have expanded the number and types of applications available to them. People want their applications to share data and to be consistent with one another with respect to terminology and appearance. They also frequently need access to applications and data on computers in other locations; the computers may be models and types that these persons do not normally use. Integrating application functions in a seamless environment is an important step toward satisfying some of these requirements. This paper discusses what integrated applications are, why they are valuable, and how Systems Application Architecture (SAA) can make it easier to develop them.

Application enabling in SAA

Abstract: The Common Programming Interface (CPI), one of the four key elements of Systems Application Architecture, comprises a growing set of programming languages and services. The CPI indirectly offers end-user access through the Common User Access by providing the application developer with the necessary interfaces. The CPI addresses the application development requirement for portability of applications and programmer skills. As the CPI continues to expand, it addresses the requirements for access to host data through intelligent workstations and for transparent access to remote data and applications.

Writing an operating system/2 application

Abstract: This paper illustrates use of the key facilities of Operating System/2™ (OS/2™). It provides some guidance on how to use the interfaces and functions implemented by the system and then introduces the program development environment. Two examples demonstrate the use of some of the more interesting capabilities. The paper discusses many of the significant differences between the functions of OS/2 and those of the Disk Operating System (DOS).

Understanding device drivers in operating system/2

Abstract: To meet its design goals for multitasking, Operating System/2™ requires a device driver architecture for interrupt-driven device management. A device driver in OS/2™ is affected by the new architecture both in its structure and in its relationship to the system. An OS/2 device driver contains components, such as the Strategy Routine and Hardware Interrupt Handler, which have well-defined responsibilities. The basic form of these components is a FAR CALL/FAR RETURN model. The operating system calls the device driver components to handle certain types of events, such as an application I/O request or a device interrupt. In responding to these events, an OS/2 device driver must cooperate with the operating system to preserve system responsiveness by helping to manage the multitasking of concurrent activities. Since OS/2 uses both the real mode and the protected mode of the system processor to support DOS and OS/2 applications, respectively, the components of an OS/2 device driver must execute in both modes. In this manner, an OS/2 device driver can be viewed as an installable extension of the Operating System/2 kernel. Comparisons between IBM Personal Computer DOS and Operating System/2 are drawn to illustrate differences between device management and device driver architecture.

An introduction to typographic fonts and digital font resources

Abstract: Type has evolved from blocks of wood or metal bearing the raised character shape to the many and varied digitized representations of the character that are available through computer system technology. Typography is the art or technique of composing printed material from type. The evolution of digital type into the computers of today has opened the door of typography to people who have had little or no previous knowledge of the subject. It has also introduced a higher level of complexity to document composition and presentation service software than was previously required. Discussed in this paper are the art of composing printed material, the selection of an appropriate type design for a given application, the information required to create and manage a digital font resource, and the computer system's use of digital font resources to produce typographic-quality documents. These matters are examined in a way that introduces the reader to typographic fonts, the additional complexities involved, and the need for consistency in the definition and application of digital font resources.

Advanced function printing: a tutorial

Abstract: Advanced Function Printing (AFP) is an IBM product for printing mixed text, image, and graphics in a system-printing environment. Described is the AFP printing model. We demonstrate the way in which this model is used for existing printing applications, enhanced line printing, and full advanced-function printing.

Designing SAA applications and user interfaces

Abstract: This paper describes a framework for developing applications that conform to Systems Application Architecture (SAA). The paper shows a high-level approach to creating a design; it gives examples of early modeling work with the user interface; and it appraises SAA through the eyes of several system designers. The usability of user interfaces has been evaluated through the modeling of office tasks. That experience is described, showing the influence of the SAA Common User Access (CUA) on the model and the influence of the model on CUA. Discussed is a design for distributed applications that fit within the SAA framework and the influence of SAA on the design of integrated distributed applications.

The Cross System Product application generator: an evolution

Abstract: An application generator is a generalized application development tool with which professional programmers develop applications using a fourth-generation language. This paper describes the requirements that led to the Cross System Product application generator, and how the product progressed from a single-environment product to the current multienvironment product. Also described are how the Cross System Product fits within Systems Application Architecture and how that may affect the future of the Cross System Product.

OS/2 query manager overview and prompted interface

Abstract: Operating System/2™ (OS/2™) Query Manager provides a user interface for both novice and sophisticated database users of the OS/2 Database Services. It offers defaults and standard options for the novice user. Prompting provides access to the database without requiring extensive knowledge of Structured Query Language (SQL), yet it also allows the advanced user to completely customize screens and reports. Direct keying of SQL statements is allowed as a fast path for the knowledgeable SQL user. Functions of OS/2 Query Manager are described, including details of the user interface.