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 System Management
Created by Guest
Created on Jan 24, 2013

Change cache algorithm to manage XML-converters in ICON

The ICON parameter MAXCVRT to set cache size of XML-converters is fine.

What is not optimal is the algorithm used to unload/load XML-converters if the cache is full.

current algorithm: Due to some discussions with IBM employees the less used converter will be unloaded. If two converter have exactly the same usage count the least recently used will be unloaded. Every time a converter will be loaded its usage counter starts with zero.

Because every time the counter starts with zero the risk is very high that a just loaded converter will unloaded again after first usage.

A more efficient algorithm would be the simple LRU (least recently used, http://en.wikipedia.org/wiki/Cache_algorithms#Least_Recently_Used)

To demonstrate these effects I wrote a simulation program that simulates the cache behavior in dependence of cache size in our (credit-suisse) future expected production environment: We plan to migrate our widely used CORBA infrastructure through web services. To simulate the cache I just took all CORBA requests (i.e. timestamp, operation name) from one day an executed the simulation program (see attachement)

Idea priority High
  • Guest
    Reply
    |
    Jun 6, 2014

    This requirement has also been implemented in IMS Version 12, with apar PI16271, PTF UI18463.

  • Guest
    Reply
    |
    Jun 6, 2014

    This requirement has been implemented in IMS Version 13, with apar PI16273, PTF UI18464.
    The algorithm for determining which converter to unload has been changed, so that only the least recently used will be considered.