IBM Support

PI75315: OSLC PUT REQUEST FAILS TO UPDATE ATTRIBUTES OF TYPE CCM_TEXT.

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

  • Prerequsiites:
    
    1. Change 5.3.1.1 iFix 7. (it was reported this problem did not
    exist before now).
    
    2. OSLC mechanism to update a CR object. Update should be of an
    attribute of type CCM_TEXT (attr1), and not CCM_TEXT (attr2),
    for example STRING (for example a listbox).
    
    
    Steps to reproduce:
    
    1. Initiate the OSLC Put request to update a CR object,
    specifically attr1 and attr2.
    
    
    Expected Results:
    
    1. attr1 and attr2 both updated with new values.
    
    OR
    
    2. An error is displayed informing the user that the values
    failed to be updated.
    
    
    Actual Results:
    
    1. attr2 is updated but attr1 value is not changed.
    
    2. There is no indication to the user (200 OK request received)
    or in the log files that there is a reason why attr1 was not
    updated.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * ALL USERS                                                    *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Prerequsiites:                                               *
    *                                                              *
    * 1. Change 5.3.1.1 iFix 7. (it was reported this problem did  *
    * not                                                          *
    * exist before now).                                           *
    *                                                              *
    * 2. OSLC mechanism to update a CR object. Update should be of *
    * an                                                           *
    * attribute of type CCM_TEXT (attr1), and not CCM_TEXT         *
    * (attr2),                                                     *
    * for example STRING (for example a listbox).                  *
    *                                                              *
    *                                                              *
    * Steps to reproduce:                                          *
    *                                                              *
    * 1. Initiate the OSLC Put request to update a CR object,      *
    * specifically attr1 and attr2.                                *
    *                                                              *
    *                                                              *
    * Expected Results:                                            *
    *                                                              *
    * 1. attr1 and attr2 both updated with new values.             *
    *                                                              *
    * OR                                                           *
    *                                                              *
    * 2. An error is displayed informing the user that the values  *
    * failed to be updated.                                        *
    *                                                              *
    *                                                              *
    * Actual Results:                                              *
    *                                                              *
    * 1. attr2 is updated but attr1 value is not changed.          *
    *                                                              *
    * 2. There is no indication to the user (200 OK request        *
    * received)                                                    *
    * or in the log files that there is a reason why attr1 was not *
    * updated.                                                     *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • This issue is fixed in Rational Change 5.3.1.1. ifix 11.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI75315

  • Reported component name

    TLOGIC CHANGE

  • Reported component ID

    5724V87CG

  • Reported release

    531

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-01-23

  • Closed date

    2017-03-21

  • Last modified date

    2017-03-21

  • 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

    TLOGIC CHANGE

  • Fixed component ID

    5724V87CG

Applicable component levels

  • R531 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYQQ2","label":"Rational Change"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"531","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
21 March 2017