IBM Support

PI13573: DEFAULT DXL EXECUTION CYCLE LIMIT DIFFERS IN BATCH MODE COMPARED WITH GUI (AND DIFFERENCE IS BECOMING MORE PRONOUNCED).

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Default DXL execution cycle limit differs in batch mode when
    compared with the GUI (and that difference has become more
    pronounced in recent versions).
    
    This manifests itself in DXL scripts failing in batch mode which
    succeed in the GUI. There is a further defect which means that
    the error given does not mention the timeout, but adding the
    line "pragam runLim, 0" to the start of the script fixes it.
    
    To recreate the problem run code such as the following in batch
    mode:
    
    "
    Stream out = write "C:/myLog1.log"
    
    int i
    for (i =0; i<20000; i++) {
     out << "test aaaaaaaaaaaaaaaaaaaaaaaaa
    bbbbbbbbbbbbbbbbbbbbbbbbbbbbb ccccccccccccccccccccccccccccc
    ddddddddddddddddddddddd " i "\n"
    }
    "
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Batch mode users/environments affected                       *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Default DXL execution cycle limit appears to differ in batch *
    * mode when compared with the GUI (and that difference has     *
    * become more pronounced in recent versions).                  *
    * Batch mode scripts time out while running the same script    *
    * from the GUI is OK.                                          *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to 9.6.0.1                                           *
    ****************************************************************
    This is a client side fix
    

Problem conclusion

  • Batch mode timeout reset when starting an external script;  so
    the full execution time is available.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI13573

  • Reported component name

    TLOGIC DOORS

  • Reported component ID

    5724V61DR

  • Reported release

    930

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-03-12

  • Closed date

    2014-09-11

  • Last modified date

    2014-09-11

  • 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

    TLOGIC DOORS

  • Fixed component ID

    5724V61DR

Applicable component levels

  • R960 PSY

       UP



Document information

More support for: Rational DOORS

Software version: 9.3

Reference #: PI13573

Modified date: 11 September 2014