|
View previous topic :: View next topic
|
| Author |
Message |
vijikesavan
Active User
Joined: 04 Oct 2006
Posts: 118
Location: NJ, USA
|
|
|
|
Hi,
I have program A calling program B, which in turn calls programs C-Z.
I made some changes in program B. Compiled to my local dataset.
Provided the following overrides, but it is not taking my modified load module and still pointing to production library.
Prod load library is required for other modules.
My JCL
| Code: |
//STEPXXS.STEPLIB DD DISP=SHR,DSN=<My PDS>
// DD DISP=SHR,DSN=<Prod Load lib>
// DD DISP=SHR,DSN=SYSDB2.DBMS.DEVR1.SDSNLOAD
//* |
My proc has
| Code: |
//STEPLIB DD DISP=SHR,DSN=SYSDB2.DBMS.DEVR1.SDSNLOAD
// DD DISP=SHR,DSN=<Prod load lib> |
Have anyone faced this problem? pls help
Appreciate your help and time.
Thanks,
Viji |
|
| Back to top |
|
 |
Pedro
Global Moderator
Joined: 01 Sep 2006
Posts: 2547
Location: Silicon Valley
|
|
|
|
Did you look at your PDS to ensure it has your new program? Is there some eyecatcher there so you can readily see it is the new version?
Did you linkedit? |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
Is the "old" version of pgmB statically linked into pgmA? |
|
| Back to top |
|
|
vijikesavan
Active User
Joined: 04 Oct 2006
Posts: 118
Location: NJ, USA
|
|
|
|
| yes. program B is statically linked to Program A. I compiled first B, then A pointing to the modified load ilb. |
|
| Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8696
Location: Dubuque, Iowa, USA
|
|
|
|
Possibility 1: <MY PDS> doesn't contain the program. In this case, the production version is being picked up via the concatenation. Try removing the concatenation and run with only your PDS as the STEPLIB; if it doesn't find the program then your PDS needs to be updated with the program.
Possibility 2: STEPXXS isn't the right step to override the STEPLIB in. Verify your override statements (XX and X/ in the expanded JCL listing) are correctly located.
Possibility 3: <MY PDS> contains the production version of the program. Try removing the concatenation and run with only your PDS as the STEPLIB; if it still picks up the wrong version then you know your PDS has the wrong version.
Possibility 4: <MY PDS> isn't a load library. Run AMBLIST on your <MY PDS> for the program to confirm the load module attributes. |
|
| Back to top |
|
|
Pedro
Global Moderator
Joined: 01 Sep 2006
Posts: 2547
Location: Silicon Valley
|
|
|
|
| Quote: |
| program B is statically linked to Program A. |
Sorry, but your statement is not clear to me.
Is program B a load module by itself? That is, is 'B' a member of the load lib?
Or is there a single load module which consists of both program A and program B?
| Quote: |
| I compiled first B, then A pointing to the modified load ilb. |
The key is not the compile, but the link edit. |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
It may help if you post the CALL from pgmA and link edit output from pgmA.
You could also try to recompile pgmA usng a dynamic call . . . |
|
| Back to top |
|
|
vijikesavan
Active User
Joined: 04 Oct 2006
Posts: 118
Location: NJ, USA
|
|
|
|
Thanks everyone for your time.
One of the member in link library was not correct...Its fixed now.
Thanks,
Viji |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Good to hear it is working - thank you for letting us know 
d |
|
| Back to top |
|
|
|
|
