Skip to Main Content
IBM Sterling

This portal is to open public enhancement requests for IBM Sterling products and services. 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 Not under consideration
Workspace Self Service Tool
Created by Guest
Created on Oct 29, 2020

OMoC platform cap of 1MB for the YFS_EXPORT.MESSAGE needs to be increased

To troubleshoot/debug issues we need to log outgoing/incoming messages to yfs_export table and few messages are more than 1 MB. Service fails if YFS_EXPORT.MESSAGE is more than 1 MB.This imitation needs to be increased as DB2 supports 2GB of CLOB data to be stored in YFS_EXPORT.MESSAGE.

What is your industry? Retail
How will this idea be used?

As part of the design TB is capturing Email XMLs in YFS_EXPORT table.

An email is sent to customer ON_SUCCESS of CREATE_CONFIRM_SHIPMENT transaction and email XML is stored in YFS_EXPORT.

For a specific order (790007814) the email XML posting to YFS_EXPORT is failing with error "The data bound to the column is invalid in this context." SQLState Value=22001.

Below is the query

INSERT INTO YFS_EXPORT(EXPORT_KEY,SYSTEM_NAME,API_NAME,FLOW_NAME,SUB_FLOW_NAME,USER_REFERENCE,STATUS,MESSAGE,REPLY_TO_ID,FROM_ORG_CODE,TO_ORG_CODE,ENTERPRISE_KEY,SHIP_NODE,PRIORITY,CREATEUSERID,MODIFYUSERID,CREATEPROGID,MODIFYPROGID,CREATETS,MODIFYTS,LOCKID) values ( '202010141853251216394464',' ',' ','TBEmailMsgToDB','YIFTBEmailMsgToDB',' ','00','A-Clob-Value','',' ',' ',' ',' ',0.0,'TBProcessDCMessageIntegServer','TBProcessDCMessageIntegServer','TBProcessDCMessageIntegServer','TBProcessDCMessageIntegServer','2020-10-14T18:53:25','2020-10-14T18:53:25',0 )

The length of the XML to be inserted in CLOB column is 1359320 in Unicode. The length allowed for CLOB in DB2 is 2 GB.