Program preparation in db2

But remember, we converted business logic, not SQL. This is a built-in capability of CloudFrame that allows you to simply reuse the same package information that was already generated and bound earlier. And that is a good thing, right? Conversion and migration are already time-consuming processes; eliminating performance problems due to changing access paths means that one less issue to worry about during a COBOL to Java conversion when you use CloudFrame.

Post a Comment. Posted by Craig S. No comments:. Regards, CKumar. Back to top. When we change SQL query code in a Cobol-Db2 program, is it necessary to follow the program preparation steps again. Posted: Fri Oct 09, am. A typical Interview question. You should check over this forum first and then you can save your time expecting answers. Thank you. But can any body give me clarity on these queries. What exactly happens during each scenario? When we say : do the rebind due to some SQL code change, I mean it's complete program preparation steps again.

Correct me if I'm deviating. Posted: Fri Oct 09, pm. What 'exactly' happens varies from shop to shop, but in general: 1 If you change your SQL, you will need to PreCompile or equivalent , Compile, Link your program. You need to Compile your program even though you only made an SQL change. Compile 4. Translate 5. Posted: Tue May 24, pm. Hi, Thanks for u r reply priya. Is it possible for u to get me the whole procedure so that i can know the steps and dd names present in that procedure.

And i want to know what is that second "Translate" step will do? Just check the sample Compile JCL from ibmmainframes. Posted: Wed May 25, am. Posted: Wed May 25, pm. Compile and linkedit you know to check the syntax and genrate the load module Executable.