IBM Support

PI93742: POST PROCESSING SCRIPT MAY EXECUTE BEFORE THE OUTPUT LOG HAS BEEN FULLY WRITTEN

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • If you have plugin steps that are failing such as the 'WebSphere
    deploy' plugin's 'check app is installed' step you may be
    affected by this issue. Any plugin step that uses post
    processing scripts may be affected. There will be an ifix to
    address this APAR.
    
    Post processing scripts may fail because they are executed
    before the output log has been fully written. The log is not
    properly flushed before the post processing script is run; so
    the scanner which matches lines of output may not match lines
    that haven't been written yet.
    
    Steps to reproduce:
    1) Set up a process has a shell step that displays the contents
    of a file, the file should have a few lines of text, using a
    program such as cat.
    2) Modify the post processing script by adding a function that
    matches each line of output and prints it out:
    
    scanner.register(".*", function(lineNumber, line) {
        commandOut.println(lineNumber + ", '" + line + "'");
    });
    
    3) run the process
    
    expected:
    The process displays the contents of the output log including
    the text file correctly
    actual:
    The last line(s) of the log are not included or are truncated in
    the post processing script.
    

Local fix

  • Write additional lines of output to the file, such that the text
    you are searching for in the post processing script is not at
    the end of the output log.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * ALL                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * If you have plugin steps that are failing such as the        *
    * 'WebSphere                                                   *
    * deploy' plugin's 'check app is installed' step you may be    *
    * affected by this issue. Any plugin step that uses post       *
    * processing scripts may be affected. There will be an ifix to *
    * address this APAR.                                           *
    *                                                              *
    * Post processing scripts may fail because they are executed   *
    * before the output log has been fully written. The log is not *
    * properly flushed before the post processing script is run;   *
    * so                                                           *
    * the scanner which matches lines of output may not match      *
    * lines                                                        *
    * that haven't been written yet.                               *
    *                                                              *
    * Steps to reproduce:                                          *
    * 1) Set up a process has a shell step that displays the       *
    * contents                                                     *
    * of a file, the file should have a few lines of text, using a *
    * program such as cat.                                         *
    * 2) Modify the post processing script by adding a function    *
    * that                                                         *
    * matches each line of output and prints it out:               *
    *                                                              *
    * scanner.register(".*", function(lineNumber, line) {          *
    *     commandOut.println(lineNumber + ", '" + line + "'");     *
    * });                                                          *
    *                                                              *
    * 3) run the process                                           *
    *                                                              *
    * expected:                                                    *
    * The process displays the contents of the output log          *
    * including                                                    *
    * the text file correctly                                      *
    * actual:                                                      *
    * The last line(s) of the log are not included or are          *
    * truncated in                                                 *
    * the post processing script.                                  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to 6.2.7.1.ifix03 or later                           *
    ****************************************************************
    

Problem conclusion

  • Fixed in version 6.2.7.1.ifix01
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI93742

  • Reported component name

    UC DEPLOY

  • Reported component ID

    5725M5400

  • Reported release

    627

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-02-13

  • Closed date

    2018-03-15

  • Last modified date

    2018-03-15

  • 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

    UC DEPLOY

  • Fixed component ID

    5725M5400

Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS4GSP","label":"IBM UrbanCode Deploy"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"627","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
15 March 2018