Tags

Sometimes when developing a flow we find that the flow becomes non-responsive. This can be caused by a few different reasons but one of the most common is that the flow is stuck in a logic loop. This can be caused by poor code design or design of the flow itself. Even after identifying and fixing the logic within the flow, you are still stuck with the task of replacing the deployed flow within the Broker. WebSphere Message Broker has built in recovery measures. This means, if the Broker detects that the EG has crashed or stopped unexpectedly,... [More]

There are a number of different examples of loops we encounter on a daily basis which are beneficial to our everyday lives (traffic circles, musical loops, shoe laces). But the type of loop I want to discuss today causes your CICS Transaction Server for z/OS (CICS TS) region to become inoperative which may lead to some unhappy users. In this particular blog entry I will walk you through how and why this problem occurs and the solutions to alleviate this in your CICS environment. The problem is triggered with PTF UK63439 (APAR PM24620 ) for CICS... [More]