Re: Cannot Add a logical file member. Not sure why

Hi Pete,

There is a Command in TAATOOLS that will give you a report that shows all
LF that are not in the same library that the PF is in.

I am moving from a 620 at V4R5 to an 810 at V5R4 and this Command has
helped me. I was lucky, there are only 3 files that I have to worry
about. But one of the LF is in my Test Environment and points to the PF
in Production. I "may" have to take a look at this one.

As for the Level Check, I believe if you Add a Field, or Change the
Attributes of a Field, it will change the Level Indicator.




Thanx,

Nick



Nick Radich
Sr. Programmer/Analyst
EPC Molding, Inc.
Direct (320) 679-6683
Toll free (800) 388-2155 ext. 6683
Fax (320) 679-4516
nick_radich@xxxxxxxxxxxxxx



From: Pete Helgren <pete@xxxxxxxxxx>
To: midrange-l@xxxxxxxxxxxx
Date: 10/27/2010 04:09 PM
Subject: Re: Cannot Add a logical file member. Not sure why
Sent by: midrange-l-bounces@xxxxxxxxxxxx



"See you in May?" Absolutely!

As for the logical /physical file issue. It's not huge. A nuisance.
But helpful to know if I run into this again, I'll need recreate the
logical.

As a follow up: If the source for the logical hasn't changed and the
file is recompiled, does it cause a level check? I have always been
fuzzy on what causes the level indicator to change on a compiled file.

Pete Helgren
Value Added Software, Inc
www.asaap.com
www.opensource4i.com


On 10/27/2010 2:47 PM, Vern Hamberg wrote:

LOL Pete - you've been unlucky enough to use only good habits in where
your PFs and LFs go! You've not considered trying the naughty bits that
are discussed in the manuals!

I suspect that IBM won't change this, since it has been this way
forever. But you can always submit a requirement at the COMMON site -
under members, look for the requirements page - membership not required,
just get a user and password.

See you in May?
Vern

On 10/27/2010 3:08 PM, Pete Helgren wrote:

It's the first time I have come across it. I have never seen a case
where the logical and physical didn't reside in the same library but
then, I have only been around the box for 30 years or so and have lived
a sheltered life ;-)

Yeah, it makes sense on one level. Maybe an additional parameter on

the

create duplicate object for *file types would be helpful.

Pete Helgren
Value Added Software, Inc
www.asaap.com
www.opensource4i.com

-snip-