That's correct. It's very annoying. I keep telling myself to look for a way to clear it and submit an RFE if I can't a way to do it but since it's only painful once a year when we upgrade software, it hasn't made it to the top of my list yet.
Coy Krill
Core Processing Administrator/Analyst
Washington Trust Bank
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Rob Berendt
Sent: Monday, February 11, 2019 10:26
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: Alternative to QSYS2.OBJECT_STATISTICS to find file journal info
Importance: Low
Coy,
So what you are saying is do not just look at JOURNAL_NAME and JOURNAL_LIBRARY but first you need to look at JOURNALED?
That was it.
create schema deleteme;
create table deleteme.trash (mychar char(1));
cl: endjrnpf deleteme/trash;
SELECT *
FROM TABLE(QSYS2.OBJECT_STATISTICS('DELETEME', '*FILE')) AS a
WHERE OBJNAME = 'TRASH';
-- JOURNALED = NO
-- JOURNAL_NAME=QSQJRN
-- JOURNAL_LIBRARY = DELETEME
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Krill, Coy
Sent: Monday, February 11, 2019 12:50 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: Alternative to QSYS2.OBJECT_STATISTICS to find file journal info
Matt, if a file was journaled and then is no longer journaled, the last journal still shows on the object forever. What I do is ignore the journal information when journaled says NO. My guess is you need to do the same. Unless of course you can see that it is journaled and there is a discrepancy between dspobjd and object_statistics.
We first saw this as an issue with files we move over to our test environment and had tons of errors because our vendor software was seeing the old journal name and then trying to start journaling on the file when we don't have those same journals running over in test.
IBM told us it was as designed but the problem is then how does one know that we should or should not journal? The answer, keep a table of what was journaled before you turn it off and only turn it back on for those objects when you want it back on. Not the best answer in my book.
Coy Krill
Core Processing Administrator/Analyst
Washington Trust Bank
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Matt Olson
Sent: Monday, February 11, 2019 06:56
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Alternative to QSYS2.OBJECT_STATISTICS to find file journal info
Importance: Low
We have been using the following query to find which files are attached to which journal in our system and recently discovered that it can return incorrect results (showing files attached to journals that no longer exist for instance):
SELECT * FROM TABLE (QSYS2.OBJECT_STATISTICS('libraryname','FILE') ) AS X
Is there another, more reliable way to find all files that are attached to specific journals that can be easily queried ?
Anyone know why QSYS2.OBJECT_STATISTICS might return incorrect information? Perhaps we need to run some routine to "refresh object statistics" or something?
Matt
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
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:
https://amazon.midrange.com
This electronic mail message and any attachments may contain confidential or privileged information and is intended for use solely by the above-referenced recipient. Any review, copying, printing, disclosure, distribution, or other use by any other person or entity is strictly prohibited under applicable law. If you are not the named recipient, or believe you have received this message in error, please immediately notify the sender by replying to this message and delete the copy you received
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
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:
https://amazon.midrange.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
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:
https://amazon.midrange.com
This electronic mail message and any attachments may contain confidential or privileged information and is intended for use solely by the above-referenced recipient. Any review, copying, printing, disclosure, distribution, or other use by any other person or entity is strictly prohibited under applicable law. If you are not the named recipient, or believe you have received this message in error, please immediately notify the sender by replying to this message and delete the copy you received
midrange.com
