Re: Schedule start delayed

2006-04-21 Thread Gill, Geoffrey L. 
I actually got this working. Here is what I remember. All TSM settings, when
compared to the other server, matched perfectly. PROMPTED is in fact being
used.

Could be related to daylight savings time but smit showed the date and time
differently than when issuing the command line "date" through the OS, which
as it turns out was 1 hour different. This did not match what TSM was
showing also. An accept date said it accepted the date and changed but it
still did not match what the OS was saying. I forced through the OS command
line, the time to be correct, accepted the date in TSM, once they matched
things cleaned themselves up.

Thanks,

Geoff Gill
TSM Administrator
PeopleSoft Sr. Systems Administrator
SAIC M/S-G1b
(858)826-4062
Email: [EMAIL PROTECTED]



-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Andrew Raibeck
Sent: Friday, April 21, 2006 6:06 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Schedule start delayed

Well, of course it appears in the QUERY STATUS output. But that does not
change the fact that randomization has no bearing when SCHEDMODE PROMPTED
is being used, which is what Geoff says he is using. Randomization affects
POLLING schedulers only (see HELP QUERY STATUS and HELP SET RANDOMIZE)..

Now... having said that... my response to Geoff indicated that he should
verify that PROMPTED is indeed being used, and if not, then randomization
would certainly contribute to the symptom he is seeing.

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED]
Internet e-mail: [EMAIL PROTECTED]

IBM Tivoli Storage Manager support web page:
http://www-306.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageMan
ager.html

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.

"ADSM: Dist Stor Manager"  wrote on 04/21/2006
00:45:17:

> Schedule Randomization.
> Q STAT and it's in the middle
>
> On 06.04.18 at 09:19 [EMAIL PROTECTED] wrote:
>
> > Date: Tue, 18 Apr 2006 09:19:56 -0600
> > From: Andrew Raibeck <[EMAIL PROTECTED]>
> > Reply-To: "ADSM: Dist Stor Manager" 
> > To: ADSM-L@VM.MARIST.EDU
> > Subject: Re: Schedule start delayed
> >
> > It would certainly help to see some more specifics. For example, the
> > dsmsched.log file for one of the clients in question that did not kick
off
> > when expected, just to verify that, for sure, it is using prompted
> > scheduling; and the activity log from the scheduled start time and on,
to
> > see what the server was doing, as well as other things like the client
> > dsm.opt file for the aforementioned client, and the client option set
> > definition for that client.
> >
> > Server-side randomization has no effect on prompted scheduling.
> >
> > Regards,
> >
> > Andy
> >
> > Andy Raibeck
> > IBM Software Group
> > Tivoli Storage Manager Client Development
> > Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED]
> > Internet e-mail: [EMAIL PROTECTED]
> >
> > IBM Tivoli Storage Manager support web page:
> > http://www-306.ibm.
> com/software/sysmgmt/products/support/IBMTivoliStorageManager.html
> >
> > The only dumb question is the one that goes unasked.
> > The command line is your friend.
> > "Good enough" is the enemy of excellence.
> >
> > "ADSM: Dist Stor Manager"  wrote on 2006-04-17
> > 22:13:06:
> >
> >> I'm trying to remember what it is about a backup schedule that, even
> > though
> >> scheduled for say 8PM, does not kick off right away, nodes show
pending
> > for
> >> some time. I've been comparing the 5.2 and 5.3 server settings but
can't
> >> find any obvious differences, yet the 5.2 server kicks off each
schedule
> >> right at the specific time whereas the 5.3 server I'm putting up does
> > not.
> >>
> >>
> >>
> >> I have a clopt set that has schedmode as prompted, which is the same
on
> > both
> >> servers and scheduling modes is set to any, same on both servers.
> >>
> >>
> >>
> >> What am I missing that I thought I'd taken care of? I'd actually
prefer
> > to
> >> have these guys start right away.
> >>
> >>
> >>
> >> Thanks,
> >>
> >>
> >>
> >> Geoff Gill
> >>
> >> TSM Administrator
> >>
> >> PeopleSoft Sr. Systems Administrator
> >>
> >> SAIC M/S-G1b
> >>
> >> (858)826-4062
> >>
> >> Email:  <mailto:[EMAIL PROTECTED]> [EMAIL PROTECTED]
> >

Re: Schedule start delayed

2006-04-21 Thread Andrew Raibeck 
Well, of course it appears in the QUERY STATUS output. But that does not
change the fact that randomization has no bearing when SCHEDMODE PROMPTED
is being used, which is what Geoff says he is using. Randomization affects
POLLING schedulers only (see HELP QUERY STATUS and HELP SET RANDOMIZE)..

