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 Apr 8, 2026

CEEROPT ENVAR=(('NLSPATH=should accept path coded in USSHOME SYSIN Parm .

Hi,

We have a customized CEEROPT module where i am using ENVAR=(('NLSPATH=/usr/lpp/cics/cicsts61.. , I am upgrading the CICS to CICSTS6.3 now i am reassembling it with parm ENVAR=(('NLSPATH=/usr/lpp/cics/cicsts63.. , as per the current setup CEEROPT we have to change for every upgrade.

The path /usr/lpp/cicsts63 is same as USSHOME path so my ask is if one generic way we can code in NLSPATH which will resolve the path coded in USSHOME.

Benefit of doing it is CEEROPT we don't have to change it for every release.

Idea priority Low
  • Admin
    Mark Pocock
    May 22, 2026

    This idea is being rejected.

    CICS is not involved in processing any content within the CEEROPT file or in using the NLSPATH setting, so cannot make a change to allow this symbolic reference to be resolved.

    The NLSPATH could use a fixed location that either holds a copy of the required messages file or has a symbolic link to the actual file. That avoids having to update CEEROPT during a CICS upgrade. Both of those methods would still involve a change in some way when CICS was upgraded (either copying the file or changing the symbolic link), which still might not be suitable.


    CEEROPT is processed by LE, so raising a new idea against LE would be an option if the other suggestions are not suitable.

  • Guest
    Apr 21, 2026

    Hi Mark, 

    Our complete path is ENVAR=(('NLSPATH=/usr/lpp/cicsts/cicsts63/wlp/lib/native
    /zos/s390x/nls/wola_cics_messages.cat'),OVR), we use this for WOLA for Liberty  connectivity. 

    /usr/lpp/cicsts/cicsts63 value is same for USSHOME.