|
No preceding message in the joblog?
Again, keep in mind that if the directory is flagged that way the
individual files may not be, however they will still be skipped.
From my 7.3 RTVDIRINF
Select count(*) as NbrObjects, QEZSYSRSSV
from routines.QAEZD0064O
group by QEZSYSRSSV;
1,017,386 flagged with 0
69 flagged with 1
Select qezobjnam, qezdiridx
from routines.QAEZD0054O
where qezsysrssv=1
order by qezdiridx, qezobjnam;
samples include QOPT, QSR
What did not appear included the directories in:
Cannot save /fixes.
Cannot save /QIBM/ProdData/OS/SNMP.
So good luck with that.
DSPATR OBJ('/fixes')
Can be saved . . . . . . . . . . . . . : No
select d.qezdirnam1, d.*
from routines.qaezd0054d d
where qezdirnam1 = '/fixes';
QEZDIRIDX=96870
Select qezobjnam, qezdiridx, qezsysrssv
from routines.QAEZD0054O
where (QEZOBJNAM = 'fixes' and qezdiridx=1) or qezdiridx=96870
order by qezdiridx, qezobjnam;
qezobjnam qezdiridx qezsysrssv
fixes 1 0
CUME 96870 0
V7 96870 0
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/27/2018 09:48 AM
Subject: Re: IFS Object Catalog
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
I do not get CPD37C3. I do get CPD3775 - Cannot save or restore
/home/gord/myfile2.txt and
CPC3715 - No objects saved, all objects were excluded
Neither message shows in DSPLOGBRM which implies that nothing has been
getting skipped. Bu I don't know now if I trust this.
I have bitten the bullet and submitted a RTVDIRINF.
Gord
On Tue, Mar 27, 2018 at 9:24 AM, Rob Berendt <rob@xxxxxxxxx> wrote:
So, on your existing 7.1 machine, if you have the following:being
'/home/GORD'
'/home/GORD/myfile.txt'
'/home/GORD/myfile2.txt'
and you run
CHGATR OBJ('/home/GORD/myfile2.txt') ATR(*ALWSAV) VALUE(*NO)
SAV DEV('/QSYS.LIB/GORD.LIB/GORD.FILE') OBJ(('/home/GORD/*.txt'))
You do not get:
CPD37C3 - Cannot save /home/GORD/myfile2.txt.
Because if you do, then you can easily use that to see what has changed.
See also:
EDTF STMF('/home/GORD/myfile2.txt') used to create test.
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/27/2018 09:15 AM
Subject: Re: IFS Object Catalog
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
Rob, the point you are missing is that on 7.1 these objects are NOT
flagged with the CPD37C3 message. This is why I am trying to find away,
on 7.1, to find the objects with ALWSAV *NO.have
On Mon, Mar 26, 2018 at 4:00 PM, Rob Berendt <rob@xxxxxxxxx> wrote:
We're talking a whole bunch of concepts and thoughts being jumbledomit
together.
1 - Flagging stuff in BRMS. I was not talking about this, and "link
lists" in BRMS. No way, no how. I was talking solely about usingset
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
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
likethe inclination to figure out how to do this in BRMS.changed
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
all ours to go to *PND and this allows me to query them using tools
fileshttps://www.ibm.com/developerworks/community/all
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
those files that are over x days old? For example, if the directoryname
is .../logs... and it's flagged as ALWSAV(*NO) and there's 45,000
in<midrange-l@xxxxxxxxxxxx>
there might that give you back some space? At least since upgradingfrom
7.1 you don't have to worry about these slowing down your saves ortaking
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
objectsDate: 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
iswithin the directory are ALWSAV(*YES).partition
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
so who knows.
I'm trying to find a quick way of finding anything in production that
inset incorrectly. Nothing is flagged in BRMS on the developmentpartition
prior to the upgrade to 7.3 so I know there won't be anything flagged
existingproduction (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
butIBMfor
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
ALWSAV(*YES).example.
Be careful of just trying to change the IBM directories to
usIBM has a history of setting IFS attributes at each IPL. Several of
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
Ithey
don't know about other directories and the ALWSAV option and how
Ofset
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
hasn'tTheyGordtifs
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
all created at the same time. 3 were ALWSAV *YES and one was *NO.
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
webeenthe
saved in production.wrote:
Gord
On Mon, Mar 26, 2018 at 12:03 PM, David Gibbs <david@xxxxxxxxxxxx>
On 3/26/2018 11:00 AM, Gord Hutchinson wrote:
We just upgraded our development partition from 7R1 to 7R3. With
change IBM made in 7R3 to report the CPD37C3 (Cannot save ....)
thattheyfind a lot of random IFS objects that aren't being saved because
have ALWSAV set to *NO. I say random because we have objects
afromwere 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
QTNC.business!
david
--
David Gibbs
midrange.com
IBM i on Power Systems: For when you can't afford to be out of
https://list.diabetessucks.net.
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
See where I get my donations from ... visit
https://lsteml.diabetessucks.n et/map for an interactive map (it's
subscribe,mailinggeeky
thing).
I may have diabetes, but diabetes doesn't have me!
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To
mailingtakeunsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please
affiliatea 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
link: http://amzn.to/2dEadiD
--
Gord Hutchinson
TST Overland Express
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
takelist
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
aaffiliate
https://archive.midrange.com/midrange-lmoment to review the archives at
.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our
mailinglink:
http://amzn.to/2dEadiD
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
affiliatelist
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
mailinglink: http://amzn.to/2dEadiD
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
affiliatelist
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
listlistlink: 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
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
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
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.