AW: Does the recommendation against variable names starting with SQL apply to constants?

In either way I'd avoid naming constants, variables, procedures (everything)
beginning with SQL.
At least for future development.
In the current programs you simply may add a prefix for example
cSQL_STATE_SUCCESS.

Mit freundlichen Grüßen / Best regards

Birgitta Hauser

"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"

-----Ursprüngliche Nachricht-----
Von: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] Im
Auftrag von Charles Wilt
Gesendet: Tuesday, 31. August 2010 22:33
An: RPG programming on the AS400 / iSeries
Betreff: Does the recommendation against variable names starting with SQL
apply to constants?

All,

I've got an SQLSTATE copy member with SQLSTATE code values defined
that I've used for a long time:

// Class Code 00: Unqualified Successful Completion
d SQL_STATE_SUCCESS...
d c '00000'

// Class Code 02: No Data
d SQL_STATE_NO_DATA...
d c '02000'
d SQL_STATE_NO_MORE_RS...
d c '02001'

It just hit me that I could run into trouble in the future given IBM's
recommendation to not start user variable names with SQL. Since IBM
reserves the right to add variables that begin with SQL.

Unless for some reason the proscription on user created names with SQL
wouldn't apply to constants??

On the other hand, given the long names being used it's probably
pretty unlikely that IBM would use the same name for
something...right??

Thanks!
Charles Wilt