This is tricky since jobs don’t actually use job descriptions (*JOBDs). They are used by users to tell Work Management how to set up an environment for a job to run under. Once the environment is set, the *JOBD is no longer important.
That’s why you can change a *JOBD attribute after a job starts and the change doesn’t affect the job.
You can retrieve attributes of jobs that are currently tracked in the system to see what *JOBD was used for it. The information can be retrieved for each job from format JOBI0400 of the <a href=”http://publib.boulder.ibm.com/infocenter/iseries/v5r4/index.jsp?topic=/apis/qusrjobi.htm”>Retrieve Job Information (QUSRJOBI) API</a>. However, this can only tell you about jobs that are in the system when you call the API.
It can’t tell you about a job that completed an hour ago and that left no object such as a spooled file on an *OUTQ.
Ideally, you have auditing enabled and you are tracking *JOBDATA. You can then retrieve T/JS entries from QUADJRN. Look for entry-specific data sub-type ‘B’ (Submit). The *JOBD name begins in position 50 of the entry-specific data.
That lets you see how every submitted job had a *JOBD specified going back as far as your journal goes. You could extract and review T/JS entries on a daily basis for a few days or for as long as needed to make it through an accounting cycle — however long you choose.
Details of JS entries are in Appendix F of the Security Reference manual for your version/release of the OS.