Compiler Command Overrides

I know that when changing site command defaults (CHGCMDDFT) that
you have to be careful to respecify any previous command defaults that may
have been set by the site -- or you will lose them without realizing it
(until things stop working as expected). Well, that is what appears to be
happening to us right now.

A change was made to the command defaults for CRTBNDRPG (and
apparently CRTRPGMOD) and now our compiles are failing with the following
message.

RNF0265 The sequence number in the source file is not valid;
OPTION(*SRCSTMT) is ignored.

We have been running with OPTION(*SRCSTMT) for years and years.
So, we are not sure what we have done to ourselves. I looked at the
*SEQSRC option and though this allows us to compile, it also generates
different source sequence numbers than those in the source member. Thus,
we don't think we want this option because we think it means that error
messages which give statement numbers will only match compile listings and
not actual member source. Is this true?

Otherwise, I have a compile listing from Friday which I am
comparing to a compile listing from today that is failing. The one thing
that jumps out at me is Friday's compile has the following lines in it
(generated by the precompiler):

/SET CCSID(*CHAR:*JOBRUNMIX)
...
/RESTORE CCSID(*CHAR)

while today's failing compile listing doesn't have the above but
has a lot of the following lines generated by the SQL precompiler that
weren't generated on Friday:

/FREE
...
/END-FREE

Any ideas?

Sincerely,

Dave Clark