Convert a Call Function parameter into Non-unicode

Former Member — Tue, 25 Jun 2013 16:28:44 GMT

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        = 2 MESSAGE L_MSG
        COMMUNICATION_FAILURE = 3 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

Re: Convert a Call Function parameter into Non-unicode

RaymondGiuseppi — Wed, 26 Jun 2013 06:39:24 GMT

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

Re: Convert a Call Function parameter into Non-unicode

Former Member — Wed, 26 Jun 2013 07:29:59 GMT

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

Re: Convert a Call Function parameter into Non-unicode

Former Member — Thu, 27 Jun 2013 10:56:24 GMT

Hello,

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

Thanks a lot,

Dominique

topic Convert a Call Function parameter into Non-unicode in Application Development and Automation Discussions

Convert a Call Function parameter into Non-unicode

Re: Convert a Call Function parameter into Non-unicode

Re: Convert a Call Function parameter into Non-unicode

Re: Convert a Call Function parameter into Non-unicode