Then MONMSG command can be very useful.It is usually used to catch & FIX errors on the fly. For every command there are specific messages you can monitor for. If a member is not found in a file, you can monitor for that and add the member and keep on going.When using MONMSG, you need to determine what errors are HARD STOPS and what ones can you ignore, make adjustments if necessary and continue processing. You can also have them setup so they will send a message and halt the process until a response is revceived.
From your requirements stated above, you may just want to do DSPJOBLOG OUTPUT(*PRINT) . That would give you the information on where it failed,
So what I am trying to say here, is first determine the types of errors you want to check for and the types of responces you want to have. Then you can update your CL programs to hanbdle the specific issues.
Remember the EXEC portion of the MONMSG can be DO, and you can issue multiple commands and/or call a variety of programs.
How this helped some.