Re: CCSID - change from 65535 to 37...issues? stories?

On Thu, Sep 18, 2014 at 2:28 PM, Gqcy <gmufasa01@xxxxxxxxx> wrote:

about the only problem we had was
that when we changed our Source physical files, it changed the member change
date (like you would see in PDM).
some of our programmers depended on that to denote that a program change was
made...

Well, if you're using PDM, and don't have any version control
software, that date *is* pretty handy.

Now, I happen to be a PDM/SEU user. Laugh, jeer, offer sympathy,
whatever. Fact is, that's what I use. I noticed that most of our
source PFs are CCSID 37 but some are 65535. I tried to do CHGSRCPF on
one of the 65535 ones, and it told me the file was changed, didn't
give me any error messages, but the CCSID remained stuck at 65535...
AND the member change dates were all updated. Not cool.

Any idea what I have to do, besides

CHGSRCPF FILE(MYLIB/QRPGLESRC) CCSID(37)

???

I can live with the dates changing, as long as the file ACTUALLY CHANGES.

I'm on 7.1. I know that a few releases ago, the default copy behavior
was changed from "reset the change date on the newly added member" to
"copy the change date from the original member" (so the creation date
will be new, but the change date will be old). If all else fails, I
can probably create a brand-new empty source PF with the proper CCSID,
and copy all the "hex" members into the new file.

John Y.