This "requirement" comes from someone who knows nothing about mainframes. There is NEVER a valid reason to cause a batch job to "sleep" like you want. If the batch job cannot get needed resources, either schedule it to run at a different time or ensure the job doesn't start until the resources are available.There is one requirement to halt execution of a batch program (sleep for some time) in some specific case
In my experience, every deadlock that i've helped resolve was due to code that should have been done differently. . .What is causing the deadlock?
Typically causes a "timeout" in a database."not having access to something because something else is using it."
Long ago this was typically the case.in case of a deadlock both program will sit there <halted> waiting for the other to free the resource needed
a deadlock will be resolved only by <killing> one of the offending partners