I'm the guy (or at least one of) that discovered this on V5R4 and opened the
PMR on it.

I went to 6.1 about 18 months ago and I just flat out don't remember whether
PTFs were/are required on 6.1. By that time, however, all my files had been
recreated via DDL instead of DDS, so I would not have experienced the issue.


On Wed, Jun 9, 2010 at 3:04 PM, Crispin Bates <cbates@xxxxxxxxxxx> wrote:

Hello all,

I am looking to see if I can replace existing LF's with Index's at i 6.1. I
thought that the new RCDFMT keyword would allow that, and it certainly seems
to work quite nicely.

I remember there being some PTF's (SI23355 and SI27866) for V5R4 issues
where the newly created file had a different Record Format Level Idenfifier
(RFLI) and this was caused by files that had Date Fields in them. I am
finding that if my TABLE (PF) has a DATE field in it, then I am getting a
different RFLI.

To see what was happening I removed the Date Field, and I then get the same
RFLI as the original LF had (which is exactly what I am after).

Is this a case of the same issue has raised it's head at 6.1, but for a
different reason (because the INDEX now supports the RCDFMT keyword)?, or am
I completely missing something, and there is a PTF for this that I need to
apply?

Thanks,

Crispin.
--
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.





As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.