IBM Support

PI20845: RFT LOGS WHEN VIEWED FROM RQM DO NOT HONOR LOG.APPEND('\N') WHEN A SCRIPT IS RUN IN RQM .

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Customer uses RQM4.0.3+RFT 8.5.1.2 to test Java's web
    application.
    They need to logging some messages to the log files and they use
    API logInfo method for it
    
    In the script, they add the below scripts using StringBuilder
    class and print the message
    to the log using logInfo():
    
    log.append('??? ?????? ?????? ?????? ?????? ????????? ??? ??????
      ??? ??????  ???  ??? ??????  ??? ??????  ???  ???  ');
                                                          log.append
    (', ');                                               log.append
    ('\n');                                               log.append
    ('???  ??? ??????  ??? ????????? ?????? ?????? ??? ??????  ??? ?
    ?????  ??????????????? ???  ???  ???  '); log.append(', ');
                                              log.append('\n');
    
    
                                              logInfo(log.toString()
    );
                                              (similar to something
    like:                                     log.append('Action: Ch
    eckup Input Value');                      log.append(', ');
                                              log.append('\n');
                                              log.append('Checkup Su
    mmary: Value verification');              log.append(',');
                                              log.append('\n');
    
                                              logInfo(log.toString()
    );                                        )
    
                                              When running the scrip
    t in RFT, \n works as expected, new line  is added properly in t
    he log file.                              When running the scrip
    t in RQM, \n becomes a hankaku(1 byte)    space and all messages
     print to the log in one line.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Users running RFT scripts through RQM and users having log   *
    * type as xml.                                                 *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Newline characters in the log messages are missing in XML    *
    * logs, when running RFT scripts either locally or through     *
    * RQM.                                                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • The issue is fixed in 8.6.0.2, now the newline character will be
    displayed properly on XML logs.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI20845

  • Reported component name

    RATL QUALITY MG

  • Reported component ID

    5724V1000

  • Reported release

    860

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-06-26

  • Closed date

    2014-12-16

  • Last modified date

    2014-12-16

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    RAT FUNC TESTER

  • Fixed component ID

    5724G2503

Applicable component levels

  • R860 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSJMXE","label":"Rational Functional Tester"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"860","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
17 October 2021