Now... having said that... my response to Geoff indicated that he should
verify that PROMPTED is indeed being used, and if not, then randomization
would certainly contribute to the symptom he is seeing.

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED]
Internet e-mail: [EMAIL PROTECTED]

IBM Tivoli Storage Manager support web page:
http://www-306.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.

"ADSM: Dist Stor Manager"  wrote on 04/21/2006
00:45:17:

> Schedule Randomization.
> Q STAT and it's in the middle
>
> On 06.04.18 at 09:19 [EMAIL PROTECTED] wrote:
>
> > Date: Tue, 18 Apr 2006 09:19:56 -0600
> > From: Andrew Raibeck <[EMAIL PROTECTED]>
> > Reply-To: "ADSM: Dist Stor Manager" 
> > To: ADSM-L@VM.MARIST.EDU
> > Subject: Re: Schedule start delayed
> >
> > It would certainly help to see some more specifics. For example, the
> > dsmsched.log file for one of the clients in question that did not kick
off
> > when expected, just to verify that, for sure, it is using prompted
> > scheduling; and the activity log from the scheduled start time and on,
to
> > see what the server was doing, as well as other things like the client
> > dsm.opt file for the aforementioned client, and the client option set
> > definition for that client.
> >
> > Server-side randomization has no effect on prompted scheduling.
> >
> > Regards,
> >
> > Andy
> >
> > Andy Raibeck
> > IBM Software Group
> > Tivoli Storage Manager Client Development
> > Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED]
> > Internet e-mail: [EMAIL PROTECTED]
> >
> > IBM Tivoli Storage Manager support web page:
> > http://www-306.ibm.
> com/software/sysmgmt/products/support/IBMTivoliStorageManager.html
> >
> > The only dumb question is the one that goes unasked.
> > The command line is your friend.
> > "Good enough" is the enemy of excellence.
> >
> > "ADSM: Dist Stor Manager"  wrote on 2006-04-17
> > 22:13:06:
> >
> >> I'm trying to remember what it is about a backup schedule that, even
> > though
> >> scheduled for say 8PM, does not kick off right away, nodes show
pending
> > for
> >> some time. I've been comparing the 5.2 and 5.3 server settings but
can't
> >> find any obvious differences, yet the 5.2 server kicks off each
schedule
> >> right at the specific time whereas the 5.3 server I'm putting up does
> > not.
> >>
> >>
> >>
> >> I have a clopt set that has schedmode as prompted, which is the same
on
> > both
> >> servers and scheduling modes is set to any, same on both servers.
> >>
> >>
> >>
> >> What am I missing that I thought I'd taken care of? I'd actually
prefer
> > to
> >> have these guys start right away.
> >>
> >>
> >>
> >> Thanks,
> >>
> >>
> >>
> >> Geoff Gill
> >>
> >> TSM Administrator
> >>
> >> PeopleSoft Sr. Systems Administrator
> >>
> >> SAIC M/S-G1b
> >>
> >> (858)826-4062
> >>
> >> Email:  <mailto:[EMAIL PROTECTED]> [EMAIL PROTECTED]
> >

Re: Schedule start delayed

2006-04-21 Thread Josh-Daniel Davis 

Schedule Randomization.
Q STAT and it's in the middle

On 06.04.18 at 09:19 [EMAIL PROTECTED] wrote:


Date: Tue, 18 Apr 2006 09:19:56 -0600
From: Andrew Raibeck <[EMAIL PROTECTED]>
Reply-To: "ADSM: Dist Stor Manager" 
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Schedule start delayed

It would certainly help to see some more specifics. For example, the
dsmsched.log file for one of the clients in question that did not kick off
when expected, just to verify that, for sure, it is using prompted
scheduling; and the activity log from the scheduled start time and on, to
see what the server was doing, as well as other things like the client
dsm.opt file for the aforementioned client, and the client option set
definition for that client.

Server-side randomization has no effect on prompted scheduling.

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED]
Internet e-mail: [EMAIL PROTECTED]

IBM Tivoli Storage Manager support web page:
http://www-306.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.

"ADSM: Dist Stor Manager"  wrote on 2006-04-17
22:13:06:


I'm trying to remember what it is about a backup schedule that, even

though

scheduled for say 8PM, does not kick off right away, nodes show pending

for

some time. I've been comparing the 5.2 and 5.3 server settings but can't
find any obvious differences, yet the 5.2 server kicks off each schedule
right at the specific time whereas the 5.3 server I'm putting up does

not.




I have a clopt set that has schedmode as prompted, which is the same on

both

servers and scheduling modes is set to any, same on both servers.



What am I missing that I thought I'd taken care of? I'd actually prefer

to

have these guys start right away.



Thanks,



Geoff Gill

