Raphel Sagayaraj

COBOL Deployment Working Storage Variable change issue

Discussion created by Raphel Sagayaraj on Apr 25, 2013
Latest reply on Apr 26, 2013 by Raphel Sagayaraj

We are recently started working on COBOL version of Blaze Advisor 6.5. We have a baselined version from which the COBOL deployment file is generated and integrated into mainframe environment. On top of this baselined version, we made few changes, and generated the deployment file. When we compare this COBOL file with the one generated from the baselined version, we see that many of the working storage variable names have changed. It does not have any functional impact, but the working storage variable names have changed in the latest code. Is it an issue or something that always happens when you generate COBOL deployment file without affecting the functionality?