MBM 303

INTRODUCTION

MIS

A management information system (MIS) is a system that provides information needed to

manage organizations efficiently and effectively. Management information systems involve

three primary resources: technology, information, and people. It's important to recognize that

while all three resources are key components when studying management information

systems, the most important resource is people. Management information systems are

regarded as a subset of the overall internal controls procedures in a business, which cover the

application of people, documents, technologies, and procedures used by management

accountants to solve business problems such as costing a product, service or a business-wide

strategy. Management information systems are distinct from regular information systems in

that they are used to analyze other information systems applied in operational activities in the

organization. Academically, the term is commonly used to refer to the group of information

management methods tied to the automation or support of human decision making,

e.g. decision support systems, expert systems, and executive information systems.

“Management Information Systems (MIS) is the term given to the discipline focused on the integration of computer systems with the aims and objectives on an organisation.”

Application of MIS

MIS systems can be used to transform data into information useful for decision

making.

MIS systems provide a valuable function in that they can collate into coherent reports

unmanageable volumes of data that would otherwise be broadly useless to decision makers.

MIS systems can also use these raw data to run simulations – hypothetical scenarios

that answer a range of ‘what if’ questions regarding alterations in strategy.

Not only do MIS systems allow for the collation of vast amounts of business data, but

they also provide a valuable time saving benefit to the workforce.

GENERAL MANAGEMENT INFORMATION SYSTEM

HISTORY AND PURPOSE OF GMIS

GMIS is being developed at the M.I.T. Energy Laboratory in conjunction with the Sloan School's Center for Information Systems Research and IBM,The project started in 1973 based on ongoing research in the Sloan School on file systems [Madnick, 1970] and operating systems [Donovan, 1972; Madnick and Donovan, 1974]. However, it has been the urgency of particular applications to energy problems that has shaped the work and quickened its pace.Essentially, the need is for a software facility suitable for situations where the problem addressed is constantly changing, or where an information system is in its formulative stages and users are unable to specify exactly what they want the system to do, or precisely what the data streams will look like in the future.

CHARACTERISTICS OF GENERAL MANAGEMENT INFORMATION SYSYTEM

It needs to be multi-user and interactive; It should be capable of storing, validating, and retrieving data; and It ought to have the capability to respond to changing data and data structure, and to

varying protection requirements. It should provide tools for constructing analytical and statistical models to be applied

to the data.

Many economists and modelers have strong preferences for particular modeling facilities such as TROLL [NBER, 1973], XSIM [Dynamics Association, 1974], TSP [Hall, 1975], PL/I, EPLAN [Schober, 1974], and FORTRAN; large investments have been made in packages using these languages, and access to these facilities can save tremendous costs in retraining personnel and converting existing models. The modeling and analytical capabilities introduce several additional features. Since GMIS provides access to such faciliites as APL, PL/I, TSP, EPLAN, and FORTRAN, it provides the user with an efficient flexible environment to specify, construct, and execute statistical analyses and model studies, and to produce the associated plots and reports.

General management information systems--which directly support global business strategies-are used to:

coordinate operations via enterprise resource planning (ERP) packages service customers via customer relationship management (CRM) systems support global product design, sourcing, production, and distribution through the

supply chain management (SCM) systems create centers of core competency (computer chips may be designed in California,

manufactured in China, and sold worldwide)

create flexible manufacturing operations (the ability to move production between facilities)

share resources (petroleum companies share tankers) reduce risks associated with currency conversions (investment bankers can trade in

several global markets, 24 hours a day).

GENERALIZED INFORMATION SYSTEM MODEL

Information theory only considered the reliability during the communication process but not the reliability of the information of information source itself, it also pointed out that most information are unreliable. Analyzed the inadequate definition of information theory and proposed the definition of information based on the reliability. In view of the strong similarity between the communication system and the realistic information system, we construct a generalized information system to approximate the realistic information system. Although Shannon’s information considered the reliability and completeness, for example, the posterior probability is a probability under more conditions and it is more complete than the prior probability. We can realize more reliability of communication with error correction encoding, but it is not a consideration with enough consciousness and it does not emphasize the reliability and it does not come down to the reliability of the information of information source.

