Skip to Main Content
IBM Z Software


This portal is to open public enhancement requests against IBM Z Software products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Delivered
Categories Runtime
Created by Guest
Created on Aug 23, 2012

Report detailed target AOR health to MVS WLM using IWM4HLTH

Looking for an alternative to having to use "fat" TORs to receive inbound web requests and then dynamically route business logic to target AORs.

Problem:
A CICSplex topology typically consists of TORs and AORs . The TORs and AORs are used to separate the transport logic from business logic respectively. In most cases, the TORs perform dynamic routing to the AORs based on WLM (Workload Manager) algorithms to select the healthiest target AOR with the shortest queue of work using the CICSPlex System Manager WLM component of the CICS Transaction Server for z/OS. When the inbound transport to the TORs is IP traffic from the web, the role of the TORs becomes more complex and more application logic must run within the TOR before the business logic can be dynamically routed to an AOR as the IP socket connection must be owned and managed by the TOR at all times. This typically involves codepage decoding/encoding schemes, security, webservices pipeline handlers...etc. The AOR has no knowledge of the socket connection and cannot transmit data outbound on the socket. The AOR must return its business data to the TOR and the TOR must apply logic for preparing and transmitting the business data to the network. When the TORs are managing socket connections, they represent significant overhead in the transaction lifecycle as well as the risk of running complex user code in the TOR to manage the connection and ensure the right data is sent on the right connection.

Idea priority Medium
  • Guest
    Reply
    |
    Jun 16, 2017

    This RFE is satisfied by CICS TS 5.4 which is generally available from today June 16th 2017.
    For more information see the announcement letter https://www-01.ibm.com/common/ssi/cgi-bin/ssialias?infotype=an&subtype=ca&supplier=897&letternum=ENUS217-113

    CICS now uses the z/OS Workload Manager Health (IWM4HLTH) API as a means of controlling the flow of work into a CICS region. This service is used to inform z/OS WLM of the health state of a server (in this context, a CICS region). This can allow a CICS region to have a warm-up process after the end of system initialization until the region is fully ready to receive work.

    The WLMHEALTH system initialization parameter specifies the parameters to be used by CICS on z/OS WLM Health API (IWM4HLTH) calls, which CICS makes to inform WLM about the health state of a CICS address space. You can view the z/OS WLM health service settings for CICS regions through the INQUIRE WLMHEALTH SPI command or the CEMT INQUIRE WLMHEALTH command. You can also change the health service settings by using the SET WLMHEALTH SPI command or CEMT SET WLMHEALTH.

    The primary user of CICS regions' health indicator values is TCP/IP, but the values are also used by CICS and CPSM components. When TCP/IP is configured, the health indicator will feed into the WLM server recommendations to sysplex distributor affecting when connections are established with a CICS region. In CICS, the health indicator will affect when MQ trigger monitors, the MQ Bridge, and user-written MQ consumers that are using the MQMONITOR resource are started and stopped. In addition, CPSM workload management will take into account the health state of target AORs when deciding where to route work.

  • Guest
    Reply
    |
    May 16, 2017

    This RFE is satisfied by CICS TS 5.4 which was announced on May 16th 2017 with a planned general availability date of June 16th 2017.
    For more information see the announcement letter https://www-01.ibm.com/common/ssi/cgi-bin/ssialias?infotype=an&subtype=ca&supplier=897&letternum=ENUS217-113

    CICS now uses the z/OS Workload Manager Health (IWM4HLTH) API as a means of controlling the flow of work into a CICS region. This service is used to inform z/OS WLM of the health state of a server (in this context, a CICS region). This can allow a CICS region to have a warm-up process after the end of system initialization until the region is fully ready to receive work.

    The WLMHEALTH system initialization parameter specifies the parameters to be used by CICS on z/OS WLM Health API (IWM4HLTH) calls, which CICS makes to inform WLM about the health state of a CICS address space. You can view the z/OS WLM health service settings for CICS regions through the INQUIRE WLMHEALTH SPI command or the CEMT INQUIRE WLMHEALTH command. You can also change the health service settings by using the SET WLMHEALTH SPI command or CEMT SET WLMHEALTH.

    The primary user of CICS regions' health indicator values is TCP/IP, but the values are also used by CICS and CPSM components. When TCP/IP is configured, the health indicator will feed into the WLM server recommendations to sysplex distributor affecting when connections are established with a CICS region. In CICS, the health indicator will affect when MQ trigger monitors, the MQ Bridge, and user-written MQ consumers that are using the MQMONITOR resource are started and stopped. In addition, CPSM workload management will take into account the health state of target AORs when deciding where to route work.

  • Guest
    Reply
    |
    May 15, 2017

    This is something we would like to address. The RFE is being moved into 'Planned for Future release' status. Please note:
    IBM’s statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM’s sole discretion. Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remains at our sole discretion.

  • Guest
    Reply
    |
    May 19, 2016

    Whilst this requirement is valid, based on our current plans and priorities, it is not likely that this could be implemented in the next 12 months, or in the next CICS TS release. Correspondingly this requirement is being declined at this point. The requirement will be kept in the RFE system and might be reassessed in the future. You also have an opportunity to resubmit in twelve months time if you wish it to be reconsidered then.

  • Guest
    Reply
    |
    Oct 5, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - Transaction Processing
    Product - CICS Transaction Server

    For recording keeping, the previous attributes were:
    Brand - WebSphere
    Product family - Transaction Processing
    Product - CICS Transaction Server