| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Question in MQSeries triggering in Mainframe |
« View previous topic :: View next topic » |
| Author |
Message
|
| wilsonho3 |
 Posted: Thu Jul 18, 2002 7:02 am Post subject: Question in MQSeries triggering in Mainframe |
 |
|
Voyager
Joined: 20 Nov 2001
Posts: 98
Location: Hong Kong
|
It seems that all triggering on OS/390 is by CICS transaction ID. Does
any one know that it is possible triggering on OS/390 by program name
rather than by tran. iD in CICS environment. Thank |
|
| Back to top |
|
 |
| nimconsult |
| Posted: Thu Jul 18, 2002 9:45 pm Post subject: |
|
|
Master
Joined: 22 May 2002
Posts: 268
Location: NIMCONSULT - Belgium
|
You can trigger batch applications on OS/390. In the process definition use APPLTYPE(MVS) for batch applications and APPLTYPE(CICS) for CICS applications.
There is a batch trigger monitor proposed in support pac MA12
_________________
Nicolas Maréchal
Senior Architect - Partner
NIMCONSULT Software Architecture Services (Belgium)
http://www.nimconsult.be |
|
| Back to top |
|
|
| wilsonho3 |
| Posted: Sun Jul 21, 2002 5:25 am Post subject: |
|
|
Voyager
Joined: 20 Nov 2001
Posts: 98
Location: Hong Kong
|
Hi, Nicolas
Thank for your response. I know triggering can be in CICS or Batch
model. I think you misundestanding my problem. When we define
a process within a CICS environment. what we define is to trigger a
CICS transaction by ID whan triggering situation meet. Can the process
trigger a program directly. Saying in CICS techical term. Can a trigger
using CICS LINK (....) rather than using CICS STRAT(.....) in case of
using a CTKI feature rather than a MQSeries-CICS bridge feature.
Thank you[/url] |
|
| Back to top |
|
|
| oz1ccg |
| Posted: Sun Jul 21, 2002 11:10 pm Post subject: |
|
|
Yatiri
Joined: 10 Feb 2002
Posts: 628
Location: Denmark
|
Hi,
NO, NJIET, NEIN, NEJ, NO, etc. 
CICS is pretty simple, all it can start is TRANACTIONS and CKTI acts the same way and thats that.
You can write your own CKTI add-on and place it on a new transaction and let CKTI start it, and then let your add-on do the LINK PROGRAM(). based on the message content and/or PROCESS USERDATA-field.
Depending on your program design, if the wrapper do the MQGET, the message is gone when the program will retrieve it... There a some analysis to be done.
I've seen some of this kind of wrapper applications, but they face some problems:
1. how about running more programs simultainously ?
2. how about performance mesaurements, regarding SLA ?
3. how about accounting ?
4. what about security ?
and the list is longer. 
Well, what I've seen (and it works fairly good) is a single wrapper program (single transaction), which just uses the MQTM (trigger message) to deside which program to start (One application program per queue), and based on USERDATA, start the program, and pass the MQTM as commarea. Then it's completely up to the application program to do all the MQ-stuff.
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 |
|
|
|
|
|
| |
|
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
|
|
|
|
