IBM Support

IV95836: MAXMESSAGE ENTRY MISSING FOR OSLC#STABLERESOURCENOTFOUND ERROR

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • There is no maxmessage defined for the error
    oslc#stableresourcenotfound
    
    Steps to reproduce
    
    The error occurs when the stableid can't be found when querying
    through multiple pages of OSLC data.
    
    When the error occurs the logs print the message
    oslc#stableresourcenotfound instead of an associated maxmessage
    entry describing the cause of the issue.
    
    Open Database Configuration and select messages, then filter
    for stableresourcenotfound and no results will be returned as
    the Message Group and Key are not defined for the error.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Maximo integration OSLC users                                *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * There is no maxmessage defined for the error                 *
    * oslc#stableresourcenotfound.                                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Steps to reproduce
    
    The error occurs when the stableid can't be found when querying
    through multiple pages of OSLC data.
    
    When the error occurs the logs print the message
    oslc#stableresourcenotfound instead of an associated maxmessage
    entry describing the cause of the issue.
    
    Open Database Configuration and select messages, then filter
    for stableresourcenotfound and no results will be returned as
    the Message Group and Key are not defined for the error.
    

Problem conclusion

  • The fix for this APAR is contained in the following maintenance
    package:
    	  Release 7.6.0.9 of Base Services
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV95836

  • Reported component name

    MAXIMO SYSTEMS

  • Reported component ID

    5724R46AV

  • Reported release

    760

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-05-04

  • Closed date

    2017-08-14

  • Last modified date

    2017-08-14

  • 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

    MAXIMO SYSTEMS

  • Fixed component ID

    5724R46AV

Applicable component levels

  • R760 PSY

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCHPP5","label":"System Related"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"760","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
14 August 2017