SUMMARY:   You'll need this course if you're going to write complex messaging applications yourself, or to use any of WebSphere MQ's more advanced features such as channel exits. This course is also necessary for those who will act as in-house consultants to junior staff. PREREQUISITES:   The participant should have a sound working knowledge of WebSphere MQ design and the WebSphere MQ program calls, such as might be gained from the WebSphere MQ Application Programming Workshop class, plus six months' practical experience. DURATION:   3 days APPROACH:   This class is taught by lecture with hands-on workshops and class discussions. OBJECTIVES:   Design and code complex transactions using any of the three kinds of WebSphere MQ triggers, and specifically the queue depth type of trigger in conjunction with MQSET Write and implement a trigger monitor program Code WebSphere MQ exits, particularly the channel message and data conversion exits Write and implement handlers for dead-letter queues and performance events Use WebSphere MQ distribution lists for: "fuzzy" broadcast queries precisely-controlled multi-destination transactions Implement Web access to servers using alternate userid's Implement multiple instances of server applications in a cluster of WebSphere MQ queue managers COURSE CONTENT:   Writing triggered server applications Trigger on First Trigger on Every Trigger on Depth MQSET with triggering Writing and implementing a trigger monitor Setting up the process and initiation queue Receiving and parsing the trigger message Starting the application and passing parameters Coding WebSphere MQ exits User-written formats and the data conversion exit Channel message exit Using distribution lists Designing applications to use distribution lists List creation and usage Analyzing returns Special handler programs Parsing the Dead-Letter Header Running a dead-letter handler Handling queue threshold conditions Clustered WebSphere MQ applications Setting up a queue manager cluster Advertising cluster queues Programming considerations PL/2B