Figure 1. Generalized Information System

In the generalized information system, the information source and the information sink and the communication channel are all generalized, and these concepts are more generalized than the corresponding concepts in Shannon’s information theory. The things (e.g. objects, facts and so on) needed to be known can be treated as the information sources, and any things which can be used to transmit information can be treated as the communication channels. The information sinks are the things used to receive, apperceive and analyze information,

including the sense organs of people and the objects. The sequence that the information sink processes information is as following: Each information sink (including the relay information sink) will use error correction encoding technology to process the information from single information source to enhance the reliability in the communication and decrease the interferences in the channels, and then it needs to fuse the information from multiple information sources to enhance the reliability and completeness of the information. Each information sink can estimate the reliability of the information from each information source according to various kinds of information and the sources of the information of the information sources, and the information sink can use the information from all the information sources according to the reliability of various information sources. The fusion process is similar to the error correction encoding and checking of the information with redundancy, but it is more complicated than the error correction encoding. Using this method we can enhance the reliability of information and finally obtain the most or more reliable information.

THEORATICAL FRAMEWORK

Neo-institutional theory has its focus on how values, norms and modes of rationality influence the way organized action unfolds (Scott 1992). One of its distinctive features is that it calls attention to cultural and normative frameworks in an organization’s environments and its formal governance structures. Organizational structures are argued to have importance apart from, and regardless of, their impact on participant behaviour. The structures are viewed as signalling internal purposefulness and rationality, but also—especially to external audiences—demonstrating the organization’s connection to and congruence with wider belief and rule systems (Scott 1995). Within a neo-institutional perspective, formal organizational means such as MIS are considered rationalized myths. Rationalized myths are impersonal (collectively defined), taken-for-granted notions about what is ‘rational’ relative to given (institutionalised) ends. They tend to persist over time because they are so deeply rooted in institutional environments, professions, programs and technology (Meyer and Rowan 1991 p. 41). In organizational fields that undergo changes and reform efforts, there will be conflicting and competing rationalities, and complex and conflicting environments. Heterogeneous functions, tasks, professions, client groups, and organizational cultures are key features of public health care services at the local governmental level in Norway. The heterogeneity is reflected in different organizational principles that are in simultaneous action. This combination makes it possible to strike a fragile balance between differing interests and values, but at the same time it creates dilemmas and contradictions between democratic, administrative and professional rationalities. Institutional values, such as the right to participate in critical decision-making (a democratic logic), must compete with the necessity to manage and control the organization (an administrative logic), and the professionals’ claim for autonomy within their domain (a professional logic). The key to holding this together is the client. On a general level, they represent a shared legitimising base for all actors in the field, but this does not mean that there is agreement about how to deliver care to the client. When the actors express their opinions more concretely, they reflect the values and interests that prevail in their own domain. Accordingly, human judgment is an important element. This judgment gives rise to difficult discussions and negotiations about how to prioritise and what criteria to use. It is a complex mixture of professional, administrative and political judgments. According to Barley and Tolbert (1997), neo-institutional theory— although concerned with the dynamic relation between action and structure— has, to a large extent, ignored the processes, by which structures emerge from, or influence, action. I agree with these considerations and argue that by focusing on how structures emerge within an organizational

practice, we gain insight about how decoupling may or may not occur as a contingent process. In that respect, we intend to combine actor-network theory with neo-institutional theory.

IBM System/370

The IBM System/370 (S/370) was a model range of IBM mainframes announced on June 30, 1970 as the successors to the System/360 family. A new computer system - - the IBM System/370 was announced worldwide today by International Business Machines Corporation. Its two models use advanced design techniques previously available only in IBM's ultra-high-performance computers. They can use nearly all existing IBM peripheral devices, as well as a new 2,000-line-per-minute printer and 800 million character-capacity disk storage. The printer and disk storage units included in today's announcement are designed to step up input and output capabilities to System/370's high internal operating speed. Both models of System/370 are now in production -Model 155 at Poughkeepsie, N.Y., and Montpelier, France; Model 165 at Kingston, N.Y. Model 155 is being demonstrated today in Poughkeepsie.

