return() and retain job log

Hello,

when a batch job fails, the job log is not deleted but retained as spooled file.

I would have expected that when I submit a C program to batch and it returns with != 0, the batch job would be indicated to have failed. This is not the case.

What would be the correct way to indicate failure from a C program to the operating system, so the job log (with possibly contained debug output from Qp0zLprintf) isn't discarded?

A typical "batch job failed" condition occurs when e. g. a syntax error prevents batch mode compilation of a program. The job log is retained then.

I assume the needle is deeply buried in the haystack of the Job Management PDF, but I fail to see it.

Thanks for hints towards a solution!

:wq! PoC