MVSFORUMS.com

[Jeba]

Hai all,

I have an Online (CICS) program which will read all the messages from Message Queue A (i.e., Until Queue depth is 0 ) and process it. This Program will be triggered when a new message is written on the Message Queue A (i.e., When Queue depth changes from 0 to 1 ).

We can't see whether the particular program is running or not as this program is running on a default terminal. By viewing the Output of the program, we can say whether it is running or not. Currently I am using Display statements to debug the program for solving the abends or problems. Can any one tell me how to xpedit this kind of triggered program ?
_________________
Thanks,
Jeba
(Known is a drop Unknown is an ocean)

[Jeba]

Ravi,

I think I didn't tell you the exact problem.

Program A is triggered by Message Queue 1. Program A Starts Program B. Program B triggers program C by putting a message in Message Queue 2. Program C triggers Program B by Putting Message in Message Queue 3. Program B has 2 Functionalities, 1. if started by Program A 2. If triggered by Message Queue 3. Now I want to xpedit Program B when it is triggered by Message Queue 3. Since a Single transaction has some limitations (Memory), the same programs (Transactions) will be started again to read the rest of the messages in the Queue once the message count exceeds 20 for each transaction.

We don't have PQEDIT in our shop. We have a Batch program which will read a message from a file and put it in a Message Queue.

I think I have explained everything. We can do Disabling and Enabling and starting the transactions to xpedit Program A and Program C. I am doing the same from the Beginning. How can we xpedit the program B when it is triggered by Message Queue 3 ( Program C).
_________________
Thanks,
Jeba
(Known is a drop Unknown is an ocean)

[Bill Dennis]

This may help...... What we have done is to turn off triggering on the queue, place the desired record in the queue and then start the transaction in xpediter when we decide.
I am the MQ admin who disables the trigger for the CICS programmer, but I think this is the idea.

Bill

[Jeba]

Hai all,

Thanks for your suggestions. I think i have confused a lot. I don't want to confuse you once again. I have solved the problem by using Display statements itself.
_________________
Thanks,
Jeba
(Known is a drop Unknown is an ocean)

[sreen]

Try this , I have been using this technique since long time
What we do is setup the break point and remove the terminal ID ; Option 1; Option 6 , remove the terminal ID by putting ****,

Now put the message in the queue , The program will stop on your terminal , one disadvantage is other messages in the queue will wait until you release this task