IBM Support

IV58508: SET VALUE TO NULL IN RULES YOU WILL GET NULLPOINTER EXCEPTION

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When you set value to null in rules you will get
    NullPointerException. Currently it is not supported to setting
    value to a null in Rules in a fields which required conversion
    from any date types to string.
    
    Fix is required to that will set value to null.
    
    
    STEPS TO REPRODUCE:
    -----------------------------------
    1.  Login to MAM.
    2.  Open "Integration" > "Enterprise Services" application.
    3.  Open "MXWOInterface" (work order).
    4.  Select "WORKORDER" in Object Structure Sub-Records.
    5.  Open "Object Processing Rules" sub-tab, and click on "new
    row".
    6.  Create a processing rule with the following values.
    
    Rule     : TESTRULE01 (Test Rule 01)
    Action   : Set Data
    Sequence : 1 (default)
    Enabled? : Checked (default)
    Apply on Primary Object Insert? : Checked (default)
    Apply on Primary Object Update? : Checked (default)
    
    7.  Click on "Sub-Record Fields", and click on "New Row".
    8.  Add the following object field.
    
    Field : TARGSTARTDATE
    Value : Selected, and no value (NULL) is set.
    
    9.  Open "System Configuration" > "Platform Configuratoin" >
        "Cron Task Setup".
    10. Open "JMSSEQCONSUMER" (JMS sequencial queue consumer).
    11. Check "Active?" of "SEQQIN" and "SEQQOUT" instances, and
        save it.
    
    12. Open "Work Orders" > "Work Order Tracking" application.
    13. Create a new work order of which work order number (WONUM)
    is   "1028" if you do not have it.
    
    This work order record is overwritten with the following import
    data ("test.xml" sent from the customer).
    
    <?xml version="1.0" encoding="UTF-8"?>
    <max:SyncMXWO xmlns:max="http://www.ibm.com/maximo">
      <max:MXWOSet>
        <max:WORKORDER action="Change">
          <max:DESCRIPTION>test</max:DESCRIPTION>
          <max:SITEID>BEDFORD</max:SITEID>
          <max:WONUM>1208</max:WONUM>
          <max:TARGSTARTDATE>2014-03-30</max:TARGSTARTDATE>
        </max:WORKORDER>
      </max:MXWOSet>
    </max:SyncMXWO>
    
    14. Open "Integration" > "External Systems".
    15. Open "EXTSYS1", and open "Enterprise Services" tab.
    16. Select "MXWOInterface" (work order), and click on "Data
    Import".
    17. Select "test.xml" which changes the work order created
        at step #13, and click on OK.
    
    18. See SystemOut.log and find the following error.
    
    java.lang.NullPointerException
    at
    psdi.iface.mos.ConversionUtil.stringToDate(ConversionUtil.java:5
    6)
    .....
    

Local fix

  • Enter a Value
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Any user who creates inbound processing rules to set vaue to *
    * null and field is not a string                               *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Rules processing is not handling setting value to null       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Prior to the fix the only way not to set field is to         *
    * restrict it.                                                 *
    ****************************************************************
    

Problem conclusion

  • Processing rules need to support setting value to null
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV58508

  • Reported component name

    INTEGRATION

  • Reported component ID

    5724R46I1

  • Reported release

    750

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2014-04-01

  • Closed date

    2014-04-02

  • Last modified date

    2014-04-02

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

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

Modules/Macros

  • MIF
    

Fix information

  • Fixed component name

    INTEGRATION

  • Fixed component ID

    5724R46I1

Applicable component levels

  • R750 PSY

       UP

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

Document Information

Modified date:
02 April 2014