I don't have Syncsort but if my guess is correct, INCLUDE COND is processed before INREC (OVERLAY or BUILD). So your new sort card is INCLUDing condition before TIME3 is populated and won't produce required results.
If you consult your manual you'll find what order the different types of sort card are actually processed in. The position of include/omit for instance, is irrelevant to the processing, it will always be actioned at the same stage. Try putting it as the last sort card, it'll still include/omit as early as possible to cut down on the amount of data procesed.
You're loosing out on that process because you have the unusual situation of selecting on something which is not on the input file.
I don't really understand why you are doing what you are doing, but I don't have to!
Thanks for all the additional information. And yes, I am happy. :-)
And just to add a background, our Ops team have this existing sort job scheduled to run every hour that sends out an alert if it gets something out of it and for SOME reason they don't what to change the existing schedule and just change the sort parm to NOT to get anything on specific hours(s).
So, they where wondering if we can just to add the RUN time as a condition on the SORT.
As trivial as it may seem, I was thinking that the reason that they don't want to go through the 'pain' of requesting a schedule change is because it takes several approvals and 2 weeks to change a job schedule. [bummer]