Problem due to 'INITIAL' in Sub Program

pkmurali · Active User Joined: 15 Dec 2005 Posts: 271

Hi,

Program A is calling sub program B twice. Since Program 'B' is in Inital the Local-storage values remains the same when program 'A' calls Program 'B' second time.

What are all the possibilities to convert Program 'B' non-initial
apart from recompiling Program 'B'. (i.e. without changing Program 'B').

Please let me know.

Thanks,
Murali.

Bill O'Boyle · Posted: Thu Jul 02, 2009 7:52 pm

Remove "PROGRAM IS INITIAL" from the PROGRAM-ID clause?

pkmurali · Active User Joined: 15 Dec 2005 Posts: 271

I agree it will help, but my scenario is not to touch the Program 'B'. I feel 'CANCEL' will help...

dbzTHEdinosauer · Posted: Thu Jul 02, 2009 7:56 pm

pkmurali,

you have everything ass-backwards.

INITIAL and CANCEL have the same effect.

pkmurali · Active User Joined: 15 Dec 2005 Posts: 271

Dick Brenholtz

I am using a existing COBOL Program in my project(similar to Program 'B' mentioned in the previous post) which retains it's local storage variables, i can't able to find the keyword 'INITIAL' or 'CANCEL' used in the program.Since we use Endevor the compiling details are not available. Please let me know what should be done to make that program non-initial.

Thanks,
Murali.

Bharath Bhat · Posted: Fri Jul 03, 2009 1:49 pm

pkmurali · Active User Joined: 15 Dec 2005 Posts: 271

My objective is to make the program 'B' to be non-initial without touching the program 'B'. Is it possible?

dbzTHEdinosauer · Posted: Fri Jul 03, 2009 4:56 pm

does program b have PROGRAM IS INITIAL in the PROGRAM-ID clause?????

if not, then your objective has been obtained - without action.

If Program b has the INITIAL phrase in the PROGRAM-ID clause,
then you have to change Program b.

you said that there are no CANCEL Program b instructions in Program a,
so that is not an issue.

pkmurali · Active User Joined: 15 Dec 2005 Posts: 271

does program b have PROGRAM IS INITIAL in the PROGRAM-ID clause?????

NO

if not,
then if there are no CANCEL Program b instructions in Program a,
then program b's working-storage,
will
on subsequent CALLs,
have the same values as when exited on the previous invocation.

No Cancel statement coded

dbzTHEdinosauer · Posted: Fri Jul 03, 2009 5:02 pm

then you do not have a problem. and you don't need to take any action.

dbzTHEdinosauer · Posted: Fri Jul 03, 2009 5:05 pm

I have overlooked the possibility that Program b executes INITIALIZE instructions.

Does Program b initialize all of its working-storage via INITIALIZE instructions?

pkmurali · Active User Joined: 15 Dec 2005 Posts: 271

I have xpedited the subprogram, where WS-END-OF-CB002003 is the working storage variable.

This is the first call...

Robert Sample · Posted: Fri Jul 03, 2009 7:41 pm

Is the sub program statically called or dynamically called? If it is statically called, change your calling program to make it a dynamic call.

Use CANCEL after returning from the subprogram -- but note that this verb only works on dynamically called routines.

pkmurali · Active User Joined: 15 Dec 2005 Posts: 271

To Addwith,

The Sub program is treated as Stored Procedure in earlier application, but i am using it as BatchLoad. Sub-Program can be called as Stored Procedure as well as Batch Program.

Thanks,
Murali.

dbzTHEdinosauer · Posted: Fri Jul 03, 2009 7:56 pm

now I understand the problem.
some jerk coded a stored procedure,
knowing that it would not be re-invoked during the task,
and laid crap code so that it is not re-entrant.

you are screwed Murali,

as Robert said, you can only CANCEL dynamically CALLed modules,
so your process must eat the overhead created by CANCELing and reLOADing the module for each invocation.

pkmurali · Active User Joined: 15 Dec 2005 Posts: 271

To be more specific,

I have coded Program 'A1' which calls Program 'A2' and Program 'A2' calls Program 'B' all are dynamic calls, after one invocation by Program 'A1' if i cancel Program 'B' will it initialize WS-END-OF-CB002003.

The syntax must be
CANCEL (IDENTIFIER-1,
lITERAL-11....)

Please suggest the above approach is correct or not.

Thanks,
murali.

pkmurali · Active User Joined: 15 Dec 2005 Posts: 271

Now It's working Fine.

Thanks Dick Brenholtz and Robert Sample.

dbzTHEdinosauer · Posted: Fri Jul 03, 2009 8:33 pm

glad you were able to solve it. Have a good weekend.

pkmurali · Active User Joined: 15 Dec 2005 Posts: 271

I have one doubt,what could be the chances of the Program 'B' to hold the value which is being stored on first call? whether it could be the compiler option which made the program to do so?

Thanks,
Murali

dbzTHEdinosauer · Posted: Sat Jul 04, 2009 6:56 pm

what you are asking is
'if a compiler option would override the existence or non-existence of the INITIAL phrase in the PROGRAM-ID clause'.

I don't think so.

pkmurali · Active User Joined: 15 Dec 2005 Posts: 271

I'm confused about the behavior of the program, i guess it may be due to compiler options. I'm not sure.

dbzTHEdinosauer · Posted: Sat Jul 04, 2009 7:17 pm

pkmurali · Active User Joined: 15 Dec 2005 Posts: 271

If a sub program(dynamic call) is called twice, for the first call normally a sub program(goback) returning the control back to main program the local variable will contain the initial values for second call. In my case why that program retains the values (first call) in second call. Please let me know.

Thanks,
Murali.

Robert Sample · Posted: Sat Jul 04, 2009 10:13 pm

What are the compile options? What does the CALL statement look like? Is program B linked into program A or is it an independent module?

You've stated that the call is dynamic, but you've provided no proof of this. A static call will retain values, and unless you've read and understood the COBOL Programming Guide and Language Reference manuals on dynamic calls, it is easy to think a static call is dynamic.

dbzTHEdinosauer · Posted: Sun Jul 05, 2009 2:46 am

a dynamic call will also perform the same.

the only time a CALLed module
does not retain working-storage values, generated during the invocation,
on second, third call is

the CALLed program is CANCELed
the CALLed program has the INITIAL phrase as part of the PROGRAM-ID statement
the CALLed program has code in procedure division that modifies working-storage variables before start of processing

Murali,
you want the working-storage variables at an initialized value for each invocation:
you don't want to change the sub-module
you need to CANCEL the module after return to the CALLing module each time.