| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Triggering on MF |
« View previous topic :: View next topic » |
| Author |
Message
|
| techno |
 Posted: Fri Mar 05, 2004 12:45 pm Post subject: Triggering on MF |
 |
|
Chevalier
Joined: 22 Jan 2003
Posts: 429
|
Trying to trigger a Unix script (which is on OMVS) by triggering. I see a message on dead letter queue for each of the triggering message. Could you help me to solve this.
DLH:
Reason 266
DestinationQ: SYSTEM.CHANNEL.INITQ
Message Format: MQTRIG
Destination qmgr: QM11
Put App Name: QM11CHINCSQXSUPR00000000
I have application type as UNIX and applicationid as '/u/usr1/scripts/test.sh' in process definition.
Also let me know where should find out what is happening? Logs etc..
I guess we are not using CICS trigger monitor, because we have 'CSQX START' to start the channel. Could you let me know what other trigger monitor it can be based on?
Thanks |
|
| Back to top |
|
 |
| oz1ccg |
| Posted: Sat Mar 06, 2004 1:23 am Post subject: |
|
|
Yatiri
Joined: 10 Feb 2002
Posts: 628
Location: Denmark
|
You have to use a triggermonitor that supports that kind of work.
USS (which is Unix on z/OS) can't use the MQ'trigger monitor (SYSTEM.CHANNEL.INITQ), you have to use a USS-triggermonitor like the way you do it on AIX, LINUX UNIX.
I guess there is a supportpack for this, maybe it need a bit of customization before your security folks will let you run i in the z/OS environment.
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 |
|
|
| techno |
| Posted: Sat Mar 06, 2004 10:45 am Post subject: |
|
|
Chevalier
Joined: 22 Jan 2003
Posts: 429
|
Later I tried to run a JCL. I gave the appltype= MVS, applid as jcl's dataset.
I changed the initq to something else(defined a new one) . I realized that system.channel.initq is being used by channel initiator.
which logs I should see? I am not able to understand what is happening. I would like to see what are the exact errors. |
|
| Back to top |
|
|
| oz1ccg |
| Posted: Sun Mar 07, 2004 3:01 pm Post subject: |
|
|
Yatiri
Joined: 10 Feb 2002
Posts: 628
Location: Denmark
|
Take a look on supportpack MA12 (Batch support pack):
http://www.ibm.com/support/docview.wss?rs=203&uid=swg24000076&loc=en_US&cs=utf-8&lang=en
This support pack might give you a clue why your current setup don't work.
I think it can give you an idea of how to write an USS triggermonitor, or someone else. The last point of info is Programming guide/ref. on triggering (yes I know it's heavy stuff, but it's worth it).
Another way is if the source from windows was/is available....
Just my $0.02
_________________
Regards, Jørgen
Home of BlockIP2, the last free MQ Security exit ver. 3.00
Cert. on WMQ, WBIMB, SWIFT.
Last edited by oz1ccg on Mon Mar 08, 2004 3:21 am; edited 1 time in total |
|
| Back to top |
|
|
| bob_buxton |
| Posted: Mon Mar 08, 2004 2:11 am Post subject: |
|
|
Master
Joined: 23 Aug 2001
Posts: 266
Location: England
|
As an alternative to writing a USS trigger monitor you could use the batch trigger monitor (from SupportPac MA12) and then run a USS process from a triggered batch job using program BPXBATCH which should be documented in the Unix system services books.
_________________
Bob Buxton
Ex-Websphere MQ Development |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
