Skip to Main Content
Cloud Management and AIOps


This is an IBM Automation portal for Cloud Management, Technology Cost Management, Network Automation and AIOps 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 Submitted
Created by Guest
Created on Oct 25, 2024

Improving Resiliency #4: avoid impacts to r3batch when SAP have enabled trace to BTCOPTIONS BATCHTRACE_MODULE / BAPI_XMI_LOGON

TWS was unable to establish a RFC connection with SAP and submit jobs when a trace was enabled to BTCOPTIONS BATCHTRACE_MODULE / BAPI_XMI_LOGON in SAP system.

 

Through the logs, the error returned was limited to "EEWO0950W the RFC user is already logged on", not providing a clear message to what could be the root cause of the issue.

 

While the trace was enabled to BTCOPTIONS BATCHTRACE_MODULE / BAPI_XMI_LOGON in SAP, the r3batch seemed to not provide the correct INTERFACE and XBP values, which prevented the operation (submit job) to complete.

 

It is required that the r3batch parses the correct arguments to the SAP system, or TWS to avoid being impacted when traces are enabled in SAP system.

Idea priority Urgent