Re: File attributes PF38, LF38, PF38-DTA, PF38-SRC

Neil,

I'm just curious, but what happens if you take your LF38 source (that does
not have a PFILE library qualification) and recompile it into a temporary
library as an LF?

Will it use the existing access path?  I'd be surprised if it did not.

In which case it would be pretty fast and painless to compile all of the
LF38's as LF's (assuming proper library lists and PF to LF dependencies),
then delete the LF38's (or move them to a temporary holding library) and
move the LF's into the production library.  Sounds like it should take about
2 minutes per LF, no?

This should be easy and painless to test.  And you'll know in minutes if you
got it right.

(John's law:  Everything is easy if someone else has to do it :)

Does this sound reasonable to you?

jte


--
John Earl
www.powertechgroup.com  john.earl@powertechgroup.com
The Powertech Group Inc. Seattle, Washington
Where the Security Experts Live!

Phone: +1-253-872-7788
Fax:      +1-253-872-7904
--
----- Original Message -----
From: "Neil Palmer" <neilp@dpslink.com>
To: <midrange-l@midrange.com>
Sent: Thursday, August 01, 2002 11:14 AM
Subject: Re: File attributes PF38, LF38, PF38-DTA, PF38-SRC


> Now that was so obvious wasn't it !  ;-)
> Yeah - changing the DDS source and just running something like
> CHGPF FILE(SSPYDTA/PPCCMP) SRCFILE(SSPYSRC/QDDSSRC) SRCMBR(PPCCMP)
> takes care of PF38-DTA to PF-DTA
>
> Still, don't see a way to change LF38 to LF, PF38-SRC to PF-SRC....
>
> ...Neil
>
>
>
>
>
> jmoreno@militarycars.com
>
>
>
>         To:     midrange-l@midrange.com
>         cc:
>         Subject:        Re: File attributes PF38, LF38, PF38-DTA, PF38-SRC
>
>
>
> How about the CHGPF command ?
>
> I think it should work
>
>
>
>
>
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>