Portal | Manuals | References | Downloads | Info | Programs | JCLs | Mainframe wiki | Quick Ref
IBM Mainframe Forum Index
 
Register
 
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Profile Log in to check your private messages Log in
 
COBOL programs dynamic linking
Goto page Previous  1, 2
 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> COBOL Programming
View previous topic :: :: View next topic  
Author Message
shreya19

New User


Joined: 13 Mar 2014
Posts: 28
Location: USA

PostPosted: Thu Jul 17, 2014 11:17 pm    Post subject:
Reply with quote

am rm 24 24 calling 2 modules with am rm 31 any.

Can call 1st successfully, but gets stuck on 2nd

I changed am rm of calling module to 31 any. Still the same, no change.
S

Loadlib is pdse. I have old load lib which is in pds, when i use that, it doesnt event call the 1st module
Back to top
View user's profile Send private message

Bill O'Boyle

CICS Moderator


Joined: 14 Jan 2008
Posts: 2504
Location: Atlanta, Georgia, USA

PostPosted: Thu Jul 17, 2014 11:37 pm    Post subject: Reply to: COBOL dynamic linking
Reply with quote

AMODE 31 modules have no problem addressing parmlists built and passed by an AMODE 24 Caller. It's when an AMODE 31 Caller (building and passing an AMODE 31 parmlist) calls an AMODE 24 Caller and then you've got trouble.

I'm fresh out of ideas.

Please use English that we can all understand.

I can't read Pig-Latin.... icon_eek.gif
Back to top
View user's profile Send private message
shreya19

New User


Joined: 13 Mar 2014
Posts: 28
Location: USA

PostPosted: Fri Jul 18, 2014 1:47 am    Post subject:
Reply with quote

Our load libraries exist from long time and Changeman was set up just few years back.

I found that the modules that were recently modified (using changeman)get called dynamically. whereas the ones that have not been modified since years (did not ever use changeman) throw error.

So there might be some mismatch. Will try contacting Changeman team.
Back to top
View user's profile Send private message
shreya19

New User


Joined: 13 Mar 2014
Posts: 28
Location: USA

PostPosted: Sat Jul 19, 2014 1:10 am    Post subject:
Reply with quote

Changeman team sent me back saying it is a coding issue icon_cry.gif
Back to top
View user's profile Send private message
Bill Woodger

DFSORT Moderator


Joined: 09 Mar 2011
Posts: 7312

PostPosted: Sat Jul 19, 2014 5:31 am    Post subject: Reply to: COBOL dynamic linking
Reply with quote

Perhaps you approached them in the wrong way. If they've not changed anything for years, they won't take kindly to you jumping in their faces saying its wrong.

It sounds like when they set up the Changeman, they used at least one different compile option (DYNAM). Someone should have noticed at the time.

You need to look at one of the old programs, a loadmodule containing it, and find out the compile options used. You need to check those compile options to those currently used. If there are any other differences in options which generate code, so may have some "interesting" impact analysis for someone to do.

You currently have two systems sharing the same libraries and sharing some sub-programs.

You are splitting those out to separate libraries, and need still to be able to use the common sub-programs in both systems.

Who is responsible for maintaining the common sub-programs? Same Project for all, or some split?

You've already changed at least some programs to use CALL data-name instead of CALL literal. That was unnecessary. Compiler option DYNAM will cause the CALL literal source to generate the code for a dynamic CALL.

The change would only be necessary if you are unable to change the compile option to DYNAM. Guess who knows the answer to that question?

You will need to get the bosses responsible for the two different systems and the Changeman team together. The discussion will require technical input, from someone who is aware of the meaning and impact of the compile options. That, along with the way the Changeman team have as their standard for managing source/executable systems should lead to a list of what needs to be done and who needs to do it. Get your best COBOL person in on that meeting.

Anything you come up with yourself will likely be bounced by the Changeman team as not the standard way to do it. If they are left on their own, I'd be worried they'd not have the knowledge to set the correct compile/linker-binder options. If common modules are "shared", there will always be problems when one Project wants a change, and the other doesn't. So you have to get all that sorted out before you can get anywhere.

So, stop what you are currently doing, reveal to your boss the mess that exists, so that such a meeting (probably not just one) can be arranged. Don't do anything else until you are doing what everyone has agreed to. Else you'll be continuing in the same manner for weeks, only for all your work to be scrapped when someone finally realises independently that there is a problem.
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> COBOL Programming All times are GMT + 6 Hours
Goto page Previous  1, 2
Page 2 of 2

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
This topic is locked: you cannot edit posts or make replies. COBOL/CICS with real time MQ Series u... BPranav CICS 2 Mon Sep 16, 2019 9:19 pm
This topic is locked: you cannot edit posts or make replies. Compare two files logic in COBOL Nishant Singhal COBOL Programming 4 Sun Aug 25, 2019 2:25 am
This topic is locked: you cannot edit posts or make replies. Upgrade to Enterprise COBOL 6 JPVRoff COBOL Programming 4 Thu Aug 01, 2019 7:21 am
No new posts COBOL copybook to Focus anandgbe COBOL Programming 7 Wed Jul 31, 2019 11:52 am
No new posts Odd bit of COBOL socker_dad COBOL Programming 3 Tue Jul 09, 2019 4:46 am

Facebook
Back to Top
 
Job Vacancies | Forum Rules | Bookmarks | Subscriptions | FAQ | Polls | Contact Us