IBM Support

Environment Variables gone after bash update

Question & Answer


Question

Since applying a fix to BASH on a Linux host, in response to the POODLE vulnerability, it is no longer possible to access or use inherited environment variables that used to work fine within IBM Sterling Connect:Direct for Unix RUN TASKs. Why?

[{"Product":{"code":"SSKTYY","label":"IBM Sterling Connect:Direct for UNIX"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Component":"--","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"}],"Version":"4.2;4.1","Edition":"","Line of Business":{"code":"LOB77","label":"Automation Platform"}}]

Log InLog in to view more of this document

This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.

Document Information

Modified date:
24 July 2020

UID

swg21691386