|
View previous topic :: View next topic
|
| Author |
Message |
Craig Schreoder
New User
Joined: 24 Oct 2012
Posts: 2
Location: USA
|
|
|
|
We are confused. Regions supporting one of our applications
receive "RESP = 09909051: RESP2 = 02388760" on the EXEC CICS LINK
call. Other regions converted to CICS V4.2.0 do not experience this
issue. We even had applications just have a display within the
"linked" program and then issue a GOBACK. It still fails with this
return code.
We cannot find the meaning of these return codes. It appears to be
something unique about this application or region settings but do not
know how to pursue this issue.
Can you help us interpret what is happening?
Thanks for your help!... |
|
| Back to top |
|
 |
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8697
Location: Dubuque, Iowa, USA
|
|
|
|
| This is the kind of problem where you need to contact the vendor -- IBM -- IMMEDIATELY for help. If there is an issue resulting from the upgrade, they will probably know about it and how to fix it; if this is a new issue then they need to know about it so they can fix it. |
|
| Back to top |
|
|
Craig Schreoder
New User
Joined: 24 Oct 2012
Posts: 2
Location: USA
|
|
|
|
| We opened a ticket at IBM and they are convinced it is not related to the CICS upgrade. We sent them a trace and our CLER settings. Anyone seen anything like this. We are stumped. Thank you moderator for the quick reply. |
|
| Back to top |
|
|
Bill O'Boyle
CICS Moderator
Joined: 14 Jan 2008
Posts: 2501
Location: Atlanta, Georgia, USA
|
|
|
|
In order to test outside of the application-code, try issuing a LINK-API, using transaction CECI, specifying the problem sub-program as well as others.
Have you walked the program through using CEDF?
Do other DFHEIBLK fields get whacked as well, like EIBRCODE? |
|
| Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8697
Location: Dubuque, Iowa, USA
|
|
|
|
| This sounds like a mismatch between the length of DFHCOMMAREA in the calling program and subprogram causing EIB fields to be stepped on. As Bill menitoned, using CEDF (or other debugging tool) would be your best place to start figuring out the problem. |
|
| Back to top |
|
|
dbzTHEdinosauer
Global Moderator
Joined: 20 Oct 2006
Posts: 6966
Location: porcelain throne
|
|
|
|
| Quote: |
| Regions supporting one of our applications |
is this application working correctly in any of the other regions?
what is this application?
you are sure all the other regions are working ok?
have you compared the cics tables of each region?
have you compared the started task jcl?
if other regions are not experiencing the problem,
i can understand why ibm is telling you it is not a conversion problem.
is the code written in cobol with up-to-date cics api calls,
or is this older, assembler, old cics calls? |
|
| Back to top |
|
|
|
|
