3. What new in the latest update
What is managed code and why should you care
Reusable Frameworks
Moving to managed code
Agenda
4. New capabilities for working with Microsoft Visual Studio 2013 and
Microsoft .NET 4.5
New platform support for Windows 8.1, Oracle Linux 6.5, Red Hat
Linux 6.5 and AIX 7.1
Many enhancements to increase runtime performance
JDBC Connection Sharing
And more …..
What’s New in 2.2 Update 1
5. Managed code = .NET or JVM
Native code or unmanaged = everything else
Terminology
6. Virtual execution environment
• Portable Intermediate Language
• JIT
Garbage collection
Object-oriented
Extensive frameworks/Class Libraries
COBOL code generated directly to byte code
What is Managed code
12. Debug C#/Java and COBOL together
End-to-end testing
Single IDE for building and testing
Single debug process
Same developer
Why managed code
End-to-end debugging
17. Good to go in .NET and JVM
Be mindful of performance for IO intensive batch operations
Significant improvements to file handling operations with Visual
COBOL VC 2.2+
File Handling
18. COBOL programs can contain embedded SQL
Your choices:
1. Database vendor pre-compiler such as Oracle
Pro*COBOL
a) COBSQL provides single compile-step integrated with the IDE
2. Micro Focus OpenESQL
a) Connect to any ODBC, JDBC, ADO.NET enabled data source
Database access Primer
procedure division.
exec sql
connect to Northwind
end-exec
if sqlcode not = 0
display "Error during CONNECT : " SQLCODE
display mfsqlmessagetext
goback
end-if
19. Oracle does not support managed code using Pro*COBOL
Use OpenESQL for JDBC and ADO.NET
Use Pro*COBOL directives MODE=ANSI and FIPS to determine non-
standard ANSI syntax
Some Oracle extensions supported by OpenESQL other extensions
will need to be reworked
No PL/SQL support
Database access under Managed Code
21. To do anything “Thin” will involve an app server
All major Java App Servers supported in Visual COBOL 2.2
• Tomcat
• JBOSS
• Webshere
• WebLogic
Web Services and JSPs
Java coding required
See community.microfocus.com for walkthrus
Java App Servers
22. COBOL JVM Roadmap
R3/4
JVM COBOL
Preview
JVM COBOL
Launch
2.0
JDBC support
Pure JVM
2.1
Web Container
support under
Tomcat
Web services, JSP
and Servlet
deployment
2.2
Web container
support
WebLogic
Websphere
JBOSS
2.3
EJB container
deployment
From desktop to J2EE EJB deployment…
…re-use core COBOL applications directly within
the Java Virtual Machine
23. • COBOL, Java or C#, VB…Presentation
• OO COBOL Wrapper
• Run unit
Business Access
• Existing Procedural COBOLBusiness logic
• Isolated data IO modulesData Access
• RDBMS
• Data filesData
Modernizing your architecture
24. Dialog System
3rd Party support
Win32APIs
CBL_ routines
Pointers
Native code
Other considerations
25. Micro Focus Product Documentation
Visual COBOL Forum at the Micro Focus Community Site
http://community.microfocus.com – Our community Site
Managed Code Tutorial in the Product Documentation
Web Based Training Resource
Resources to get you started
27
26. Managed code is a fantastic way to modernize your application
• Get more done using Java and .NET frameworks
• Create new user interfaces and services based deployments
Be prepared
• New skills – OO, Java, .NET, frameworks
• Check for unsupported options such as APIs and database pre-
compilers
Speak to Micro Focus before you start or at least, let us know once
you’ve deployed!
Summary
• CALL statements are on average 30% faster
• Generation of very large programs is now maximized enabling the JVM to generate code for faster execution. The speed of this is often many times faster than previously seen.
• Packed decimal operations are now 200-300% faster
• File and directory searching in .Net is now over 600% faster
• File handling operations are up to 15% faster.
Deploying COBOL applications within the JVM often means COBOL applications will provide backend functionality to Java modules. To help applications share resources across COBOL and Java, COBOL applications can now access existing database connections created in Java, ensuring efficient use of database resources and consistency of transactional operations
We provide the tools to deploy COBOL and take advantage of the platform
Documented IL means everything can just about integrate with everything else
If we spent our time writing new apps all the time just to take advantage of the latest innovation, we’d always be out of date