IBM Data and AI Ideas Portal for Customers
This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. 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
Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
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.
IBM Employees should enter Ideas at https://ideas.ibm.com
My tests were run with the 3.10 distribution that provides compatibility from RHEL7 onwards.
If I regress to the 2.6 distribution (RHEL5 onwards) it fails.
From searching the kernel/glibc archives, there are differences in some of the max variable lengths. As the LSF libraries are statically linked, they have the 2.6 kernel glib2.3 definitions - so an incompatibility between the glibc version the binary is built with, and the glibc version installed.
So the solution is to use the newer distribution files.
With RHEL7 now officially end of life, we will be moving the baseline up, and plant to release a RHEL9 baseline next year.
2003: RHEL5: kernel 2.6 glibc 2.3
2013: RHEL7: kernel 3.10 glibc 2.17
2022: RHEL9: kernel 5.14 glibc 2.34
Bill,
Did you test on RHEL7 and RHEL8? getcwd() works as expected unless the number of characters is limited in the code as in getcwd(cwd, 256). I uploaded the test script along with bsub logs and strace information to the problem ticket.
Mark
The length of TMPDIR is not limited to 200 characters, there is no "allowable number of characters".
I cannot reproduce your error on my cluster with >500, >1000, >2000 characters.
The error message in your example is an OS call failing for an unspecified reason. The fact that the OS error occurs only when the directory exists suggests that a getcwd() call or similar may be failing - which may be an OS or filesystem issue.
If you wish to pursue this further, opening a ticket with Support would be the appropriate channel.
with over 1000 characters
With over 2000 characters
The limited size of this variable causes some job submission failures. When will you have a timeline for working on this issue?
We're using LSF10.1 ServicePack 14