log on


Conversions – Log-On Software Experience

Log-On Software has successfully performed a vast number and different types of conversion projects both locally and internationally.

Our conversion philosophy is one that always chooses the best approach that fits the task at hand – sometimes with homemade tools – sometimes with purchased tools – in order to achieve the aim of the best possible conversion result – producing maintainable code, adhering to time limits and optimize the costs involved for the customer.

More than 250 professionals are working for Log-On Software with a wide range of technical and project management skills – from IBM mainframes over to Unix and Windows platforms – including DBA’s, System programmers, application programmers in a wide variety of programming languages and QA teams for testing requirements.

Following customers used Log-On Software for their conversion projects:

• Several local commercial banks
• Mortgage bank
• Transport company
• Credit Card company
• Government agencies

Y2K projects (Conversions and verifications) were performed for a:

• Large supermarket chain in Australia
• Large industrial company in Germany
• Large bank in Germany
• Travel advice company in Germany
• Administration of a city in Germany

EURO projects were performed for a:

• Administration of a city in Germany
• Savings bank in Germany

Conversions types

• Assembler to Cobol – manual conversion
• Cobol dialect upgrades (Cobol for MVS, Cobol for VSE, Cobol1 to Cobol2 etc) – tool conversions
• Y2K/EURO conversions – tools and some manual work
• Support for introduction of LE (Language Environment) – mainly manual approach
• Single to multi-bank conversion – tools and some manual work
• Y2K verification services – use of tools

Those projects included but were not limited to following major tasks:

• Initial survey of code to be changed
• Help with conversion strategy
• Clusterization of conversion packages
• Developing of standard, pre-tested solutions including performance checking
• Code fixing with semi-automatic approach
• Delivery of packages into test environments
• Database/File/Field changes – developing of conversion routines
• Retrofitting of sources
• Test support
• Close relationship with project management and different application managers