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:
Post your ideas
Start by posting 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
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notifications on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
Please use the following category to raise ideas for these offerings for all environments (traditional on-premises, containers, cloud):
Cloud Pak for Multicloud Management
Cloud Pak for Network Automation - incl Orchestration and Performance Management
Cloud Pak for Watson AIOps - incl Netcool Operations Management portfolio
Edge Application Manager
IBM Observability with Instana
ITM-APM Products - incl IBM Tivoli Monitoring v6 and Application Performance Monitoring v8
Workload Automation - incl Workload Scheduler
Tivoli System Automation - inc Tivoli System Automation Application Manager (SA AM), Tivoli System Automation for Multiplatforms (SA MP)
Modify how DA launches a job to mimic how FTA launches the same job
FTA launches a job by first launching jobmanrc and then if LOCAL_RC_OK is set to true, it launches .jobmanrc in the logon user's home dir. In this process, it never sets the variable PATH.
A DA launches a job by first launching taskLauncher.sh and then if LOCAL_RC_OK is set to true, it launches .jobmanrc in the logon user's home dir. In this process, it sets the variable PATH to a new set of DA directories and then appends the original value of PATH.
I am in the process of upgrading RCCL from 8.5.1 to 126.96.36.199. One of their FTAs, which is at v9.2, runs a job successfully, bu the same job fails in 9.4 DA. When the FTA runs a job script that runs the curl command without fully specifying the path to it, the system finds it in, /usr/bin. But, when the DA runs it, it finds it in /opt/IBM/IWA/TWS/ITA/cpa/ita/curl, which fails with the following error message:
curl: error while loading shared libraries: libgsk8sys_64.so: cannot open shared object file: No such file or directory
One of the ways this can be fixed is by setting LD_LIBRARY_PATH to /opt/ibm/iwa/TWS/tmpGSKit64/8/lib64 in .jobmanrc in the logon user's home dir. But, no custom configuration should be required to run a job by the DA that runs successfully by the FTA. The DA should be able to run it as is. To fulfill this requirement, I found that PATH was being set in /opt/IBM/IWA/TWS/bin/taskLauncher.sh as PATH=$PATH:/bin:/usr/bin causing the curl command to be found in DA's dir before finding the system default one in /usr/bin. I reversed the order so that the system default one is found first, i.e., PATH=/bin:/usr/bin:$PATH. This resulted in the job running successfully without any more custom configuration.
I believe this is the way it should've been setup to begin with so that same behavior as FTA can be expected from the DA. I would like this to be reviewed and if agreed, would like to see this changed in the next release/fix pack.
The supporting files and joblogs can be found in the case TS002751065.
Do not place IBM confidential, company confidential, or personal information into any field.