Home > CICS, CICS Tools, CICS TS, CICSPlex SM, Q&A > CICSPlex SM Workload Management and Tech Zone Q&A

CICSPlex SM Workload Management and Tech Zone Q&A

Impact 2008 is coming to a close tomorrow and I have to say I met some really nice people out here in Vegas and several on twitter.  I ran two presentations on CICSPlex SM workload management (a basics and an advanced session) and both sessions were followed by some good questions I thought I would share the answers to. I’ve also added in some questions from the Tech Zone. Thanks to everyone who attended the presentations!

I have two equal LPARs but CICSPlex SM workload balancing only routes to one of them?

This is a really common question that we get asked a lot. The answer is that CICSPlex SM workload balancing does not actually round-robin the workload across all available target regions. What it does do is try to route to the best available region at all times.  This is commonly the region we routed to last time.  Once that region starts to become heavily loaded CICSPlex SM will begin to route work away into a different region.

Another potential factor here is the utilization of routing regions. CICSPlex SM will always try to route locally if possible, as remote routing goes through slower links. So if you are constantly using the routing regions on LPAR1 you will find that the target regions on LPAR1 are the most frequently used.

Can I associate a routing region with more than one workload?

No. This also means that if you are considering switching to distributed routing from dynamic routing you should be careful that your target regions also do not appear in more than one workload.  When you switch to distributed routing, your target regions need to be able to route as well (i.e. a requesting region). So these new requesting regions can also only be associated with one workload at a time.

Does CICSPlex SM work out the affinities for me?

No. This is a bit of a manual task I’m afraid, although the excellent CICS Interdependency Analyzer is certainly able to help you detect them. The aim over a period of time should be to make sure no new applications are created with affinities without good reason. Work should also be done on the current affinities to see if their lifetime could be reduced or if the affinity could be removed all together.

Is it possible to move a Maintenance Point (MP) CMAS from LPAR1 to LPAR2 if for instance LPAR1 goes down?

Yes, this is possible.  Simply bring the MP CMAS up in LPAR2 without any changes. Note that although it is possible to rename your maintenance point, this is a lot more tricky.

That’s your lot for the moment. If you have other questions you would like to know the answer to then feel free to add them to the new “Ask a question” section available from the top navigation.

  1. No comments yet.
  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: