Skip to Main Content
IBM System Storage Ideas Portal

This portal is to open public enhancement requests against IBM System Storage 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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Created by Guest
Created on Mar 3, 2017

Improve information in ANR3605E messages

Any ANR3605E message which appears in the server activity log does not indicate which storage agent is the subject of the communication failure. In large LAN-free environments (10s or 100s of storage agents) this can make identifying the source of the error difficult.

The only clue provided in the message is the session number, but in such cases this usually references a session which no longer exists and no other message accompanies it to say which system is the source of the session which has ended.

Such storage agent sessions are typically long-established - beginning either when the storage agent was last restarted, or when the server instance was last restarted. If the duration of the session exceeds the activity log retention then all evidence as to the originator of the session has been lost.

Ideally the name of the storage agent needs to be included in the message text.

Idea priority Low