IBM Support

PI83397: WORKING DIRECTORY PATH USING "FILE.SEPARATOR" VALUE FROM SERVER INSTEAD OF AGENT; CAN CAUSE PATHING ERROR ON OS MISMATCHES

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

  • it generates the workingDirectory by the following way. so
    when UCB server on Windows, agent on Linux, the
    workingDirectory is not valid path.
    --------------------------------------------------------
    workingDirectory += File.separator +
    ParameterResolver.resolve(config.getWorkDirOffset());
    
    Should be using agent properties to get the agent's
    File.separator, but / will work on Windows as well.
    

Local fix

  • APAR to be created; do not use working directories
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Server on Linux machine and agent on Windows, or vice versa. *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Working directory path using "File.Separator" value from     *
    * server instead of agent can cause path issues when server    *
    * and agent use different path schemas.                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • Fix is included in cumulative patches released on or after
    2017-06-20 for UCB 6.1.2.x versions (build number 922222) and
    2017-06-29 for UCB 6.1.3.x versions (build number 922825).
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI83397

  • Reported component name

    URBANCODE BUILD

  • Reported component ID

    5725P5700

  • Reported release

    612

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-06-20

  • Closed date

    2017-10-18

  • Last modified date

    2017-10-18

  • 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

    URBANCODE BUILD

  • Fixed component ID

    5725P5700

Applicable component levels

  • R612 PSN

       UP

  • R612 PSY

       UP

  • R613 PSN

       UP

  • R613 PSY

       UP

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

Document Information

Modified date:
18 October 2017