Showing results for 
Search instead for 
Did you mean: 

EHS *.key file - Windows>Unix format

0 Kudos


I wonder if I have a "Windows-Unix" systems compatibility issue here with a file I have for processing. Read on...

When I opened to view the contents of a key file in a Unix dir via SAP tc AL11, it showed '#' character at the end of each line. (This is not the case when I open one in a SAP Windows NT system envt.)

The file was created from a Windows system and uploaded to a Unix system via tc CG3Z.

Once in the SAP app server, tc CG36 reads this key file to perform the function of importing EHS Report files.

However, CG36 errored it upon reading the first line in the file.

How can I check if the key file is formatted for unix system. I also read a related note from IMG documentation: "Your system administrator must ensure that *.KEY files that were created on a DOS system were converted to Unix format before import." Does this apply in my case?

I appreciate your thoughts.


Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Maria,

Could you provide the following additional information?

- Is your SAP System a Unicode System

- When you used CG3Z - did you upload to the Application Server in Binary or ASCII mode?

- Are you really using Windows NT - or a newer windows version that has Unicode capability?

My frist try would be to upload the file in ASCII mode.



0 Kudos

Thanks, Mark. It was the ASCII upload mode that was missed.

Answers (1)

Answers (1)

Active Contributor
0 Kudos

Hello Maria

if I remember correct:

if you perform file actions in Windows the "end of line" is normally defined by using ASCII characters 10 + 13 (line feed + charriage return). UNix uses as end of line If i remember correct only character 10. The "#" in your view is the "character 13" which is there in the Windows file. Therefore the remark ""Your system administrator must ensure that *.KEY files that were created on a DOS system were converted to Unix format before import." That means in "theory" that you need ot "parse" the export file to remove the combination char(10)/Char(13) and to replace it by "Char(10) only.

Now there are may be additional "buts". As explained in the different thread all depends on the top of "unicode" enabled or not topic and which format you haves used in "Export" and in "import".

The "dat" files for specifications etc. contains this information and If i remember correct this information is asked for in import and export process.

May be this helps a little bit.


PS: may be us this link:

Edited by: Christoph Bergemann on Feb 5, 2011 4:55 PM

0 Kudos

Thanks, Christoph. Key file was re-uploaded in ASCII mode. However, it's the PDF file that cannot be opened now by CG36. This was uploaded in BIN mode. I still have to trace the error (C$ 155).