I think I screwed up the layout on my previous post, so here it is
again:
The MatriDigm Story For those of you who still don't know what, how &
why, here is MatriDigm's own words
>>We all know what the problem is.
By now you know that your computing environment and the applications
which depend on date calculations will begin to produce disasterous
results as the year 2000 approaches.
If you do not act now to prevent this, you may find that many
traditional solutions are no longer viable. By then, it may be too
late. Industry experts predict that by the end of 1999, less than 70%
of IS organizations will be Year 2000 compliant in mission-critical,
customer-focused, external applications. They estimate that the cost
to fix this problem will range between $300 and $600 billion in the
global market, since 40% to 80% of all code will need modification.
Unfortunately, at the same time the cost of the solution is increasing,
the availability of skilled resources is decreasing. The situation
will get worse before it gets better.
We know why it happened.
In the 1960's and 70's, the high cost of storage processing as well as
hardware design limitations resulted in the Year 2000 dilemma. In the
interest of conserving resources, software programs were written with
simplistic two-digit fields representing years. For example, '96' to
represent '1996.' Since that time, programming convention and
compatibility requirements have perpetuated the use of the two-digit
fields. Solving one problem has created another. The Year 2000
problem is greater and the solution more critical.
Time is running out.
We know some solutions take too long to implement. There are an
estimated 180 billion lines of COBOL code currently in use in business
applications throughout the world, representing a $2 trillion
investment. As you can see from the size of your IS department, the
average programmer can only handle 100,000 lines of code annually. To
make matters worse, 80 to 90% of their time is dedicated to
maintaining existing applications rather than adding new business
functions. How do you solve the year 2000 problem without compromising
your existing business responsibilities? With Time as the enemy, the
potential for catastrophe is real. First,recognize you cannot solve
the problem yourself. Time constraints preclude this. In fact, some
companies that started four years ago to solve the year 2000 problem
still are not compliant. The time for traditional approaches -- if
there ever was one -- is long past.
What you need to know now.
The MatriDigm year 2000 solution significantly reduces the time,costs,
resources and risk of your Year 2000 conversion. Send us your code.
MatriDigm can process up to 50 million lines of code in a week. This
means a solution in days or weeks instead of months or years.
In addition, our conversion service will integrate with your current
IS processes without sacrificing your current enterprise technology
responsibilities.
The MatriDigm Code Analyzer captures the business rules and data
interactions of each application in a unique hyperlinked data base.
This allows MatriDigm to analyze your applications as a whole. As a
result, MatriDigm is able to employ a unique data identification
technique to find all of the date fields in an application.
MatriDigm's year 2000 solution provides a 2-byte representation of a
4-digit date filed that enable both converted and non-converted
applications and data files to coexist in the same production
environment. Additionally, most existing data files and JCL do not
require any conversion. Because of this fully automated solution, the
potential for human error is diminished and testing time and staff
effort minimized.
Finally, it incorporates a unique method of fragment testing that
exhaustively tests all changes made. This ensures that returned code
will function precisely the same as before, with the addition of being
Year 2000 compliant. With MatriDigm, the year 2000 solution is fast
and fully automated. Because you have selected MatriDigm, you can
win the race against Time.
That is what you need to know. Now. <<< |
