This article explains how to prevent the command line from discontinuing processing a batch compile to ask the user for input. Using the given directives will ensure that it continues the whole way through.
Problem:
When compiling a long list of applications, there may be the need to ignore some errors and just continue on to the next application. Normally, if the compiler comes across a reference to a copybook that cannot be found, the user is prompted to Stop/Retry/Continue/Alter-path and the user must select one of the options before the compiler will continue. This is not the desired behavior when running batch compiles.
Resolution:
To avoid the batch stoppage, the user can specify the compiler directive NOQUERY. It details that for each missing copybook the compiler encounters; it will produce an error message and continue without any interface with the user. This is the ‘Continue’ option that the user was presented with before.
The user should also be sure that the compiler directive ERRQ is not set. Setting this directive causes the compiler to stop at each error it encounters, and ask the user if they wish to continue. This occurs even for trivial errors, such as Missing Period Assumed. The default is NOERRQ, and it should be left this way unless there is a reason to be prompted for every small error.
