| Author |
Message
|
| Vitor |
 Posted: Fri May 24, 2013 10:06 am Post subject: |
 |
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| ankurlodhi wrote: |
| what can we do to fix it. as i am not handling MQ over mainframe. |
Well I'd see if there's any way to reset the sequence numbers. Two methods spring to mind:
- Looking it up in the InfoCenter
- Waiting for someone here to give you the syntax.
I leave choice of method to your good judgement.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
 |
| ankurlodhi |
| Posted: Fri May 24, 2013 10:10 am Post subject: |
|
|
Master
Joined: 19 Oct 2010
Posts: 266
|
mainframe people say it's not there issue.
will refreshing the SSL security on the mainframe side help ?
i am looking up the infocenter for this. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Fri May 24, 2013 10:21 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9475
Location: US: west coast, almost. Otherwise, enroute.
|
| ankurlodhi wrote: |
| i am looking up the infocenter for this. |
Looking for what exactly? What is "this?"
I'd suggest that you search for the error message CSQX526E. Look close at the Resolving the problem section.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri May 24, 2013 10:26 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| ankurlodhi wrote: |
| will refreshing the SSL security on the mainframe side help ? |
If you think refreshing the security configuration will make the "missing" messages pop out of nowhere.
Randomly refreshing and changing things in the hope the magic will come back never works out. Think, research, plan.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| ankurlodhi |
| Posted: Fri May 24, 2013 10:38 am Post subject: |
|
|
Master
Joined: 19 Oct 2010
Posts: 266
|
|
| Back to top |
|
|
| bruce2359 |
| Posted: Fri May 24, 2013 10:41 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9475
Location: US: west coast, almost. Otherwise, enroute.
|
And, then what happened?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| ankurlodhi |
| Posted: Fri May 24, 2013 10:44 am Post subject: |
|
|
Master
Joined: 19 Oct 2010
Posts: 266
|
| is there a way to manually set the message sequence number on the receiver side. |
|
| Back to top |
|
|
| ankurlodhi |
| Posted: Fri May 24, 2013 10:56 am Post subject: |
|
|
Master
Joined: 19 Oct 2010
Posts: 266
|
On z/OS, the command server and channel initiator must be running.
This command can be issued to a channel of any type except SVRCONN and CLNTCONN channels, (including those that have been defined automatically). However, if it is issued to a sender or server channel, then in addition to resetting the value at the end at which the command is issued, the value at the other (receiver or requester) end is also reset to the same value the next time this channel is initiated (and resynchronized if necessary). Issuing this command on a cluster-sender channel might reset the message sequence number at either end of the channel. However, this is not significant because the sequence numbers are not checked on clustering channels.
If the command is issued to a receiver, requester, or cluster-receiver channel, the value at the other end is not reset as well; this must be done separately if necessary.
Where there is both a locally defined channel and an auto-defined cluster-sender channel of the same name, the command applies to the locally defined channel. If there is no locally defined channel but more than one auto-defined cluster-sender channel, the command applies to the channel that was last added to the local queue manager's repository.
If the message is non-persistent, and the RESET CHANNEL command is issued to the sender channel, reset data is sent and flows every time the channel starts
this is what infocenter says.. should we go with this. |
|
| Back to top |
|
|
| ankurlodhi |
| Posted: Fri May 24, 2013 12:45 pm Post subject: |
|
|
Master
Joined: 19 Oct 2010
Posts: 266
|
well I manually reseted the message sequence number on the mainframe side and everything is now working fine.
Thanks everyone for there valualbe input i learnd i lot
Thank you very much. |
|
| Back to top |
|
|
|
|
