Connect Direct issue on the Square bracket
Select messages from
# through # FAQ
[/[Print]\]

MVSFORUMS.com -> Other Technical Topics

#1: Connect Direct issue on the Square bracket Author: nbdtrjk_1 PostPosted: Tue Jul 04, 2023 12:42 am
    —
All,

I am sending mainframe file to a Windows machine via Connect Direct, the transmission was successful and the file landed at the target system.

but there is an issue on the content, in the mainframe, there is a square bracket "[]," however in the Ascii version, its an unprintable format(see below).

Code:

[ is converted to â

[ - X'BA'
â - Ascii is 131



Note: other special chars like %, @,( ),$ etc. are transmitted correctly except the square bracket.

any ideas? What's the problem?

Thanks

#2:  Author: kolusuLocation: San Jose PostPosted: Tue Jul 04, 2023 9:58 am
    —
nbdtrjk_1,

Check this link

https://www.ibm.com/support/pages/how-use-codepage-function-when-sending-data-connectdirect-zos-connectdirect-windows

You need to use IBM-1047 for the mainframe side and UTF8 for windows side

Kolusu

#3:  Author: nbdtrjk_1 PostPosted: Wed Jul 05, 2023 1:01 am
    —
Hi,

I used like SYSOPTS="CODEPAGE=(IBM-1047,UTF-8)" but still conversion is not coming properly.
Code:

STEP2 COPY FROM (DSN=YOURHLQ1.CODEPAGE.TEST.FILE -
SYSOPTS="CODEPAGE=(IBM-1047,UTF8)" -
DISP=SHR ) -
TO (DSN='C:\CODEPAGE.TEST1.TXT' DISP=RPL -
SYSOPTS="DATATYPE(TEXT) XLATE(NO)" )

instead I used CODEPAGE=(37,UTF-8), this resolved the square bracket issue but decimal values not converted properly.

#4:  Author: kolusuLocation: San Jose PostPosted: Wed Jul 05, 2023 10:48 am
    —
nbdtrjk_1 wrote:
this resolved the square bracket issue but decimal values not converted properly.


nbdtrjk_1,

What do you mean by decimal values? If the data on the mainframe is numeric (Binary, Zoned decimal with sign overpunch or packed decimal) then you need to convert them to readable format, before you can send them to PC side.

#5:  Author: nbdtrjk_1 PostPosted: Wed Jul 05, 2023 8:48 pm
    —
Hi Kolusu,

I have numeric decimal values in the mainframe file like 0000.1234(Readable format only), but the PC file received after transmission has 0000Ý1234, which is incorrect.

however, 'MR.ABC' (named with a dot), which is successfully translated into PC

seems some issue on the '.' conversion logic between numeric & Alpha.

#6:  Author: kolusuLocation: San Jose PostPosted: Thu Jul 06, 2023 10:23 am
    —
nbdtrjk_1,

what is the HEX value of DOT in the numeric field? It should X'4B'. If it is something different then it explains why you have bad values on PC side?

#7:  Author: nbdtrjk_1 PostPosted: Thu Jul 06, 2023 8:32 pm
    —
Hi,

yes. Its X'4B'.
We reported this issue to C: D team and they did minor change on the Transaction Table and started working now. Thanks for your help Kolusu.

Cheers



MVSFORUMS.com -> Other Technical Topics


output generated using printer-friendly topic mod. All times are GMT - 5 Hours

Page 1 of 1

Powered by phpBB © 2001, 2005 phpBB Group