Problem due to 'INITIAL' in Sub Program

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

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

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

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

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 Post subject:

pkmurali,

you have everything ass-backwards.

INITIAL and CANCEL have the same effect.

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

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

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

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 Post subject:

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: 143

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 Post subject:

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 Post subject:

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: 143

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 Post subject:

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: 143

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 Post subject:

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.