Visual COBOL Development for         Unix & Java        Darren Self & Paula Willis         Product Development
Visual COBOL for Eclipse• Complete COBOL development environment  – Modern IDE  – Remote development  – Native and managed...
Why work remotely?                 3
RSE/SAMBA            • Project Creation/Maintenance            • Compilation            • Debugging     4
Why hold with tradition?© Daily Telegraph                    5
From this...               6
To this...             7
Develop on all platforms     Well, almost!          © Science Museum, London
Remote Development Supported Platforms     Desktop Eclipse IDE       Server Hubs                           9
Seeing more details...10                 © Darren Self, 2012
11
Java                                          JVMsource code               managed codejava (.java)               JVM byte...
COBOL                                           JVMsource code                managed codeCOBOL (.cbl)                JVM ...
Mixing languagessource code              managed code   JVM              COBOL              compiler COBOL                ...
What is JVM COBOL?• COBOL with extensions to take advantage of features of  the JVM framework                set/invoke   ...
Choice of 2 runtime configurations                                   Pure runtime                          Impure runtime ...
SmartLinkage•   If legacy COBOL app contains COBOL data types in linkage•   Set ilsmartlinkage directive on legacy COBOL a...
Darren.Self@microfocus.comPaula.Willis@microfocus.com
Upcoming SlideShare
Loading in …5
×

Visual COBOL Development for Unix and Java

1,137
-1

Published on

Do you want to reinvigorate your COBOL development environment for Unix? How about bringing your COBOL business logic into the Java ecosystem?
In this session we will investigate two major features of the Visual COBOL product line. You will see how the power of the Eclipse IDE can be used to develop your COBOL applications on remote Unix machines. You will also see how Java technologies can breathe new life into your COBOL code.

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
1,137
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
1
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Why?Limited hardwareGeographical realitiesCompile with local librariesThird party limitations (Tuxedo for instance)Debug on platform where code will be running
  • RSE over TCPIP – can be secured over SSLOptional SAMBA connection for project accessLong running daemon on server Starts processes per user under their authentication These processes control compilation and debugging of remote applications
  • Connect to anything – almost!
  • Visual COBOL Development for Unix and Java

    1. 1. Visual COBOL Development for Unix & Java Darren Self & Paula Willis Product Development
    2. 2. Visual COBOL for Eclipse• Complete COBOL development environment – Modern IDE – Remote development – Native and managed code 2
    3. 3. Why work remotely? 3
    4. 4. RSE/SAMBA • Project Creation/Maintenance • Compilation • Debugging 4
    5. 5. Why hold with tradition?© Daily Telegraph 5
    6. 6. From this... 6
    7. 7. To this... 7
    8. 8. Develop on all platforms Well, almost! © Science Museum, London
    9. 9. Remote Development Supported Platforms Desktop Eclipse IDE Server Hubs 9
    10. 10. Seeing more details...10 © Darren Self, 2012
    11. 11. 11
    12. 12. Java JVMsource code managed codejava (.java) JVM bytecode Java ... class c1 compiler iconst_0i aload { javac istore_1 } jsr .class/.jarWrite Once Run Anywhere
    13. 13. COBOL JVMsource code managed codeCOBOL (.cbl) JVM bytecode Program-id P COBOL ... working-stor compiler iconst_0i procedure di aload display “hel jvmgen istore_1 goback. jsr .class/.jar
    14. 14. Mixing languagessource code managed code JVM COBOL compiler COBOL Java compiler ... Java JVM bytecode JRuby compiler JRuby
    15. 15. What is JVM COBOL?• COBOL with extensions to take advantage of features of the JVM framework set/invoke set/invoke OO syntax OO syntax inner-class inner-class annotations annotations exception handling exception handling collections collections declare declare Core COBOL extension methods extension methods sync verb sync verb predefined types predefined types linkage-less linkage-less enums enums and much more.... and much more....
    16. 16. Choice of 2 runtime configurations Pure runtime Impure runtime native native native app app app app app myapp.jar/class myapp.jar/class runtime componentsMicro Focus FileHandler SQL Native Native SQL mffilehandler.jar mfsqljvm.jar FileHandler pure runtime runtime mfcobolrtspure.jar mfcobolrts.jar & mfcobol.jar • Pure JVM runtime, JVM FileHandler, JVM SQL • JVM runtime with native interop support • No support for interop to native code • Calls the native FileHandler
    17. 17. SmartLinkage• If legacy COBOL app contains COBOL data types in linkage• Set ilsmartlinkage directive on legacy COBOL app• On compilation auto-generates managed types• So you can access COBOL linkage data from other managed languages transparently. – No hand-written wrapper classes needed – No changes required to the original code – COBOL data shown in C#/Java/COBOL intellisense
    18. 18. Darren.Self@microfocus.comPaula.Willis@microfocus.com

    ×