Static linking and changeman

[shreya19]

Hi all,

I have a COBOL program A to be modified. It has static call to another program B.

I have included these two programs to the changeman package and promoted and tested it, it works well. However the Audit step fails.

It gives SYNCH8 and says there are 30 other programs that call program B and they have to be compiled first and then program B.

If I include these 30 programs, these further call and are called by many other programs around 200 or more.

Please suggest me how to resolve this.

Thank You!!!

[shreya19]

Tried using dynamic linking. Then the job that calls these COBOL programs failes with S0C1 abend

[enrico-sorichetti]

something smells foul in the state of denmark

if You had changed also B then it would be proper to rebuild/promote/WTF all the callers

but since YOU told that only A was changed no reason to rebuild all the other thingies ?

I have a COBOL program A to be modified. It has static call to another program B.

why not speak to our support ???

[shreya19]

Unfortunately there is no support

[enrico-sorichetti]

Unfortunately there is no support

hard to believe,
who did the CHANGEMAN customization ?

I have not worked with CHANGEMAN
but under SCLM and ENDEVOR noooo way for something like that to happen
if the PACKAGES have been defined properly

just think a bit please, when You modify something
the integrity/consistency is guaranteed by rebuilding all the ancestor chain ( THE CALLERS )

no reason to rebuild the descendants ( THE CALLED )

looks like there is something wrong in the definitions

[shreya19]

Ex-team member. No longer in the company.

[enrico-sorichetti]

pretty shortsighted organization isn' t it

better if somebody with the proper authority takes care of it

Your organization cannot expect to get free consultancy on a forum

[NicC]

The question is: why do anything with B when only A needed modifying? Endevor thinks B has been modified so it needs to be re-linked in. Just get rid of B out of your package and the original B load module will be linked in and Changeman will be happy.

[shreya19]

If I dont include B, i get following error while compiling A. Since A calls B statically.

MODULE B IDENTIFIED BY DDNAME SYSLIB IS NOT A VALID PROGRAM OBJECT. CODE 1
ERRORS ENCOUNTERED ATTEMPTING TO INCLUDE MEMBER B DURING AUTOCALL
SYMBOL B UNRESOLVED. MEMBER COULD NOT BE INCLUDED FROM THE DESIGNATED CALL LIBRARY.

[dick scherrer]

Hello,

I'd recommend hyour organization "rent" an expert to review your implementation, document what you have, and teach you (or someone else) to be the new administrator. I'd be quite uncomfortable is i believed some/all of my source might be at risk.