Input
The database to be unloaded must be a primary physical DBD or GSAM DBD which has been defined using DBDGEN. The data files for secondary index databases are not required by Unload. When unloading databases containing logical children, the database files for the logical parents is not required. An error message will result if you attempt to unload one of the following databases:
- The primary index for a HIDAM database.
- Secondary index databases. If you need to extract 'user data' from a secondary index, you can use the DBUTIL utility or develop your own program.
- Databases defined as ACCESS=LOGICAL. IMSDBU manages logical relationships using the physical databases. If you need to unload data using a logical DBD, you can use the DBUTIL utility or develop your own program.
Remote IMS and User Exit program Database Catalog types cannot be unloaded by IMSDBU. Unload is supported for single-user exclusive use databases, shared read-only databases, and shared update Fileshare databases. The DBUTIL utility can unload User Exit and Remote IMS databases.
Output
There is a variety of output file formats supported for unloading databases. See the Specialized and Generic Load Inputs topic for complete details of the different formats. Any of the formats supported by the Load function can be created using Unload.
