Copying an executable module from the file system

There are two methods for copying an executable module from the file system into a data set. These methods are not exactly copy operations; instead, they bind the executables over to the data set. As a result, certain attributes are not preserved, but rather, re-established:

Use OGETX without the TEXT or BINARY option. If you are copying into a target data set that is a PDS or PDSE with an undefined record format, OGETX treats the files as executables. Because the entry point is re-established, this option only works if the original entry point is at the beginning of the executable.
Along with the entry point, other attributes are re-established, such as the authorization (AC) value, which is reset to AC=1 (the AUTH option allows it to be set to AC=1).
Be aware that most executables will not copy successfully into a PDS. When you attempt to execute this kind of operation, you'll receive the following type of error:
```
IEW2606S 4B39 MODULE INCORPORATES PROGRAM MANAGEMENT 3
FEATURES AND CANNOT BE SAVED IN LOAD MODULE FORMAT.
```
Instead of copying into a PDS, executables created with OS/390® V2R4 or later can be copied into a PDSE.
Another exception is DLL-enabled executables created with OS/390 V2R4 or later. These executables will not copy successfully into both PDSs and PDSEs. This occurs because the information that is provided by the IMPORT control statements is not preserved, and must be specified again during the rebind.
Use JCL that invokes the binder before you copy the executable into the data set. See the following example for sample JCL.