Problem:
When using the the cobol command line to compile programs within a batch file (for example:
cobol sourcename,,nul,,directives;) -
the user will observe that when a copyfile for this source does not exist, the compiler requests:
FILE BELOW NOT FOUND - Stop/Retry/Continue/Alter-path
and starts waiting for keyboard response, the entire build batch stops because of this and operator intervention is necessary.
Resolution:
To change the behaviour of the cobol command line so it only reports the missing copyfile, and continues without intervention all that is required is to add the directive NOQUERY to the command line, thusly:
cobol sourcename,,nul,,NOQUERY directives;
