IBM Support

PI66538: TRIGGERS WON'T RUN IN BATCH MODE UNLESS EITHER THE PROJECT OR MODULE LEVEL SPECIFIERS ARE NAMED

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as unreproducible.

Error description

  • If the specification of a trigger does not include a named
    project or module (i.e. it uses "project->all->module->all") it
    will not fire when using batch mode.
    
    To recreate:
    
     - create a trigger on all modules in all projects using code
    such as:
    
    " Trigger t = trigger("Trigger obj_pre_modify",
    project->all->module->all, pre, close, 1, "#include
    <C:/test_trigger.inc>")"
    
     - in test_trigger.inc put a print statement e.g. "print
    "trigger running""
     - open and close a module to ensure the statement is printed
    and the trigger running
     - create batch.dxl and put in it code such as :
    
    "
    Module m = edit ("/MyProject/New Module", false)
    close m
    "
    
     - now open a command prompt inside the client bin directory and
    test the batch behaviour using a command such as:
    
    "doors.exe -u Administrator -P password -batch C:\batch.dxl"
    
     - once the module gets opened/closed, which will take a few
    seconds, you should see the printed text indicating that the
    trigger is running in a new command prompt, but that doesn't
    happen
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Users of DOORS triggers                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * If the specification of a trigger does not include a named   *
    * project or module (i.e. it uses "project->all->module->all") *
    * it                                                           *
    * will not fire when using batch mode.                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • This issue has been resolved in DOORS 9.6.1.7
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI66538

  • Reported component name

    TLOGIC DOORS

  • Reported component ID

    5724V61DR

  • Reported release

    961

  • Status

    CLOSED UR5

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-07-27

  • Closed date

    2016-12-20

  • Last modified date

    2016-12-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

  • R961 PSY

       UP



Document information

More support for: Rational DOORS

Software version: 961

Reference #: PI66538

Modified date: 20 December 2016