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

John,

Interesting. I wonder at the behavior when the file is a data file.

I expect that the new CCSID 37 file will need to be created and the CCSID 65535 data copied into it. Then all of the programs that access the file will need to be recompiled because I expect the result will be level checks(?).

Steve Needles


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of John Yeung
Sent: Thursday, September 18, 2014 2:54 PM
To: Midrange Systems Technical Discussion
Subject: 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.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.

________________________________
This communication, including attachments, is confidential, may be subject to legal privileges, and is intended for the sole use of the addressee. Any use, duplication, disclosure or dissemination of this communication, other than by the addressee, is prohibited. If you have received this communication in error, please notify the sender immediately and delete or destroy this communication and all copies.

TRVDiscDefault::1201