RE: Index journalling WAS: List all objects attached to a journal

Interesting! Thanks for the info, another problem solved!



-----Original Message-----
From: rob@xxxxxxxxx [mailto:rob@xxxxxxxxx]
Sent: Monday, July 06, 2015 8:17 AM
To: Midrange Systems Technical Discussion
Subject: Index journalling WAS: List all objects attached to a journal

Because you can journal indexes also. Methinks that was added not as an audit feature but more as a recovery feature.
Ancient history (+20 years ago). We used to save without saving access paths. Saved time during the save and saved a lot of tape space. Then we did that full system restore. Some files were not usable for a week as access paths were still being rebuilt. Granted, much slower hardware, etc. Stuff like this is why they allow you to journal indexes also.


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: Matt Olson <Matt.Olson@xxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 07/06/2015 08:58 AM
Subject: RE: List all objects attached to a journal
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



Yep, changing the column to convert 65535 worked well. Thanks everyone!

Now to figure out why it listed indexes on physical files as being
journaled instead of just the physical file itself...



-----Original Message-----
From: Vernon Hamberg [mailto:vhamberg@xxxxxxxxxxxxxxx]
Sent: Friday, July 03, 2015 10:33 AM
To: Midrange Systems Technical Discussion
Subject: Re: List all objects attached to a journal

All well and good - but it seems, from another post from Matt, that the
column is set to 65535, so one should still set the JDBC connection to
convert 65535, it seems.

Vern

On 7/3/2015 6:34 AM, Alan wrote:

IBM help desk told us that IBM recommends changing the system value for

CCSID to 37 and discourages 65535.

BUT with the caveat of caution and research to avoid undesired

consequences.

On July 2, 2015 5:42:52 PM EDT, Buck Calabro <kc2hiz@xxxxxxxxx> wrote:

On 7/2/2015 5:33 PM, Matt Olson wrote:

Any idea why when I select from that file it is all hexadecimal

gibberish when using tools like iSeries navigator run sql scripts?

I can view it fine with strsql from a 5250 session, but still run

into limits of the 5250 session display and paging.

Almost there! Just need to figure out how to get it to display

properly in a "real" query tool like run sql scripts in navigator,
sqldbx, or ibm data studio

Wow, that is ugly.
The reason is that the WRKJRNA command apparently creates each column
with CCSID(65535) - which is 'binary data, do not translate'. That
seems a defect to me, since on my system the default CCSID is 37 - US
English. I'll have to take that up with IBM.

For the moment, if you are using the IBM i Navigator, go to
Connection Temporary JDBC Settings, click the Translate tab and
select Translate CCSID 65535. That should help some, although the
columns out on the end still look goofy to me.

--
--buck

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

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