For the record, sp_update_job is in the MSDB database, and the rule about stored procedures beginning with 'sp_' doesn't apply.  My daylight saving time adjustment job was pointed at the Master database and failed on every server it was deployed on!!!  The up side is that I learned that SQL 2000 handles the change even when the job is scheduled as "every 15 minutes".  The down side is that I learned that SQL 7.0 doesn't handle it.  Fortunately, I only have two SQL 7.0 servers, and one of them wasn't affected.  However, the other one created two transaction log backups at "2:00".  The first one ran for "-95444:-90:-51" but reported a successful backup.  Its already been archived to tape, so I haven't tested it yet.  I have a feeling it will probably be ok, as long as I get the sequence right. 

Steve