The Add Function's Inputs and Outputs

Input

There is a variety of input file formats supported for the Add function. See Specialized and Generic Load Inputs for complete details of the different formats.

The database for the segment Add function must be an existing primary physical database. It must be either Zeroloaded or previously loaded with data. An Add should not be run, for any other kinds of databases. An error message will result if you attempt an Add function to one of the following databases:

• The primary index for a HIDAM database. A primary index database is not required. The .IDX component of an MFIMS database is the equivalent of this index and is modified automatically when adding segments to the primary database.
• Secondary index databases. These are modified automatically when adding segments to the primary database they index.
• Databases defined as ACCESS=LOGICAL. The physical databases contain the required pointers to support logical relationships.
• GSAM databases. The Add function does not support GSAM databases.
• A database which has not been Zeroloaded or previously loaded with data.

Exclusive use databases and shared update Fileshare databases may be used with the Add function. IMSDBU does not support adding segments to Remote IMS or User Exit databases. The DBUTIL utility can be used for adding segments to User Exit databases. You must develop your own program if you need to add segments to a Remote IMS database from the workstation.

Shared read-only databases must be processed as an exclusive use or shared update Fileshare database and copied to the shared directory.

Output

The database data files are modified by this function. Any secondary index databases are also modified. If the database contains logical children definitions, the PtrUpdate function must be run before the database can be accessed by an application program.