MQseries with Windows-NT and Mainframe(Urgent!!!!!)

[COBOLMQ]

Hello.,
hope someone will be able to give me some suggestions..
I am trying to do a very simple operation of sending messages from Local ie., Windows-NT to Host ie., Mainframe.I have created a Local Queue in the Host and a REmote queue in the Windows-NT with the Remote Que name as the one that is present in the Host . I have created a Transmission Queue(as a Local Queue) in Windows-NT. Ofcourse the Transmission Queue mentioned in the created Remote queue(queue in Windows-NT) is the same as Transmission Queue Created there.
A Sender Channel on Windows-NT and a receiver Channel on Host have been created.
My problem now is many a time I am really not able to start the channel.and even when the channel is running no messages are passed on to the queue in the Host.What exactly is the procedure for starting the Channel on the Windows-NT side?..because once the transmission queue is open if I try to start the channel it says MQOPEN failed. Also on the host it always says Inactive even If I have started the channel. Am I messing up something somewhere?...How do I go about debugging things?...

Thanks and regards
Shobha Gowda

 

[aixmurderer]

Did you define the Xmit queue in the sender channel definition on the NT server?

IBM Certified Confused - MQSeries
IBM Certified Flabbergasted - AIX 5 pSeries System Administration

 

[kevinf2349]

This is how we did it. (using a SENDER/RECEIVER pair)

Define a Transmission Queue on NT with the same name as the remote Qmgr (i.e CSQ2)

Define a Remote queue on NT with the desired name (i.e CSQ2.QUEUE.NAME). In this definition remember to specify Remote name (i.e QUEUE.NAME), Remote QMGR (CSQ2) and transmission queue (i.e CSQ2)

Define a channel specifying the transmission queue name (i.e CSQ2) as part of the definition

On CSQ2 make sure you have the local queue defined (QUEUE.NAME).

When all this is complete...start the channel.

Your program needs to connect to its local queue manager and place a message onto the remote queue (ie. CSQ2.QUEUE.NAME). That should work.

 

[Guest_imported]

Hi friends,
thanks for your valuable support....Would u be kind enough to give me the definition of the NT Queue Manager...Because during the installation I had created a Que Manager where in I had disabled remote monitoring of the Queue Manager...Also is there any way of finding out the port number where it is supposed to listen?...Is there any hard and fast rule which states the transmission queue should have the same name as the Remote que manager name?....is there any chance of this having been customized by an organisation.
Waiting for ur reposnse
Shobha Gowda

 

[aixmurderer]

To answer the XmitQ question, no, you can name it whatever you want, as long as in the definition you define the remote Q manager's correct name. We "normally" name it the same as the remote Q Manager, but sometimes for ease of recognition we will name it differently if the remote QManager has some meaningless name which doesn't identify itself clearly as a specific customers Q Manager.

So, to answer your question, it is very likely that an organisation may have changed the Xmit Q name for a similar reason. IBM Certified Confused - MQSeries
IBM Certified Flabbergasted - AIX 5 pSeries System Administration

 

[kevinf2349]

The TCP/IP port number on the mainframe (by default) is 1414, however this is only the default. You could seek out the command that starts the listener. If this doesn't have PORT(xxxx) then it will be 1414. If it does have PORT(xxxx) then xxxx will be the port number.

I believe the default on other platforms is 5010 but I could be wrong on that.

 

[Guest_imported]

How can I find out if the host Que manager has been enabled for remote administration or not?...With the normal installation of MQ on Windows-NT..when I check the properties of Queue Managers I find that in the Local/RemoteConnection it is Local...How should the Queue Manager be defined for me to make Queue Manager residing on host as a remote que manger
My present definition of Que Manager is as under.
DESCR( ) DEADQ( )
DEFXMITQ(MQE3.TXNQUEUE) CHADEXIT( )
CLWLEXIT( ) CLWLDATA( )
REPOS(MY_NEW_CLUSTER) REPOSNL( )
COMMANDQ(SYSTEM.ADMIN.COMMAND.QUEUE) QMNAME(QM_cbu56147)
CRDATE(2002-09-16) CRTIME(11.55.39)
ALTDATE(2002-09-16) ALTTIME(17.02.08)
QMID(QM_cbu56147_2002-09-16_11.55.39) TRIGINT(999999999)
MAXHANDS(256) MAXUMSGS(10000)
AUTHOREV(ENABLED) INHIBTEV(DISABLED)
LOCALEV(ENABLED) REMOTEEV(ENABLED)
PERFMEV(DISABLED) STRSTPEV(ENABLED)
CHAD(ENABLED) CHADEV(ENABLED)
CLWLLEN(100) MAXMSGL(4194304)
CCSID(437) MAXPRTY(9)
CMDLEVEL(520) PLATFORM(WINDOWSNT)
SYNCPT DISTL(YES)

My definition of RemoteQueue on NT
DESCR( ) RNAME(MQE3.LOCAL)
RQMNAME(MQE3) XMITQ(MQE3.TXNQUEUE)
CLUSTER( ) CLUSNL( )
QUEUE(MQE3.REMOTE) ALTDATE(2002-09-16)
ALTTIME(13.39.33) PUT(ENABLED)
DEFPRTY(0) DEFPSIST(NO)
SCOPE(QMGR) DEFBIND(OPEN)
TYPE(QREMOTE)

My definition of LOCAL transmission Queue
DESCR(Transmission queue) PROCESS( )
BOQNAME( ) INITQ( )
TRIGDATA( ) CLUSTER( )
CLUSNL( ) QUEUE(MQE3.TXNQUEUE)
CRDATE(2002-09-16) CRTIME(11.58.24)
ALTDATE(2002-09-16) ALTTIME(17.02.29)
GET(ENABLED) PUT(ENABLED)
DEFPRTY(0) DEFPSIST(NO)
MAXDEPTH(5000) MAXMSGL(4194304)
BOTHRESH(0) SHARE
DEFSOPT(SHARED) HARDENBO
MSGDLVSQ(PRIORITY) RETINTVL(999999999)
USAGE(XMITQ) TRIGGER
TRIGTYPE(FIRST) TRIGDPTH(1)
TRIGMPRI(0) QDEPTHHI(80)
QDEPTHLO(20) QDPMAXEV(ENABLED)
QDPHIEV(DISABLED) QDPLOEV(DISABLED)
QSVCINT(999999999) QSVCIEV(NONE)
DISTL(NO) DEFTYPE(PREDEFINED)
TYPE(QLOCAL) SCOPE(QMGR)
DEFBIND(OPEN) IPPROCS(1)
OPPROCS(1) CURDEPTH(0)

Is there anything wrong with the defintions....

thanks and regards
Shobha Gowda