IBM Support

IJ49455: USING THE EXPORT FUNCTIONALITY IN THE EXTERNAL SYSTEM WHERE A BATCH SIZE IS DEFINED USING JSON FORMAT, DEPENDING ON WHETHER THE

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:
    Using the export functionality in the external system where a
    batch size is defined using JSON format, depending on whether
    the result is under or over, the batch limit fields are
    suppressed.
    
    STEPS TO REPRODUCE:
    The steps below use MAXDEMO as an example:
    
    1)Go to the Publish Channel MXPERSONInterface and check Publish
    JSON checkbox.
    
    2)Go to External System EXTSYS1 => Publish Channels tab =>
    select MXPERSONInterface publish channel and click on Data
    Export button.
    
    Set 2 in Batch Size.
    
    Click OK.
    
    3)Click on Data Export button again.
    
    Set 20 in Batch Size.
    Set personid like 'BO%' in Export Condition
    
    Click OK.
    
    RESULTS:
    In step 2 where the total amount of records is over the batch
    limit, there are no null values, "_action" is exported.
    
    In step 3 where the total amount of records is under the batch
    limit, there are null values, "_id" appear in the result, which
    is the primary key of the table, "_action" is not exported.
    
    EXPECTED RESULTS:
    If the result is under or over the batch limit the format of the
    export file needs to be the same
    
    REPORTED IN VERSION:
    TPAE 7613
    

Local fix

  • NA
    

Problem summary

  • ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Using the export functionality in the external system where  *
    * a                                                            *
    * batch size is defined using JSON format, depending on        *
    * whether                                                      *
    * the result is under or over, the batch limit fields are      *
    * suppressed.                                                  *
    ****************************************************************
    Dropnull behaves differently for pagination and non-pagination
    exports
    

Problem conclusion

  • Added a system property that will control the dropnull
    behaviour
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ49455

  • Reported component name

    INTEGRATION

  • Reported component ID

    5724R46I1

  • Reported release

    761

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2023-12-06

  • Closed date

    2024-02-07

  • Last modified date

    2024-02-07

  • 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:
07 February 2024