> Now the Admin Manual states that for Administative command schedules

> When the configuration manager distributes schedules,the schedules are
not
> active on the managed server. An administrator on the managed server must
> activate any managed schedules to have them run on a managed server.

> A configuration refresh does not replace or remove tay local schedules
that
> are active on a managed server. However, a refresh can update an active
> schedule  that is already managed by a configuration manager.

> When I subscribe to my profile the command schedules are added marked as
> inactive and the last updated field is set to $$CONFIG_MANAGER$$.  All is
> OK at this point.  Now if I make the schedules active the last updated
> field is set to my userid.  If I then refresh the configuration it fails
on
> each schedule with the following

>     ANR3354W Locally defined administrative schedule XXXX is active and
> cannot be replaced with a
>                       definition from the configuration manager.

> I believe that for the refresh to consider the schedule as managed by a
> configuration manager the last updated by field must be set to
> $$CONFIG_MANAGER$$.

> Does anybody know how I can mark an admin schedule as active and leave
the
> last updated by field intact.?
> Or is this a bug? Or is the doco wrong?  Or any ideas?

The value in the "Last update" field has no bearing on whether an object is
treated as managed or locally defined.  An object is treated as managed or
locally defined based on database tables that track managed objects.  You
got message ANR3354W because an active admin schedule was not recorded as a
managed schedule (i.e., was locally defined) and therefore could not be
replaced during refresh processing.  To verify that the schedule is locally
defined, issue the Query Schedule T=A F=D command and look at the "Managing
Profile" field; if this field is empty, the schedule is locally defined
rather than managed.

Why is the schedule treated as locally defined even though it was created
during refresh processing?  A couple possibilities come to mind.  Perhaps
the refresh processing failed after creating the schedule; in this
situation the new schedule will not be marked as managed and therefore will
be treated as locally defined.  Another possibility is that after the
schedule was created, you deleted the subscription to the managing profile,
leaving behind the administrative schedule which would now be treated as
locally defined.

Dave Cannon
ADSM Server Development, IBM
cannon AT us.ibm DOT com
Tie-line: 321-4052     Phone: (520)799-4052