Re: Benefits of declaring literals in D-specs

One other thing concerning Named Constants.

If something needs to externalized, then almost always it is something
that should be in database table. For example, company name should be in
a database table.

We end up hard coding stuff on the AS/400 because we don't have database
independence when use file I/O and nobody want to recompile programs
when fields are added to the database.

I use a copy member that has standard constants in it but the only thing
that I keep of is things like the name of the company message file name,
etc.

d cYes...
d c 'Y'
d cNo...
d c 'N'
d cTrue...
d c *On
d cFalse...
d c *Off
d cXVMessageFileName...
d c Const('XVMSGF *LIBL ')

* Exotic Metal Standard Message File.
d cEMMessageFileName...
d c Const('EMFCO *LIBL ')

d cCPFMessageFileName...
d c Const('QCPFMSG *LIBL ')
d cBsearchLessThan...
d c Const(-1)
d cBsearchEqual...
d c Const(0)
d cBsearchGreaterThan...
d c Const(1)
* Sql Values.
d cSqlStateOk c Const('00000')
d cSqlStateNoRow c Const('02000')
d cSqlErrLastRow c Const(100)
d cCloseLabel c Const('Close')
d cOpenLabel c Const('Open')
d cFetchLabel c Const('Fetch')