|
View previous topic :: View next topic
|
| Author |
Message |
krish2309
New User
Joined: 29 Jan 2014
Posts: 17
Location: Kuala Lumpur
|
|
|
|
Dear All,
the following message appears in the CICSLOG. Can any one please help to advise whether that message appears because of system/ application issue. also please advise how do i investigate further on this.
Other application send transaction to our application program using transaction ID X020 which receives the information and process and respond back to other application by allocate, connect and Send operation with different trans ID.
| Code: |
DFHZN2701 01/07/2015 15:21:49 XXXMCICS Log data sent on ISC session is DFHZC4923 I 01/07/2015 15:21:49 XXXMCICS -AA5 X020
Conversation abnormally terminated by transaction end in system XXXMMCICS |
|
|
| Back to top |
|
 |
Bill Woodger
Moderator Emeritus
Joined: 09 Mar 2011
Posts: 7309
Location: Inside the Matrix
|
|
|
|
| I think you've missed a message-numer: Have a look at something like this, but for the version you are using. |
|
| Back to top |
|
|
krish2309
New User
Joined: 29 Jan 2014
Posts: 17
Location: Kuala Lumpur
|
|
|
|
Hi Bill,
May i know what do you mean by Message-number?
I already gone through the link which you shared previously. I tried to simulate the scenario but cannot. I requested system guy to release the session before transaction send back to other application but it failed with SYSIDERR.
Thank you |
|
| Back to top |
|
|
Nic Clouston
Global Moderator
Joined: 10 May 2007
Posts: 2455
Location: Hampshire, UK
|
|
|
|
| Every message has a message number so that it can be referred to in the manuals. The message number of your first ine is DFHZN2701. Your second line is not showing a message number, although it could be a continuation of the first line. |
|
| Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8696
Location: Dubuque, Iowa, USA
|
|
|
|
| My guess would be an application error. Specifically, I think the APPC interface has not been fully implemented -- allocate, connect, and send are fine but there is more to an APPC conversation (such as the FREE that is needed at the end of the conversation before the transaction ends). |
|
| Back to top |
|
|
Rohit Umarjikar
Global Moderator
Joined: 21 Sep 2010
Posts: 3053
Location: NYC,USA
|
|
|
|
I am not sure but see if this helps, however that is an informational message.
| Code: |
State changes for the SYNCPOINT and SYNCPOINT ROLLBACK
commands
When the SYNCPOINT and SYNCPOINT ROLLBACK commands are issued, they
are propagated on, and affect the state of, all the conversations that are currently
active for the task, including MRO conversations.
Following rollback, the conversation can be in SEND or RECEIVE state,
depending on the conversation state at the start of the current distributed unit of
work. The conversation can be in FREE state if it ended abnormally due to session
failure or due to deallocate abend being received, or if the partner transaction
issued a SEND LAST WAIT or FREE command.
After a syncpoint or rollback, it is advisable to determine the conversation state
before issuing any further commands against the conversation. |
|
|
| Back to top |
|
|
|
|
