The upgrade and installation process depends on whether upgrade and/or installation files exist.

When both upgrade and installation files exist, upgrade files are processed against matching installation files and then the updated installation files are installed. Each installed application is verified and made available. Matching is done on the application name, language, and type. If conflicts are found during the upgrade of an installation file, the conflict is documented in the ISPF log and also in the terminal output stream. Processing of the current installation file is discontinued. Processing continues with the next installation file.

When an upgrade file exists without a matching installation file, the identified application is automatically exported, upgraded, installed, verified, and made available. The application is exported to the output installation library with a unique member name.

When an installation file exists without a matching upgrade file, the installation file is installed. Each installed application is verified prior to being made available.

When you request backup and an application in the Application Manager administrator and user table data sets is to be replaced during an installation, that application is exported to the backup installation library with a unique member name before it is replaced.

When the mass upgrade and installation process is complete, the successfully processed applications are available to on-line users. Each of the applications has a corresponding file in the output installation library that is equivalent to the final contents of the modified application. If BACKUP(YES) was specified, the backup files will be installation files corresponding to the original version of each application that was modified during the process.