Legacy Mainframe Connectivity

Legacy mainframe connectivity via "screen-scraping" algorithms which emulate user logins to legacy mainframe systems. These solutions do not involve new development on the mainframe side. Expertise with tools that provide shortcuts when using this type of solution.


United States Air Force

Lead Developer
March, 2000 - June, 2000

Provided programming support to a marketing effort for upgrading the user interface to existing legacy applications related to aircraft maintenance. Converted a canned demonstration to a working prototype providing a core set of legacy functionality through a web interface. Used Yrrid Legacy Objects Framework technology to acquire and update data in legacy mainframe system tracking aircraft maintenance data. Demonstrated prototype to USAF personnel.

Skills

  • Java
  • Legacy Objects Framework
  • SQL Server
  • WebObjects
  • Windows 2000

United States Postal Service

Lead Developer
March, 1996 - December, 1996

Developed software infrastructure on a contract for the United States Postal Service using the Legacy Object Framework toolkit for screen-scraping legacy systems. LOF was used to retrieve information from USPS databases for display on the web via WebObjects.

The software infrastructure was geared towards the construction of rapid prototypes which were scalable and deliverable. Support tools included a mechanism for mapping database objects directly into windows for display purposes. Developed a server application supporting stand-alone server platforms as opposed to requiring all client platforms to perform legacy access directly.

Skills

  • Bison
  • Flex
  • Legacy Objects Framework
  • NextStep
  • Objective-C
  • OpenStep
  • SQL Server
  • WebObjects
  • Windows NT
March, 1991 - March, 1994

MCI

June, 1993 - March, 1994
Developer

Developed communications and display components of a workstation for transmission network surveillance analysts. The Transmission Surveillance Workstation (TSWS) gathered data related to ongoing transmission alarms and correlated this data with reference information about the alarm sites and cognizant personnel. The workstation also supported the generation and tracking of trouble tickets for these alarms.

The TSWS replaced a number of separate systems which previously cluttered analysts' desks with a single, integrated platform. The PC-based system communicated with several mainframes via both asynchronous protocols and simulated 3270 terminal sessions.

Mr. Adkins developed generic software for inter-process communication and display management, including script-based window support and a prototyping system which could be used as the basis for production code. The result was a set of reusable software components at both the module and application levels. OS/2 Dynamic Link Libraries (DLLs) provided much of the flexibility for this system.

Skills
  • C++
  • CSet++
  • OS/2
  • Presentation Manager
December, 1992 - June, 1993
Lead Developer

Mr. Adkins was the lead engineer on a system for automatically handling trouble tickets relating to network problems at MCI. Information in the trouble tickets was used to initiate automated testing, and the results of the testing were used to guide the trouble tickets to appropriate sites for resolution. The PC-based system communications with three mainframes via simulated 3270 terminal sessions and with test equipment located in the network via asynchronous communications links.

Several separate modules are used to handle the processing. These modules communicated as peers via NetBIOS datagrams and automatically started secondary versions of themselves on other machines so that software or hardware failures did not result in system failure. Ticket, machine, and host connectivity status were all reflected in the user interface, which also supported system functions including the automatic flushing of tickets which became stuck in testing.

Skills
  • C++
  • OS/2
  • Object PM
  • Presentation Manager
August, 1992 - December, 1992
Lead Developer

Led the development of a workstation for collecting mainframe information and presenting it to the user in graphical format. The PC-based system communicated with up to four mainframes by simulating users at 3270 terminal sessions. The menus and screen-oriented data returned by the mainframes were parsed and collated on the PC for presentation to the user.

Mr. Adkins was responsible for constructing a spin-off of the original system which handled one new mainframe data stream and structured the data returned from the other mainframes in a totally different manner from the original product. The project for which Mr. Adkins was responsible met an extremely challenging schedule.

Skills
  • C++
  • OS/2
  • Object PM
  • Presentation Manager
April, 1992 - July, 1992
Developer

Developed a series of classes implementing protocols for screen-scraping legacy mainframe systems. The class structure permitted extension for new systems via subclassing and overloading of appropriate methods. More than four legacy systems were eventually served by this class library.

Skills
  • C++
  • OS/2
  • Object PM
  • Presentation Manager