IBM Support

PM37769: it is not possible to tell if DXL run in batch mode times-out (runLim execution cycles)

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as documentation error.

Error description

  • Problem
    If you are running batch DXL and it timesout by reaching the
    limit in the allowed number of execution cycles, you will not be
    able to determine why it has failed.
    
    When the same happens in a GUI session the user is presented
    with a message 'DXL Execution timeout: You may:' with options to
    'Halt execution', 'Continue' and 'Continue, double existing
    timeout'
    
    If you opt to halt the script the DXL error is given '-I- DXL:
    execution halted'
    
    In batch mode you get no options (what could be done with them
    anyway?) only the '-I- DXL: execution halted' error.
    
    To Reproduce
    Run the following DXL as a batch job:
    
    '
    int j = 0
    
    for (i=0;i?100000;i++){
            j++
    }
    
    print j
    '
    
    Using a command such as:
    
    'doors.exe -u Administrator -P password -b
    C:\pathToTheAboveCode\InAFile.dxl'
    
    Possible Workarounds
    Add a 'pragma runLim, 0'
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    DXL documentation needs updated with guidelines about pragma
    runLim
    

Problem conclusion

  • DXL documentation needs updated with guidelines about pragma
    runLim
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM37769

  • Reported component name

    TLOGIC DOORS

  • Reported component ID

    5724V61DR

  • Reported release

    910

  • Status

    CLOSED DOC

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-04-26

  • Closed date

    2011-06-20

  • Last modified date

    2011-06-20

  • 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

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSYQBZ","label":"Rational DOORS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.1","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

Modified date:
27 October 2021