by Robert Sample » Fri Jun 18, 2010 5:17 pm
First of all, this is not a good use of resources -- it is wasteful to the extreme. Second, there is no way in JCL to do this. You cannot implement delays in jobs. You could write a program that basically waits for the desired time but you are tying up an initiator, CPU, memory, address space, and so forth for however long the delay is -- as I said, extremely wasteful. Third, in a production environment you would split off the fourth step into a separate job and schedule it to run 3 minutes and the first job.