Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Strange\s+message\s+in\s+TSM\s+5\.1\.10\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Strange\s+message\s+in\s+TSM\s+5\.1\.10\s*$/: 5 ]

Total 5 documents matching your query.

1. Strange message in TSM 5.1.10 (score: 1): Author: Bob Booth - CITES/UIUC <booth AT UIUC DOT EDU>; Date: Sat, 20 Aug 2005 08:55:44 -0500; ANR9999D smutil.c(11273): ThreadId<26> Affinity ID is 0 for session nnnn I only see them when a couple of different clients connect. It seems that the client doesn't get its session when this happens; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2005-08/msg00415.html (10,904 bytes)
2. Re: Strange message in TSM 5.1.10 (score: 1): Author: Pétur Eyţórsson <petur.e AT NYHERJI DOT IS>; Date: Sat, 20 Aug 2005 15:23:23 +0000; Bob the famus ANR9999D is an error message that happens wen the server/client does something that is not expected of them, or the programers at Tuscon Arizona did not expect the Client/server to do t; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2005-08/msg00416.html (14,923 bytes)
3. Re: Strange message in TSM 5.1.10 (score: 1): Author: Richard Sims <rbs AT BU DOT EDU>; Date: Sat, 20 Aug 2005 11:39:24 -0400; ANR9999D smutil.c(11273): ThreadId<26> Affinity ID is 0 for session nnnn At www.ibm.com, search on +ANR9999D +smutil.c; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2005-08/msg00417.html (11,034 bytes)
4. Re: Strange message in TSM 5.1.10 (score: 1): Author: Fred Johanson <fred AT UCHICAGO DOT EDU>; Date: Sat, 20 Aug 2005 11:23:22 -0500; Bob, I've seen this on scattered clients at various levels of V5R1. Some of the maintenance levels were real flaky. Upgrade to something in 5.2 or 5.3, and the problem probably goes away. At least th; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2005-08/msg00418.html (14,566 bytes)
5. Re: Strange message in TSM 5.1.10 (score: 1): Author: Matt Anglin <matt AT ANGLIN DOT US>; Date: Sat, 20 Aug 2005 13:39:55 -0700; Truth be told, this particular problem is directly related to down-level clients. We had some bugs a few years back in the summary statistics processing (of which affinity id plays a part). The bugs; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2005-08/msg00420.html (15,592 bytes)

Current List: 1 - 5
Page: [1]