It begs the question....why do you want to stop it? Use DISCINT on the channel definition and it will go inactive itself.
A stopped channel cannot be restarted using triggering, if fact it can only be restarted manually.
Try the IBM website itself. It may have some, apart from that ... good luck. Terms and conditions of taking the test forbid disclosure of the questions.
Best bet is to search the IBM website I am pretty sure there were some there last time I looked.
Run a RUNMQSC and input
display channel(SYSTEM.ADMIN.SVRCONN)
It should be created when the queue manager is but it may have been deleted on your system to prevent client attachments.
Do you know if you are using SSL?
A SRVCONN is a channel type defined on the QMGR that you want to client in to. You will need one defined before you are able to Client connect to the qmgr.
DEFINE CHANNEL(xxxxx) CHLTYPE(SVRCONN) TRPTYPE(TCP) +
DESCR('Server-connection')
The trigger monitor will sit and watch the initiation queue.
When a message lands of your triggered queue and prividing all the trigger conditions are met, then MQ will generate a trigger message internally and drop it on the initiation queue. The trigger monitor will read that message and...
Why do you need to check for queues? You shouldn't need to do anything like that.
If you try and issue an open for a non-existing queue you will get the return code of 2085 so you will know it isn't there.
What exactly is the requirement?
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.