In DBUTLTY, each function will produce its own completion code. Here, since the EDIT function itself completed successfully, even if the results of the EDIT showed problems, the completion code will be zero. The output of the EDIT function should be seen as a report, with any *****- ERROR or *** INVALID KEYWORD items seen as details on that report.
While having a different completion code for errors could make it easier to identify some syntax problems, it is important to note that not every possible failure can be tested with EDIT (due to files and databases not being opened). Therefore, using a CC of other than zero to indicate a problem can set a false expectation, as an EDIT can complete with CC=0 but the command could later fail upon execution.
As the description of EDIT says, "This function does not attempt to verify that any database, area, or table specified in the input actually exists. The editing is for most conditions, but not every edit occurs when the function is completely processed."
For more information about the DBUTLTY EDIT function, please see the following documentation:
CA Datacom/DB Version 14.02 DBUTLTY Reference Guide, in the section "EDIT (Validate Syntax)"
CA Datacom/DB Version 15.0 Docops Space, on the page "> Reference > DBUTLTY Reference > Utility Function Summary > EDIT (Validate Syntax)"
CA Datacom/DB Version 15.1 Docops Space, on the page "> Reference > DBUTLTY Reference > Utility Function Summary > EDIT (Validate Syntax)"
As always, please contact CA Technologies support for CA Datacom if you have further questions.
***