The above appears to assume that a schedule is packaged in a DXI file. This is not the case. A schedule is configured on a server, and I am not aware of a way of packaging it up as a file. Therefore a DXI deployment cannot overwrite a schedule. With autorun, you are effectively just setting some chores to run after importing the file (at startup) and they will run as configured. This is not the same as importing a schedule, so it would not override any scheduling that is configured on the server.
It seems to me that the answer is to allow a permission-restricted user to adjust the schedule using Server Console on the production system. You could also consider moving away from using Autorun to start jobs and just schedule them to run at startup, perhaps so that the full logical schedule can be viewed in the UI.
Alternatively you could use an external scheduler which of course means not having to access or adjust anything in EDQ at all.
Hi Mike, thanks for the info. I seem to have wrongly convinced myself I'd seen job schedule info in an unpacked dxi file when I was doing something else. We have these jobs in the "chores" because they have to run consecutively at start up and this is what was set up by the Oracle Consultant that was here at the time. I'm not server savvy so I'll have a chat with our server team about external schedulers.