Why did my job not schedule as expected using the DONT SCHEDULE fields on the CA 7 CPU JOB DEFINITION (DB.1) screen?
You can use the DONT SCHEDULE BEFORE/AFTER fields on the CA 7 CPU JOB DEFINITION (DB.1) screen to either keep a job from automatically scheduling during the specified time frame.
The DON'T SCHEDULE values are checked when CA 7 is attempting to bring the job record into the queue (current time at that time, not the due-out or dead-line start time of the job, but the current time when schedule scan is checking to bring in the job) and if it is not within the allowable dates/times (DON'T SCHEDULE BEFORE/AFTER) then the job is skipped.