General discussion


Question Mainframe Mentality in the New Millineum

By newby7718 ·
Althought there is a time and place for mainframe mentality from IBM, the need for such technology diminishes with time and progress from vendors like Microsoft who prefer the "mom and pop" business and home user approach.

Mainframe mentality may be acceptable in a large corporate environment where thousands of transactions occur instantly and a large staff of IT people support the "beast's" operations, but in real life it is costly overkill that can be much better served by putting a full load of user software on the user's desktop system and sharing other resources (databases, print spoolers,Internet access/security, etc.) on the servers.

If the "mainframe" (server, etc.) crashes every user on that system is affected. This process is a great inconvenince to users and cost companies millions of dollars in productivity every day the mainframe hickups.

If a desktop has the appropriate software, the user can continue working while the server is down .... and if a desktop is down, it only affects the user of that desktop. A desktop or server can usually be revived within minutes while mainframes can take hours.

Properly designed Server/Desktop sites have much lower cost and better "uptime" ratios than any Mainframe site.

I doubt that IBM/Lotus will have successes with on this old mainframe mentality based idea ... but, as usual they keep trying old methods instead of trying to conform with the new technology that is available to us in the new millenium.

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

Collapse -

Time and Place for each

by TheChas In reply to Question Mainframe Mental ...

The places where I still see mainframe systems do not have or need large IT staffs to keep the "beast" running.

Quite the contrary, their mainframes have better up-times than their Windows networks.

But, the mainframes are running dedicated functions for authorized users.

Inventory Management, Production Control, and related activities for most manufacturing tasks still run better on a mainframe than a networked computing environment.

Even if on a Windows network, these applications rely on a SINGLE database.
If the network goes down, these users CANNOT continue to function until they can access the database.

Yes, if you are performing single user tasks, a Windows network is a better option.

However, when sales, purchasing and production need to work off of a common set of numbers, a mainframe architecture may still be the "best" choice for all but the smallest companies.


Related Discussions

Related Forums