Hi,

I am running into an issue trying to access a DB2 stored procedure from VB using Neon Shadow. After making some changes to the DB2 SP, I compile and bind it to a package and then have the package as part of the plan. This plan is given while creating the DSN for my VB app. However, though the DSN points to my plan, the load module of the SP accessed is not from my library, but the default production/development library, to which I dont have access to put my code. I know that while executing a batch DB2 program, we specify the plan (which will have the DBRM) and the load library in the run JCL. However, while calling from VB using Shadow, I dont see any place where I can specify the load library, so that the VB app calls the correct modified code. Has anybody run into this issue or can help me get some insight into this?

Thanks.