Readmes are available
IBM Tivoli 4.0.0-TIV-SSM-FP0010
IBM Tivoli 4.0.0-TIV-SSM-FP0011
IBM Netcool System Service Monitor SSM 4.0 Fix Pack 12 README 4.0.0-TIV-SSM-FP0012
IBM Netcool System Service Monitor SSM 4.0 Fix Pack 13 README 4.0.0-TIV-SSM-FP0013
IBM Netcool System Service Monitor SSM 4.0 Fix Pack 14 README 4.0.0-TIV-SSM-FP0014
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 1 README 4.0.0.14-TIV-SSM-IF0001
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 2 README 4.0.0.14-TIV-SSM-IF0002
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 3 README 4.0.0.14-TIV-SSM-IF0003
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 4 README 4.0.0.14-TIV-SSM-IF0004
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 5 README 4.0.0.14-TIV-SSM-IF0005
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 6 README 4.0.0.14-TIV-SSM-IF0006
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 7 README 4.0.0.14-TIV-SSM-IF0007
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 8 README 4.0.0.14-TIV-SSM-IF0008
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 1 README 4.0.0.15-TIV-SSM-IF0001
APAR status
Closed as program error.
Error description
With Windows 2008 Server a new king of Window service has appeared: Service in automatic startup but delayed. These kind of services starts or stops on internal preferences (like Windows Update). In fact it is not possible to monitor them, because it is not possible to say if a service stop is a fail or normal! So the solution would be to exclude these services; The default behaviour for monitoring theses services (like with arithmetic MIB), doesn't work: arithmetic expression= ((.ntServiceTableCurrentState.*==7)&&(.ntServiceTableStartType. [*]==1))? @name = .ntServiceTableDisplayName.[*]; @result = 'Automatic service \@name has stopped' : \@result = 0; \@result These services are really of nsServiceTableStartType 1 [automatic]; But we don't have the information anywhere in the MIB file that the type is DELAYED: on the ntService Mib is information misses : NtServiceTableEntry ::= SEQUENCE { ntServiceTableName DisplayString, ntServiceTableDisplayName DisplayString, ntServiceTableDescription DisplayString, ntServiceTableBinaryPath DisplayString, ntServiceTableParameters DisplayString, ntServiceTableType INTEGER, ntServiceTableCurrentState INTEGER, ntServiceTableControl INTEGER, ntServiceTableStartType INTEGER, ntServiceTableErrorControl INTEGER, ntServiceTableStartName DisplayString, ntServiceTableDependencies DisplayString } As we can see in the Registry the "Delayed" status is supported by a specific Key called 'DelayedAutoStart". If this information should be in the MIB, the filter could be updated to exclude these services
Local fix
N/A
Problem summary
**************************************************************** USERS AFFECTED: Users of the ntscm MIB on Windows Server 2008 or later. **************************************************************** PROBLEM DESCRIPTION: ntscm MIB cannot identify or distinguish "Automatic (Delayed)" start services **************************************************************** RECOMMENDATION: Upgrade to Fix Pack 10 for SSM 4.0. ****************************************************************
Problem conclusion
Added new enumeration values "autoDelayed" to the MIB for the delayed startup type. The fix for this APAR is contained in the following maintenance packages: | fix pack | 4.0.0-TIV-SSM-FP0010
Temporary fix
Comments
APAR Information
APAR number
IZ74902
Reported component name
NETCOOL SYS SVC
Reported component ID
5724P4300
Reported release
320
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2010-04-23
Closed date
2010-05-14
Last modified date
2010-05-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
NETCOOL SYS SVC
Fixed component ID
5724P4300
Applicable component levels
R400 PSN
UP
Document Information
Modified date:
14 May 2010