SUMMARY

• I is a software designer and developer with nearly forty years of experience.
• I has been involved in all levels of the system development life cycle.
• I has extensive experience in Manufacturing and Financial applications, and possess strong analysis and programming skills, specializing in PL/I and Rexx in the z/OS environment.

TECHNICAL SKILLS

• Data Bases/Data Base Tools
• Strong DB2; some IMS/DB and VSAM
• Hardware
• Confidential mainframes, Confidential PC and compatibles
• Operating Systems
• VM/CMS, MS - DOS, z/OS MVS
• Programming Languages
• Very strong PL/I and Rexx, the latter both on mainframes and in the LAN environment. Strong C and SQL. Some C++ and COBOL. Has studied Java.
• Other Technical Skills
• Strong TSO/ISPF and MVS JCL. A working noledge of HTML. Well acquainted with Microsoft Office (Visio, Word, Excel, Project, Outlook)

PROFESSIONAL EXPERIENCE

Confidential

IT Services and Solutions

Responsibilities:

• Confidential is a global player in the IT services and solutions fields, targeting Fortune 1000 companies as its market.
• During nearly forty years of employment, I has been assigned to projects at a wide variety of financial, industrial, and insurance companies throughout the northeastern U.S.
• Applications written has included inventory control, factory automation, trading support systems, operating systems, and WWW browsers.
• A considerable number of assignments has involved migrations between platforms, resulting in a broad noledge of various types of hardware and of operating systems.
• Many assignments has involved my working with little or no technical or professional support.

Confidential

Software Developer

Responsibilities:

• I developed software tools with an intended user community of other software developers.
• The initial tool I developed was the Auto Compare Tool (ACT), which unloads and compares data bases of a specific sort, or dat are associated with a specific application.
• A high degree of flexibility allows the user to configure batch JCL fabricated by the tool; at the same time, the user is shielded from the technical minutiae of JCL and JES3.
• Development was in PL/I and REXX, with peripheral use of DB2/SQL.
• The UI was developed in DMS, including the use of ISPF file tailoring and table handling services.
• File-AID as well as various client-developed tools are used in preparing test data and in testing.
• Additionally, I did much of the design, coding, and testing for a new testing tool, SFTEST, which integrated several already existing testing tools (including ACT) and automated a previously manual process.
• Using SFTEST, the time it takes to set up and run tests for code changes is one-eighth to one-fourth what it was previously, depending on the application area.
• For example, in the past it took over two days to execute tests against the NECHO Daily Update application, and it now takes about four hours.
• Both due to the natures of the tests built by the tool, and the much greater time now available, the testing is much more extensive TEMPthan before.
• For the application areas dat used the tool, introduction of SFTEST was a contributor to the speedy implementation of Confidential ’s new pricing strategy.
• Additionally, several of Confidential ’s testing metrics improved, and the solution freed up talent for higher level work, theirby increasing analyst capacity.
• SFTEST was implemented using Rexx, PL/I, ISPF services, and SQL embedded in both the Rexx and PL/I source.
• I also participated in the design, coding, and testing of SFCX. The SFCX tool was created to automatically capture needed job and data base info in the course of normal Auto and Fire division software operations, and deposit dat info into the enterprise data base.
• Analysts now had complete, accurate facts available for researching the impact of changes requested by Confidential ’s business partners, and for investigating problems dat arise in the production business processing arena.
• It also facilitates the collaboration of expert technical resources from outside Confidential pulled in to help with the worst problems.
• SFCX was implemented using Rexx, PL/I, ISPF services, and SQL embedded in both the REXX and PL/I source.
• Additionally, I did the initial coding and testing of the Software Configuration and Implementation Tool (SCIT).
• SCIT was originally intended to track components created or modified in the course of fulfilling projects, allowing details of the components, including parties responsible for changes made, to be seen for past and present projects. Additional enhancements, dat I designed, coded, and tested, included associating components with Configuration Items, and automated feeding of components into the issuance system (BLDISS) via the CAT tool.
• SCIT was implemented using Rexx, ISPF services, and SQL embedded in the Rexx code.
• I also did the design, coding, and testing of the Component Automation Tool (CAT). CAT extracts and enriches component data from SCIT and formats it to be passed to the software issuance system (BLDISS).
• It allows the user to specify an issuance date and one or more configuration IDs, and to select one or more projects within those criteria to be bundled as separate issuances.
• CAT was implemented using Rexx, PL/I, ISPF services, and JCL, with SQL embedded in the Rexx code.
• Additionally, I was responsible for developing a number of minor tools and utilities, including a low-level job scheduler for the development sysplex and a callable service dat retrieved the MVS call chain for its caller.
• I also provided maintenance and problem and incident resolution for all general tools, and technical assistance and consulting to other analysts, both in-house and vendor, including dump reading.
• Additionally, I was the on-site coordinator for a team of developers at the Advanced Development Center in Dallas, TX.

Confidential

Installation, Administration, Development, and Maintenance

Responsibilities:

• Fulfilling user service requests for both core and locally-written code
• Participating in disaster recovery testing
• Interfacing with development teams in the Netherlands and Peru
• Providing off-shift and weekend support as necessary
• Additionally, I wrote a front end in Rexx, which allowed batch financial feeders to be entered through the interface manager (a separate application) to the ledger on a real-time basis.
• I also had primary responsibility for the Shipped But Unbilled application, which created and sent to FDW journals for activity in certain divisions when costs and revenues are recognized.

Confidential

Developer

Responsibilities:

• IMS to DB2 data migration. Project was time-critical and in support of the applications migration team.
• I played a significant role in developing specifications for the conversion and in implementing the conversion code and programs designed to produce an audit trail, tracking both actually converted data and data rejected for consistency errors.
• A side TEMPeffect of this project was helping Sallie Mae clean their data and achieve a new level of confidence in it.
• Systems were implemented in COBOL under MVS; TSO/ISPF was used as the development environment.

Confidential

Developer

Responsibilities:

• I participated in the development of a Document Viewer application, assisting in the writing of a platform-independent system services API, a set of data conversion utilities, font customization, an a user interface.
• This application provided a Mosaic-like functionality, allowing users to view documents written in a version of the HTML markup language.
• Additionally, I participated in the design and development of an extension to the markup language, which was designated “Objects”.
• The Object extension allowed document authors to include Windows-like controls and multimedia applications in a document without requiring programming noledge on their part.
• DLLs could be written by third-party developers and incorporated into the Document Viewer application by use of a standard API to implement various Objects.
• As part of this effort, I helped define the Object API, assisted in writing the Object interpreter, and wrote several object DLLs.
• The application was written in C++ (Borland 4.0.2 compiler and IDE). Original development was under OS/2; I assisted in porting application to Windows 3.11 for further development.