TSM Administrator

PeopleSoft Sr. Systems Administrator

SAIC M/S-G1b

(858)826-4062

Email:  <mailto:[EMAIL PROTECTED]> [EMAIL PROTECTED]

Re: Schedule start delayed

2006-04-18 Thread Andrew Raibeck 
It would certainly help to see some more specifics. For example, the
dsmsched.log file for one of the clients in question that did not kick off
when expected, just to verify that, for sure, it is using prompted
scheduling; and the activity log from the scheduled start time and on, to
see what the server was doing, as well as other things like the client
dsm.opt file for the aforementioned client, and the client option set
definition for that client.

Server-side randomization has no effect on prompted scheduling.

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED]
Internet e-mail: [EMAIL PROTECTED]

IBM Tivoli Storage Manager support web page:
http://www-306.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.

"ADSM: Dist Stor Manager"  wrote on 2006-04-17
22:13:06:

> I'm trying to remember what it is about a backup schedule that, even
though
> scheduled for say 8PM, does not kick off right away, nodes show pending
for
> some time. I've been comparing the 5.2 and 5.3 server settings but can't
> find any obvious differences, yet the 5.2 server kicks off each schedule
> right at the specific time whereas the 5.3 server I'm putting up does
not.
>
>
>
> I have a clopt set that has schedmode as prompted, which is the same on
both
> servers and scheduling modes is set to any, same on both servers.
>
>
>
> What am I missing that I thought I'd taken care of? I'd actually prefer
to
> have these guys start right away.
>
>
>
> Thanks,
>
>
>
> Geoff Gill
>
> TSM Administrator
>
> PeopleSoft Sr. Systems Administrator
>
> SAIC M/S-G1b
>
> (858)826-4062
>
> Email:   [EMAIL PROTECTED]

Re: Schedule start delayed

2006-04-18 Thread Thomas Denier 
- Geoff Gill wrote: -

>I'm trying to remember what it is about a backup schedule that,
>even though scheduled for say 8PM, does not kick off right away,
>nodes show pending for some time. I've been comparing the 5.2 and
>5.3 server settings but can't find any obvious differences, yet
>the 5.2 server kicks off each schedule right at the specific time
>whereas the 5.3 server I'm putting up does not.

Is the schedule randomization percentage (controlled by the 'SET
RANDOMIZE' command) the same on both servers?

Re: Schedule start delayed

2006-04-18 Thread Alexander Verkooijen 
Did you have a look at the
"Schedule Randomization Percentage"
in the output of "q stat" ?

Regards,

Alexander


Alexander Verkooijen
Senior Systems Programmer
High Performance Computing
SARA Computing & Networking Services
 

> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] 
> On Behalf Of Gill, Geoffrey L.
> Sent: dinsdag 18 april 2006 7:13
> To: ADSM-L@VM.MARIST.EDU
> Subject: Schedule start delayed
> 
> I'm trying to remember what it is about a backup schedule 
> that, even though
> scheduled for say 8PM, does not kick off right away, nodes 
> show pending for
> some time. I've been comparing the 5.2 and 5.3 server 
> settings but can't
> find any obvious differences, yet the 5.2 server kicks off 
> each schedule
> right at the specific time whereas the 5.3 server I'm putting 
> up does not.
> 
> 
> 
> I have a clopt set that has schedmode as prompted, which is 
> the same on both
> servers and scheduling modes is set to any, same on both servers.
> 
> 
> 
> What am I missing that I thought I'd taken care of? I'd 
> actually prefer to
> have these guys start right away.
> 
> 
> 
> Thanks,
> 
> 
> 
> Geoff Gill
> 
> TSM Administrator
> 
> PeopleSoft Sr. Systems Administrator
> 
> SAIC M/S-G1b
> 
> (858)826-4062
> 
> Email:  <mailto:[EMAIL PROTECTED]> [EMAIL PROTECTED]
>

Schedule start delayed

2006-04-17 Thread Gill, Geoffrey L. 
I'm trying to remember what it is about a backup schedule that, even though
scheduled for say 8PM, does not kick off right away, nodes show pending for
some time. I've been comparing the 5.2 and 5.3 server settings but can't
find any obvious differences, yet the 5.2 server kicks off each schedule
right at the specific time whereas the 5.3 server I'm putting up does not.



I have a clopt set that has schedmode as prompted, which is the same on both
servers and scheduling modes is set to any, same on both servers.



What am I missing that I thought I'd taken care of? I'd actually prefer to
have these guys start right away.



Thanks,



Geoff Gill

TSM Administrator

PeopleSoft Sr. Systems Administrator

SAIC M/S-G1b

(858)826-4062

Email:   [EMAIL PROTECTED]