export [name[=value] ...]
export marks each name so that the current KornShell exports it automatically to the environment of all commands executed from that shell. Exported variables are thus available in the environment to all subsequent commands. Several commands (for example, cd, date, and vi) look at environment variables for configuration or option information.
Variable assignments of the form name=value assign value to name as well as marking name for export.
Calling export without arguments presents a list, with appropriate quoting of the names and values of all variables in the format:
If you re-input this format to another shell,
variables are assigned appropriately but not exported.
The exporting of environment variables is one way in which the MKS KornShell differs from cmd.exe. cmd.exe always export all currently defined environment variables; the MKS KornShell only exports those that you have marked for export (through the export command or some other mechanism).
Possible exit status values:
Failure due to invalid command line argument.
Failure resulting in a usage message, usually due to invalid command line option.
POSIX.2. x/OPEN Portability Guide 4.0. Windows Server 2012. Windows 8.1. Windows Server 2012 R2. Windows 10. Windows Server 2016. Windows Server 2019.
export is a special built-in command of the Bourne Shell and KornShell on UNIX systems.
This is a special built-in command of the MKS KornShell.
PTC MKS Toolkit for Power Users
PTC MKS Toolkit for System Administrators
PTC MKS Toolkit for Developers
PTC MKS Toolkit for Interoperability
PTC MKS Toolkit for Professional Developers
PTC MKS Toolkit for Professional Developers 64-Bit Edition
PTC MKS Toolkit for Enterprise Developers
PTC MKS Toolkit for Enterprise Developers 64-Bit Edition
PTC Windchill Requirements and Validation
PTC MKS Toolkit 10.3 Documentation Build 39.