IBM Sterling Ideas

formerly Watson Supply Chain

Submit new product ideas for IBM Sterling solutions. Before you submit, please review existing ideas; if an idea close to yours already exists, it's better to add comments or vote on the existing idea. We will review your ideas and use them to help prioritize our product development. Best of all, the portal will automatically update you when the status of your idea has been changed. Order Management, Store Engagement, Watson Order Optimizer, Inventory Visibility, CPQ and Call Center are now part of Watson Supply Chain

Connect with IBM experts and your peers on the Supply Chain Collaboration Community and the Order Management Interest Group

Connect Direct defaults to a 002 umask on unix platforms

Files delivered to unix systems are given rw-rw-r-- pemissions as CD is not recognising the system umask of 027 and is defaulting to 002.
  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Jan 4 2018
  • Delivered
How will this idea be used?
What is your industry?
What is the idea priority? High
DeveloperWorks ID DW_ID82553
RTC ID RTC_ID489224
Link to original RFE http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=82553
  • Attach files
  • Admin
    Chris Sanders commented
    January 11, 2018 18:31

    Thank you for your patience as we worked on this enhancement.  It was delivered in April 2016 as APAR IT14769.  I've included the details of the fix below.  You can download this fix from IBM's Fix Central website to take advantage of it.


    003) RTC498204 / APAR IT14769  commit date:  22 Apr 2016

    --------------------------------------------------------

         When receiving a new data file, C:D UNIX uses create mode 664 by

         default.  These permission settings may not be appropriate in some

         scenarios.

     

         Fix adds two new initparms to the copy.parms record in initparm.cfg:

     

         recv.file.open.perm=nnn, where nnn is an octal integer describing the

         desired default permissions for new files received.  It's the same as

         the value documented for the copy sysopt "permiss".

     

         recv.file.open.ovrd=x, where x is one of the following three values:

     

            'Y' - Allow copy step sysopt "permiss" value to override

                  recv.file.open.perm value when receiving a new file.  This is

                  the default.

            'N' - Disallow copy step sysopt "permiss" value to override

                  recv.file.open.perm value when receiving a new file.

            'P' - Allow copy step sysopt "permiss" value to override

                  recv.file.open.perm value when pnode is receiving a new file.



    Sincerely,

    Chris Sanders

    Connect:Direct Offering Manager