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?
>
>