Application Development and Automation 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: 
Read only

Convert a Call Function parameter into Non-unicode

Former Member
0 Likes
549

Hello Team,

I am currently working on an upgrade where a "fully specific add-on" was developped in 46C to interface data with an external system.

Now that we upgraded to ECC6 Unicode, some functionalities are not working anymore such as below one that seems tricky :

      CALL FUNCTION 'SendToMQ'
      DESTINATION ZU150S-RFCDEST
      EXPORTING
        QUEUEMGR          = L_QMGR
        QUEUE                 = L_QUEUE
        COMMIT                = L_COMMIT
      IMPORTING
        RETURN                = L_RC                       

        COMPCODE              = L_COMPCODE
        REASONCODE            = L_REASONCODE
      TABLES
        MESSAGES              = LT_MSGS                    

        MSGIDS                = LT_INIDS                   

        MQMDS                 = LT_MQMD                    

        MQPMOS                = LT_MQPMO                   

      EXCEPTIONS
        SYSTEM_FAILURE        = MESSAGE L_MSG
        COMMUNICATION_FAILURE = MESSAGE L_MSG
        OTHERS                = 9.

This call, which is supposed to send data contained in [TABLES] to the external system MQSeries, fails because parameter QUEUE is not correctly understood by the external system.

In ECC6 release, L_QUEUE = AQ.SEND.LU.JOB01.DATAGRAM but in hexadecimal, L_QUEUE = 00410051002E00530045004E0044002E......

In 46C release, L_QUEUE in hexadecimal = 41512E53454E442E....

We think what could fix the problem is to translate L_QUEUE ECC6 into an L_QUEUE non-unicode in order to allow the external system to read it correctly.

Do you know how to make such a conversion ? Have you ever experienced similar case ?

Could you please help ?

Thanks a lot,

Dominique

3 REPLIES 3
Read only

RaymondGiuseppi
Active Contributor
0 Likes
453

Check definition of RFC destination ZU150S-RFCDEST, is it checked as Unicode ?

SM59 - look at tab "MDMP and Unicode", where conversion are defined.

Regards,

Raymond

Read only

0 Likes
453

Hello Raymond,

RFC destination is checked as NON-UNICODE because Target system is non-unicode.

("Target is not a unicode system (character size 1)")

Regards,

Dominique

Read only

Former Member
0 Likes
453

Hello,

Does someone know a function that can convert contents of Unicode internal tables/Structures in Non-Unicode ?

Thanks a lot,

Dominique