IBM Support

IJ39067: PUBLISH CHANNEL SUB RECORD VALIDATION ISSUES WHEN SETUP WITH RETAIN MBOS=N

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

  • System allows to untick the "Retain Mbos" flag and save the
    publish channel which has "Object" based set rules.
    
    STEPS TO REPRODUCE:
    1. Create a publish channel with this configuration:
    a. Create Publish Channel  MYWO .
    b. Associate the OOTB Object Structure MXWO
    c. Save the publish channel
    d. Untick the  Retains Mbo s?  flag
    e. Enable Message Tracking for this publish channel.
    f. Add a Processing Rule with Action=SET
    g. Click on  Sub-Records Fields  button, dialog opens
    h. Click  New Row  button and populate  WOL1  in the  Field
    text box.
    i. Choose the  Object  Radio button. An error message
    appears. This error is expected and is not an issue for this
    document/case. The error occurs because the  Retain
    Mbo s?  flag is unticked on the Publish Channel.
    j. Click OK on the error message. "BMXAA6021E - Object
    processing rules are not allowed."
    k. Click Cancel on the Sub-Record dialog
    l. Tick the  Retain Mbos  flag on publish channel and
    repeat steps g, h and i of this section.
    m. Now it allows the user the select the  Object  radio
    button without any errors.
    n. Fill in the Object values and click OK button
    
    2. Add this publish channel the External system, provide end
    point, enable it and save the external system.
    System allows to untick the  Retain Mbos  flag and save
    the publish channel which has  Object  based set rules
    1. Open the publish channel MYWO (created above)
    2. Verify it has the Sub Record dialog with rows
    3. Exit the dialog
    4. Untick the  Retain Mbos  flag and save.
    5. Record is saved and the system did not throw any errors
    (like step-J of step 1).
    6. It should not have allowed me to save, as the publish
    channel had SET rules based on Object.
    
    EXPECTED RESULTS:
    Expecting an error message when the  Retain Mbos  flag is
    unticked on a publish channel which has object based SET rules.
    Inverse error message of BMXAA6021E (see Step J of Step 1).
    
    REPORTED IN VERSION:
    Maximo Asset Management 7.6.1.2
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Maximo MIF Publish Channel users                             *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * System allows the "Retain Mbos?" flag to be unchecked and    *
    * saved on Publish Channel having object-based set rules.      *
    ****************************************************************
    STEPS TO REPRODUCE:
    1. Create a publish channel with this configuration:
    1a. Create Publish Channel MYWO .
    1b. Associate the OOTB Object Structure MXWO
    1c. Save the publish channel
    1d. Untick the "Retains Mbos?" flag
    1e. Enable Message Tracking for this publish channel.
    1f. Add a Processing Rule with Action=SET
    1g. Click on Sub-Records Fields button, dialog opens
    1h. Click New Row button and populate WOL1 in the Field
    text box.
    1i. Choose the Object Radio button. An error message
    appears. This error is expected and is not an issue for this
    document/case. The error occurs because the Retain
    Mbo s? flag is unticked on the Publish Channel.
    1j. Click OK on the error message. "BMXAA6021E - Object
    processing rules are not allowed."
    1k. Click Cancel on the Sub-Record dialog
    1l. Tick the Retain Mbos flag on publish channel and
    repeat steps g, h and i of this section.
    1m. Now it allows the user the select the Object radio
    button without any errors.
    1n. Fill in the Object values and click OK button
    2. Add this publish channel the External system, provide end
    point, enable it and save the external system.
    System allows to untick the "Retain Mbos?" flag and save
    the publish channel which has Object based set rules
    2a. Open the publish channel MYWO (created above)
    2b. Verify it has the Sub Record dialog with rows
    2c. Exit the dialog
    2d. Untick the Retain Mbos flag and save.
    2e.Record is saved and the system did not throw any errors
    (like step-1J of step 1).
    2f. It should not have allowed me to save, as the publish
    channel had SET rules based on Object.
    EXPECTED RESULTS:
    Expecting an error message when the "Retain Mbos?" flag is
    unticked on a publish channel which has object based SET rules.
    Inverse error message of BMXAA6021E (see Step J of Step 1).
    

Problem conclusion

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

Temporary fix

Comments

APAR Information

  • APAR number

    IJ39067

  • 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-03-29

  • Closed date

    2023-08-17

  • Last modified date

    2023-08-17

  • 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:
17 August 2023