COMMIT(pick one) in the SQL precompiler

[Rob Berendt <rob@xxxxxxxxx>]

Is there a way to control this command parameter via an HSPEC?  
Forgive me but I'm just too flipping lazy today to RTFM.  As a 
general rule most people change this from *CHG to *NONE.  Well, 
I actually used commitment control and someone used *NONE.  Will 
the precompiler flag this as an error?  Ohhh noooo.  However the 
COMMIT statement will then eat all of your CPU even though it has 
an error.  What is really cool is that mine is an FTP exit point so 
therefore you get three copies of this Pac-man on your system.
Let me guess, having an hspec wouldn't make any sense because it's
not an RPG issue, it's the SQL precompiler.  And we all know what
a superb piece of code that is.

(Hey, my Notes spell checker corrected Pacman to Pac-man!)
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---