APAR status
Closed as program error.
Error description
getting following warning when creating assets using RAM API: WARNING message in the console is: Failed to find community for id ... Failed to find community for id ... ....
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * * RAM * **************************************************************** * PROBLEM DESCRIPTION: * * 1. Problem description and statement * * this issue is happening for iRAM since they have migrated to * * RAM 7512. the issue is that they are getting following * * warning when creating assets using RAM API: * * WARNING message in the console is: ¶ * * Failed to find community for id 1774 * * Failed to find community for id 2084 * * Failed to find community for id 2725 * * Failed to find community for id 2726 * * Failed to find community for id 2743 * * Failed to find community for id 2756 * * Failed to find community for id 2758 * * Failed to find community for id 2759 * * Failed to find community for id 2756 * * Failed to find community for id 1103 * * Failed to find community for id 2725 * * Failed to find community for id 2756 * * Failed to find community for id 2084 * * Failed to find community for id 1103 * * Failed to find community for id 2725 * * Failed to find community for id 2756 * * Failed to find community for id 2756 * * Failed to find community for id 2725 * * Failed to find community for id 2756 * * Failed to find community for id 2756 * * Failed to find community for id 2756 * * Failed to find community for id 1103 * * Failed to find community for id 275 * * * * The issue is reproducible using iRAM CDT server but not our * * RAm server. * * iRAM says this issue is not happening when they are using * * RAM admin - super admin user. * * * * A brief chat with Peter, he explained it to me that the * * warning msg is in the method * * RAMCategorySchema.getRestrictedCommunities() * * He guesses occurs when that schema is restricted to specific * * community and probably that person running the api doesn't * * have access so the community. * * * * Checking the permision of the user who is running the API * * shows that this is correct. The person who is running the * * API does not have access to the communities listed by * * warnings. * * * * Now the questions are : * * - of course we cannot get access to all the communities to * * all users. What is the benefit of showing these warnings to * * the user? * * - These warnings make users confuse why they are getting * * them. How can they avoid them? * * - why is it started since migration to 7512? * * * * this log information this function returned before 7512 is * * used foe debug, because getSession().getCommunity(id) in * * this function returned all communities. Now since * * getSession().getCommunity returns only communities users has * * access to, then some communities can not be return. There is * * no need for user to know the information about the id of * * communities they can not access to. * **************************************************************** * RECOMMENDATION: * ****************************************************************
Problem conclusion
Fixed in https://jazz.net/jazz02/resource/itemName/com.ibm.team.workitem. WorkItem/95497
Temporary fix
Comments
APAR Information
APAR number
PM97607
Reported component name
RATL ASSET MGR
Reported component ID
5724R4200
Reported release
751
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-09-23
Closed date
2014-06-15
Last modified date
2014-06-15
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
RATL ASSET MGR
Fixed component ID
5724R4200
Applicable component levels
R752 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSUS84","label":"Rational Asset Manager"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5.1","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
15 June 2014