BillyBoyo wrote:Robert asked if it had any CICS commands in it. Does it?
Yes it has CICS commands in it.
BillyBoyo wrote:Why do you think CALL more efficient than LINK?
It may be under some circumstances. 2 that I can think of are:
1. If a prog is called multiple number of times at the same logical level the WORKING STORAGE remains in its last-used state . It is not freed and initialized again and again as in case of LINK
2. CALL can pass more than 32K bytes of data unlike LINK(as it uses only dfhcommarea) and CALL can pass multiple parameters unlike LINK.
However I think we are digressing here; besides I dont think i can change the call to link coz it is an existing prog in production i dont want to change. I am just analysing it.
BillyBoyo wrote:Definitely the 2nd call is bad practice. Someone maintaining the program will see it, and wonder what is going on. Maybe they'll fix it.
I don't understand
If I do not want to use WS-VARIABLE in PROGB and want the contents of WS-VARIABLE from PROGA in DFHCOMMAREA of PROGB
What do you mean? Why wouldn't you "want" to use WS-VARIABLE?
Actually this 2nd call is coded in an existing prog in production and I was suspecting its a bad coding practise and posted in this respected forum to confirm. Its not that I do not "want" to use WS-VARIABLE. I just wrote to explain. Apologise for any confusion i may have caused. I did not code this 2nd CALL
However I got wat i was looking for from this post i.e. "2nd Call is bad coding practise and shud be corrected"