Post on 17-Dec-2015
Enterprise COBOL Executive Brief
Mike Montgomery, DirectorDivision of Portfolio ManagementOffice of Application Development
Commonwealth Office of TechnologyCommonwealth of Kentucky
October 27, 2005
©2005 Commonwealth Office of Technology 2
Background
• COT maintains (3) production COBOL compilers
– COBOL 68– COBOL II– COBOL 390
• IBM service support has been discontinued for all three COT production COBOL compilers since 12/31/2004
• IBM currently provides service support for Enterprise COBOL for z/OS, version 3.4
• 1,344 COBOL 68 programs in production (8%)
– COT (1,210)– CHFS (134)
• 13,797 COBOL II programs in production (85%)
– COT (11,885)– CHFS (1,912)
• 1,081 COBOL 390 programs in production (7%)
– COT (1,078)– CHFS (3)
©2005 Commonwealth Office of Technology 3
Issues
• Compiler Support– Current compilers not
supported
• XML Support– Current practice is brute
force, roll your own approach
• Service Oriented Architecture (SOA)– Code Integration
• Enterprise Java• .NET
©2005 Commonwealth Office of Technology 4
Plan
• Implement Enterprise COBOL for z/OS. • Sunset the COBOL 390 compiler one year from date of
implementation of Enterprise COBOL.• Be prepared to review COBOL II applications for
potential to upgrade.
©2005 Commonwealth Office of Technology 5
Enterprise COBOL
• Vendor supported• Backwards compatible w/COBOL 390
– Minimum impact
• XML Support– EMARS interfaces– Federal interface projects like MCSIA
• Integration and Interoperability Support– .NET through Enterprise Java– Enterprise Java to COBOL Interfaces– COBOL to Enterprise Java Interfaces– Positions for SOA and ESB
©2005 Commonwealth Office of Technology 6
COBOL 390 Sunset
• Efficiency– Eliminates one unsupported compiler (COBOL 390)– No net gain of COBOL Compiler support– Some reduction in cost to maintain– Minimizes cost of COBOL compiler licenses renewal
• Sunset period (1 yr)– Reduces pressure to convert all at once
• Cost– Cost expected to be minimal (backwards compatible, smallest
number of programs to review)
©2005 Commonwealth Office of Technology 7
COBOL II Sunset
• Efficiency– Eliminates add’l unsupported compiler (COBOL II)– Some reduction in cost to maintain– Minimizes cost of COBOL compiler licenses renewal
• Sunset period (TBD)– Reduces pressure to convert all at once
• Cost (TBD)– May not be practical for all systems– Requires system-by-system review