Licence File as XML: Invalid Input

General discussion on the JZOS batch launcher and toolkit
Post Reply
asroger
Posts: 2
Joined: Tue Mar 28, 2006 4:09 am

Licence File as XML: Invalid Input

Post by asroger »

Hello !

We use a third party library. This libary needs the following licence file:

<?xml version="1.0" encoding="windows-1252"?>
<!-- edited with XML Spy v4.4 U (http://www.xmlspy.com) by Friedhelm Hellerhoff (3M Medica) -->
<signedXml>
<srcData>
<LICENSE COPYRIGHT="3M HIS">
<PRODUCT>GROUPERJEDITION</PRODUCT>
<IKLIST>
<IK>999999999</IK>
</IKLIST>
<TEXT>OEM Lizenz für die GWI AG</TEXT>
<MAXDATUM> . .</MAXDATUM>
<MAXDURATION>0</MAXDURATION>
</LICENSE>
</srcData>
<sign>key/sign>
</signedXml>

We got the following error:

LicenseValidationException: Invalid input: `L' (0x4c), SystemID='file:.', Line=1

Here is our JCL:

//F53606A JOB 'NA ',NOTIFY=F53606,CLASS=E, JOB04921
// REGION=0M,MSGCLASS=T,MSGLEVEL=(1,1) 00000200
//*********************************************************************
//*
//* Stored procedure for executing the JZOS Java Batch Launcher
//*
//* Tailor the proc your installation:
//* 1.) Replace '<HLQ>.JZOS.LOADLIB' with the PDSE that contains the
//* JZOSVMxx modules that were installed during installation
//*
//*********************************************************************
//EXJZOSVM PROC JAVACLS=, < Fully Qfied Java class..RQD
// ARGS=, < Args to Java class
// LIBRARY='F536.JZOS.LOADLIB', < STEPLIB FOR JZOSVM module
// VERSION='14', < JZOSVM version: 13, 14, 50
// LOGLVL='', < Debug LVL: +I(info) +T(trc)
// REGSIZE='0M', < EXECUTION REGION SIZE
// LEPARM=''
//JAVAJVM EXEC PGM=JZOSVM&VERSION,REGION=&REGSIZE,
// PARM='&LEPARM/&LOGLVL &JAVACLS &ARGS'
//STEPLIB DD DSN=&LIBRARY,DISP=SHR
// DD DISP=SHR,DSN=SYS1.CEE.SCEERUN
// DD DISP=SHR,DSN=SYS1.CEE.SCEERUN2
//SYSPRINT DD SYSOUT=* < System stdout
//SYSOUT DD SYSOUT=* < System stderr
//STDOUT DD SYSOUT=* < Java System.out
//STDERR DD SYSOUT=* < Java System.err
//CEEDUMP DD SYSOUT=*
//ABNLIGNR DD DUMMY
//*
//*The following DDs can/should be present in the calling JCL
//*
//*STDIN DD < OPTIONAL - Java System.in
//*STDENV DD < REQUIRED - JVM Environment script
//*MAINARGS DD < OPTIONAL - Alternate method to supply args
// PEND
//*
//JAVAJVM EXEC EXJZOSVM,
// LOGLVL='+T',
// ARGS='/bknu/lib/test/F536/ka/Grouper.properties',
// JAVACLS='de.bundesknappschaft.host.grouper.HostGrouperStart'
//*
//STDENV DD *
export JAVA_HOME=/usr/lpp/java/J1.4:.
export PATH=/bin:/usr/lpp/java/J1.4/bin:
export PATH=$PATH:/usr/lpp/java/J1.4/bin/classic:.
export LIBPATH=/usr/lpp/java/J1.4/bin
export LIBPATH=$LIBPATH:/usr/lpp/java/J1.4/bin/classic
export LIBPATH=$LIBPATH:/bknu/JZOS/jzos
export LIBPATH=$LIBPATH:/bknu/lib/test/F536/ka/Grouper.properties:.
export CLASSPATH=/bknu/lib/test/jarfiles/3MGDRGGrouper.jar
export CLASSPATH=$CLASSPATH:/bknu/lib/test/jarfiles/3MReimbursement.jar
export CLASSPATH=$CLASSPATH:/bknu/lib/test/F536/ka
export CLASSPATH=$CLASSPATH:/bknu/lib/test/F536/ka/HostGrouper.jar
export CLASSPATH=$CLASSPATH:/bknu/lib/test/F536/ka/Grouper.properties
export CLASSPATH=$CLASSPATH:/usr/lpp/java/J1.4
export CLASSPATH=$CLASSPATH:/bknu/JZOS/jzos/jzos.jar:.
IJO="-Xms16m -Xmx128m"
IJO="$IJO -Djzos.home=/bknu/JZOS/jzos"
IJO="$IJO -Dfile.encoding=ISO8859-1"
export IBM_JAVA_OPTIONS="$IJO "
export JZOS_OUTPUT_ENCODING="IBM-273"
export DB2_HOME=/usr/lpp/db2/db2710/jcc/classes
for i in "$äDB2_HOMEü"/*.*; do
CLASSPATH="$CLASSPATH":"$i"
done
export CLASSPATH="$CLASSPATH":
/*
//*


Any suggestions would be appriciated.

Thank you

asroger
coz
Posts: 391
Joined: Fri Jul 30, 2004 5:29 pm

Post by coz »

It looks like your license file probably got converted to an EBCDIC codepage (maybe during a file transfer).

Make sure that it is in ASCII and try again.
asroger
Posts: 2
Joined: Tue Mar 28, 2006 4:09 am

Post by asroger »

Hello !

I transfered the file in binary mode(with smartFTP), but it's still the same problem.

asroger
dovetail
Site Admin
Posts: 2022
Joined: Thu Jul 29, 2004 12:12 pm

Post by dovetail »

Its not uncommon for Java programmers to write code that parses an XML file (incorrectly), so that it assumes that the default JVM codepage is ASCII.

As a workaround, try running your JVM (under JZOS) with -Dfile.encoding=ISO-8859-1

(this is a line commented out in the sample JCL for this)

If this doesn't work, pls double check that the file is in ascii:

iconv -f ISO-8859-1 -t IBM-1047 filename | more

Hope this helps...
Post Reply