[j-nsp] purpose of "commit check"?

[Chuck Anderson]

"commit comment" will log the comment even if the commit fails.  Doing
"commit check" first allows you to avoid this extra comment in the
"show system commits" log.

On Tue, Sep 29, 2015 at 12:24:41AM +0300, Martin T wrote:
> when I commit the candidate configuration in Junos, I tend to execute
> "commit check" and if configuration check succeeds, then I execute
> "commit comment <COMMENT>". However, when I think about it, "commit
> (comment)" itself should perform those very same checks that "commit
> check" does. If yes, then what is the point of "commit check"? Only
> purpose I could see is to check the validity of the candidate
> configuration in the middle of the configuration process, i.e. to
> check if the changes made in candidate configuration so far are fine
> but the candidate configuration is not ready to be committed.