IBM Support

IJ44452: PROCESSING RULES STARTED TO FAIL AFTER APPLYING 7612 IFIX, STRING VALUES LIKE Y OR N ARE NOT ACCEPTABLE, ONLY 1 OR 0.

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • PROBLEM DESCRIPTION:
    Processing rules started to fail after applying 7612 IFIX,
    String values like Y or N are not acceptable, only 1 or 0.
    
    
    STEPS TO REPRODUCE:
    The steps below use MAXDEMO as an example:
    
    1)Go to MXASSETInterface Enterprise Service.
    
    Click on New Row in Object Structure Processing Rules.
    Fill out as below:
    Rule: Test
    Action: SET
    
    Click on Sub-Record Fields button.
    Click on New Row.
    
    Field: MOVED
    Value: Y
    
    2)Import in the External System the XML below:
    <?xml version="1.0" encoding="UTF-8"?>
    <SyncMXASSET xmlns="http://www.ibm.com/maximo"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    creationDateTime="2018-02-15T22:47:37-06:00" baseLanguage="EN"
    messageID="1518756456960817941">
         <MXASSETSet>
           <ASSET action="AddChange">
             <ASSETNUM>PF1112</ASSETNUM>
             <SITEID>BEDFORD</SITEID>
    
     <DESCRIPTION>test</DESCRIPTION>
    
      </ASSET>
         </MXASSETSet>
       </SyncMXASSET>
    
    RESULTS:
    Import will fail leading in the stack below:
    [11/28/22 9:18:33:490 PST] 000000ae SystemOut     O 28 Nov 2022
    09:18:33:490 [ERROR] [MAXIMO] [] BMXAA7094E - The entered value
    Y is not valid. Enter a valid integer value.
    psdi.util.MXApplicationException: BMXAA7094E - The entered value
    Y is not valid. Enter a valid integer value.
    	at psdi.iface.mos.ConversionUtil.stringToInt(ConversionUtil.ja
    va:238)~[businessobjects.jar:?]
    	at psdi.iface.mos.ConversionUtil.setValueAsObject(ConversionUt
    il.java:895)~[businessobjects.jar:?]
    	at psdi.iface.proc.ProcProcesser.setReplaceColumns(ProcProcess
    er.java:600)~[businessobjects.jar:?]
    	at psdi.iface.proc.ProcProcesser.processAssignments(ProcProces
    ser.java:346)~[businessobjects.jar:?]
    	at psdi.iface.proc.ProcProcesser.checkAssignmentProcs(ProcProc
    esser.java:143)~[businessobjects.jar:?]
    	at psdi.iface.proc.PreRulesProcessor.applyRulesToLevel(PreRule
    sProcessor.java:135)~[businessobjects.jar:?]
    	at psdi.iface.proc.PreRulesProcessor.applyRules(PreRulesProces
    sor.java:102)~[businessobjects.jar:?]
    	at psdi.iface.mic.MicSetIn.applyXMLRules(MicSetIn.java:246)
    ~[businessobjects.jar:?]
    	at psdi.iface.mos.MosProcessImpl.fillMaximoTables(MosProcessIm
    pl.java:766)~[businessobjects.jar:?]
    	at psdi.iface.mos.MosProcessImpl.processExternalData(MosProces
    sImpl.java:356)~[businessobjects.jar:?]
    	at
    psdi.iface.mic.MicSetIn.processExternalData(MicSetIn.java:149)
    ~[businessobjects.jar:?]
    	at psdi.iface.mic.EntMicService.processDataIn(EntMicService.ja
    va:1476)~[businessobjects.jar:?]
    	at psdi.iface.mic.EntMicService.processExternalData(EntMicServ
    ice.java:1372)~[businessobjects.jar:?]
    	at psdi.iface.jms.QueueToMaximoProcessor.processMessage(QueueT
    oMaximoProcessor.java:129)~[businessobjects.jar:?]
    	at psdi.iface.jms.JMSContQueueProcessor.processMessage(JMSCont
    QueueProcessor.java:227)[mboejb.jar:?]
    	at psdi.iface.jms.JMSListenerBean.onMessage(JMSListenerBean.ja
    va:203)[businessobjects.jar:?]
    	at psdi.iface.jms.MDBProxyJMSContQueueProcessor_1_5bf7eeaa.onM
    essage(MDBProxyJMSContQueueProcessor_1_5bf7eeaa.java)[?:?]
    	at com.ibm.ws.sib.api.jmsra.impl.JmsJcaEndpointInvokerImpl.inv
    okeEndpoint(JmsJcaEndpointInvokerImpl.java:258)[com.ibm.ws.sib.s
    	at com.ibm.ws.sib.ra.inbound.impl.SibRaDispatcher.dispatch(Sib
    RaDispatcher.java:919)[com.ibm.ws.sib.server.jar:1.0.0]
    	at com.ibm.ws.sib.ra.inbound.impl.SibRaSingleProcessListener$S
    ibRaWork.run(SibRaSingleProcessListener.java:597)[com.ibm.ws.sib
    	at com.ibm.ejs.j2c.work.WorkProxy.run(WorkProxy.java:669)
    [com.ibm.ws.runtime.jar:?]
    	at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1909)
    [com.ibm.ws.runtime.jar:?]
    
    EXPECTED RESULTS:
    No errors should return.
    
    
    REPORTED IN VERSION:
    
    Tivoli's process automation engine 7.6.1.2-IFIX20220628-1241
    Build 20200715-0100 DB Build V7612-284 HFDB Build HF7612-129
    

Local fix

  • NA
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Maximo MIF users                                             *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Importing with rules when payload contains Y or N for YORN   *
    * values ==> BMXAA7094E - The entered value Y is not valid.    *
    * Enter a valid integer value.                                 *
    ****************************************************************
    PROBLEM DESCRIPTION:
    After applying 7.6.1.2 IFIX022 and MIF IFIX014, processing rules
    started to fail with BMXAA7094E - The entered value Y is not
    valid. Enter a valid integer value.
    Only 1 or 0 are accepted.
    STEPS TO REPRODUCE:
    The steps below use MAXDEMO as an example:
    1)Go to MXASSETInterface Enterprise Service.
    Click on New Row in Object Structure Processing Rules.
    Fill out as below:
    Rule: Test
    Action: SET
    Click on Sub-Record Fields button.
    Click on New Row.
    Field: MOVED
    Value: Y
    2)Import in the External System the XML below:
    <?xml version="1.0" encoding="UTF-8"?>
    <SyncMXASSET xmlns="http://www.ibm.com/maximo"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    creationDateTime="2018-02-15T22:47:37-06:00" baseLanguage="EN"
    messageID="1518756456960817941">
    <MXASSETSet>
    <ASSET action="AddChange">
    <ASSETNUM>PF1112</ASSETNUM>
    <SITEID>BEDFORD</SITEID>
    <DESCRIPTION>test</DESCRIPTION>
    </ASSET>
    </MXASSETSet>
    </SyncMXASSET>
    RESULTS:
    Import will fail leading in the stack below:
    [11/28/22 9:18:33:490 PST] 000000ae SystemOut O 28 Nov 2022
    09:18:33:490 [ERROR] [MAXIMO] [] BMXAA7094E - The entered value
    Y is not valid. Enter a valid integer value.
    psdi.util.MXApplicationException: BMXAA7094E - The entered
    value
    Y is not valid. Enter a valid integer value.
    at psdi.iface.mos.ConversionUtil.stringToInt(ConversionUtil.ja
    va:238)~[businessobjects.jar:?]
    at psdi.iface.mos.ConversionUtil.setValueAsObject(ConversionUt
    il.java:895)~[businessobjects.jar:?]
    at psdi.iface.proc.ProcProcesser.setReplaceColumns(ProcProcess
    er.java:600)~[businessobjects.jar:?]
    at psdi.iface.proc.ProcProcesser.processAssignments(ProcProces
    ser.java:346)~[businessobjects.jar:?]
    at psdi.iface.proc.ProcProcesser.checkAssignmentProcs(ProcProc
    esser.java:143)~[businessobjects.jar:?]
    at psdi.iface.proc.PreRulesProcessor.applyRulesToLevel(PreRule
    sProcessor.java:135)~[businessobjects.jar:?]
    at psdi.iface.proc.PreRulesProcessor.applyRules(PreRulesProces
    sor.java:102)~[businessobjects.jar:?]
    at psdi.iface.mic.MicSetIn.applyXMLRules(MicSetIn.java:246)
    ~[businessobjects.jar:?]
    at psdi.iface.mos.MosProcessImpl.fillMaximoTables(MosProcessIm
    pl.java:766)~[businessobjects.jar:?]
    at psdi.iface.mos.MosProcessImpl.processExternalData(MosProces
    sImpl.java:356)~[businessobjects.jar:?]
    at
    psdi.iface.mic.MicSetIn.processExternalData(MicSetIn.java:149)
    ~[businessobjects.jar:?]
    at psdi.iface.mic.EntMicService.processDataIn(EntMicService.ja
    va:1476)~[businessobjects.jar:?]
    at psdi.iface.mic.EntMicService.processExternalData(EntMicServ
    ice.java:1372)~[businessobjects.jar:?]
    at psdi.iface.jms.QueueToMaximoProcessor.processMessage(QueueT
    oMaximoProcessor.java:129)~[businessobjects.jar:?]
    at psdi.iface.jms.JMSContQueueProcessor.processMessage(JMSCont
    QueueProcessor.java:227)[mboejb.jar:?]
    at psdi.iface.jms.JMSListenerBean.onMessage(JMSListenerBean.ja
    va:203)[businessobjects.jar:?]
    at psdi.iface.jms.MDBProxyJMSContQueueProcessor_1_5bf7eeaa.onM
    essage(MDBProxyJMSContQueueProcessor_1_5bf7eeaa.java)[?:?]
    at com.ibm.ws.sib.api.jmsra.impl.JmsJcaEndpointInvokerImpl.inv
    okeEndpoint(JmsJcaEndpointInvokerImpl.java:258)[com.ibm.ws.sib.s
    at com.ibm.ws.sib.ra.inbound.impl.SibRaDispatcher.dispatch(Sib
    RaDispatcher.java:919)[com.ibm.ws.sib.server.jar:1.0.0]
    at com.ibm.ws.sib.ra.inbound.impl.SibRaSingleProcessListener$S
    ibRaWork.run(SibRaSingleProcessListener.java:597)[com.ibm.ws.sib
    at com.ibm.ejs.j2c.work.WorkProxy.run(WorkProxy.java:669)
    [com.ibm.ws.runtime.jar:?]
    at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1909)
    [com.ibm.ws.runtime.jar:?]
    EXPECTED RESULTS:
    No errors should return.
    REPORTED IN VERSION:
    Tivoli's process automation engine 7.6.1.2-IFIX20220628-1241
    Build 20200715-0100 DB Build V7612-284 HFDB Build HF7612-129
    

Problem conclusion

  • The fix for this APAR will be contained in a future release.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ44452

  • Reported component name

    INTEGRATION

  • Reported component ID

    5724R46I1

  • Reported release

    761

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2022-12-01

  • Closed date

    2023-01-29

  • Last modified date

    2023-01-29

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    INTEGRATION

  • Fixed component ID

    5724R46I1

Applicable component levels

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSLKT6","label":"Maximo Asset Management"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"761","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

Modified date:
29 January 2023