Thanks people! I didn't realize this detail.
It worked fine as you wrote, James. That's really what I needed.
----- Original Message -----
From: "James Thorne" <james.thorne AT IT.OX.AC DOT UK>
To: ADSM-L AT VM.MARIST DOT EDU
Sent: Thursday, November 26, 2015 1:56:13 PM
Subject: Re: [ADSM-L] Fwd: Simple doubt on scheduling
That definitely looks like the answer:
> tsm: TSM-UFPE>update sched xxxxx yyyyyyy duration=1 durunits=days
> period=1 perunits=hours
Period of one hour but the duration is a day. Perhaps you meant:
tsm: TSM-UFPE>update sched xxxxx yyyyyyy duration=1 durunits=hours period=1
perunits=days
(A one-hour window every day)
James.
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Krzysztof Przygoda
Sent: 26 November 2015 14:22
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Fwd: Simple doubt on scheduling
Hi
Maybe the server answer is not hitting the point but i think you are somehow
reaching this limit:
"The duration of the window must be shorter than the period between windows."
Regards
Krzysztof
2015-11-26 15:06 GMT+01:00 Fábio Chicout <fabio.chicout AT ufpe DOT br>:
> Guys,
>
> I've tried to set up a schedule on TSM 7.1.1, and got myself on a
> interesting situation here.
>
> Tried to update a schedule to run hourly, and the TSM shell gave me
> this
> message:
>
> tsm: TSM-UFPE>update sched xxxxx yyyyyyy duration=1 durunits=days
> period=1 perunits=hours ANR2614E UPDATE SCHEDULE: Invalid combination
> of the following parameters:
> duration, duration units, period, period units.
> ANS8001I Return code 3.
>
> And it only accepted period greater or equal 2 hours.
>
> I've searched documentation, and didn't find anything explicit about
> not setting hourly schedules. Is possible any workaround?
>
> Att,
> Fábio Chicout
>
--
|