Artur (and group members):
I've read your answer, gave it a second thought and I will rephrase it.
I know that I have the 'manual' options to submitting the utilities
and, as a 'seasoned' DBA, this is what I always tell my customers to
do.
But it's not the utilities that I'm worried about, but the new
automation features.
As a DB2 technical support person, I'm usually contacted by my
customers (being them internal or external) asking me several
questions.
In this particular issue, they may contact me to explain why their DB2
instance's utilities are not executing automatically (at least they are
not being executed as frequently as they want or with a specific
timing).
This is precisely what I'm studying now. How to govern/control the new
automation features.
I've seen that there's a SYSTOOLS.POLICY table that contains
information regarding these automated tasks (Backup, Reorg, Runstats)
and I'm wondering if there are any means to 'touch' this table (or any
other DB2 object) that would influence/control the automation features.
Almost all the automated job/task scheduling software products that I
had the opportunity to deal with had the chance to submit a 'RUN NOW'
command to activate any given scheduled task to execute immediately,
regardless of its schedule.
This is what I'm looking for.
I hope that I'm making my point now. Better yet, I hope that the
group's members get my point.
Thanks in advance
Enrique Valdez
Certified DB2 UDB for z/OS v8.1 Database Administrator