240 likes | 293 Views
Pacbase Modernization PACStudio and PAC2COBOL General presentation. March 2018. TELEBIG, in a nutshell. Since 1983, TELEBIG is specialized in the Modernization, Migration of Legacy applications portfolios towards Open Systems.
E N D
Pacbase Modernization PACStudio and PAC2COBOL General presentation March 2018
TELEBIG, in a nutshell • Since 1983, TELEBIG is specialized in the Modernization, Migration of Legacy applications portfolios towards Open Systems. • More than 90 projets de migration/modernisation succesfully performed • Clients on the 5 continents • Strong modernization experts team • Own tools (Migration+ Suite, PACStudio, PAC2COBOL, COBAngular…) • Cultural fixed price and commitment to results for project deliveries • Parteners of reckoned IT vendors • Global actors: Atos/Bull, CapGemini, EMC, HP, IBM, Oracle, SopraSteria, SQLI,… • Global technology leaders : Atos/Bull, Dell EMC, HP, IBM, Micro Focus, Microsoft, Oracle, Veryant, … • Specialists in modernization/migration: COBOL-IT, GT Software, Heirloom Computing, HTWC, Morphis, Oracle, SoftwareMining, TmaxSoft, Veryant,… • Member fournder of Bonede Alliance - www.bonede.com (50+ modernization experts) • Veryant France (exclusive representative of Veryant)
Pacbase replacement- Our double approach • PACStudio tool: tactical approach • Keep intact Pacbase functionnalities and results • Tactical solution as it allows with minimum risk to replace IBM Pacbase by an equivalent product therefore maintaining the applications in PAC language and generating the exact same source COBOL code as Pacbase. • Continuity, modernity • Today’s Development/Maintenance environment under Eclipse with any local relationnal database for the support of the imported Pacbase dictionnary • Local COBOL compile • Possible local testing • PAC2COBOL solution: strategic approach • Full disengagement of Pacbase artefacts to the profit of iso-functionnal fully maintenable code • Tool-based solution handled in project mode • The 2 options can be progressively combined
PACStudio and PAC2COBOL Pacbase Importation EXLI COBOL généré Pacbase PACStudio Génération COBOL Maintenable PAC2COBOL Dictionnaire PACStudio Génération
Pacbase replacement Continuity and Modernization • PACStudio is the answer to the request of many users of VisualAge Pacbase, very satisfied with the historical product, but question themselves regarding its replacement, no lmater that end of 2019 now • Development and maintenance compatible with Pacbase including regeneration of identical COBOL code as of Pacbase for the various target platforms (ie. z/OS, Bull GCOS, UNIX,AS/400, Windows, UNISYS,...).
PACStudio : Main caracteristics • « Visual Pacbase like » fully integrated Eclipse plug-in • Import of VisualAge Pacbase, from full or selective libraries into a relationnal database (commercial or Open source) • Maintenance at PAC / Pacbase Macro-langage level • Generators producing the same exact code as VAP, reducing to the minimum, or even eliminating Regression tests • Build from our own technologies combined with Open source components, without any other third party dependency, allowing us to provide PACStudio source code to our customers
PACStudio : Local compilation • PACStudioallows the local compilation of the COBOL generated code beforeitisshipped for final compilation to the targetenvironment • Today, associated COBOL compiler can be: • Veryant isCOBOL (generates Java) • GnuCOBOL (Full Open source) • Micro Focus COBOL • COBOL-IT • HeirloomElastic COBOL (generates Java, directly IBM z/OS Enterprise COBOL compatible) • TmaxSoft OFCOBOL (directly IBM z/OS Enterprise COBOL compatible)
PACStudio : Administrative functions • Library handling • Definition • Hierarchies • User rights management • Users/Groups (roles for Oracle) • Assigning privileges to specific users • Lock/unlock of entities • Backup/restore/replacement of historical sessions • Base / snapshots • Integrate with GIT/CVS/SVN • Dictionnary on shared SQL database and/or local XML synchronizable files
PACStudio : Implementation • Provision standard server/workstations infrastructure (in premises or Cloud) • Installation or integration of PACStudio plug-in alone or under a Mainframe development/ off-loadingenvironmentsuch as the Micro Focus Enterprise Developper, CompuwareTopaz , IBM RDZ, Metrixware Cobos,.. for example • Installation of the local databasehosting the dictionnary (PostgreSQL, MySQL, Oracle database, SQL Server, Tibero,…) • Import of librariesusingPacbase EXLI exported data • Integrationwith Customer preferred version control, …. tools • Validation of iso-code generation of the entirecustomer’s portfolio • Short training (one week) as thereisverylimited change for the developpers (Eclipse hands on required) • Continuous Assistance / hot line • Specificadjustements / simplifications availablefromour team, for instance to replace programs using PAF with native SQL • Optionnal PAC2COBOL
PAC2COBOL • « Product/Service » solution integrated in our tool/methodology Migration+, aiming at the modernization of Legacy portfolios • Objective : obtain from PACStudio dictionnary and sophisticated code modernisation tools, fully maintenanable, iso-functionnal COBOL applications. • Based on our code analysis and automated COBOL code modernization tools • Progressive levels of migration/optimisation • Documented Testing strategy • Recommandation of Testing tools for the target
PAC2COBOLTransformations • These are realized both with PACStudio specific generators completed by code refactoring/optimisation coming from our mining / analysis / transforming tools • Typical type of transformations (non exhaustive) : • Normes ANSI 85 • Indentation • Données (segments) référencées dans des COPY • Suppression des GOTO, PERFORM THROUGH • Restructuration des IF • Remplacement des GOTO DEPENDING par EVALUATE • Renommage des zones • Eventuelle restructuration des données COBOL (Niveaux multiples, OCCURS, REDEFINES) • Options de remplacement des macro-structures • Reprise de commentaires • Elimination des paragraphes redondants
PAC2COBOL: Project organisation • Project handled as a tool-based migration (Migration+) • Optionnal PoC / Proof of Concept • Alloting of programs to be modernized • Work sessions with Customer to select the transformation rules to be used for each type of lot/subsets of programs • Detailed specification for each transformation Lot • BIG BANG or progressive transformation • Set up of testing strategy • Test plans (scenarios, cas , baseline, interfaces) • Code instrumentation / probes • Test coverage • Regression Testing tools • Migration+ TestFramework • Preferred by Customer • Réalization of Regressions tests • Technical support and assitance