| Author |
Message
|
| shobha gowda |
 Posted: Tue Sep 10, 2002 5:20 am Post subject: Problem with message transmission |
 |
|
Novice
Joined: 10 Sep 2002
Posts: 13
Location: Frankfurt
|
 Hello,
I have installed MQseries for Windows NT on my system.I am trying to send messages from my Windows to Mainframe..for this I have created a local que in the Mainframe and a remote que in the Windows-nt. A Transmission que as local queue and a sender channel was created in the Windows nt.A receiver channel was created in the Mainframe. Many a time the channel fails to start up in the windows-nt and even when it is running messages does not get passed on to the Mainframe que at all..I would be glad if someone can help me out in this.. It is very urgent for me..
_________________
regards
Shobha Gowda |
|
| Back to top |
|
 |
| dgolding |
| Posted: Tue Sep 10, 2002 5:43 am Post subject: |
|
|
Yatiri
Joined: 16 May 2001
Posts: 668
Location: Switzerland
|
hi Shobha
You need to publish:
NT:
Remote queue definition
Xmit queue definition
Sender channel defn
OS/390:
Receiver channel defn
Local queue defn (highly unlikely the problem is here)
Can you do a PING CHL on the NT side sucessfully? |
|
| Back to top |
|
|
| shobha gowda |
| Posted: Tue Sep 10, 2002 6:36 am Post subject: |
|
|
Novice
Joined: 10 Sep 2002
Posts: 13
Location: Frankfurt
|
Hello,
thanks for the quick response.
On the NT side
Remote que definition:
Queue Name : SHOBHA.REMOTE
Put MEssages : allowed
Default Persistent : Persistent
Scope : Que Manager
REmote Que Name : SHOBHA.LOCAL
REmote Que Mgr Name : MQE3
Transmission Queue : TXNQUEUE
Transmission Queue Name
Queue Name : TXNQUEUE
Type : LOCAL
PUT MESSAGEs : Allowed
GET MESSAGES : Allowed
Default Priority : 0
Defatult Persistence : Not Persistent
Scope : QUE Manager
Usage : Transmission
Sender Channel Definition
Channel Name : SHOBHA.RECEIVE
Type : Sender
Transmission Protocol : TCP/IP
Connection Name : eoo3.esb.eur.deuba.com(1414)
Transmission Queue : TXNQUEUE
********************************************
On the Host Side
LOCAL queue Definition.
QUeue Name : SHOBHA.LOCAL
Put enabled : Yes
Get enabled : Yes
Default Persistence ; No
Default Priority : 0
Permit shared Access : No
Default Share Option : Exclusive
IndexType : None
Default bind : Open
Receiver Channel Definition
Channel Name : SHOBHA.RECEIVE
Have I messed up with data anywhere?...
thanks
_________________
regards
Shobha Gowda |
|
| Back to top |
|
|
| dgolding |
| Posted: Tue Sep 10, 2002 6:51 am Post subject: |
|
|
Yatiri
Joined: 16 May 2001
Posts: 668
Location: Switzerland
|
Ha, you work for a competitor, I can't help you 
Can you ping the sender channel on the NT side?
Is the sender channel running on the NT side?
Are there any messages on the Dead-Letter Queue on the OS/390 side?
What does the AMQERR01.LOG say for the NT queue manager?
What does the CHIN job log on the OS/390 say (I think it's this job, if not , MSTR job log)? |
|
| Back to top |
|
|
| shobha gowda |
| Posted: Tue Sep 10, 2002 7:17 am Post subject: |
|
|
Novice
Joined: 10 Sep 2002
Posts: 13
Location: Frankfurt
|
Hey...this is not fair!!!!!!????????..........
ok now
I can successfully ping the channel. Coming to the sender channel...I did mention in my first mail..that most of the time it fails to start running...and remains in the retrying mode.Even at times when it is up and running it fails to deliver messages.I am unable to read the error log created on the NT side and there are no messages delivered to the dead letter queue on the host side.Anything more??....
thanks
_________________
regards
Shobha Gowda |
|
| Back to top |
|
|
| dgolding |
| Posted: Tue Sep 10, 2002 7:25 am Post subject: |
|
|
Yatiri
Joined: 16 May 2001
Posts: 668
Location: Switzerland
|
I'm surprised there's NOTHING in the AMQERR01.LOG. Are you sure you're looking at the right one, the one under the \qmgrs\<QMGR NAME>\errors directory? If a channel starts there MUST be an entry in this log, similarly if it goes into retry. And any info from the OS/390 side, looking at the job log for the CHIN program?
Do the messages just sit in the transmit queue? |
|
| Back to top |
|
|
| shobha gowda |
| Posted: Tue Sep 10, 2002 7:35 am Post subject: |
|
|
Novice
Joined: 10 Sep 2002
Posts: 13
Location: Frankfurt
|
ok ok I am sorrry...
it gives me these messages
09/10/02 16:10:06
AMQ7880: Error code 0 starting QM_cib11051/Channel Initiator MQSeries service.
EXPLANATION:
The MQSeries service was unable to start QM_cib11051/Channel Initiator. The
error message reported was as follows: The process has terminated with return
code 20.
ACTION:
Use MQSeries Services to investigate why the service could not begin. If
recovery for this service is active, MQSeries will attempt to recover.
or the following
-------------------------------------------------------------------------------
09/10/02 16:10:06
AMQ7882: Attempting to recover QM_sho11051/Channel Initiator MQSeries service.
EXPLANATION:
The MQSeries service has detected that QM_sho11051/Channel Initiator has
failed, and is attempting to restart it.
ACTION:
No Action Required.
_________________
regards
Shobha Gowda |
|
| Back to top |
|
|
| maxis |
| Posted: Tue Sep 10, 2002 8:30 am Post subject: |
|
|
Centurion
Joined: 25 Jun 2002
Posts: 144
|
Shobha,
As, recommended by IBM's best practise, always
1. name transmission queue as that of target queue manager.
on which port your queue manager is running ? .. Make sure thats not occupied by other application ...
let us know how it goes
M |
|
| Back to top |
|
|
| shobha gowda |
| Posted: Tue Sep 10, 2002 11:11 pm Post subject: |
|
|
Novice
Joined: 10 Sep 2002
Posts: 13
Location: Frankfurt
|
Hello,
sorry it still isn't working.....Now my transmission queue name is SHOBHA.LOCAL. Why doesn't the channel get started up?..
Sometimes when the transmission queue is not open trying to start the channel gets it running but if the transmission queue is open trying to start the channel never gets it running. Also on the host side though the return code returned while starting the channel is 0 the status shown is INACTIVE why is that so?...
thanks
_________________
regards
Shobha Gowda |
|
| Back to top |
|
|
| oz1ccg |
| Posted: Wed Sep 11, 2002 2:15 am Post subject: |
|
|
Yatiri
Joined: 10 Feb 2002
Posts: 628
Location: Denmark
|
What is in the log of xxxxCHIN task on the OS/390 end, the clue might lay there. f.x. no deadletter queue... bad remote def, you know it's case sensetive (very).
Just my $0.02 
_________________
Regards, Jørgen
Home of BlockIP2, the last free MQ Security exit ver. 3.00
Cert. on WMQ, WBIMB, SWIFT. |
|
| Back to top |
|
|
| shobha gowda |
| Posted: Wed Sep 11, 2002 2:40 am Post subject: |
|
|
Novice
Joined: 10 Sep 2002
Posts: 13
Location: Frankfurt
|
Hello Perdersen,
I am sorry I did not get what u meant by xxxCHIN task!!???.....On the NT side yes there was a message saying there is no Dead Letter Queue defined for the said Que Manager...so I did assign it one.......So now all the messages which earlier used to reside in the Transmission queue are getting stored in the Dead Letter Queue....Yes ofcourse I know the objects are case sensitive...
thanks
_________________
regards
Shobha Gowda |
|
| Back to top |
|
|
| dgolding |
| Posted: Wed Sep 11, 2002 2:50 am Post subject: |
|
|
Yatiri
Joined: 16 May 2001
Posts: 668
Location: Switzerland
|
An obvious thing to check - are you MQPUTing your message to the REMOTE queue or the XMIT queue? Can you dump one of the messages on your DLQ using AMQSBCG and post it?
On the OS/390, if you use SDSF, followed by DA, and look for the job called xxxxCHIN where xxxx is the four-character queue manager name, then "S" will let you look at the job log. Get a OS/390 guru sys-proggie type person to guide you.... |
|
| Back to top |
|
|
| shobha gowda |
| Posted: Fri Sep 13, 2002 12:05 am Post subject: |
|
|
Novice
Joined: 10 Sep 2002
Posts: 13
Location: Frankfurt
|
hi....
I did try looking at the chin log but it gives me only the active sender channels...and none of the receiver channels started are shown. Also will u be able to tell me how to find the port number where it is supposed to listen?....Most importantly I think the problem lies with the Queue Manager definition...Because while installing MQ for Windows-Nt I had disabled 'Allow remote monitoring of the queue' option. Also how is opening of a queue and starting a channel related?...because when the queue is closed starting of the channel gets it running but not otherwise.also once the channel is up and running trying to open a transmission queue fails with the message 'object in use'...
Can u give me the queue manager definition as to what it supposed to be is?...
thanks
_________________
regards
Shobha Gowda |
|
| Back to top |
|
|
| mgrabinski |
| Posted: Mon Sep 16, 2002 12:54 am Post subject: |
|
|
Master
Joined: 16 Oct 2001
Posts: 246
Location: Katowice, Poland
|
Shobha,
Your error messages state that the channel initiator couldn't start. Can you just start the sender channel? Any errors here?
_________________
Marcin Grabinski <>< |
|
| Back to top |
|
|
| shobha gowda |
| Posted: Mon Sep 16, 2002 7:15 am Post subject: |
|
|
Novice
Joined: 10 Sep 2002
Posts: 13
Location: Frankfurt
|
Hello,
looks like there is really some connection problem..because with the same setup sometimes the channel fails to start depending on whether the Transmission Queue is open or not. But even when the channels are up and running the messages fail to reach the host they just take shelter in the dead letter queue.. I have some serious doubts...Is there a possibility where in remote administration of the host is disabled . Because I work in an organisation where there is lot of need for security and though the environment which I am trying to access is a development environment there could be a possiblity of that...If at all that is the case how am I supposed to find out such a setup.or is asking the system admin the only way of finding it out?...
thanks
_________________
regards
Shobha Gowda |
|
| Back to top |
|
|
|
|