The series maintained backward compatibility with the S/360, allowing an easy migration path for customers; this, plus improved performance, were the dominant themes of the product announcement. Improvements over the S/360 first released in the S/370 model range included:

standard dual-processor capability; "monolithic main memory" based on integrated circuits instead of magnetic cores, full support for virtual memory through a new microcode floppy disk on the 370/14 and a

hardware upgrade to include a DAT box on the 370/155 and 370/165; these were not announced until 1972;

128-bit floating point arithmetic on all models

FEATURES OF IBM/370 SYSTEM

It provides a natural evolution for the users of the predecessor product STAIRS It helps the customer to create, store, retrieve, display, process, and distribute

documents that contain text as well as references to graphics and images It provides Boolean and context operators for full-text search Ease-of-use through extended wildcard search capability (front, end, and middle

masking) It also enables customers to use full-text retrieval in their applications via an

application programming interface (API) It provides a graphical retrieval interface for OS/2 and Windows workstations acting

as a client to the MVS or VM server It offers a business solution for customers who need text retrieval integrated into their

business applications. It is an ideal product in the following areas of business: Office System Support, Customer Services, Research and Development, Human Resources, Legal, Library, Planning and Documentation Center.

IBM Search Manager/370 Migration Component as part of IBM Search Manager/370 provides the IBM Storage and Information Retrieval System (STAIRS) end-user interface. It can be run in parallel to IBM Search Manager/370 both accessing the same index, and contains all utilities necessary to migrate from an existing IBM Storage And Information Retrieval System (STAIRS) application to IBM Search Manager/370 at any suitable time.

The source code of IBM Search Manager/370 Migration Component will be available to ease migration and allow for the transition from source code to object code for those customers who have changed STAIRS/VS (5740-XR1) or STAIRS/CMS (5664-189) source code.

A new feature is added to Search Manager/370 Release 3. This feature provides the capability to access Search Manager/370 from a Web browser via the World Wide Web (WWW), to perform the simple attribute search queries and browse their results. This feature is only available in the English language.

MIS MODEL

CICS Transaction Server for VSE/ESA is a new release of CICS for the VSE/ESA environment that protects your investment and delivers significant benefits to enable you to grow and extend your applications. It includes CICS Web Support, REXX for CICS, CICS Universal Client, and CICS Transaction Gateway function in a single product at a single price that offers:

Integration of business with new world of electronic commerce via the intranet Flexible entry point into network computing and e-business, with a scalable and

reliable growth path Support for all models of Client/Server computing Comprehensive client support for IBM and non-IBM platforms A coexistence environment to aid migration from CICS/VSE V2R3

A Web browser is an HTTP client. The Web browser constructs an HTTP request, which is passed across the network to TCP/IP for VSE/ESA in the server. TCP/IP for VSE/ESA relays the request to the CICS Web Interface, which calls a CICS program to service the request. The output from the CICS program is sent back to the Web browser in an HTTP response. The CICS Web Support can be used to allow Web browsers to use:

Existing CICS programs and the transaction processing services they provide Newly-created CICS programs that exploit the facilities of HTTP and the hypertext

markup language (HTML)

The HTTP request is subject to the limitations of the remote procedure call model of distributed computing because:

It is not possible to coordinate changes to recoverable resources in successive requests to the same CICS system

Committing changes to recoverable resources is under the control of the CICS system, not the Web browser

The called program executes under a CICS transaction that has no principal facility. That means that certain application programming interface commands cannot be used. These include:

Terminal control commands that refer to the principal facility Options of EXEC CICS ASSIGN that return terminal attributes BMS commands Signon and signoff commands

In addition, the CICS Web Support, in conjunction with the 3270 Bridge, can be used to provide Web browser access to existing 3270-based transactions without requiring any application changes.

OVERVIEW OF THE SYSTEM ARCHITECTURE

