SET IMPORT DUPLICATE Command

Transporting Applications in Source Form › Source Transport Commands › SET IMPORT DUPLICATE Command

SET IMPORT DUPLICATE Command

Specifies the action to take when an imported entity already exists. If you do not enter this command, processing stops when a duplicate entity is found (QUIT).

This command has the following format:

                     { REPLACE        }
                     { NEXT [VERSION] }
SET IMPORT DUPLICATE { SKIP           }
                     { QUIT           }

REPLACE: Overwrites the existing entity when status is TEST.
NEXT: Create an entity at the next available version without changing the existing entity.
SKIP: Continue to process the source input without changing the existing entity or adding a new one.
QUIT: Quit processing the source input without changing the existing entity.

Note:

For dataviews and HELP members, the NEXT option is treated as SKIP because these entities do not have version numbers.
An import does not replace an existing dataview if a program in Production status is using it.

SET IMPORT RESOURCE Command

Specifies the version requirements for the relationships established in an imported program's resource table. If you do not specify this command, the resources are imported with the version set in the export file.

This command has the following format:

SET IMPORT [PGM] RESOURCE [entity] version clause

entity

Identifies the entity for which the version clause is specified. Valid values are DVW, PGM, PNL, and RPT. If you do not specify an entity, the version clause applies to all entity types.

version clause

Indicates the version of the specified entity that is related to the program in the program's resource table. The version clause has the following format:

      { ASIS }
      { PROD }
[VER] { nnn  }
      { Tnnn }
      { LAST }

ASIS

The imported program's resource table uses the version set in the export file.

PROD

The imported program's resource table uses the production version, regardless of the version shown in the export file. If no PROD version of the entity exists, the relationship is not added and a warning message is included on the source and SYSPRINT listings.

nnn

The imported program's resource table uses version number nnn, regardless of the version shown in the export file.

Tnnn

The imported program's resource table uses version number Tnnn for CA Datacom/DB native access dataviews, regardless of the version shown in the export file. This version can only be specified for CA Datacom/DB native access dataviews (DVW).

LAST

The imported program's resource table uses the most recently created version for the specified entity, regardless of the version shown in the export file. You can only specify this version for unmodeled dataviews, programs, panels, and reports (DVW, PGM, PNL, and RPT).

Note: Resources associated using this keyword must exist before the program is imported. If the resources are imported from the same tape as the program and they were not exported in the correct sequence (resources before program), you must import the application in two job steps: the first job imports the resources and the second imports the program.