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 Client Install
Created by Guest
Created on Feb 13, 2018

Installationmanager for IDz language independend from OS

A way to preset the language of the installation manager itself (to english) during (silent) installation is needed.
Adding "-nl en" to the command line for installation of IM has only two effects:
- output during installation is in english
- installation manager in Windows-start is named in english.
By now starting the IM ignores this and switches back to operating system language.
Changing IBMIM.ini file or shortcut in Windows-Start is no solution because they are created by installation and the clients can't be changed centrally afterwards.

Idea priority High
  • Guest
    Reply
    |
    May 7, 2018

    Thank you for taking the time to suggest an enhancement to our product. Many of our product enhancements result from feedback from our customers, so your input is always very important to us. However, your request for enhancement is not currently aligned with our product strategy and vision and we have no plans to address your request in the near future. Again, thank you for your suggestion and continued support.

  • Guest
    Reply
    |
    Mar 23, 2018

    We have choosed to use the Packaging Utility, because we don't have any access to the clients of our developers. Nearly all of them are external suppliers.
    Normally neither we nor the users themself are authorisized to change the registry manually or via scripting. Parameters the users may change are sometimes reset to the company defaults by administration.
    Our chalange is to provide a global solution fitting to all of our suppliers. That's why the two PMRs are in development.

  • Guest
    Reply
    |
    Mar 20, 2018

    An alternate method of globally setting the runtime language for all Eclipse-based products would be to define the following environment variable on the client workstations:
    JAVA_TOOL_OPTIONS=-Dosgi.nl=en_DE

    The osgi.nl system property is functionally equivalent to the -nl command line/eclipse.ini option, and determines the displayed language for Eclipse applications. The JAVA_TOOL_OPTIONS environment variable offers a way to globally set the option for all Eclipse applications, rather than a piecemeal approach for each individual Eclipse application, so this approach may satisfy both this RFE and the two PMRs on the same subject.

    Would it be possible for your workstation deployment mechanism to set the JAVA_TOOL_OPTIONS environment variable on each of your client workstations? This would only need to be done once per workstation. A Windows registry editor script could be used to programmatically create environment variables under the HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\Environment registry key.