Currently GMIS is implemented on an IBM System/370 computer. It uses the Virtual Machine (VM) concept extensively.1 A virtual machine may be defined as a replica of a real computer system simulated by a combination of a Virtual Machine Monitor (VMM) software program and appropriate hardware support. For example, the VM/370 system enables a single IBM System/370 to appear functionally as though it were multiple independent System/370 (i.e., multiple "virtual machines"). Thus, a VMM can make one computer system function as though it were multiple, physically isolated systems.A configuration of virtual machines used in GMIS is depicted in Figure 1, where each box denotes a separate virtual machine. Those virtual machines across the top of the figure are executing programs that provide user interfaces, whether they are analytical facilities, existing models, or data base systems. All these programs can access data managed by the general data management facility running on the virtual machine depicted in the center of the page. A sample use of this architecture might proceed as follows. A user activates a model, say in the APL/EPLAN machine. That model requests data from the general data base machine (called the Transaction Virtual Machine, or TVM), which responds by passing back the requested data. Note that all the analytical facilities and data base facilities may be incompatible with each other, in that they may run under different operating systems. The communications facility between virtual machines in GMIS. Existing commercial data base systems -- e.g., IMS [IBM, 1968], DBTG [Association for Computing Machinery, 1971], System 2000 [MRI Systems, 1974], TOTAL [Cincom Systems, Inc., 1974] etc. -- have proved their usefulness in particular applications. But none has the range of desired characteristics outlined above. Some are lacking the statistical and modeling packages, not all are interactive, and not all can allow multiple users to access the same data base. Most important, none was designed for a changing environment; the GMIS system has taken a long step in this direction. Using this facility, it is possible to construct an information system in a matter of days.

VM 2 VM 3 VM 4 VM 5 …………. VM (n)

VM 1

GMIS software has been designed using a hierarchical approach [Madnick, 1975, 1970; Dijkstra, 1968; Gutentag, 1975]. Several levels of software exist, where each level only calls the levels below it. Each higher level contains increasingly more general functions and requires less user; sophistication for use. The transaction virtual machine depicted in Figure above shows only two of these levels, the Multi-User Interface and SEQUEL [Chamberlain, 1974]. The data base capabilities of this machine are based on the relational view of data [Codd, 1970). In this section, each box will be briefly described.

2.1 Structured English Query Language (SEQUEL)

In the current version of GMIS the data management capability is based on an experimental relational query and data definition language known as SEQUEL which has been developed at the IBM San Jose Research Laboratory [Chamberlain, 1974].In cooperation with the IBM Cambridge Scientific Center and the IBM Research Laboratory at San Jose, by increasing the allowable lengths of identifiers and character strings. It also designed mechanisms for security and for handling missing data, expanded the bulk loading facilities, added additional syntax, and made several changes to improve performance.

AnalyticalVirtualMachines

CUSTOMIZE

INTERFACE

WRITTEN IN PL/I

TSP

INTERFACE

TRANSACT INTERFACE

APL/EPLAN

INTERFACE

HIGH LEVELLANGUAGEINTERFACE,e.g., PL/I,FORTRAN

TransactionVirtualMachine

MULTI-USERINTERFACE………………......

RELATIONALDATAMANAGEMENTLANGUAGESEQUEL

2.2 Multi-User Transaction Interface

