I agree with Angel - this sounds like a bug to me.  If it isn't a bug, but
rather a new "feature" of V3, could someone from IBM comment on why there was
a change?  I for one have many scheduled with short windows (to control when
they start), and they run for long periods of time - perhaps 12 hours.  I
only want "missed" as a status if the  scheduled event never occurred.

Jerry Lawson
jlawson AT thehartford DOT com


______________________________ Forward Header __________________________________
Subject: Re: Quickie question,
Author:  owner-adsm-l (INTERNET.OWNERAD) at SNADGATE
Date:    4/9/98 11:14 AM


It seems to me that if your ADSM server is Version 3, then the scheduled
event will show missed is it is past its window.  It did not do this
with Version 2.  Version 2 marked the event as complete.  Our ADSM
server is AIX.  I am not sure it this is true on other Version 3
platforms.

Sounds like a version 3 bug to me.
Angel Boles

Westinghouse Electric
(412) 374-3230
Win 284-3230
bolesav AT westinghouse DOT com

> ----------
> From:         Matthew
> Warren[SMTP:Matthew.Warren AT marks-and-spencer DOT com]
> Sent:         Thursday, April 09, 1998 5:36 AM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Re: Quickie question,
>
> I have had a couple of different replies to this,
>
>         Some of you have said, Yup, it does return a status of missed,
> some have said it doesnt.
>
>         I have now tested it and seen it report missed when the job
> completed outside the window, although I did originally think that it
> should report completed.
>
>         Is there some quirk that is causing both types of behaviour? I
> shall investigate further.........
>
>
> Matthew Warren.
> HOIST - Head Office Infrastructure Support Team.
> ADSM (FAB) + Unix support.
>         Marks & Spencer Plc.
>         Baker Street.
>         London.
> Email: matthew.warren AT marks-and-spencer DOT com
 >
>
>
>
> > -----Original Message-----
> >
> > Hi Mathew,
> >
> > Nowhere do you define within the ADSM schedule how long a scheduled
> > job
> > should take. You nominate a start time, and then a window in witch
> the
> > job should start. So, if you specify a start time of midnight, and a
> > startup window of 2 hours, the job must start by 2am, or it will
> show
> > up
> > as 'Missed'. But the job could run until after 2am, and still finish
> > with a 'Completed' status.
> >
> >
> > Trevor
> >
> >         -----Original Message-----
> >         From:   Matthew Warren
> >         Hello All,
> >
> >                 Just a quick point,
> >
> >                 If a schedule takes longer than its duration to
> > complete, bit
> >         still completes fine, am I right in that  the scheduler
> still
> > shows the
> >         status as missed?
> >
> >
>