Quote:
> During my first class in BAL, the assistant (who was grading all of the
> exercises) said "always use PRINT GEN" to which the instructor said
> "you mean, never use PRINT GEN". I tend to the "always" mode.
PRINT NOGEN can hide programming errors. Long ago, as a consultant
for student programmers, I was presented with an abend S0C4 in low
core (yep, it was long ago). It was abending on a PUT to a file.
Given the logic flow of the simple program, it was clear that there
was no way the open could not have been executed, yet the file wasn't
open! Here is the relevant part of what I saw:
LA R4,SYSPRINT
OPEN (R4)
...
LA R4,SYSPRINT
PUT (R4),...
With PRINT NOGEN, this error is extremely difficult to spot. I told
the student to never use PRINT NOGEN around executable code.
Leonard D. Woren Senior MVS Systems Programmer
University of Southern California What would be the point?