IBM Support

PK91801: ERROR WHILE RUNNING A SAMPLE MASTERMIND EXE FROM TCHK

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as fixed if next.

Error description

  • TST:1068517
    
    
    Summary:
    --------
    Error while running a TCHK exe for mastermind
    
    Description:
    ------------
    When trying to run the exe from Testchecker a following runtime
    error is observed as shown in the screenshot.
    
    From the error message, we suspect that runtime libraries not
    loading correctly.
    
    This error is only observed with VC8 installed on the system.
    The same steps does not show any errors with vc6 and vc7.
    
    Customer has a work around now, They have changed the order in
    which makelog.bat looks for the installed compilers. And have
    changed it from
    
    if exist "%VC8%" goto vc8
    if exist "%VC7%" goto vc7
    if exist "%VC6%" goto vc6
    
    to
    
    if exist "%VC7%" goto vc7
    if exist "%VC6%" goto vc6
    if exist "%VC8%" goto vc8
    
    This is working for the moment, however customer has to use an
    older compiler.
    
    Version Details:
    Logiscope: 6.5 and 6.6
    OS: Windows xp
    Compiler: vc8
    
    Steps to Reproduce:
    -------------------
    1. Open Testchecker Mastermind with Logiscope 6.5/6.6
    2. Build the project.
    3. Launch Testchecker.
    4. Select the Test tab
    5. Create a new test 'File->new' and then 'Edit-> New Tests'.
    6. Select the new test and select any metric from the view, eg:
    DDP SPY.
    7. Press Go and observe the behavior.
    
    Support Observations:
    ---------------------
    We were able to observe the same behavior at our support labs.We
    suspect that Logiscope is not loading the runtime libraries
    correctly for vc8. If we use vc6 or vc7 the error is not
    observed.
    Customer has changed the makelog.bat so that it looks for vc6
    and vc7 before vc8. However this means that they will have to
    use an older compiler.
    
    We are of the opnion that this behavirois a defect. Please let
    us know if there is any solution for the same.
    

Local fix

  • Customer has a work around now, They have changed the order in
    which makelog.bat looks for the installed compilers. And have
    changed it from
    
    if exist "%VC8%" goto vc8
    if exist "%VC7%" goto vc7
    if exist "%VC6%" goto vc6
    
    to
    
    if exist "%VC7%" goto vc7
    if exist "%VC6%" goto vc6
    if exist "%VC8%" goto vc8
    
    This is working for the moment, however customer has to use an
    older compiler.
    

Problem summary

  • This defect is fixed in Logiscope 6.6.1. This information is
    available in the release notes.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    PK91801

  • Reported component name

    TLOGIC LOGISCOP

  • Reported component ID

    5724V81LS

  • Reported release

    650

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-07-20

  • Closed date

    2009-10-23

  • Last modified date

    2010-01-14

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

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

Fix information

Applicable component levels

  • R660 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYQHS","label":"Rational Logiscope"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.5","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
14 January 2010