ADSM-L

Re: Antw: 4.1.3.0-scheduling-problem

2001-05-14 11:06:08
Subject: Re: Antw: 4.1.3.0-scheduling-problem
From: Tom Tann{s <tom.tannas AT USIT.UIO DOT NO>
Date: Mon, 14 May 2001 17:06:53 +0200
Guess I'll submit an APAR tomorrow.
Did just run a trace on a client, and, as I thougt, the server sends wrong
information to the client.

05/14/2001 16:52:34.0790 : cusched.c ( 290): SendStartOp: Sending a 
CSStartOpVerb, node: 'SUMO'
05/14/2001 16:52:34.0790 : cusched.c ( 291):              scheduleName: 
'TEST_2', startDateToken: 05/14/2001 16:48:00
05/14/2001 16:52:34.0790 : session.c (1696): Send Verb: Length:    29 Code: 
00000022 Type: CSStartOp

At 16:46 the schedule's startup-time was changed to 05/15/2001 16:48:00.

Anyway, thanks for suggestions.



On Mon, 14 May 2001, Michael Donabauer wrote:

> Level 4.1.3.2  > upgrade
>
> >>> tom.tannas AT USIT.UIO DOT NO 14.05.2001  02.23 Uhr >>>
> Hello!
>
> Whith server-level 3.7 and earlier, if a client-scheduler was scheduled to
> do something whithin its queryschedperiod, and the schedule on the server
> in the meantime was changed to run at a later time, the client scheduler
> would report a ANS1814E and "rescheduled" itself.
>
> I just upgraded to 4.1.3, and in this case, the client runs the original
> scheduled task, just as if nothing was changed at the server.
>
> Is this another case of "buffers not cleared/updated" on the server?
>
> Anyone else seen this behaviour?
>
>
>                              Tom
>
<Prev in Thread] Current Thread [Next in Thread>