It does look as if job number controls the sequence. I don’t recall anything that can be done about it. I’ve never cared before since I rarely use WRKSBMJOB without a specific purpose in mind. Almost always it’s only because it has the option to work with jobs submitted from the current session. And there shouldn’t be many jobs on the list.
 
If WRKUSRJOB is used instead, does it include options that help? The ASTLVL() parameter can change how jobs are listed particularly when JOBTYPE(*BATCH) is specified with it. The resulting ‘Work with Jobs’ display has F14=’Select other jobs’ that filters on a number of elements. Unfortunately none are by date/time.
 
As near as I can tell, you need to create a custom list of jobs if you want them listed with current jobs at the end. Either that or use iSeries Navigator to create a desktop shortcut for jobs. With the iNav function, users can sort any way they want including by date/time. They can also choose to include only chosen types of jobs.
 
That might be the only choice without some programming.
 
Tom

Sounds like the job# wrap issue. That’s easy enough to verify just change the view so you see the job#s.  Another way you can cut down on what is displayed is use the command WRKSBMJOB *WRKSTN this will show job for this workstation only. Other that than you may have to follow Tom’s suggestion and write some custom code to put them in date/time sequence.