View previous topic :: View next topic |
Author |
Message |
edkir98 Beginner

Joined: 27 Aug 2007 Posts: 102 Topics: 42 Location: Chennai
|
Posted: Thu May 14, 2009 10:21 am Post subject: Output display in Stored Procedure |
|
|
We got an issue while executing a stored procedure builder for a Stored Proc to return a result-set. When it was run in the development environment the column names were displayed as 1,2,3.. but when it ran in prod the original column names of the result set is displayed.
eg.. in DEV
Code: |
1 2 3
ABCD 678 2009-05-02
EFGK 536 2008-02-02 |
in PROD
Code: | Name Acct_No Date
ABCD 678 2009-05-02
EFGK 536 2008-02-02 |
can some one explain what the reason for this could be.. is there any compiler settings that we need to change. _________________ Thanks |
|
Back to top |
|
 |
kolusu Site Admin

Joined: 26 Nov 2002 Posts: 12380 Topics: 75 Location: San Jose
|
Posted: Thu May 14, 2009 10:42 am Post subject: |
|
|
edkir98,
May be somebody qualified the columns in the development region for testing and removed it later
Code: |
select Name 1
,Acct_no 2
,Col_Date 3
from table
|
|
|
Back to top |
|
 |
edkir98 Beginner

Joined: 27 Aug 2007 Posts: 102 Topics: 42 Location: Chennai
|
Posted: Thu May 14, 2009 10:45 am Post subject: |
|
|
hi Kolusu.. Thanks for your response.. its the same code which was promoted to production.. _________________ Thanks |
|
Back to top |
|
 |
kolusu Site Admin

Joined: 26 Nov 2002 Posts: 12380 Topics: 75 Location: San Jose
|
Posted: Thu May 14, 2009 12:22 pm Post subject: |
|
|
edkir98,
There is a setting on Application programming defaults pane DSNTIP4 which contains a field DESCRIBE FOR STATIC ===> YES. If it is set to YES then your OUTPUT from SP will have the actual column names instead of relative column names like (1,2,3...)
I am guessing that the test version had that set to NO (which is default for DB2 v7 and lower). DB2 v8 and v9, the default value is YES.
Contact your DBA and see if that is the cause
Kolusu |
|
Back to top |
|
 |
edkir98 Beginner

Joined: 27 Aug 2007 Posts: 102 Topics: 42 Location: Chennai
|
Posted: Thu May 14, 2009 2:19 pm Post subject: |
|
|
Kolusu, i've raised this with DBA. They said they'll get back. I'll definitely post the result of their investigation. Thanks a ton!! _________________ Thanks |
|
Back to top |
|
 |
edkir98 Beginner

Joined: 27 Aug 2007 Posts: 102 Topics: 42 Location: Chennai
|
Posted: Tue May 26, 2009 4:38 am Post subject: |
|
|
hi Kolusu.. you were right..but even in the testing region we have DB2 8 but the parameter was set as NO.. the DBA contacted IBM and had the issue fixed.. Thanks!! _________________ Thanks |
|
Back to top |
|
 |
kolusu Site Admin

Joined: 26 Nov 2002 Posts: 12380 Topics: 75 Location: San Jose
|
Posted: Tue May 26, 2009 9:12 am Post subject: |
|
|
edkir98 wrote: | hi Kolusu.. you were right..but even in the testing region we have DB2 8 but the parameter was set as NO.. the DBA contacted IBM and had the issue fixed.. Thanks!! |
edkir98,
So what exactly is the problem?
kolusu |
|
Back to top |
|
 |
edkir98 Beginner

Joined: 27 Aug 2007 Posts: 102 Topics: 42 Location: Chennai
|
Posted: Thu May 28, 2009 4:34 am Post subject: Re |
|
|
hi Kolusu..sorry for the delayed reply.. we had a meeting with IBM yesterday.. It was found that the DESCSTAT parameter was set to YES by some new software and package(which i dint understand during the call - something related to the DBA task) that the DBA was installing in PROD that day and when the time the SP was bound in prod, the DESCSTAT parameter was YES. So now they changed it to NO and rebound the SP. now its ok.
Thanks for your help. Your suggestion helped in taking the first step. _________________ Thanks |
|
Back to top |
|
 |
dbzTHEdinosauer Supermod
Joined: 20 Oct 2006 Posts: 1411 Topics: 26 Location: germany
|
Posted: Thu May 28, 2009 4:38 am Post subject: |
|
|
edkir98,
isn't it nice that IBM can referee between departments in your organization? _________________ Dick Brenholtz
American living in Varel, Germany |
|
Back to top |
|
 |
|
|