Hi Ulrich,
since level 4 is the highest trace level, it think it should display the data as well(?)
Level 4 = RemoteFunctionCall,PublicAPI,InternalAPI,RfcData (so logged in dev_nco_rfc.log)
I tested it again, this time in another test system, and to my suprise in this system I get a readable (i.e. with ASCII characters) hexdump in files nco_rfc_NNNNN_NN.trc like this:
06110 | 53393E3C 50545854 313E3C2F 50545854 |S9><PTXT1></PTXT|
006120 | 313E3C50 54585433 3E3C2F50 54585433 |1><PTXT3></PTXT3|
006130 | 3E3C5647 42454C3E 3C2F5647 42454C3E |><VGBEL></VGBEL>|
006140 | 3C2F6974 656D3E3C 6974656D 3E3C4D41 |</item><item><MA|
006150 | 4E44543E 3032303C 2F4D414E 44543E3C |NDT>020</MANDT><|
So the problem - that the hexdump is not readable - does only occur on the customer's system.
Any idea in which case the dump is readable and in which case not?