That is true. What strikes me as weird though is that the following piece of CL code I inherited (with file.encoding for whatever reason specified as 1253, not Cp1253) worked fine on V5R1 w/ JRE 1.2.2. RUNJVA CLASS(<classname goes here>) PARM(&USRID &PASSWD) CHKPATH(*IGNORE) PROP((os400.stderr 'file:/JAVAAPPS/SRVCLASS_ErrorLog.doc') (os400.stdio.convert 6) (file.encoding 1253) (os400.stdout 'file:/JAVAAPPS/SRVCLASS_Console.doc'))) "Clapham, Paul" <pclapham@xxxxxxxxxxxxx> wrote: "1253" isn't a valid encoding, it's a CCSID. The encoding that corresponds to it is "Cp1253". PC2 -----Original Message----- From: java400-l-bounces@xxxxxxxxxxxx [mailto:java400-l-bounces@xxxxxxxxxxxx] On Behalf Of Panagiotis Varlagas Sent: November 23, 2005 06:31 To: Java Programming on and around the iSeries / AS400 Subject: Re: Strange problem We could distinguish between two types of files here: - The files that standard output and standard error are redirected to - The log files to which we write directly (via Java I/O) from the application When we specify -Dfile.encoding=1253 on the java command then neither a log file gets created nor do the stdout and stderr get written to their respective files. When we do not pass a -Dfile.encoding flag to the java command at all, or when we use -Dfile.encoding=ISO8859_7, both types of files get written to.
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.