View previous topic :: View next topic
|
Author |
Message |
gadiyarampavan
New User
Joined: 22 Feb 2005 Posts: 18 Location: Hyderabad
|
|
|
|
Hello Folks,
As one of COBOL application program is executed successfully in the production environment and the same program is giving different results in Development environment.
We are using the concept of Dynamic call and we are processing the file input data by the execution of that program.
Please suggest me the reason behind this problem.
Thanks,
Pavan Kumar |
|
Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008 Posts: 8696 Location: Dubuque, Iowa, USA
|
|
|
|
Quote: |
As one of COBOL application program is executed successfully in the production environment and the same program is giving different results in Development environment. |
Are you absolutely sure the exact same file is being processed by production and development programs? Is there a database involved that could have different versions? What are the compile options for production and for development? How do you know the program hasn't been changed between development and production? |
|
Back to top |
|
|
gadiyarampavan
New User
Joined: 22 Feb 2005 Posts: 18 Location: Hyderabad
|
|
|
|
We are using the same file in production and Development also and this program is not dealt with any database. Here, the compiler options are also be same for the production and Development.
We are calling a sub program by using the Dynamic call.
Please let me know, any other causes for this problem as it is giving different results.
Thanks,
Pavan Kumar |
|
Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008 Posts: 8696 Location: Dubuque, Iowa, USA
|
|
|
|
Is the subprogram coming from a different library? Since you claim -- without any proof I note -- that you're getting different results in production and development, there is a difference in the environments. My experience has been that in such cases, the difference is usually some input file is different, or there's a difference in compiler options.
If you're absolutely sure that the compiler options are the same (I wouldn't be unless I visually verified them myself in both environments -- since a system upgrade could have been done between the development compile and production compile that caused a difference), and the same input files are being used, then the difference must be code related. Either the program itself is not the same, or one (or more) of the subprograms are not the same -- from different libraries. |
|
Back to top |
|
|
Terry Heinze
JCL Moderator
Joined: 14 Jul 2008 Posts: 1249 Location: Richfield, MN, USA
|
|
|
|
Are the same Language Environment run time libraries involved in Dev as in Prod? Also, what exactly is your definition of "different results"? |
|
Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006 Posts: 19244 Location: Inside the Matrix
|
|
|
|
Hello,
Quote: |
the same program is giving different results in Development environment. |
Is there some reason that you have not shown what the different results are?
How have you verified that the exact same module is being executed in development and production? The exact same called module?
Simply said, the process runs differently because of different executables or different data. It may help if you post the execute jcl from this step. |
|
Back to top |
|
|
Terry Heinze
JCL Moderator
Joined: 14 Jul 2008 Posts: 1249 Location: Richfield, MN, USA
|
|
|
|
Pavan,
It's not considered good manners to post the same question on multiple bulletin boards within 13 minutes of each other. |
|
Back to top |
|
|
|