|
View previous topic :: View next topic
|
| Author |
Message |
GaganGarg
Active User
Joined: 31 Mar 2010
Posts: 134
Location: India
|
|
|
|
Hi All,
In our project, for COBOL Stored procedures, we are facing sqlcode -805 as and when web screen accesses the SP. Whenever we make any changes to SP and we do compile and bind, we are getting this error. We believe that the reason behind the error might be latest bind info is not getting updated in Catalog tables immediately. Because without making any fix, the issue is automatically getting corrected after 5 to 6 hrs. Not sure how to reduce this delay and see the results of our code changes in SP immediately. Please advise any suggestions if you have faced similar issue before.
Options that we tried:
1. Dropped the Stored procedure ; recreated and then bound the SP.
2. Deleted the load and DBRM. Compiled and bound the SP.
Both of the above options didn’t solve the issue.
Thanks |
|
| Back to top |
|
 |
dbzTHEdinosauer
Global Moderator
Joined: 20 Oct 2006
Posts: 6966
Location: porcelain throne
|
|
|
|
| Quote: |
| might be latest bind info is not getting updated in Catalog tables immediately |
you have it backwards. the bind updates the db2 catalog tables immediately.
That's one of the reasons db2 has to be running to accomplish a bind.
you can pre-compile without db2, but you need db2 to bind - because it updates the catalog tables...
what you may wish to explore:
the loadlib containing the sp
and working copy of the loadlib
are are maintained in memory.
Applications like CICS and Websphere need their 'loadlib's refreshed
and for CICS
a newcopy of the loadmodule is required
if the module has been changed and you want to see the effects of that change. |
|
| Back to top |
|
|
GuyC
Senior Member
Joined: 11 Aug 2009
Posts: 1281
Location: Belgium
|
|
|
|
| WLM_REFRESH ? |
|
| Back to top |
|
|
GaganGarg
Active User
Joined: 31 Mar 2010
Posts: 134
Location: India
|
|
|
|
The solution is to do WLM refresh. In our case, refresh was done automatically after certain hours and we were concentrating on finishing unit testing. In future, if we face this issue, we will do WLM refresh.
Thanks all for your valuable inputs  |
|
| Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006
Posts: 6250
Location: Mumbai, India
|
|
|
|
If you do WLM refresh and this is the "common WLM", all the SPs executing in that WLM will loose what they might have in spool. Check with your support, if you can get a dedicated subsystem ID of the DB2 subsystem with which the WLM environment can be associated; in simple terms if you can get a different address-space for your application/team. Otherwise other team-members might hunt for you to and not with very good intentions ...  |
|
| Back to top |
|
|
|
|
