Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[ADSM\-L\]\s+Odd\s+ANR2716E\s+messages\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[ADSM\-L\]\s+Odd\s+ANR2716E\s+messages\s*$/: 2 ]

Total 2 documents matching your query.

1. [ADSM-L] Odd ANR2716E messages (score: 1): Author: Thomas Denier <Thomas.Denier AT JEFFERSON DOT EDU>; Date: Fri, 13 Oct 2017 17:24:38 +0000; One of our Windows client backups has had a minor but very puzzling problem on three of the last four days. On each of the three days the following sequence of events occurred: 1.The TSM server displ; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2017-10/msg00049.html (9,963 bytes)
2. Re: [ADSM-L] Odd ANR2716E messages (score: 1): Author: Dwight Cook <cookde AT US.IBM DOT COM>; Date: Thu, 19 Oct 2017 02:16:27 -0500; Well, all that code is out of date but other than that... make sure SCHEDMODE PROMPT is in the client's dsm.opt file. Also if you are running only a scheduler, look at switching over to the CAD and l; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2017-10/msg00061.html (11,215 bytes)

Current List: 1 - 2
Page: [1]