If the class was really BAL, then why were you using PRINT GEN?

    Note: The last S/360 BAL that IBM had was for the S/360-20.
 Later, when IBM came out with the MACRO Assemblers, they called
 them Full Assemblers.

    Classes that teach assembler without teaching macros are still
 called BAL, even though there has never been a S/370 BAL product.

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?