I’m not quite sure I understand what you’re getting at. As far as the Operating System would be concerned the job would be *ACTIVE as it is waiting for a record lock to be released.
As the job would be in a LCKW status, the implication is that it would not actually be doing anything at the time although the job could be in the middle of a transactional process (i.e. some files may have been updated, but others not) in which case ending the job could leave you with half completed transactions in your database.
If that is the sort of thing you want to guard against then you need to look into the use of journals and commitment control. This would allow you to update all files in a transaction set and then commit the updates to the database once they have all been made. Should the job end before the commitment step is done, the updates would be rolled back out of the files and you would need to recreate the entire transaction.
All the best
You possibly want the Retrieve Job Information (QUSRJOBI) API for format JOBI0200. Look for ‘Active job status’. One of the most likely statuses that could indicate the job isn’t doing anything might be DSPW “Waiting for input from a work station display”.
You’ll have some decisions to make about what it means not to be ‘doing anything’.