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 Not under consideration
Categories Runtime
Created by Guest
Created on Feb 19, 2020

CREATE A NEW CPSM USERID/SIGNON AFFINITY TYPE.

We found that affinity USERID/SIGNON in a trangroup has a limitation: if an AOR fails and has to be restarted, this type of affinity will not allow the signed on user to route another transaction to the this AOR.
'EYUWR003W -The affinity AOR APPLID (NNNNNNNN) is not available because the AOR job is different. The affinity remains.'
If we signoff, the affinity is deleted, and after that I can route my transaction to the AOR successfully.

Idea priority High
  • Guest
    Reply
    |
    May 27, 2020

    We have assessed this requirement. We have no current plans for this to be implemented and so 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
    |
    Mar 26, 2020

    There aren't specifics reasons because the users must return to the restarted Region, but.......if we have 2 WLM target Regions (R1 and R2) and R2 goes down, after R2 is restarted why 50% users can't continue working on R2? Now, they can only work in R1, right? And if R1 goes down? Or if R2 goes down newly, then 50% + 50% users can't working no more on R2?

  • Guest
    Reply
    |
    Mar 25, 2020

    Thanks for raising the RFE. CPSM WLM does support a USERID/SYSTEM affinity, which might help with your scenario but you would lose the affinity to that region as it shutsdown. It sounds like you must return to the restarted region again, is that correct?

    If so, could you also provide a little more information on the nature of the affinity you have with this region that would require it to be maintained across a region restart?