Identifying the main program thru sub program

Madhu Reddy · New User Joined: 28 Sep 2006 Posts: 56

Hi,

I have sub programs , i am getting the input to this sub program thru the
linkage section, how to identify the main program ?

Could you please answer as early as possible.
Thanks

vicky10001 · Active User Joined: 13 Jul 2005 Posts: 136

You need to search subprogram into cobol Library.

You will get main program otherwise You search bindeck also

cobolunni · Posted: Mon Mar 05, 2007 10:22 pm

do you need to identify the main program thru subprogram itself or you need to find out manualy. For the second one you need to go for library check

dineshness · Posted: Tue Mar 06, 2007 1:02 am

May be you can pass the main program name as a string to the Sub program thru the linkage section.

Dinesh.

IQofaGerbil · Posted: Tue Mar 06, 2007 5:25 pm

Marso · Posted: Tue Mar 06, 2007 7:44 pm

That's what we do too:

dick scherrer · Posted: Tue Mar 06, 2007 10:48 pm

Hello,

This will work, but will require changing every program that calls the "subprogram". If the called program is some kind of common subroutine (like a date handling routine) it may be called by hundreds of other modules. Changing all of them may not be feasable.

Back to the original request. . . .

Is there a problem in the subprogram caused by the passed-in data? If so, you could cause the subprogram to abend and find the calling module from the dump. If the problem currently causes an abend, you will already have a dump.

cobolunni · Posted: Tue Mar 06, 2007 11:27 pm

reddy for what purpose you are looking for name of main module do you need any logical things to be performed within your data or just to find which is the main module. what king of call is used in your program is it static or dynamic

dick scherrer · Posted: Wed Mar 07, 2007 12:48 am

Hello,

To continue with the thought Cobolunni brings up. . .

If you do need to do processing dependng on which module was the "caller", it is time for a new subroutine that has an expanded parameter list (as was described above). This, unless there is the ability to make the change to all of the modules that currently call this subprogram.

If a second subprogram was created, i'd encourage phasing out the original so that 2 of them do not have to be maintained.

William Thompson · Posted: Wed Mar 07, 2007 4:25 am

Don't forget, the parm list can be optionally longer than all the calling programs know about. The called program can test for its presence and act accordingly.

dick scherrer · Posted: Wed Mar 07, 2007 5:16 am

As long as the new data is not put first in the parms