Skip to Main Content
IBM Power Ideas Portal

This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. 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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Future consideration
Workspace IBM i
Created by Guest
Created on Oct 11, 2019

Allow naming threading resources from PASE for debugging purposes

Being able to name pthread threads, mutexes, locks, and other multi-threading resources was added to the ILE in IBM i 7.1. Thread naming is a popular non-POSIX extension to pthread, but other pthread objects being nameable is an IBM i-specific change. However, this functionality wasn't added to PASE, and AIX has no functional equivalent. This means applications using PASE cannot name threads without a somewhat hairy manual call to the ILE, including converting strings and only working on the current thread due to an inability to convert PASE to ILE pthread handles.

What could be added is a version of pthread_setname_np (and others) that work with PASE pthread handles. In case AIX decides to add this functionality in the future, they can be prefixed with Qp2 for PASE specific functionality, like Qp2getifaddrs. Alternatively or in addition to this, a generic way to convert PASE to ILE pthread handles could be useful.

Use Case:

Being able to name threads would simplify debugging threaded applications; particularly heavily multi-threaded PASE applications where there are several similar threads running concurrently (say, in a thread pool, where all workers have the same thread function), but must be distinguished. A user could go into "Work with Jobs", select the job, show its threads, and all threads with their names would be shown.

Being able to name other resources could be useful, but may require more invasive changes to program portability; whereas thread naming is usually accounted for by programs and require minimal changes for PASE.

Idea priority Low
  • Guest
    Oct 12, 2019

    Maybe also add A kind of stack trace for messages created inthese calls... this is perhaps a candidate for an other RFE i will post