Patch Name: PHSS_31114 Patch Description: s700_800 11.11 Support Tool Manager Jun 2004 patch Creation Date: 04/07/06 Post Date: 04/07/29 Hardware Platforms - OS Releases: s700: 11.11 s800: 11.11 Products: Support Tools Manager A.45.00 Support Tools Manager A.45.05 Filesets: Sup-Tool-Mgr.STM-UUT-RUN,fr=B.11.11.14.15,fa=HP-UX_B.11.11_32/64,v=HP Sup-Tool-Mgr.STM-CATALOGS,fr=B.11.11.14.15,fa=HP-UX_B.11.11_32/64,v=HP Sup-Tool-Mgr.STM-MAN,fr=B.11.11.14.15,fa=HP-UX_B.11.11_32/64,v=HP Contrib-Tools.CONTRIB,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP Contrib-Tools.PDCINFO,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP Sup-Tool-Mgr.STM-SHLIBS,fr=B.11.11.14.15,fa=HP-UX_B.11.11_32/64,v=HP Automatic Reboot?: No Status: General Release Critical: No Category Tags: defect_repair enhancement general_release manual_dependencies Path Name: /hp-ux_patches/s700_800/11.X/PHSS_31114 Symptoms: PHSS_31114: 1)DTS JAGaf11951 SR 8606351139 MP Error logs occur when Diagnostics tries to read the FRUS on IPF systems. "READ_FRU_FAILED" messages occur in the MP logs. The LEDs on the system may flash as a result of these errors. 2)DTS JAGaf19257 SR 8606358558 User may see the following error message logged to Activity log file after running the CPU info tool. The returned status from PDC_SYSTEM_INFO call: (-2). Possible Causes/Recommended Action The PDC_SYSTEMINFO call return status indicates an invalid option in the call to PDC_SYSTEMINFO. Try running the program again. This error is probably due to an error in this program but could be an indication of more serious system problems. 3)DTS JAGaf26198 SR 8606365566 Monconfig may lose Monitoring Requests while adding/Modifying Monitoring Requests and when more than 256 entries are found across all sapcfg files together. User may find some of the previously added Monitoring Requests being lost when the problem appears. 4)DTS JAGaf26526 SR 8606365896 Ts99 files do not contain all processor error information except for processor 0. All platform data is correct. 5)DTS JAGaf30394 SR 8606369851 send_test_event test utility will NOT find monitor name in the .sapcfg file associated with the monitor, when more than 256 entries are found across all sapcfg files together. Following error will be flashed: "send_test_event: Failed to find monitor name in sapcfg files." PHSS_30888: 1)DTS JAGaf20670 SR 8606359974 The following error would be logged in the api.log log file: -------------------Start Event-------------------- User event occurred at Thu Apr 22 07:10:31.636570 2004 Process ID: 27206 (/usr/sbin/stm/uut/bin/tools/.../fpl_em) Log Level: Error While attempting to obtain the timestamp for an event, the log file fpl_em.dat was unable to be opened, read or written. Possible Causes/Recommended Action: Internal Application error. -------------------End Event---------------------- 2)DTS JAGaf18666 SR 8606357967 The following error message gets logged in /etc/opt/resmon/log/api.log on c8000 class Workstations -------------------Start Event-------------------- User event occurred at