Some CPSM WUI thoughts....

The WUI will run fine within an existing CICS region. It is "just an application".

Some things to consider (like with all monitors):

  1. Do you want the availability of your monitor to depend on the stability of one of your own CICS applications?
  2. Do you want your monitor to get the same level of service as your other CICS regions?
  3. Do you want the other apps in the region to get the preferred service if you boost it for the WUI?
  4. Do you want to use the WUI to monitor the startup and shutdown of the other regions?
  5. Do you want changes to the WUI that require a region bounce to be tied to an application maintenance window?

Suggest keeping the WUI separate since it is a systems management tool and is not managed like a "normal" application region.

This is similar to keeping TOR's "IBM code only" regions (OK, maybe your CICS monitor is in there too).

Bring up the WUI(s) at IPL time along with the other CPSM address spaces.
The WUI(s) should run at a higher service level.

Although CPSM and the WUI are not yet a replacement for a CICS monitor, the CPSM/WUI is a tremendous tool for spotting hung transactions, disabled/released resources, dump activity, etc from a single location.

It is also a tremendous tool for a single point of corrective action.

When customized with your own menus and views, you can create a tremendous cross-plex exception monitor that gives you immediate visibility to error conditions no matter where they come from.

The ability to issue cross plex commands and see the results frees you from the MVS ROUTE command, the potential WTO buffer shortage problems and the coordinated naming conventions required to exploit it.

CPSM and the WUI are not yet the "be all to end all", but it is a great start and IBM appears to be completely behind the product.

While the "starter set" is nice, the real power comes with an effective customization based on your monitoring requirements. It is easy to customize and well worth the minor investment in time to master the tailoring. The basic menu and view tailoring is easy.

It is also possible to create customized URL's that can be imbedded in other web pages and incorporated in online documentation. You could have a project to update Web based Operations procedures to include step by step procedures that actually link to the WUI (in a frame) for the operator action.