Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

# character problem in AL11

former_member223446
Active Participant
0 Kudos

Hi Everyone,

In AL11, while trying to view a file, the text '0Dram armu201Anien ' in the file is replaced as '0Dram arm#nien'.

The file when viewed on desktop shows no # character but in AL11, it is displayed with a # character.

Kindly let me know if there is any mistake in the following code.


...
OPEN DATASET P_SERVR FOR INPUT IN LEGACY TEXT MODE  MESSAGE MSG CODE PAGE '1160' IGNORING CONVERSION ERRORS.
.
.
.
OPEN DATASET P_SERVR FOR OUTPUT IN LEGACY TEXT MODE  MESSAGE MSG CODE PAGE '1160' IGNORING CONVERSION ERRORS.
...

I have gone through the forum but I couldnt find the required information.

Please help.

Thanks.

1 ACCEPTED SOLUTION

former_member15255
Active Participant
0 Kudos

Hi,

There are two methods of uploading file to application server 'BIN' & 'ASCI' format. During upload of 'BIN' it gives '#' during display of file in application server which is normal to my knowledge. But Upload through 'ASC' format and display the file it would show the file without '#' . To me it is perfectly normal because it does not effect your data.

Thanks & Regards

Suresh Krishnan

4 REPLIES 4

former_member15255
Active Participant
0 Kudos

Hi,

There are two methods of uploading file to application server 'BIN' & 'ASCI' format. During upload of 'BIN' it gives '#' during display of file in application server which is normal to my knowledge. But Upload through 'ASC' format and display the file it would show the file without '#' . To me it is perfectly normal because it does not effect your data.

Thanks & Regards

Suresh Krishnan

former_member214857
Contributor
0 Kudos

Hello Suresh

Basically # symbols are caused because system cannot read properly opened file with suggested code page. Instead od use

CODE PAGE 1160 you can use UTF-8.

Best regards

0 Kudos

HI

Those two solutions are not working .could you please provide the proper solutoin.

regars

krian

nils_buerckel
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi,

please check the following thread:

In transaction AL11 on a Unicode system it is not possible to display Non-Unicode data properly.

Special characters like your "Windows comma" will be displayed as # (although it is stored properly).

Best regards,

Nils Buerckel