I've seen the same thing.  I reduced the authorization for an ID (it was being
used by some scripts), and none of the schedules created under it would work,
since the "controlling ID" did not have the authority.  I ended up creating a
new ID for the scripts, with the proper authority, reset the authority of the
original ID, and then locked it.  It can't be used to logon then, but the
schedules created by it still run fine.

Nick Cassimatis
Distributed Storage Management Team
RTP, NC
919-254-7302   T/L 444-7302
nickpc AT us.ibm DOT com

If you don't have the time to do it right the first time, where will you find
the time to do it again?