NODYNAM complier option - Issue
Posted: Sat May 30, 2009 4:08 pm
Hi
I am Binesh, new member to the forum. I am facing an issue with cobol online transaction which has MQ calls in a subroutine.
The online transaction X calles a MQ subroutine Y which has MQ connect , MQ open, MQ get calls.
The call inside the main progam is dyanamic as below. But the online transaction has NODYNAM = Y set in its compiler option.
Call WS-Y using MQ parameter
I was told that MQ subroutine are always coded statically with STUB entries, and my subroutine Y also has STUB entry (CSQQSTUB).
But when ever I make changes to my main module X and install, the application fails and had to backout the change and recompile the subroutine and reinstall. This happenend a couple of times and I am not sure the route cause of the issue, however compiling the subroutine resolves the issue.
However in the test env, I am able to make changes and test successfully without compiling the subroutine 'Y'.
I guess it has something to do the way the subroutine is called in the main program (Dynamically) or with the compiler option , but interestingly the issue does not appear in test.
Any inputs would be of great help..
Cheers
Binesh
I am Binesh, new member to the forum. I am facing an issue with cobol online transaction which has MQ calls in a subroutine.
The online transaction X calles a MQ subroutine Y which has MQ connect , MQ open, MQ get calls.
The call inside the main progam is dyanamic as below. But the online transaction has NODYNAM = Y set in its compiler option.
Call WS-Y using MQ parameter
I was told that MQ subroutine are always coded statically with STUB entries, and my subroutine Y also has STUB entry (CSQQSTUB).
But when ever I make changes to my main module X and install, the application fails and had to backout the change and recompile the subroutine and reinstall. This happenend a couple of times and I am not sure the route cause of the issue, however compiling the subroutine resolves the issue.
However in the test env, I am able to make changes and test successfully without compiling the subroutine 'Y'.
I guess it has something to do the way the subroutine is called in the main program (Dynamically) or with the compiler option , but interestingly the issue does not appear in test.
Any inputs would be of great help..
Cheers
Binesh