Re: Embedded SQL weirdness

Hello Dean,

Just so Nina doesn't think I correct only her ...

SQL has never required commitment control to be started outside the program.  
It has always been an attribute 
of the SQL program.  Starting commitment control in this way only affects SQL 
tables in the program; it does 
not affect any files declared in the normal fashion.

STRCMTCTL is only necessary for files processed natively regardless of whether 
the program uses SQL.

Regards,
Simon Coulter.

«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»
«» FlyByNight Software         AS/400 Technical Specialists       «»
«» Eclipse the competition - run your business on an IBM AS/400.  «»
«»                                                                «»
«» Phone: +61 3 9419 0175      Mobile: +61 0411 091 400           «»
«» Fax:   +61 3 9419 0175      mailto: shc@flybynight.com.au      «»
«»                                                                «»
«» Windoze should not be open at Warp speed.                      «»
«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»
//--- forwarded letter -------------------------------------------------------
> X-Mailer: AOL 4.0 for Windows 95 sub 205
> MIME-Version: 1.0
> Date: Mon, 18 Jan 99 14:19:31 -0500
> From: DAsmussen@aol.com
> To: MIDRANGE-L@midrange.com
> Reply-To: MIDRANGE-L@midrange.com
> Subject: Re: Embedded SQL weirdness

> 
> Ahh, the pattern emerges!  The files must be journaled on your system.  I ran
> into this a few weeks ago, and about drove myself crazy trying to figure out
> what happened because the environment in which I was testing was not
> _supposed_ to be journaled.  I forgot to change the compile defaults on an SQL
> program, which is normally not a problem because the job will tank when run
> against unjournaled data and remind me to recompile correctly.  Unfortunately,
> my test environment had recently been refreshed from production and the
> journals were not removed, as is the usual procedure.  My program threw all
> the records into the commitment buffer, and I lost half a day trying to debug
> why it wasn't working.  Compiling with COMMIT(*NONE) corrected the problem,
> after I issued a COMMIT from the command line on a lark and my data
> "magically" appeared.  Apparently, issuing the STRCMTCTL command prior to
> using commitment control is no longer a prerequisite.
> 
> HTH,
> 
> Dean Asmussen
> Enterprise Systems Consulting, Inc.
> Fuquay-Varina, NC  USA
> E-Mail:  DAsmussen@aol.com

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---