Re: SQL Pre-compiler Issue

On Wed, Oct 21, 2015 at 10:29 AM, CRPence <crpbottle@xxxxxxxxx> wrote:

FWiW: That the GENLVL(31) was not sufficiently effective seems
troublesome. Indeed, again, that situation would appear to be "something
the pre-compiler ought to be able to deal with". There seems quite possibly
to be a defect, at least as described; a defect, that if not there, would
have allowed that Severity Level specification to overcome the issue.
Effectively, by deleting the file, the problem has been circumvented, but
not resolved; i.e. the apparent defect remains to be encountered again in
another [or a repeat] incident.

To be completely honest, I haven't fully followed your analysis, so
maybe you're saying what I'm thinking, just in different words; or
maybe you're saying something different.

I am totally with you on the "seems like a defect" language. ;)

From where I'm sitting, it feels like the compilation (of correct

*syntax*) should either (1) always succeed whether or not the file is
found, and if there's a runtime error, so be it; or (2) never succeed
when the file is not found.

I would be comfortable with "default GENLVL" behavior to be either of
the above. That is, I could make sense of "default GENLVL" resulting
in behavior (1) (and possibly no way of achieving (2)); or of "default
GENLVL" behavior being (2) and "permissive GENLVL" behavior being (1).

John Y.