|
PERSONAL
PARTICULARS |
|
Name |
Christopher David DUNCAN |
|
|
Date of Birth |
|
|
|
Nationality |
Australian
Citizen |
|
|
Marital Status |
Married |
|
|
Contact |
|
EDUCATION |
|
1983 - 1987 |
B.Sc. Hons. Computing & Informatics |
|
|
1981 - 1983 |
O.N.D. Engineering Technology |
|
|
1976 - 1981 |
6 G.C.E. ‘O’ Levels |
Knowles Hill Comprehensive |
|
TECHNICAL SUMMARY |
|
Equipment |
|
IBM MAINFRAME |
IBM PC |
ROCC |
BBC MICRO |
|
Operating Systems |
|
MVS / XA |
WINDOWS / MS-DOS |
UNIX |
ROCC OS |
|
Languages |
|
NATURAL 4,3,2,1 |
NATURAL LIGHTSTORM |
NATURAL ND |
VISUAL BASIC 5 |
|
|
|
COBOL |
DL/1 |
CONSTRUCT |
SQL |
|
|
|
TELON |
BBC BASIC |
|
|
|
Database |
|
ADABAS C, D |
DB2 |
IMS |
ACCESS |
|
Other |
|
JCL |
TSO / ISPF / SDSF |
PREDICT |
PLATINUM |
|
|
|
FILE AID |
ABEND AID |
ENTIRE-CONNECTION |
PROCESS |
|
|
|
PEEK |
DEBUG |
WINDOWS 95 |
ESPERANT |
|
|
|
EXCEL |
WORD |
POWERPOINT |
PROJECT |
|
|
|
LOTUS NOTES |
VISIO |
NATURAL ENGINEER |
PAC |
|
EMPLOYMENT SUMMARY |
I have over 20 years experience
in IT covering a broad range of skills and roles, having worked in many
business areas (Finance, Insurance, Banking, Policing, Engineering, Utilities,
Software development) in the Private and Public sectors.
|
Technical Skills |
|
Roles |
|
My main
skills are in mainframe Natural Adabas but I have worked with Natural in many
different forms.
I also
have skills in :-
|
|
I have worked in a
variety of roles :-
|
|
COURSES ATTENDED |
|
Software AG |
|
|
UNIX |
|
|
· NATURAL 1 programming |
- 5 days |
|
· UNIX - Fundamentals |
- 5 days |
|
· NATURAL 2 programming |
- 5 days |
|
· UNIX - Shell Programming |
|
|
· CONSTRUCT - Introduction |
- 3 days |
|
· UNIX - Using Editors |
|
|
· CONSTRUCT - Application Modeling |
- 3 days |
|
· UNIX - Using the Shell |
|
|
|
|
|
· UNIX - Exploring the file system |
|
|
Miscellaneous |
|
|
· UNIX - Process and Data Utilities |
|
|
· Telon |
|
|
· UNIX - The User Environment |
|
|
· Mantra Interpersonal Skills |
|
|
· UNIX - Working with Files |
|
|
|
|
|
|
|
|
ASI audio visual courses |
|
|
JAVA |
|
|
· MVS OS concepts |
|
|
· Introduction to JAVA |
|
|
· JCL Basic Coding |
|
|
· 10 week evening course |
|
|
· IMS Concepts / DL1 / MFS |
|
|
· Hands on and theoretical |
|
|
EMPLOYMENT DETAILS |
|
Jun 2007 |
- |
May 2009 |
IBM Global Services |
||||||
|
Oct 2009 |
- |
Present |
|
|
|
||||
|
2 year 11 months |
|
|
Business Analyst / Analyst Programmer |
|
|
||||
|
|
|
|
NATURAL 3.1.5 & 6.3.8 |
ADABAS |
DEBUG |
PREDICT |
TSO |
|
|
|
|
|
|
ENTIRE X |
JCL |
EXCEL |
WORD |
WINDOWS |
|
|
|
|
|
|
XML |
PROJECT |
VISIO |
UNIX |
SCRIPTING |
|
|
Jemena is a GAS network company that has out sourced their IT
work to IBM Globals Services. IBM was responsible for maintaining the GASS
system during the de-merger of AGL and Jemena.
Porting Project – From Mainframe to UNIX
The GASS system was ported from the Mainframe to a Unix (AIX)
environment. My role was to automate the migration of all necessary datasets
and convert the data to a format compatible with Unix.
I remediated a number of utility tools to work under Unix and created several scripts.
GASS Make Whole Data Conversion
I was responsible for the following:-
·
Documenting
and administrating the data conversion process, consisting of about 100 jobs
and 200 programs
·
Coordinating
the work among a number of team members on the verification process
·
Adding
technical efficiency improvements to reduce the overall run time from a few
days to just several hours
Software Configuration
I was responsible for producing a detailed Software
Configuration Plan on the migration of all relevant software items, following
IBM’s methodology.
EDI Interface
The EDI interface handles the translation and processing of
XML transactions to and from the Gas Market Company’s system GRMBS
(following aseXML standards) to GASS+ functions. It sends and receives these
via EntireX Broker.
·
I
was responsible for documenting this translation process.
·
I
designed the translation table maintenance functions
Miscellaneous
·
I
was responsible for upgrading to Natural 6.3.8 and Adabas 6.1.8
·
I
helped to improve the migration process to easily provide auditing artefacts
and in the separation of duties.
·
I
wrote the business requirements documentation for the Network Diary processing
and later became the Subject Matter Expert in this area.
|
Jan 2005 |
- |
Jun 2007 |
NSW POLICE |
||||||
|
|
|
|
|
|
|||||
|
2 year 6 months |
|
|
Project Leader / Business Analyst / Analyst Programmer |
|
|
||||
|
|
|
|
NATURAL 3.1.5 |
ADABAS |
DEBUG |
PREDICT |
TSO |
|
|
|
|
|
|
ENTIRE X |
JCL |
EXCEL |
WORD |
WINDOWS |
|
|
|
|
|
|
ENTIRE CONNECTION |
PROJECT |
VISIO |
|
|
|
|
I worked on 3 separate projects (simultaneously for a large period of time) all of which were legislative driven and on the Integrated Licensing System (ILS). I liased with both internal and external stakeholders to resolve any conflicts.
- Firearms Safe Storage of firearms
- CAPI Licensing Recording the application details
for Commercial Agents (CA) and Private Inquiry Agents (PI)
- Security Licensing Recording the application and
training details for Security Licences
Firearms
Legislative changes now allow firearms users to safely store firearms at a number of locations. Previously ILS was designed to only allow for one address.
A number of enhancements were introduced including improvements to the location enquiry screen where firearm details are more prominent and readily available. Clearly the recording of firearm details is a very sensitive issue. All these enhancements were very well received by front line police officers.
CAPI Licensing
CAPI licences were previously issued as paper licences through the NSW courts. New legislation requires that the application process is recorded through Security Industry Registry, as part of NSW Police. CAPI licences will now be produced as a plastic licence card at local RTA offices.
Security Licensing
Among a number of changes,
was the recording of applicant training details from Registered Training
Organisations (RTOs). This required a web system to be built with an Entire X
interface to the ILS mainframe system. Results from the RTOs would be compared
with certificate details provided by the applicant, and therefore forgeries
could be more easily identified.
Others
I
later created two additional Business Requirement documents for Recovered
Assets and Multimedia Services, producing business flow diagrams to map the
processes and rules for all parties and systems involved.
Summary
- I have worked in many roles on these projects,
from Project Leader, Business Analyst to Senior Analyst Programmer.
- I have written the Business Requirements, Technical
Specifications, User Manuals and Test Plan documentation.
- I coordinated the projects consisting of over
500 Natural objects and managed the resources of five Analyst
Programmers.
|
Mar 2003 |
- |
Aug 2004 |
GENERATION SYSTEMS LTD |
||||||
|
|
|
East |
|
|
|||||
|
1 year 6 months |
|
|
Senior Analyst Programmer |
|
|
||||
|
|
|
|
NATURAL 6.1.1 (windows) |
ADABAS |
DEBUG |
PREDICT |
NATURAL ENGINEER |
|
|
|
|
|
|
ENTIRE X |
JCL |
EXCEL |
WORD |
WINDOWS |
|
|
|
|
|
|
PAC |
SPOD |
VISIO |
|
|
|
|
Generations System Ltd. is a
software company specialising in tools for use with Natural Adabas. As a result
they have a very strong partnership with Software AG.
Their flagship product is
Natural Engineer (based on their Y2K tool GenArt) a general analysis and
conversion tool.
Reporting Mode to
Structured Mode conversion
One of the features of
Natural Engineer is the conversion of Reporting Mode objects to Structured
Mode.
One of my primary tasks was to build, enhance, maintain and support this
function. This is achieved by:-
- First parsing a Natural application to build a
detailed repository (in the form of an Adabas file).
- Reading the repository to build a series of
tables (held in memory outside of Natural)
- Scanning the original code in combination with reading
the tables and repository, to build the Structure Mode objects
SPOD conversion
Natural Engineer could be
used with Entire Network to allow a PC front end interfacing to Mainframe
databases and source code. Unfortunately Entire Network is both expensive and
slow. Software AG developed 'Single Point of Development' (SPOD) to overcome
this.
I was part of a large
project to make Natural Engineer SPOD compliant. This involved:-
- Developing efficient techniques to transfer data
between platforms.
- Modification of dialogs to conform to the new
GUI standards.
- Fixing existing bugs.
PAC interface
I wrote the
interface between Natural Engineer and PAC using a number of supplied APIs.
Natural Engineer is
available under both Windows and Mainframe platforms, so work was required on
both platforms.
|
Mar 2002 |
- |
Feb 2003 |
JP MORGAN CHASE |
||||||
|
|
|
|
|
|
|||||
|
10 months |
|
|
Business Analyst / Analyst Programmer |
|
|
||||
|
|
|
|
NATURAL 3.1.5 |
ADABAS |
DEBUG |
PREDICT |
PEEK |
|
|
|
|
|
|
PROJECT |
JCL |
EXCEL |
WORD |
WINDOWS |
|
|
|
|
|
|
TSO |
WINDOWS |
|
|
|
|
|
I was a member of the
Finance AD team, which is responsible for the corporate General Ledger System
(GLS) and its interfacing and regulatory reporting systems.
VAT Reporting
I worked as the principal
Analyst Programmer on a project to restructure and implement the VAT reporting
suite for all major UK Legal Entities, following the Chase / JPMorgan merger.
This was a high profile
project as it meant following requirements set by Customs and Excise to create
a consistent and dynamic VAT recovery methodology. Any mistreatment or over
recovery of VAT can lead to significant financial penalties.
I was involved in all
stages of the project from the initial feasibility meetings through to post
implementation reviews.
This involved the
following:-
|
Design |
I produced the following
:-
|
|
Build |
|
|
Implementation |
|
Other Tasks
Although the VAT Reporting
project was my primary responsibility, other tasks included:-
- Impact analysis on upgrading code to Natural
3.1.5.
- Work on a new starters guide.
|
May 1999 |
- |
May 2002 |
NSW POLICE - through SOFTWARE AG |
||||||
|
|
|
|
|
|
|||||
|
3 years |
|
|
Analyst Programmer |
|
|
||||
|
|
|
|
NATURAL 2.3.2 |
ADABAS |
DEBUG |
PREDICT |
|
|
|
|
|
|
|
ENTIRE CONNECTION |
JCL |
EXCEL |
WORD |
|
|
|
|
|
|
|
TSO |
WINDOWS |
ENTIRE X |
|
|
|
|
I worked on a number of
different systems while with ITS Support. This was very challenging, as the
systems are very large and highly complex. By the sheer nature of Police
systems (dealing with criminal data) integrity and security were paramount. The
main systems I worked on were:-
|
COPS |
Warrants |
Property Management |
|
Electronic Billing |
Safe Driver |
|
Some of the key areas
were:-
Fringe Benefit Tax
Download
New legislation required
that the details of Fringe Benefits Tax (FBT) be calculated for each individual
service member occupying or has occupied a service residence within the FBT
year.
This involved consulting
with the Finance and Property Management teams to ascertain what data was
required. This was merged from the payroll work files and the Property
Management database. The data was then downloaded using Entire Connection into
spreadsheet, where a macro was run to format the information and provide the
necessary totals
Pawn Broker System
Pawn brokers and second
hand dealers are required by law to provide details of all their transactions.
This includes pawning, purchasing, and identification details. I provided
support for the whole process, from receiving the data through to numerous
property reports. This involved:-
- Disk upload to the mainframe using
Natural Connection, and data validation.
- Updating the database,
involving property and person matching (a highly sensitive issue).
- Property reports - matching
pawned property against property reported stolen.
Occupation Changes
While there were numerous
codes for standard occupations there was a need to allow a free text description.
While this was basic change, it affected all areas of the COPS system. Over 50
objects had to be modified, including a few database changes.
Improvements to the
Development and Support Environments
I made a
number of enhancements to the ‘Error Logging’ process, ensuring extra
information was logged. I also introduced a new ‘Browsing’ function which meant
useful information could be quickly and easily pulled together from a number of
sources. I developed a whole suite of general-purpose utilities. The main ones
were:-
- A quality-check program, which
scans a Natural object, performing over 50 checks.
- A general browse DDM program
generator
- A cursor sensitive utility
which provided details on a number of program entities (statements,
objects etc)
I performed a number of
live demonstrations to the IT development and support staff.
|
Feb 1999 |
- |
April 1999 |
STEELMARK - through SOFTWARE AG |
||||||
|
|
|
|
|
|
|||||
|
3 months |
|
|
Consultant |
|
|
||||
|
|
|
|
NATURAL 2.2.8 |
ADABAS |
ONLINE SERVICES |
PREDICT |
NATURAL SECURITY |
|
|
|
|
|
|
ENTIRE CONNECTION |
JCL |
EXCEL |
WORD |
NATURAL VSAM |
|
|
|
|
|
|
TSO |
WINDOWS |
ENTIRE X |
DELTA SAVE |
|
|
|
I worked in two different
areas while at SteelMark
Year 2000 remediation
This involved running N2000
workbench, SPL’s year 2000 remediation tool. Natural objects were then
categorised by their remediation type. For example 'Database changes’,
'Windowing'. These were then further categorised into:-
- Functionally related area
- Priority
- Obsolete code
I then went on to produce
new windowing routines and database conversion programs, as well as code
maintenance.
Software Upgrade
In addition to maintaining
the Natural code, numerous Software AG products had to be upgraded to ensure
SteelMark’s systems were year 2000 compliant. As their Natural systems were
being faded out, shortly after the year 2000, it was agreed that as a temporary
solution, they could upgrade to Natural 2.2.8, as opposed to 2.3.2. This meant
upgrading their environment as following: -
|
Natural |
2.2.8 |
|
Natural Security |
2.2.8 |
|
Natural VSAM |
2.2.7 |
|
Natural Connection |
2.2.8 |
|
Predict |
3.4.2 |
|
Adabas Online Services |
6.2.2 |
The upgrade process
involved liaising with the System Programmer and Database Administrator at
SteelMark and SPL (Software AG) experts based in
In summary the tasks
involved were:-
- Applying the appropriate
parameter settings (for example NATPARM).
- Submitting jobs to load, assemble
and link drivers.
- Install system files (for
example system programs, error numbers, example files etc).
- Implementing any corrections,
in the form of ZAPS, INPLs and Error load files.
|
Aug 1998 |
- |
Feb 1999 |
ALLTEL INTERNATIONAL - through SOFTWARE AG |
||||||
|
|
|
|
|
|
|||||
|
7 months |
|
|
Contract Project Leader |
|
|
||||
|
|
|
|
NATURAL 2.2.8 |
ADABAS |
TSO |
PREDICT |
|
|
|
|
|
|
|
NATURAL 2.3.2 |
JCL |
EXCEL |
WORD |
|
|
|
|
|
|
|
NATURAL
NT 3.1 |
WINDOWS |
PROJECT |
|
|
|
|
As Alltel were converting
all their Natural systems for year 2000 compliance, it was decided to upgrade
from Natural 2.2.8 to the fully compliant version, Natural 2.3.2. I was
responsible for detecting all the issues related to upgrading code to Natural
2.3.2.
My first task was to produce
a 'Natural 2.3.2 Options paper'. This discussed the following areas :-
- The various states that
Natural systems could be in, before and after Y2K compliance
- The possible implementation
options and how they applied to systems/projects under Alltel
- Provided recommendations on
which option to use for which system/project
I wrote many testing
programs to run in Natural 2.2.8 and 2.3.2 to investigate the full nature of
any syntactical and behavioral changes.
Together with my own findings,
Software AG documentation and issues specific to Alltel, I produced the
'Natural 2.3 issues' document . This outlined :-
- All the code issues associated
with upgrading from Natural 2.2.8 to Natural 2.3.2.
- Described how these issues
would be detected.
- Provided a recommended
solution.
I developed software to
detect the new Natural 2.3.2 behavioural issues. This was used in conjunction
with SPL's N2000 tool together with CATALL reports in Natural 2.2.8 and Natural
2.3.2, to highlight all the potential issues. This system produced several
Microsoft Excel reports to show the Natural 2.3.2 impact at a management level,
down to detailed reports for the programmer.
I produced a user manual
describing the whole process.
I supervised a small team
to run this process and produce the necessary reports. The team was required to
analyse every potential issues, determine if it was an actual issue and provide
a recommended solution so that the system owner could easily make the necessary
changes.
My final task was to
produce a paper showing the new and enhanced features of Natural 2.3.2. along with appropriate examples of their use.
|
Jan 1998 |
- |
July 1998 |
TIMELESS SOFTWARE |
||||||
|
|
|
|
|
|
|||||
|
7 months |
|
|
Senior Consultant |
|
|
||||
|
|
|
|
NATURAL 2.2.8 |
ADABAS |
ACCESS |
|
|
|
|
|
|
|
|
VISUAL BASIC 5 |
WINDOWS |
EXCEL |
WORD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
As I have a thorough
background in Natural together with the numerous utility / tools I have
written, I became involved in the company's Year 2000 research. I produced
several documents detailing all the date-related issues with Natural.
I was formally moved to the
Development and Research team. My duties were varied. One of my earlier tasks
was to perform general research into the Year 2000 problem. This included
reviewing Y2K publications and existing products.
I worked with a small team
to design and create the only Year 2000 tool developed in
- Detailed interviews with language
specialists to find all the date related issues.
- Database design.
- Overall system design.
- Generalised parsing techniques
to find all variables, subroutines and external objects.
- Conversion rules, ranging from
simple replacement to parameterised code insertion.
- Programming in Visual Basic 5.
I wrote the parsing and conversion modules.
By using generalised
techniques, with rules built into the database, meant the tool was very
flexible and new languages could easily be applied.
I was also responsible for
the presentation of the tool. I created a CD-ROM using Lotus Screen Cam to be
reviewed by potential customers. In addition to the CD, I would perform 'live'
demonstrations of the tool to prospective clients and outline the company's
Year 2000 methodology.
|
Feb 1997 |
- |
Nov 1997 |
SOFTWARE AG |
||||||
|
|
|
|
|
|
|||||
|
10 months |
|
|
Business Analyst / Analyst Programmer |
|
|
||||
|
|
|
|
NATURAL ND |
ADABAS D |
ACCESS |
|
|
|
|
|
|
|
|
NATURAL LIGHTSTORM |
WINDOWS |
WORD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
I joined Software
AG’s Product Services Group, to create a Reinsurance Application package.
This system was in a client / server environment running on a Windows NT
platform, using Natural ND and Adabas D.
I worked on all areas of
the system but focused mainly on the following modules :-
- Table Maintenance
- Technical Accounting
- Treaty System
- Claims
- Security
- Reporting
My worked involved the :-
- Analysis of user requirements.
- Creating time quotes.
- Database design and creation.
- Program specifications.
- Coding and user training.
I become responsible for
the development standards and quality assurance. This led to a comprehensive
document to be used for future development projects, not only in
This also involved creating
common code for :-
- System security
- Validation and formatting
- Active help routines
- Executing Natural Reporter
templates online (to print or preview WYSIWYG reports)
In addition I conducted a
three day ‘hands on’ training course for the customer's data processing
department. The course was a great success with the customer evaluation reports
scoring the highest marks obtainable.
|
Apr 1996 |
- |
Sept 1996 |
SOFTWARE AG |
||||||
|
|
|
|
|
|
|||||
|
6 months |
|
|
Analyst / Programmer |
|
|
||||
|
|
|
|
NATURAL ND |
ADABAS |
ACCESS |
|
|
|
|
|
|
|
|
NATURAL LIGHTSTORM |
WINDOWS |
WORD |
|
|
|
|
|
|
|
|
UNIX |
|
|
|
|
|
|
My first assignment at
Software AG was with the Customer Support Group. My role was to assist
customers with their enquiries. This involved logging their problems, asking
relevant questions to get a full picture of the problem / request, searching
previous log records to find similar cases and ,where necessary, consulting
with Software AG’s technical experts in Darmstadt, Germany.
My duties included
reviewing and evaluating Natural Lightstorm, Software AG’s new Natural Adabas development
package for the PC platform. This is a system that can create GUI event driven
applications.
I also assisted in the
preparation and tuition of Software AG’s Mainframe Natural Coding Course.
I worked on an analysis and
debugging task using Natural on a UNIX platform, at a client site.
Later I moved to the
Product Services Group, where I worked on what was reportedly the largest data
analysis project in
I wrote several programs to
parse the data layouts of a variety of different database systems and to create
a mirror image of their existing tables into one common data pool (Microsoft’s
Access). I helped in the data analysis by merging and normalising the different
tables into one corporate model.
|
Apr 1995 |
- |
Jan 1996 |
CHASE MANHATTAN BANK LTD |
||||||
|
|
|
|
|
|
|||||
|
10 months |
|
|
Analyst Programmer |
|
|
||||
|
|
|
|
NATURAL |
ADABAS |
PREDICT |
TSO |
VISIO |
|
|
|
|
|
|
NATURAL CONNECTION |
WINDOWS |
WORD |
JCL |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
At Chase, I worked on the MID
system, a substantial Management Information Database used in
As well as working on
numerous maintenance tasks, I developed a series of conversion programs. These
would upgrade the existing data to be compatible with the new MID
specifications.
As I had a strong technical
background in Natural / Adabas, I was well suited to act in an advisory role
for other teams in the Financial Management System area.
My work included writing a
general purpose utility to view or update Adabas data along side its associated
DDM. This aided in system development and ensured a fast, accurate means of
creating and viewing database data.
|
Mar 1994 |
- |
Mar 1995 |
I.T.S.D. ( |
||||||
|
|
|
|
|
|
|||||
|
1 year |
|
|
Analyst / Programmer |
|
|
||||
|
|
|
|
NATURAL |
ADABAS |
PREDICT |
TSO |
VISIO |
|
|
|
|
|
|
NATURAL CONNECTION |
WINDOWS |
WORD |
JCL |
REXX |
|
|
|
|
|
|
NATURAL PROCESS |
CONSTRUCT |
|
|
|
|
|
I was a member of the Applications
Support Team. A team which provided technical help for all the application and
maintenance teams, ensured programming standards and system integrity was kept
intact and produced several productivity tools to aid in developing new
systems, debugging and program documentation.
I was responsible for
creating a new Library Update System on the IBM mainframe. A
system that controlled the flow of over 30 different object types between the
development, acceptance and production environments and across development and
production LPARs.
The major features of the
system are as follows :-
|
System
Integrity |
|
|
Automatic
Object Documentation |
|
|
Comprehensive
Design |
|
It was a powerful and
complex system requiring the creation of over 70 programs on-line and 20 batch,
with approximately 200 natural objects in total. The system used a number of
Natural products :-
- Natural Process
- NATRJE
- SYSMAIN
- Natural Connection
My work in developing this
system required :-
- Interrogating the SYSDIC and
FUSER system files
- Creating 7 DDMs on a UNIX
platform
- Creation of a user guide
My work on the team’s
utility tools allowed the developers to quickly form an accurate picture of an
application’s function flow so increasing productivity in both
development and maintenance.
|
July 1991 |
- |
Dec 1992 |
PEROT SYSTEMS CORPORATION |
|||||||
|
|
|
|
|
|
||||||
|
1 year 6 months |
|
|
Analyst / Programmer |
|
|
|||||
|
|
|
|
NATURAL 2 |
ADABAS |
|
|
|
|
|
|
|
|
|
|
|
JCL |
|
|
|
|
|
|
|
|
|
|
PREDICT |
DB2 |
|
|
|
|
|
|
Perot Systems is a
computing bureau responsible for producing a vehicle insurance package for one
of their customers, ‘The Robert Plan’, a
I worked on a number of different
areas on ‘The
Claims Team
Initially, as a member of
the claims team, I was assigned to the Subrogation / Arbitration Section. I
became solely responsible for the design, development (from overall system
structure to program design & coding, JCL, implementation and
documentation), maintenance, enhancements and overnight standby for over 30
reports.
Agency Team
I analysed the requirements
for the Claims Client Interface Reporting. This is the creation of several
monthly tapes containing statistical data for four different client companies.
This led to creating and updating a number of DB2 tables, within the Client
Interface system for use by other teams. Later, I became responsible for the
Premium Interface. The on-line Management Reporting also used data updated from
the Client Interface Reporting. Here, my duties included the creation and
maintenance of a number of on-line programs and ensuring the data reconciled
with other areas of the system.
Miscellaneous
My work included designing
and creating the ‘common forms module’ together with numerous ‘specific write’
forms programs. This involved consulting with the customer for their form
requirements and the Documerge team for the physical creation of the form. While
creating the form modules, I created a number of tools to help check form
compatibility and view form data. As the data was displayed along side it’s
associated LDA, the programmer could now quickly match the physical data with
the appropriate field name.
To help with testing and
maintenance, I created a set of DB2 load and unload programs. This would dump
selected table data on a policy by policy basis to be later loaded elsewhere on
the system.
|
Aug 1990 |
- |
Nov 1990 |
CHASE AMP BANK LTD |
|||||||
|
|
|
|
|
|
||||||
|
4 months |
|
|
Analyst / Programmer |
|
|
|||||
|
|
|
|
NATURAL 2 |
ADABAS |
|
|
|
|
|
|
|
|
|
|
|
JCL |
|
|
|
|
|
|
|
|
|
|
PREDICT |
COBOL |
|
|
|
|
|
|
Whilst with Chase AMP, I
worked on three separate systems
- FRA Forward Rate Agreement
- IRS Interest Rate Swaps
- CIF Customer Information Facility
FRA and IRS provided the
users with ‘banking tools’ to help in establishing and maintaining deals. CIF
was a customer database system.
On these systems, I
produced a number of programs that provided the user with information on market-to-market
Percentages, 90 Day Bond Equivalents and Future Rate Adjustments. On CIF, I
added Tax File Number details to a number of maintenance screens.
My work was mainly
development in Natural 2. This involved developing and maintaining Report Mode
and Structured Mode programs, complex maps, windows, help routines, Adabas 5
files and reports. I also gained exposure to Predict.
|
Mar 1988 |
- |
May 1990 |
RANK HOVIS Mc DOUGAL COMPUTING LTD |
|||||||
|
|
|
|
|
|
||||||
|
2 years 2 months |
|
|
Analyst Programmer |
|
|
|||||
|
|
|
|
NATURAL 1& 2 |
ADABAS |
|
|
|
|
|
|
|
|
|
|
|
JCL |
|
|
|
|
|
|
|
|
|
|
PREDICT |
COBOL |
|
|
|
|
|
|
The Rank Hovis Mc Dougal
Group is a set of companies specialising in the food processing industry. Part
of the group is RHM Computing which acts a computing bureau, serving other companies
both within and outside the group, including Manor Bakeries Ltd, the largest
I joined the Manor Bakeries
mainframe team, which was responsible for the invoicing, file maintenance,
sales ledger, management accounts, stores analysis and product analysis. My
role was to produce program specifications and code, from user requirements, to
create new or maintain existing programs. My duties included trouble shooting
and providing overnight standby.
The Manor Team was involved
in a project, which added VAT to its products. This affected all the systems
for the Manor Team, both mainframe and distributed. Approximately 50 mainframe
programs had to be developed or maintained. This project took over six months
to complete.
Another project was the ‘TV
Region Report’. This was a report that showed sales of certain products for
depots within a TV region. This would be run before and after a TV promotion to
compare the effectiveness of a commercial. I was solely responsible for this
project which involved:-
- Liaising with the user.
- Designing the system.
- Creating the system through
the entire project cycle.
- Developing and enhancing
programs in Natural for both batch and on-line.
|
July 1985 |
- |
Aug 1986 |
FORD MOTOR COMPANY |
▼ |
||||||
|
|
|
|
|
|
||||||
|
1 year 2 months |
|
|
Analyst Programmer |
|
|
|||||
|
|
|
|
MVS / XA |
DL/1 |
IMS |
DB/DC |
|
|
|
|
|
|
|
|
|
JCL |
EDITOR |
ROSCOE |
|
|
|
|
|
|
|
|
CICS |
COBOL |
TELON |
|
|
|
|
|
I joined the system
development team producing a system called SNOOPIE (System for Non-Production
Online Ordering In Europe). This was previously a paper
system that was responsible for the ordering of commodities used in the
production of a vehicle.
My duties included :-
- Designing a cross reference
for data between SNOOPIE and an existing system.
- Designing a functional model
for the Browse Supplier Database.
- Creating several commodity
maintenance programs using TELON (an Application Generator).
- Creating a ‘Failed Access’
report for a sign on screen.
My second placement was
working on a View-Data system for dealers throughout the