A fix is available
APAR status
Closed as program error.
Error description
The current information center does not explain the concept of Master lifecycle and inherited policies. Here are the information that L2 received from L3. Q: We thought that only the policies that are in master lifecycle will show as 'inherited' L3 Answer: nope, and not just policies, all settings are 'inheritable' Q: Are you saying that users cannot edit their assets' lifecycle configuration at 'asset level'? L3 Answer: They cannot override what was done at the community or master level. Lifecycles are no longer snapshots that are taken at asset creation time and then ignores all changes at the upper levels. They are now three levels. all merged together, with Master being a complete lifecycle with any change possible, then community, which only allows additions to the master lifecycle, with the rest of the master lifecycle merged in, and then asset which only allows additions to the community lifecycle with the rest of the community lifecycle merged in. And this is active in that any change to the master or community lifecycle are automatically pushed down to the lower lifecycle the next time the lifecycle is accessed (such as an asset changes state). This is how the repo admin and community admin can be assured that anything they want to be done cannot be removed or changed by the lower level lifecycles The above information is only mentioned once in http://publib.boulder.ibm.com/infocenter/ramhelp/v7r5m1/index.js p?topic=%2Fcom.ibm.ram.web.doc%2Ftopics%2Ft_reviewprocess_invite collaborators.html. The IC mentions a lot about 'modify' or 'edit' lifecycle; however it not well explain the limitations and inherited policies and settings from different levels: Master, Community, and assets.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * **************************************************************** * PROBLEM DESCRIPTION: * **************************************************************** * RECOMMENDATION: * **************************************************************** More reinforcement is needed to indicate that asset lifecycles cannot override requirements set by master or community lifecycles.
Problem conclusion
Added text to tutorial and context-sensitive help to indicate that More reinforcement is needed to indicate that asset lifecycles cannot override requirements set by master or community lifecycles.
Temporary fix
Comments
APAR Information
APAR number
PM76511
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
2012-11-05
Closed date
2013-04-01
Last modified date
2013-04-01
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
R751 PSN
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSUS84","label":"Rational Asset Manager"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5.1","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
29 October 2021