View previous topic :: View next topic |
Author |
Message |
mls Beginner
Joined: 10 Nov 2005 Posts: 9 Topics: 5
|
Posted: Fri Sep 29, 2006 12:54 pm Post subject: Synconreturn Problem |
|
|
Hi,
I am facing one problem with calling some modules between different LPAR's.
Existing process is:
A calls B (A is in say LPAR 1 and B is LPAR 2 and B is called using EXEC LINK with synconreturn option)
I changed it to
A calls X,Y and B. X and Y calls C/D and E/F.
A calls X -> Calls C and D
Y --> Calls E an F
B
X and Y are in Lpar 1 and C,D,F and E are in Lpar 2.
Now all the programs are successful except for existing program B. It gives EIBRESP 16 and EIBRESP2 14. I looked up for these error codes and got following explanation:
INVREQ
occurs for the following situations, depending on the options specified on the LINK command:
The SYNCONRETURN option is specified but the program issuing the link request is already in conversation with a mirror task (that is, a logical unit-of-work is in progress) in the remote region specified on the SYSID option. In this case, the linked-to program is in an incorrect state to support the SYNCONRETURN option.
The program issuing the link request is already in conversation with a mirror task and the TRANSID specified is different from the transaction identifier of the active mirror.
The TRANSID specified is all blanks.
Default action: terminates the task abnormally.
I removed synconreturn while calling B and it abended. I tried adding syncnoreturn while calling X and Y and it is also not working.
Please let me know if anyone has worked on similar problem.
Thanks a lot! |
|
Back to top |
|
 |
Krish1 Beginner
Joined: 23 May 2006 Posts: 3 Topics: 0
|
Posted: Sun Oct 22, 2006 6:04 pm Post subject: |
|
|
Are you reading any File which is in Region B. If yes, then try doing Syncpoint just before Link to Program B.
I faced the similar issue while reading file in Region B and later linked the program residing in File B. I realize while you read the file for some reason connection still says and this is the reason I did Syncpoint to break the same. Since, I went to Region B to get some information and no updates and before that there was no updates it worked fine for me.
I never found a time later to research more on this as it solved the purpose at that time.
Please try this, I hope it will work for you. _________________ Thanks |
|
Back to top |
|
 |
Krish1 Beginner
Joined: 23 May 2006 Posts: 3 Topics: 0
|
Posted: Sun Oct 22, 2006 6:06 pm Post subject: |
|
|
I faced the similar issue while reading file in Region B and later linked the program residing in File B
Please read File B as Region B above. It was typo error. _________________ Thanks |
|
Back to top |
|
 |
|
|