|
Item 1 of 2: What are you getting from WRKJRNA that you couldn't get from
the "Journal Services" at http://ibm.biz/DB2foriServices
In Run SQL
Scripts you end up going into Connection, JDBC Configuration, Translation,
Translate CCSID 65535.
Two things:
Item 1 of 2: What are you getting from WRKJRNA that you couldn't get from
the "Journal Services" at http://ibm.biz/DB2foriServices
Item 2 of 2: The most common thing from this error is that your output
file is being created with CCSID 65535 which defaults to "look like crap
and don't translate". Ideally you would change system value QCCSID and
stop creating such garbage but until you do you pretty much have to go
into every utility and manually tell it to translate 65535. In Run SQL
Scripts you end up going into Connection, JDBC Configuration, Translation,
Translate CCSID 65535.
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: Jack Woehr <jwoehr@xxxxxxxxxxxxxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 03/19/2018 12:26 PM
Subject: WRJRNA output to file SQL query iACS comes back EBCDIC Hex
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
I do WRKJRNA output to a file.
I query select * from the output file in iACS run SQL query
Output comes back on my Mac in EBCDIC hex instead of readable text.
This has to be a FAQ but I can't find it ...
--
Absolute Performance, Inc.
12303 Airport Way, Suite 100
Broomfield, CO 80021
NON-DISCLOSURE NOTICE: This communication including any and all
attachments is for the intended recipient(s) only and may contain
confidential and privileged information. If you are not the intended
recipient of this communication, any disclosure, copying further
distribution or use of this communication is prohibited. If you received
this communication in error, please contact the sender and delete/destroy
all copies of this communication immediately.
--
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.
midrange.com
