The ice under my feet is becoming thinner :-) I don't consider
myself to be a code page expert, so bear with me and correct
me if I'm wrong.
>> I've not played with code pages and assembler so far, so
>> I may be missing HLASM options.
>>
>If there is such an option for HLASM, an assembler progra
In a recent note, "Hunkeler Peter (KIUK 3)" said:
> Date: Wed, 31 Jan 2007 11:01:42 +0100
>
> I've not played with code pages and assembler so far, so
> I may be missing HLASM options.
>
If there is such an option for HLASM, an assembler program
would need to be recompiled for each local
>//STDIN DD *
>ln -s /usr/lpp/db2/db2810/jcc/classes/db2jcc_license_cisuz.jar
db2jcc_license_c\
>isuz.jar
Maybe you should try:
ln -s /usr/lpp/db2/db2810/jcc/classes/db2jcc_license_cisuz.jar \
db2jcc_license_cisuz.jar
And one more thing... (Thanks to Walter Heestermans for pointing t
>At what level is this translation performed. For example,
>suppose an assembler program with source in the IBM-1047
>code page, and assembled and linked in the IBM-1047 locale
>does a BPX1RED then a CLI '\' on the data in the buffer.
>Will this match an IBM-1047 '\' or an IBM-273 '\'?
>
>What abo
>I do agree that a C program source displayed through a French
>code page does look odd...
Only if the source isn't encoded in the French code page
as well :-)
Peter Hunkeler
CREDIT SUISSE
--
For IBM-MAIN subscribe / signoff
>
>I hate EBCDIC! Is Unicode a solution?
No need to become emotional...
It is not EBCDIC that is the problem. Code pages are.
Unfortunately, Unicode is NOT the solution: there are lots of different
encoding schemes for Unicode (UTF-8, UTF-16, little/big endian, etc. etc.)
so when it comes do
In a recent note, "Hunkeler Peter (KIUK 3)" said:
> Date: Mon, 29 Jan 2007 09:18:06 +0100
>
> 3. The LE runtime runs in the C locale with CP1047 by default.
>You can tell it to do otherwiese with:
>
>//STEP1EXEC PGM=AOPBATCH,
>// PARM='ENVAR("LC_ALL=De_DE.IBM-273")/sh'
>Just for the archive and perhaps for some offline reader.
[snip]
>So this leaves at least two choices
>
>1. Switch to mode hex and enter x'E0' as a backslash (x'EC' is for
cp273)
>2. use iconv -t IBM-1047 -f IBM-273 ! /bin/sh (the '!' vary from
codepage
> to coderpage) at first statement in
In a recent note, Schiradin,Roland HG-Dir itb-db/dc said:
> Date: Sat, 27 Jan 2007 01:06:05 +0100
>
> So this leaves at least two choices
>
> 1. Switch to mode hex and enter x'E0' as a backslash (x'EC' is for cp273)
> 2. use iconv -t IBM-1047 -f IBM-273 ! /bin/sh (the '!' vary from codep
hope this helps someone in the future
Roland
-Original Message-
From: Schiradin,Roland HG-Dir itb-db/dc
Sent: Friday, January 26, 2007 7:49 PM
To: 'IBM Mainframe Discussion List'; '[EMAIL PROTECTED]'
Subject: RE: AOPBATCH Continuation character
Jantje,
at first thanks for
List
[mailto:[EMAIL PROTECTED] On Behalf Of Jan MOEYERSONS
Sent: Monday, January 22, 2007 11:09 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: AOPBATCH Continuation character
>
>ln: FSUM6245 link to target "\" failed: EDC5111I Permission denied.
>db2jcc_license_cisuz.jar: FSUM7351 not
Jan, thank you. I'll try this asap.
Roland
>>But if your input is fixed length (and it tends to be if it is instream
>>data in a JCL...) then the backslash has to go in exactly the 80th
>position.
>
>That is: the exact last position of the input record (whatever the LRECL
>is).
n MOEYERSONS
Sent: Monday January 22 2007 02:09
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: AOPBATCH Continuation character
>
>ln: FSUM6245 link to target "\" failed: EDC5111I Permission denied.
>db2jcc_license_cisuz.jar: FSUM7351 not found
>IIRC, it's the shell, not AOPBATCH
>But if your input is fixed length (and it tends to be if it is instream
>data in a JCL...) then the backslash has to go in exactly the 80th
position.
That is: the exact last position of the input record (whatever the LRECL
is).
Cheers,
Jantje.
>
>ln: FSUM6245 link to target "\" failed: EDC5111I Permission denied.
>db2jcc_license_cisuz.jar: FSUM7351 not found
>IIRC, it's the shell, not AOPBATCH, that deals with
>continuation characters.
>
>Try a backslash at the end of the line - although I'm not sure
>how this will translate with fixed
nt: Friday, January 19, 2007 8:17 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: AOPBATCH Continuation character
IIRC, it's the shell, not AOPBATCH, that deals with
continuation characters.
Try a backslash at the end of the line - although I'm not sure
how this will translate with fixed 80 col
--Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf
Of Schiradin,Roland HG-Dir itb-db/dc
Sent: Friday January 19 2007 10:31
To: IBM-MAIN@BAMA.UA.EDU
Subject: AOPBATCH Continuation character
Hi folks,
anybody know the continuation character for AOPBTACH i
Hi folks,
anybody know the continuation character for AOPBTACH if any?
The command might be larger then 80 charachters.
Currently I have a workaround using environment variables but
//STEP010 EXEC PGM=AOPBATCH,PARM='sh'
//STDOUTDD SYSOUT=T
18 matches
Mail list logo
