Author |
Message
|
bay hoe san |
Posted: Thu Dec 21, 2006 1:58 am Post subject: Applicid (CSQX Start) - Still Required During MQ Definition |
|
|
Centurion
Joined: 27 Nov 2006 Posts: 117
|
Hi,
I need your expertise advice on the followings:
1. I define a sender channel say from z/OS to AIX
- Define chl(Mychannel) chltype(sdr) trtype(tcp) +
xmitq(Myxmitq) conname('10.1.1.2 (5678)')
- Define qlocal(Myxmitq) usage(xmitq) trigger(yes) +
initq(system.channel.initq) process(Myprocess)
- Define process(Myprocess) appltype(MVS) applicid('csqx start') +
userdata(mychannel)
My question: is the above still valid in V5.3.1 and above?
Reason being I saw something like the followings in V6.0
- Define chl(Mychannel) chltype(sdr) trtype(tcp) +
xmitq(Myxmitq) conname('10.1.1.2 (5678)')
- Define qlocal(Myxmitq) usage(xmitq) trigger(yes) +
initq(system.channel.initq) trigdata(Mychannel)
The difference is in V6.0, no process defintion is required and in the definition of qlocal, in v6.0 trigdata is required, in v5.1 and below process is required.
Can experts enlighten me?
Thank you.
.Hoe San. |
|
Back to top |
|
 |
Mr Butcher |
Posted: Thu Dec 21, 2006 2:13 am Post subject: |
|
|
 Padawan
Joined: 23 May 2005 Posts: 1716
|
there was i time both worked (process and trigdata). i do not know the exact releases.
even if the process version still works in V6 (you can try it) it may stop working one day. why do you still want to use it?
just get rid of all the processes and use TRIGDATA. _________________ Regards, Butcher |
|
Back to top |
|
 |
wschutz |
Posted: Thu Dec 21, 2006 2:53 am Post subject: |
|
|
 Jedi Knight
Joined: 02 Jun 2005 Posts: 3316 Location: IBM (retired)
|
Mr Butcher wrote: |
there was i time both worked (process and trigdata). i do not know the exact releases. |
It should still work. Trigdata (for channel names) was introduced in z/OS v5.3  _________________ -wayne |
|
Back to top |
|
 |
bay hoe san |
Posted: Thu Jan 25, 2007 8:26 pm Post subject: |
|
|
Centurion
Joined: 27 Nov 2006 Posts: 117
|
Can experts like you explain the usage of TRIGDATA?
Thanks. |
|
Back to top |
|
 |
kevinf2349 |
Posted: Thu Jan 25, 2007 8:35 pm Post subject: |
|
|
 Grand Master
Joined: 28 Feb 2003 Posts: 1311 Location: USA
|
I believe that the channel name in TRIGDATA was introduced in 5.3.1. As I recall 5.3 we needed to write our own trigger monitor before that.
At least that was when we took the home grown trigger monitor out and specified channel name in TRIGDATA.
The purpose of TRIGDATA is simply to pass data to the trigger monitor. In the case of XMITQs it is the name of the associated channel to be started.
I thought I read somewhere that even this may not be needed as the queue manager will search for a channel with the matching xmitq and start it.
Can anyone confirm this?...Wayne? Nigel? Jeff? |
|
Back to top |
|
 |
fjb_saper |
Posted: Thu Jan 25, 2007 9:19 pm Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
Looking a little bit outside the box (distributed platforms) neither a process nor trigdata are needed. The first channel using the xmitq will get started.
Now trigdata is a nice way to notify the qmgr which channel to start if you have more than one using the same xmitq.
Enjoy  _________________ MQ & Broker admin |
|
Back to top |
|
 |
|