Skip to Main Content
IBM Sterling


This portal is to open public enhancement requests for IBM Sterling products and services. 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 Submitted
Created by Guest
Created on Oct 30, 2024

Keep Netmap CREATED, UPDATED, USED AS xNODE fields

There are inconsistencies with the logic of the NETMAP entry fields, CREATED, UPDATED, and USED AS xNODEs, as they can lose true history of the netmap entries.


CREATED Date/Time stamp is lost on the netmap unload and load process and if $$REPLACE is used to modify existing entries.

  1. Request to keep the original CREATED date/time stamps during DGADNTLD unload and load process. This will keep either the 1st time the fields were implemented or the true historical date the netmap entry was defined.

  2. Request to change $$REPLACE to verify if the netmap entry exists before performing the delete and deleting CREATED, UPDATED, USED AS xNODE fields. if the netmap entry exists, leave all fields alone, except the UPDATED field.


UPDATED Date/Time stamp is lost on netmap unload and load process. Also, UPDATED has incorrect information if $$UPDATE is used when netmap entry does not exist because $$UPDATE will perform $$INSERT.

  1. Request to keep the original CREATED date/time stamps during DGADNTLD unload and load process. This will keep either the 1st time the fields were implemented or the true historical date the netmap entry was defined.

  2. Request to change $$UPDATE or $$REPLACE to verify if the netmap entry exists performing the request. If the netmap entry does not exist, the $$UPDATED and $$REPLACE should change the UPDATED date/time stamp because these requests should be treated as $$INSERT.


USED AS xNODE date/time stamp is lost on $$REPLACE. Also the USED as xNODE will have older date/time stamps after the DGADNTLD unload and load process.

  1. Noted above twice for request to change $$REPLACE to verify if netmap entry exists. if yes, dont delete the fields.

  2. The USED AS xNODE fields are unload and loaded for new NETMAP vsam builds. The CREATED date will change to current date/time stamp will be when the DGADNTLD LOAD batch job executes. In this case, the CREATED date will be newer than the last ISED AS xNODE dates.

This is already in process to keep history of previous netmap vsam file. Requesting to keep all 4 fields and update the netmap $$update and $$replace commands

What is your industry? Financial Markets
How will this idea be used?

The idea is to track the historical events on each netmap entry better and not lose them as per procedural or BAU netmap updates.