MVSFORUMS.com

whizkid79 · Beginner Joined: 29 Sep 2004 Posts: 53 Topics: 14

Hi,

I have a PL1 module A that calls PL1 module B. Module B is called by other PL1 modules as well. Whenever i make a change to module B and link it with module A and load it, the latest changes are not reflected. Whereas the other modules that call module B get the latest changes. Is there any way to forcefully make the latest version of the load to be picked up?

Thanks,

Raaj · Posted: Tue Dec 07, 2004 4:30 am Post subject: Latest load module Pick

Can you look the concatenation of the loadlibs.May be incorrect?

kolusu · Posted: Tue Dec 07, 2004 8:55 am Post subject:

whizkid79,

How is the Module A calling module B? is it a dynamic call or a static call? Raaj's suggestion also might be a cause.

Kolusu
_________________
Kolusu
www.linkedin.com/in/kolusu

whizkid79 · Beginner Joined: 29 Sep 2004 Posts: 53 Topics: 14

Kolusu,
Its a static call.
Raaj...Can you please elaborate on the concatenation. I couldn't understand.

Whizkid79

kolusu · Posted: Tue Dec 07, 2004 9:44 am Post subject:

whizkid79,

whizkid79 · Beginner Joined: 29 Sep 2004 Posts: 53 Topics: 14

All the 3 steps were done. But of no use.

kolusu · Posted: Tue Dec 07, 2004 11:00 am Post subject:

whizkid79,

Also make sure that you are picking the correct loadlib in your steplib

ie.

whizkid79 · Beginner Joined: 29 Sep 2004 Posts: 53 Topics: 14

I'm using the correct loadlib.

Phantom · Posted: Tue Dec 07, 2004 11:29 pm Post subject:

Whizkid79,

I hope the load libraries of PGM A & B are the same. Just wanted to confirm. Make sure they are compiled and stored in same load PDS or when link-editing PGM A make sure u provide the load of PGM B.

Thanks,

Phantom

whizkid79 · Beginner Joined: 29 Sep 2004 Posts: 53 Topics: 14

The load libraries are same. All the loads are stored in one PDS and the same is used in the JCL.

Raaj · Posted: Wed Dec 08, 2004 12:31 am Post subject: Latest load not picked up

Hi Whiz,

Better post the Jcl with the steps compile and link edit?

Raaj.

semigeezer · Posted: Wed Dec 08, 2004 1:37 am Post subject:

Did A completely finish or is it still in use between changes? What environment are you running (TSO, ISPF, batch, CICS, etc). Most likely, a copy of A is still in storage because A is still being run. A could also be in a library which is controled by LLA or VLF or TRX (or similar) and they need refreshing. You need to find out where the actual module is being loaded from (disk, job pack area, link list or LPA). It probably isn't coming from where you think it is. If this is in TSO or ISPF, use ISRDDN to find out where it is being loaded from. You may also want to browse the load module to see if the CSECT for B is there with the changes you expect (add a static eye-catcher), or use a debugger or TSO test to be sure the module is even being called at all. Or change A and see if you are seeing those changes. You could also link it non-reentrant. There are only a few ways you will get this problem, but many ways to track it down.

kolusu · Posted: Wed Dec 08, 2004 5:29 am Post subject:

whizkid79,

Are your pgms CICS or IMS DC programs? If it is a CICS pgm then did you issue a NEW COPY ? If not then you will pick up the old load module.

If it is a pure batch program then ignore my post

Thanks

Kolusu
_________________
Kolusu
www.linkedin.com/in/kolusu

whizkid79 · Beginner Joined: 29 Sep 2004 Posts: 53 Topics: 14

Its an ordinary program. No CICS or DC.
Everytime i'm compiling the called module (module B), its overwriting the existing object load.

dtf · Posted: Fri Dec 10, 2004 4:07 pm Post subject:

Start by completly deleting the load modules for the PGM-A, and PGM-B. Then follow the procedure above (Compile and Link order).

There are a number of possible reasons for your problem

You may not actually be replacing the subroutine module in the load library

You may not be getting a new copy of your subroutine into the composite load module

You may have not named the subroutine correctly, and thus it is not picked up

The Composite load module is not being named properly, and so you are not executing what you think you just recompiled

Anyway, if you delete the existing modules, and start from scratch it may identify the problem for you.

If you are not doing explicit includes in a link deck, then you are automatically resolving external modules (subroutines). These would be pulled from the SYSLIB, and would be pulled from the libraries in the order of the contcatonation
________
Jaguar XK history