Unfortunately, as you will comprehend, sysouts are unlikely to persist on the spool or in your RYO archive long enough to provide a valid picture of your schedule. Moreover, it is also unlikely that looking at the sysouts will reveal the dependencies between jobs (my shop's proprietary scheduler -- which only runs on our development sysplex; we use Control-M in production -- uses JES3 DJC for this purpose, but is unusual in doing so).
I recommend that you find the person(s) responsible for maintaining the scheduler code, and use whatever combination of carrots and sticks are available to you to have the reporting function fixed.
"You have sat too long for any good you have been doing lately ... Depart, I say; and let us have done with you. In the name of God, go!" -- what I say to a junior programmer at least once a day