Direct links to fixes
4.1.1-TIV-SAMP-Linux64-FP0001
4.1.1-TIV-SAMP-AIX-FP0001
4.1.0-TIV-SAMP-AIX-FP0002
4.1.0-TIV-SAMP-Linux64-FP0002
4.1.0-TIV-SAMP-Linux-FP0002
3.2.2-TIV-SAMP-Linux-FP0009
3.2.2-TIV-SAMP-AIX-FP0009
3.2.2-TIV-SAMP-Solaris-FP0009
3.2.2-TIV-SAMP-Windows-FP0009
3.2.2-TIV-SAMP-Windows-FP0009
4.1.0-TIV-SAMP-AIX-FP0003
4.1.0-TIV-SAMP-Linux-FP0003
4.1.0-TIV-SAMP-Linux64-FP0003
4.1.0-TIV-SAMP-AIX-FP0006
4.1.0-TIV-SAMP-Linux-FP0006
4.1.0-TIV-SAMP-Linux64-FP0006
4.1.0-TIV-SAMP-AIX-FP0007
4.1.0-TIV-SAMP-Linux64-FP0007
SAMP4107_Verification_Signatures
4.1.1-TIV-SAMP-AIX-FP0000
4.1.1-TIV-SAMP-Linux64-FP0000
3.2.2-TIV-ITSAMP-FP0009, Tivoli System Automation for Multiplatforms
4.1.0-TIV-ITSAMP-FP0003, Tivoli System Automation for Multiplatforms
4.1.0-TIV-ITSAMP-FP0004, Tivoli System Automation for Multiplatforms
APAR status
Closed as program error.
Error description
BE Support Engineer: CJ Change Team Engineer: EJ SAMP: 4.1.0 Problem Description: When a new relationship is created from an IBM.Application resource to an equivalency the top level of the equivalency can show OpState=Unknown even though the equivalency constituents show normal/online. Besides the OpState issue, the relationship is also not honorred until the next resource validation. E.g. for a new DepednsOn relationship, the source IBM.Application resource will not be stopped (no force down) in case the supporting target member of the equivalency switches to Offline.
Local fix
Restart the cluster (stoprpdomain, startrpdomain) or recycle the Master IBM.RecoveryRM daemon
Problem summary
**************************************************************** * USERS AFFECTED: Tivoli System Automation for Multiplatform * (SA MP) 4.1 users **************************************************************** * PROBLEM DESCRIPTION: * When a new relationship is created from an IBM.Application * resource to an equivalency the top level of the equivalency * can show OpState=Unknown even though the equivalency members * are all online. * Additionally the new relationship is also not effective until * the next resource validation. This means e.g. for a new * 'DependsOn' relationship, that the source (IBM.Application) * resource will not be stopped (no force down) in case the * supporting target member of the equivalency changes to * Offline. * * LOCAL FIX: * Restart the cluster (stoprpdomain / startrpdomain) or recycle * the master IBM.RecoveryRM daemon. **************************************************************** * RECOMMENDATION: ****************************************************************
Problem conclusion
The internal handling of the RecoveryRM has been adjusted to address this issue. Now a new created relationship with an equivalency as target resource is effective immediately, and the OpState of the equivalency will not show 'Unknown'. . The official fix for this problem is included in fixpack 2 of Tivoli System Automation for Multiplatforms 4.1.0 | 4.1.0-TIV-ITSAMP-FP0002 | . Additional Search Keywords .
Temporary fix
Comments
APAR Information
APAR number
IV67468
Reported component name
SA MULTIPLATFOR
Reported component ID
5724M0000
Reported release
410
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2014-12-02
Closed date
2015-03-04
Last modified date
2015-03-04
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
SA MULTIPLATFOR
Fixed component ID
5724M0000
Applicable component levels
Document Information
Modified date:
25 September 2023