IBM Sterling Ideas

formerly Watson Supply Chain

Submit new product ideas for IBM Sterling solutions. Before you submit, please review existing ideas; if an idea close to yours already exists, it's better to add comments or vote on the existing idea. We will review your ideas and use them to help prioritize our product development. Best of all, the portal will automatically update you when the status of your idea has been changed. Order Management, Store Engagement, Watson Order Optimizer, Inventory Visibility, CPQ and Call Center are now part of Watson Supply Chain

Connect with IBM experts and your peers on the Supply Chain Collaboration Community and the Order Management Interest Group

enhanced PARSE function

In order to use the new PARSE function as a replacement for the old RUN(submap) constructs, the PARSE function should have similar behavior as RUN(submap). This essentially requires 2 enhancements:

1.) We need to pass arguments to PARSE like "-F21 -Z28", so that PARSE will use the same error handling as our current RUN(submaps). Overriding the trace settings is also used very often, e.g. "-TIC1", as well as specifying audit settings like "-ADEU=audits" and workspace parameters like "-P512:512". Basically PARSE should be able to handle all these parameters.

2.) PARSE should throw errors and set LASTERRORMSG as well as LASTERRORCODE, so that we can use it in a VALID(PARSE(), FAIL()) construct.
  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Jan 9 2018
  • Uncommitted Candidate
How will this idea be used?
What is your industry?
What is the idea priority? Medium
DeveloperWorks ID DW_ID65753
Link to original RFE
  • Attach files
  • Admin
    Luke Raiano commented
    November 14, 2018 16:32

    1) is being investigated
    2) This function was first released in WTX 8.4.1 and should work as identified above.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    November 14, 2018 18:58

    Hi Luke. No, PARSE does not throw errors. The only way to check if PARSE worked successfully is to check if a mandatory field in the target is NONE.