Customers who bought this book also bought:
Reviews
Amazon.com
The work in this book will endear itself to hard-core assembly language programmers. Over half of the book lists assembly language programs for solving a host of year 2000 problems. Two introductory chapters contain basic information about year 2000 issues and document the notational conventions used in the assembly language programs. The remaining seven chapters of the book are each dedicated to explaining a year 2000 problem, mapping out a solution, and implementing the solution in the form of a fully documented program. The book includes all of the source code on floppy disk. Book Description
For business and governments around the world, the approach of the year 2000 signals a countdown to chaos. At the dawn of the new millennium, computer systems all over the world will begin generating bad data because of the way software has been written to interpret years (as two digits instead of four). The transition for year "99" to year "00" will wreak havoc in worldwide systems unable to distinguish 1900 from 2000. From pension funds to checking accounts, the implications are enourmous. As time runs out-less than 1,250 business days to the turn of the century-the urgently needed handbook offers solutions to the problem, which large business alone are expected to spend up to $100 billion to correct. Living up to the promise of its title, the book provides a concrete plan for IS developers and consultants scrambling to beat the clock before their system collapses. This solid blueprint includes a bundled disk containing exhaustively tested source code in COBOL, RPG, and assembly language. What is presented here is a programmed and tested solution system complete with psudo code, allowing staff IS personnel maximum flexibility in implementation. Synopsis
At the dawn of a new millennium, computer systems all over the world will begin generating bad date bacuse of the way software has been written to interpret years. This urgently needed handbook offers solutions to the problem. This book provides a concrete plan for IS developers and consultants scrambling to beat the clock before their systems collapse. Back to Year 2000 Problem
Back to Project Management
Back to Main Index
|
