You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The moment you update to COBOL 6.4 please add an exercise or lab how to call java from cobol (in batch without OO-COBOL) and vice versa.
It will be helpful for COBOL-starters to see that this is possible and how to do it.
experienced COBOL-devolopers will get value from this, too. It is much harder than shown in many presentations to this.
But it is very usefull, cause COBOL has features java will not get that quick and java has features cobol will definitely not get. To get to know how to connect the worlds will give COBOL-developers abbilities they couldn't imagine.
Currently using java is done with writing info from cobol to file. In a second step (new job or jobstep) java reads that file to work with that information. There are many reasons why java doesn't access the same data-files like COBOL did before. The most common is, that in COBOL is the business-logic is and no one will rewrite that to java 1:1.
With COBOL 6.4 there will be more flexibility - but people need to get to know it.
Problems
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered:
Thank you for the feedback. We are currently running Enterprise COBOL for z/OS V6R4 on the lab system. However, Java and COBOL interaction are still in our roadmap as something we can look into in the future.
Will keep this in mind when there are progress being made for COBOL Communications with Java Methods.
Course Details
GitHub
Description
The moment you update to COBOL 6.4 please add an exercise or lab how to call java from cobol (in batch without OO-COBOL) and vice versa.
It will be helpful for COBOL-starters to see that this is possible and how to do it.
experienced COBOL-devolopers will get value from this, too. It is much harder than shown in many presentations to this.
But it is very usefull, cause COBOL has features java will not get that quick and java has features cobol will definitely not get. To get to know how to connect the worlds will give COBOL-developers abbilities they couldn't imagine.
Currently using java is done with writing info from cobol to file. In a second step (new job or jobstep) java reads that file to work with that information. There are many reasons why java doesn't access the same data-files like COBOL did before. The most common is, that in COBOL is the business-logic is and no one will rewrite that to java 1:1.
With COBOL 6.4 there will be more flexibility - but people need to get to know it.
Problems
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: