|
Bruce, If your program is RPGLE some might argue that you can put a parameter on your CRT... command. However, just like RPGLE has an H spec, SQLRPGLE has something unique for SQL that is much like the H spec: C/EXEC SQL C+ Set Option C+ Naming = *Sys, C+ Commit = *None, C+ UsrPrf = *User, C+ DynUsrPrf = *User, C+ Datfmt = *iso, C+ CloSqlCsr = *EndMod C/END-EXEC Notice the "Commit = *None"? So much easier than remembering the parameter on your CRT... statement. You do also realize that on V5R4 they added a new keyword to CREATE TABLE? You can now put your RCDFMT on it. Beats creating a table and renaming it to get around RPG's RLA requirement that the record format be different that the file name, (of course a RENAME f spec beats that into submission also). I have some style issues with that, like why use FH in front of all your field names? Really makes it hard to see all the files that have OT in them by browsing the file SYSCOLUMNS on your system. If you are using RPG's RLA and you have OT in two different files then simply use a PREFIX on the F spec. And, four character field names (the FH does not count)?! See also the LABEL ON. Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.