|
|
|
 |
Year 2000 Problem
Generally
speaking there are two approaches to this problem:
| • |
Fixing existing legacy applications |
| • |
Replacing the legacy applications
with new applications |
In
both cases it is important to have programmers who are familiar with the legacy
programming languages and systems such as COBOL, PL/1, Assembler, FORTRAN, REXX,
ISPF/PDF, CICS, IMS, etc. It is also vital to have the programmers who are familiar with
the interfaces between applications and are capable of incorporating the new interfaces
into old systems.
Our
consultants have many years of experience with legacy mainframe systems and are familiar
with different Application Programming Interfaces.
When new systems are introduced into
complex mainframe environments, it is important to rebuild the interfaces to the old
legacy systems. There are only a few alternatives:
| • |
Batch interfaces: New systems can
interface with the old ones using some sort of intermediate files or databases; |
| • |
3270 EHLLAPI: Interfaces to
old systems are based on a programmed terminal emulation of an operator using a 3270
terminal |
| • |
Intermediate Servers:
Building a mainframe interface with a legacy application on one side and the new
application on the other side. The interface to the new system can be based on SNA APPC
technology or the TCP/IP-based sockets API, or other higher level communications
technology. |
Our
company has a very thorough understanding of IBM mainframe operating systems (System/390
and VM) and has been involved in a number of projects using all the above technologies.
We are
familiar with IBM's Year2000
methodology and tools and we will be happy to assist you with the implementation of
your Year 2000 projects.
If you have any questions please contact us via E-Mail at Support@genssoft.com
Copyright 1999 Gens Software Ltd. All Rights Reserved.
|
