Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Client\s+COMMAND\s+schedule\s+weirdness\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Client\s+COMMAND\s+schedule\s+weirdness\s*$/: 4 ]

Total 4 documents matching your query.

1. Client COMMAND schedule weirdness (score: 1): Author: Zoltan Forray/AC/VCU <zforray AT VCU DOT EDU>; Date: Fri, 13 Dec 2002 09:27:50 -0500; Folks, I am experiencing some really strange stuff when updating/creating Client COMMAND type schedules, via the web admin interface ! Haven't created or updated this kind of schedule for quite a whi; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2002-12/msg00504.html (11,170 bytes)
2. Re: Client COMMAND schedule weirdness (score: 1): Author: Sias Dealy <hnre AT UREACH DOT COM>; Date: Fri, 13 Dec 2002 10:29:35 -0500; Zoltan, I have a test box with Windows 2000 running TSM 4.2.2.0 . When I use the Web Admin. I can set up a schedule with out any problem. It is when I update the schedule through the Web Admin. It lo; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2002-12/msg00511.html (12,316 bytes)
3. Re: Client COMMAND schedule weirdness (score: 1): Author: Andrew Raibeck <storman AT US.IBM DOT COM>; Date: Fri, 13 Dec 2002 09:47:09 -0700; This problem is documented in APAR PQ60516, and is fixed in 4.2.3.0. It is also broken in 5.1, but where exactly it got fixed, I don't know.... but at 5.1.5.4, I don't see the problem. Regards, Andy; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2002-12/msg00524.html (12,143 bytes)
4. Re: Client COMMAND schedule weirdness (score: 1): Author: Zoltan Forray/AC/VCU <zforray AT VCU DOT EDU>; Date: Fri, 13 Dec 2002 11:51:16 -0500; Thank you. As I said, I am about to implement 4.2.3.0 this weekend ! Andrew Raibeck <storman AT US.IBM DOT COM> Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> 12/13/2002 11:47 AM Pl; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2002-12/msg00526.html (12,534 bytes)

Current List: 1 - 4
Page: [1]