| Author |
Message
|
| sebastia |
 Posted: Mon Oct 16, 2006 7:27 am Post subject: AMQ9002 then AMQ9001 : AS/400 with W2K |
 |
|
Grand Master
Joined: 07 Oct 2004
Posts: 1003
|
We have a (normal) channel from AS/400 to W2K.
I start the receive part - nothing in windows LOGs - then the sender at AS/400. The we find in qmgr's LOG :
timestamp + AMQ9002 = channel NAME started.
timestamp + AMQ9001 = channel NAME ended normally.
We do have SSLKEYR defined, but empty.
Also, channel has SSLCAUTH(REQUIRED) but we changed it to OPTIONAL with no improvements.
What can be the reason the channel does not stay Active ?
Or a little bit better : what way can I increase the level of entries in AMQERR01 so there is something between 9002 and 9001, indicating the reason of this situation ?
Cheers. |
|
| Back to top |
|
 |
| Vitor |
| Posted: Mon Oct 16, 2006 7:31 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Does the channel actually go into a status of STOPPED (which indicates that there's a problem or someone's stopped it) or INACTIVE (which indicates that no message has been sent for a while & it's nodded off until one shows up)?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| sebastia |
| Posted: Mon Oct 16, 2006 7:46 am Post subject: |
|
|
Grand Master
Joined: 07 Oct 2004
Posts: 1003
|
MQ Explorer says INACTIVE,
but the AMQERR01 file says ... AMQ9001 = stopped !!!
( ) |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Oct 17, 2006 12:15 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
And if you query the channel status from a command prompt to get a deciding vote...???
I agree that the log will report the channel "stopping" because it is indeed no longer running. That's not what I asked - what I asked was what status the channel enters once stopped. If it's INACTIVE that's exactly what I'd expect to happen.
Especially as a) there's no messages indicating a problem in the log, just the start and stop messages, b) the Explorer says it's inactive & c) this is the designed behaviour of a channel!
If it bothers you, the channel can be set to remain constantly active i.e. not shutdown during inactivity. It's documented in the command reference IIRC but beware - using this facility can (unless caution is taken) prevent channels recovering from comms errors.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| sebastia |
| Posted: Tue Oct 17, 2006 12:22 am Post subject: |
|
|
Grand Master
Joined: 07 Oct 2004
Posts: 1003
|
on the receiving end of the channel,
it goes active
the bad news is that i have the same "central" as/400
going to another windows 2000 and in the same situation
the channel remains "ACTIVE".
In the wrong situation, the "sender" end of the channel
stays RETRYING
but the AS/400 error logs are unreadable (i just wrote the forum about this)
SO ...
a) the channel has to stay active (at least untils DISCONNECT timeout)
b) the channel is stopped from the sender part, so i wil have to look into the as/400 logs to find the reason
thanks a lot !!! |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Oct 17, 2006 12:54 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
status of RETRYING sounds more like a comms problem
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| sebastia |
| Posted: Tue Oct 17, 2006 1:02 am Post subject: |
|
|
Grand Master
Joined: 07 Oct 2004
Posts: 1003
|
at AS/400 i find lots of FDCs ...
and only "Internal Error" i AMQERR01 ...
... |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Oct 17, 2006 1:07 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| sebastia wrote: |
at AS/400 i find lots of FDCs ...
and only "Internal Error" i AMQERR01 ...
... |
Ok, so it not a channel problem per se...your MQ is broken! 
This would explain the inconsistent channel statuses (stati??)
Fix those & then see how the channels behave.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| sebastia |
| Posted: Tue Oct 17, 2006 1:59 am Post subject: |
|
|
Grand Master
Joined: 07 Oct 2004
Posts: 1003
|
FIXED : the sender part of the channel was compolaining about a missing RESOLVE CHANNEL
Once this command was given, asll went fine.
Another problem has been how to read the AS/400 AMQERR01.LOG - it HAS TO BE DONE using "EDTF", no other.
Cheers ! |
|
| Back to top |
|
|
| Hassan |
| Posted: Tue Oct 17, 2006 5:13 am Post subject: |
|
|
Voyager
Joined: 01 Apr 2004
Posts: 81
Location: Toronto, Canada
|
You can also use the wrklnk command and then option 5 to display to read the error logs. Generally for any "channel" issues this (the error logs) is the best place to start.
Cheers!
Hassan |
|
| Back to top |
|
|
| sebastia |
| Posted: Tue Oct 17, 2006 6:38 am Post subject: |
|
|
Grand Master
Joined: 07 Oct 2004
Posts: 1003
|
Thanks, Hassan. I will write it down .. so next time I will try to use it.
Best luck ! |
|
| Back to top |
|
|
|
|
