Modernization of Legacy Application Software (1998)
| Citations: | 2 - 1 self |
BibTeX
@MISC{Howe98modernizationof,
author = {Jeffrey Howe and Scott B. Baden and Tamara Grimmett and Keiko Nomura},
title = {Modernization of Legacy Application Software},
year = {1998}
}
Share
 |
 |
 |
 |
||
OpenURL
Abstract
. Legacy application software is typically written in a dialect of Fortran, and must be reprogrammed to run on today's microprocessorbased multicomputer architectures. We describe our experiences in modernizing a legacy direct numerical simulation (DNS) code with the KeLP software infrastructure. The resultant code runs on the IBM SP2 with higher numerical resolutions than possible with the legacy code running on a vector mainframe. 1 Introduction Legacy application software is typically written in a dialect of Fortran, and optimized for execution on a vector class architecture like the Cray C90 or T94. Such codes often run on just one processor and must be reprogrammed to run on today's microprocessor-based multicomputer architectures like the IBM SP2 or Cray T3E. A principal motivation for modernizing legacy code is increased memory capacity. For example, the Cray T94 at the San Diego Supercomputer Center has only about 2 Gigabytes of memory, but just 8 nodes of SDSC's 128node IBM S...
Keyphrases
legacy application software legacy code ibm sp2 legacy direct numerical simulation cray c90 san diego supercomputer center multicomputer architecture numerical resolution memory capacity resultant code run microprocessor-based multicomputer architecture principal motivation kelp software infrastructure cray t3e vector mainframe introduction legacy application software cray t94 vector class architecture
