Re: CHGPF on file with multiple format logicals.

["rick baird" <rick.baird@xxxxxxxxx>]

Pete,

of the 5 or so logicals built that way, only one had DTLINE as a key
field.  I deleted that logical and the CHGPF worked fine with about 20
other logicals intact, including the multi-format ones.

it has to be something about changing a key field, on a multi-format
logical that made it burp, but I've never run into that before.

On Dec 3, 2007 8:36 PM, Pete Hall <pbhall@xxxxxxxxxxxxx> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I don't understand what is really happening here. I suspect there are
> other relationships that are causing the problem. Are the 3 logical
> files perhaps then used as the basis for an SQL view or something? I
> suspect if you just eliminated the higher order dependency, the chgpf
> would work. I've changed field lengths with chgpf a number of times,
> although possibly not with a key field in a dependent logical, so maybe
> I've just never tried that.
>
> Could you just delete the logical files, run CHGPF, then recreate the
> logical files?
>
> Pete Hall
> pbhall@xxxxxxxxxxxxx
>
>
>
> rick baird wrote:
> > Hey all,
> >
> > I have a physical file with several multiple format logicals built
> > over it (don't ask, I wouldn't have done it this way).  The
> > multi-formats are used to sub-select certain records from the same
> > physical.
> >
> > a simplified look at how the logicals are created:
> >
> >           R ICDETLF1                  PFILE(ICDETLP)
> >             DTLVL1
> >             DTWHSI
> >             DTLINE
> > <snip lots of fields>
> >           K DTWHSI
> >           K DTLINE
> >           O DTLVL1                    CMP(EQ '1')
> >
> >           R ICDETLF2                  PFILE(ICDETLP)
> >             DTLVL1
> >             DTWHSI
> >             DTLINE
> > <snip lots of fields>
> >           K DTWHSI
> >           K DTLINE
> >           O DTLVL1                    CMP(EQ '2')
> >
> >           R ICDETLF3                  PFILE(ICDETLP)
> >             DTLVL1
> >             DTWHSI
> >             DTLINE
> > <snip lots of fields>
> >           K DTWHSI
> >           K DTLINE
> >           O DTLVL1                    CMP(EQ '3')
> >
> >
> > I'm changing DTLINE from 4A to 6A (the physical uses a reference file
> > to define the field).
> >
> > when I start the CHGPF process, it halts with the following message:
> >
> > CPF3238
> > Message . . . . :   Key field DTLINE not same as previous formats.
> > Cause . . . . . :   A logical file was being created by your job.  However,
> >   the key field DTLINE in record format ICDETLF2 has a different type and/or
> >   length than the key fields in the same position in previous formats.
> > <snip>
> >
> > so, it converted the initial format (ICDETLF1) but halted on the
> > second, I assume because it can't match up DTLINE in format ICDETLF2
> > in the new definition from the temporary new PF.
> >
> > has anyone else run into this?  any ideas on how I can get CHGPF to
> > work for these logicals, or should I quit wasting my time and just
> > delete before and rebuild them afterwards?
> >
> > Thanks,
> >
> > Rick
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.7 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFHVK8TpcZsDl8OX6kRAiPvAKCihqjLdFoxA9XvEHxT8cBYo7g/8gCfQ08l
> cIGb1DHY3ReGL4Ukc8L1o3U=
> =lDWM
> -----END PGP SIGNATURE-----
> --
> 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.