Two requirements of GMIS are that multiple users be able to access the same data base and that different analytical and modeling facilities be able to access the data base all at the same time. For example, one user may want to build an econometric model using TSP while another user will request the system to generate a standard report. Still a third user may want to query the data base from an APL [Iverson, 1962; Pakin, 19723 environment. These requirements have been met with the design and implementation of the Multi-User Transaction Interface [Gutentag, 1975]. Each GMIS user operates in his own virtual machine with a copy of the user interface he requires. Each user transaction to the data base is written into a transaction file, and that user's request for processing is sent to the data base machine (Transaction Virtual Machine) as indicated in Figure 1. The Multi-User Interface processes each request in a first-in/ first-out (FIFO) order, by reading the selected user's transaction file, and writing the results to a reply file that belongs to the user. Each user interface reads the reply file as if the reply had been passed directly from the data base management system.

2.3 User Interfaces

GMIS provides the capability for users to write their own interfaces to communicate with the data base system. TRANSACT is a general user interface that is designed to process transactions from most teletypewriters and CRT terminals. It allows the user to direct transaction output to any virtual device on the VM/370.Interfaces to APL, TSP, EPLAN and PL/I are operational and enable users to communicate with the Transaction Virtual Machine simultaneously with all other users. An interface to the TROLL econometric modeling facility is in the design stage.The architecture depicted in Figure 1 also allows the use of any of these modeling or analytical facilities independent of the transaction virtual machine. For example, functions may be written in APL to operate on data stored in the APL's work space. TSP modeling and reporting capabilities can operate on data stored in TSP's data base. FORTRAN or PL/I can operate on data stored in the virtual machine that they are running. It should be noted, however, that not using the general data base facility seriously inhibits flexibility and makes the algorithms dependent on the physical organization of the data but more importantly inhibits the community of users as they cannot conveniently access the common data base.

3. SAMPLE APPLICATION OF GMIS

To demonstrate the characteristics of the existing GMIS System. The object of this particular indicator was to give a picture of future trends in gasoline consumption.It was proposed that the indicator be depicted as a series or plot of the average miles per gallon of each month's new car sales. Policymakers could note if the average fuel efficiency of new cars was going down or up, hence reducing or increasing future demand for gasoline.

The remainder of this section shows how GMIS was used to construct and analyze this indicator. Two user interfaces of GMIS will be used:(1) TRANSACT is an interface to the data management level (SEQUEL), which includes a Data Definition language(DDL) and Data Manipulation Language (DML). This level can be used to:- restructure the data,- input the data, and- query data.(2) APL/EPLAN is the analytical, modeling, and statistical level, which resides above the multi-user interface (Figure 1). EPLAN is a set of routines imbedded in APL for doing statistical functions and reporting.

3.1 Data Manipulation

An example of creating a table and inserting data into it via TRANSACT-SEQUEL will demonstrate how a user stores data in GMIS. Note that all data are viewed as residing in tables, as in the relational model of data [Codd, 1972]. The tables have columns whose entries come from sets of elements called domains.

3.2 Reporting

A GMIS user has the full reporting capabilities of any of the modeling or analytical facilities at his disposal. For example, a GMIS user can employ the APL/EPLAN facility as a report generator and to produce plots.

Again, operating on the modeling level, the following three steps are taken (1) Extract the data using QUERY commands(2) Convert the data from a vector to a time series using theAPL DF function(3) Use the EPLAN P L 0 T function to produce the desired plot.

Modeling

In recent years increasing emphasis has been placed on the use of models to aid in policy decision making. A model is roughly defined as an incomplete representation of a system, where the purpose of the model governs which elements of a model can be adjusted to simulate a real world change in policy. The results of the simulation can then be studied and compared with other simulated courses of action before a final decision to effect change in

the actual system is made. Another useful feature of a model is that it serves as a facility through which relationships between elements of a system can be explored.

4. DETAILS OF THE GMIS DESIGN

There are three basic features of the GMIS system that give it its flexibility: (1) an overall system architecture making use of the (largely untapped) power of VM, (2) construction of the system within a hierarchical framework, and (3) the use of a relational representation of data. Section (2) gave a brief introduction to these features, and here we discuss the role of each in greater detail.

4.1 The Use of VM in the Software Architecture

Through the use of the VM concepts and the proposed architecture of Figure 1, a number of the important features of GMIS become possible, or much easier to implement:(1) Multi-user coordination of access and update to a central data base.(2) An environment where several different modeling facilities can access the same data base.(3) An environment where several different and potentially incompatible data management systems can all be accessed by the same user models or facilities.(4) Increased security and reliability [Donovan and Madnick, 1975]. VM also has disadvantages, the primary one one being the potential increase in overhead costs associated with the synchronization and scheduling of the VM system.

Figure 1 depicts a configuration of virtual machines operating on a single real computer. At the present time PL/I, FORTRAN, EPLAN/APL, andTSP are the only facilities interfaced with the data management system.Work is under way to bring TROLL to this status. Some of these modules operate under a different operating system but are made to run on the same physical machine using VM/370. All the modeling or analytic virtual machines may request data from the general data management system. In this section

4.1.1 Communication between VM's

As part of the IBM/MIT Joint Study a multi-user interface on the data base machine has been implemented [Gutentag, 1975]. This interface allows several users (programs running on the VM's) to access the single data base system. Note that for this section a distinction is made between a human user and a "user" of the multi-user interface, which is usually another program. Essentially what is needed is a means of passing commands and data to the data base machine, returning data, and a locking and queueing mechanism. One way to pass data is to use virtual card readers and card punchers. The data base virtual machine would be in wait state trying to read a card from its virtual card reader, the analytical machine would punch the commands on the virtual card reader that would be read by the data base VM. This mechanism is inefficient, however, and does not allow flexible processing algorithms.

The mechanism implemented in GMIS is as follows (note that this mechanism is invisible to a modeler when he envokes the APL/EPLAN level command QUERY, as this command automatically envokes the mechanism), Each user virtual machine (UVM), which is accessed by logging on to a separate account ID under VM/370, sends transactions to the Transaction VirtualMachine through a communications facility (described below). The Multi-

User Interface (MUI) stacks these transaction requests and processes them one at a time. The results of each transaction are passed back to the virtual machine that made the request through the same communications facility. Replies to the transactions may be processed with any software interface that is required for the application. The APL/EPLAN interface discussed earlier has been implemented in this manner.The best way to explain how the MUI works is to follow a user's virtual machine's transaction through each processing step. Refer toFigure 2 for an illustration of the transaction processing scheme described below. Each user virtual machine must have a small virtual minidisk attached to it that has been supplied with a multi-write password.This password allows more than one virtual machine to link to the disk with read/write privileges (otherwise, VM/370 only allows one user at a time to link to a disk with writing privileges).When a user's virtual machine wants to send a transaction to the data base, it writes the transaction onto its multi-write disk in a CMS1 file that is reserved for transactions (steps 1 and 2 of Figure 12). The user's virtual machine must then signal to the MUI that it wants its transaction to be processed. This is done by directing the VM/370 Control Program (CP)to send all output from the user's virtual card punch to the virtual card reader of the Transaction Virtual Machine (TVM). The user's virtual machine then punches a single virtual card containing two items of information: the ID of his virtual machine, and a code indicating the type of file format that the MUI must use when passing the transaction reply back to the user virtual machine (step 3).Each card punched by a user is actually a request to the MUI to process a transaction residing in the user's transaction file. These cards are stacked in the card reader of the TVM, and are processed one at a time, where the first card stacked is the first to be processed (FIFO) (step 4).The MUI is always running in a wait state or processing transactions.When a card is received by the TVM's virtual card reader, an interrupt is generated that activates the MUI to begin reading from its card reader.To read the user's transaction, the MUI must first access the user's transaction file. This is done by first linking to the multi-write disk of the virtual machine given by the ID on the transaction request card.(The multi-write disk is always attached at the same virtual address; in the current implementation, disk address 340 is used for all transaction files.) The disk is then accessed by the MUI, and its SEQSTAT SEQUEL file is read (step 5). It should be noted that the SEQUEL software level provides a file reading capability,

After the transaction has been processed by SEQUEL in the usual manner (step 6), the MUI writes this reply on the user's multi-write disk in a file called SEQUEL REPLY (step 7). One of several file formats may be used, depending on the user's software environment. Three general formats have been proposed that will satisfy all currently anticipated GMIS requirements. One format is to be read by APL programs, another format will be compatible with TROLL files, and a third format will be compatible with any language that can process sequential CMS files (e,g., PL/I, FORTRAN). The user's transaction request card indicates which file format is to be used by the MUI.The TVM then punches a virtual card to the UVM to signal completion of transaction processing (step 8), finally, the UVM reads its SEQUEL REPLYfile, and processes the transaction result in its own environment (step 9).

Sending a Transaction Request 3@ UVM SIGNALS TVM BY PUNCHING A CARD SPOOLED TO TVM'S VIRTUAL CARD READER

VIRTUAL VIRTUAL CARD READ/PUNCH CARD READ/PUNCH

1@TRANSACTION ENTERED 4@TVM READS CARD ANDFROM CONSOLE TO UVM GETS ID OUT OF THE UVM AND REPLY FILE FORMAT

CONSOLE USER VIRTUAL MACHINE (UVM’S) TRANSACTION VIRTUAL

MACHINE (TVM)

5@TVM LINKS TO

TRANSACTION DISK AND READS

TRANSACTION FILE

2@ UVM WRITES THE TRANSACTION MINI-DISK FOR TRANSACTION GMIS DATABASE TO A FILE ON IT’S AND REPLY FILE

TRANSACTION FILE

Returning Data

8@ TVM SIGNALS UVM THAT TRANSACTION HAS BEEN PROCESSED BY PUNCHING CARD AS IN STEP (3)

VIRTUAL CARD VIRTUAL CARD READ/PUNCH READ/PUNCH

CONSOLE UVM TVM

9@ UVM READS REPLYFILE, FORMATSOUTPUT, RETURNSTO USER 7@ RESULT WRITTEN TO UVM REPLY

6@ FILE BY TVM TRANSACTIONPROCESSED BY

TVM USING SEQUEL TRANSACTION MINI DISK GMIS DATA BASE

CLOUD COMPUTING BY IBM SYSTEM

The world is changing. A new reality is emerging for organizations of every size from every part of the planet. It’s

called the cloud—a profound evolution of IT with revolutionary implications for business and society, creating new

possibilities and enabling more efficient, flexible and collaborative computing models.

IBM is helping clients excel in cloud computing, providing secure and reliable software as a service (SaaS),

platform as a service (PaaS) and infrastructure as a service (IaaS) solutions

ADVANTAGES

The key advantage of this approach is that: It reduces complexity by decomposing the problem into a series of manageable sub-

problems. As a consequence of this reduction in complexity, the time to implement an entire system is greatly reduced.

The efficiency of the system can be increased, the improvements in efficiency come from the fact that a system so constructed can be analyzed and tuned for performance because each level can be thoroughly understood and analyzed.

Given inherent parallelism in information systems, the hierarchical approach also can capitalize on new technologies to increase the performance, reliability, and integrity of information systems.

The IBM SearchManager/370 Migration Component provides migration and coexistence for users of the predecessor products STorage And Information Retrieval System (STAIRS) in both the MVS and VM environments.

When IBM SearchManager/370 is used in conjunction with OfficeVision(TM)/MVS and its Document Writing Feature (DisplayWrite/370- MVS environment) or with OfficeVision/VM and DisplayWrite/370 (VM environment), and the Graphical Data Display Manager (GDDM)(TM), it offers a solution for creating, storing, retrieving, displaying, processing, and distributing documents consisting of text, graphics, and/or images.

In a VM environment, IBM SearchManager/370 interfaces to the OfficeVision/VM mail function to send documents stored in IBM SearchManager/370 databases.

System/370 users can take advantage of the very fast storage available with the recently announced IBM 2305 fixed head storage facility.

It permits several users to select and access data according to many criteria, as it is impossible to specify in advance all the ways the data will be used;

It allows for easy viewing of data, and contains facilities for validation of data.

Drawbacks of the approach

On the VM interface level there is need for investigation of efficient ways VM's can communicate with each other. On the VM level more knowledgeable processor schedulers need to be developed.

Work must be done on synchronization and locking policies of multiple VM configurations.

Investigation of the implications of the new technologies (e.g., memory, networks, and microprocessors) on each level in the hierarchy is called for.

CONCLUSION

It is believed that an operational relational data management facility needs to be implemented and incorporated into a system that has analytical capabilities and such a development must be done in close cooperation with real applications. Further, it is believed that those applications should be chosen in areas where this technology has (a clear advantage, that is, for systems where the problems keep changing e.g. public policy systems) or where the system is not well-defined e.g., bread boarding systems), and not to application areas that are currently being satisfactorily met by other approaches.