Re: IFS Object Catalog

We're talking a whole bunch of concepts and thoughts being jumbled
together.
1 - Flagging stuff in BRMS. I was not talking about this, and "link omit
lists" in BRMS. No way, no how. I was talking solely about using
WRKLNKBRM to see when a particular directory/file was last backed up.
2 - Your BRMS backups will have messages like
Message ID . . . . . . . . : CPD37C3
Cannot save /QIBM/UserData/OS400/TCPIP/RAS/IKEV2SOCKET
The ALWSAV attribute on /QIBM/UserData/OS400/TCPIP/RAS/IKEV2SOCKET was set
to *NO
DSPLOGBRM TYPE(*BKU) PERIOD((*AVAIL 032218))
BTW, that's a sev(0) message.

If you were doing a regular SAV command there's an option to have all
these messages go to a file to make it easier to process. I don't have
the inclination to figure out how to do this in BRMS.

These should appear in your joblog also. Many people are opposed to
change so they still have all their joblogs go to a spool file. I changed
all ours to go to *PND and this allows me to query them using tools like
https://www.ibm.com/developerworks/community/
wikis/home?lang=en#!/wiki/IBM%20i%20Technology%20Updates/
page/QSYS2.JOBLOG_INFO()%20UDTF

Here's an outside of the box thought...
If the directory is flagged as ALWSAV(*NO) and they feel the data is
expendable and shouldn't be saved, then shouldn't you go in and delete all
those files that are over x days old? For example, if the directory name
is .../logs... and it's flagged as ALWSAV(*NO) and there's 45,000 files in
there might that give you back some space? At least since upgrading from
7.1 you don't have to worry about these slowing down your saves or taking
up tape space.

Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: Gord Hutchinson <gordm1@xxxxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 03/26/2018 03:35 PM
Subject: Re: IFS Object Catalog
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



These aren't IBM directories. They are directories created within the
same
job as created the tiff document. The directory and 3 out of 4 objects
within the directory are ALWSAV(*YES).

Unless I find some current ones that are ALWSAV(*NO) I'm not going to
worry
about what happened 2 years ago. These were on our development partition
so who knows.

I'm trying to find a quick way of finding anything in production that is
set incorrectly. Nothing is flagged in BRMS on the development partition
prior to the upgrade to 7.3 so I know there won't be anything flagged in
production (which is still at 7.1).

Thanks,


Gord



On Mon, Mar 26, 2018 at 1:12 PM, Rob Berendt <rob@xxxxxxxxx> wrote:

Jim's right. Creating your directories and files in certain existing

IBM

directories is going to be trouble.

It's not like IBM spun the random wheel to flag a directory as
ALWSAV(*NO). They picked them on their intended contents, log files for
example.

Be careful of just trying to change the IBM directories to ALWSAV(*YES).
IBM has a history of setting IFS attributes at each IPL. Several of us
had to give IBM a serious beat down to stop flagging /tmp with
CHGATR OBJ('/tmp') ATR(*RSTDRNMUNL) VALUE(*YES)
at every IPL as that immediately put a stop to email from working.
Maybe they've amended their ways and no longer do changes this way but I
don't know about other directories and the ALWSAV option and how they

set

that. So it's something to be aware of.


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: Jim Oberholtzer <midrangel@xxxxxxxxxxxxxxxxx>
To: "'Midrange Systems Technical Discussion'"
<midrange-l@xxxxxxxxxxxx>
Date: 03/26/2018 01:03 PM
Subject: RE: IFS Object Catalog
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



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

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


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


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