RE: IFS Object Catalog

That sounds like an application problem.


--
Jim Oberholtzer
Agile Technology Architects


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Gord
Hutchinson
Sent: Monday, March 26, 2018 11:31 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: IFS Object Catalog

No, normal tifs created from the i. One directory I looked at had 4 tifs
all created at the same time. 3 were ALWSAV *YES and one was *NO. They
were created in 03/2017 so a little difficult to debug it now.

Since these have never been saved, I almost afraid to see what hasn't been
saved in production.


Gord



On Mon, Mar 26, 2018 at 12:03 PM, David Gibbs <david@xxxxxxxxxxxx> wrote:

On 3/26/2018 11:00 AM, Gord Hutchinson wrote:

We just upgraded our development partition from 7R1 to 7R3. With the
change IBM made in 7R3 to report the CPD37C3 (Cannot save ....) we
find a lot of random IFS objects that aren't being saved because they
have ALWSAV set to *NO. I say random because we have objects that
were created in the same time and in the same directory as other
objects that have ALWSAV(*YES).

Any chance these files were copied from the QNTC file system?

I've found that the ALWSAV attribute is *NO for IFS files copied from

QTNC.

david


--
David Gibbs
midrange.com

IBM i on Power Systems: For when you can't afford to be out of business!

I'm riding 615 miles (Yes, you read that right) in the American
Diabetes Association's Tour de Cure to raise money for diabetes
research, education, advocacy, and awareness. You can make a tax
deductible donation to my ride by visiting https://list.diabetessucks.net.

See where I get my donations from ... visit
https://lsteml.diabetessucks.n et/map for an interactive map (it's a geeky

thing).

I may have diabetes, but diabetes doesn't have me!
--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD

--
Gord Hutchinson
TST Overland Express
--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link:
http://amzn.to/2dEadiD