Privileges: TSOS
The MERGE statement merges the input syntax file with the syntax file specified here. The latter must be of the same type (system or group syntax file) as the input syntax file.
During merging, programs with their associated statements are transferred as one unit; i.e. they may replace an entire program which already exists in the input file. It is not possible to merge multiple versions of a product.
Format 1: Merging software unit syntax files
MERGE |
FILE = <filename 1..54> ,CHECK-PRODUCT = *NO / <structured-name 1..15> ,CHECK-VERSION = *NO / <c-string 1..7> ,REPLACE-PRODUCT = YES / NO ,UPDATE-SDF-GLOBALS = YES / NO |
FILE = <filename 1..54>
Specifies the syntax file to be merged with the input file named under OPEN. If MERGE statements were already executed subsequent to the OPEN, the syntax file is merged into the work file currently in use, which is the file containing the syntax files merged beforehand with MERGE (see "Handling work files ").
CHECK-PRODUCT =
Determines whether the syntax file to be merged is subjected to a check for consistency with a given product name. If the specified syntax file contains more than one software unit, message SDI0023 is issued but the merge run is completed. It is then no longer possible, however, to unmerge (with REMOVE) one or all of the SUSFs contained in this syntax file.
CHECK-PRODUCT = *NO
No name consistency check takes place.
CHECK-PRODUCT = <structured-name 1..15>
Gives the product name of the software unit contained in the specified syntax file (e.g. SPOOL, TIAM, etc.).
CHECK-VERSION =
Determines whether the syntax file to be merged is subjected to a check for consistency with a given version number.
CHECK-VERSION = *NO
No version consistency check takes place.
CHECK-VERSION = <c-string 1..7>
Version number of a software unit. The version numbers of the SUSFs supplied by Fujitsu correspond to the SDF data type <product-version>( see the “Commands“ manual [1]).
Format: ’nn.naxx’, where:
nn.na = version number of the software unit, xx = update level of the syntax file.
It is possible to specify only the left-hand part of the version number. The check uses that length which has been specified.
REPLACE-PRODUCT =
Specifies whether any existing objects in the input syntax file are to be overwritten by objects with the same internal or external name from the syntax file specified here.
REPLACE-PRODUCT = YES
Objects in the input syntax file are overwritten by objects with the same internal or external name. This enables internal or external names to be renamed.
REPLACE-PRODUCT = NO
If objects with the same internal or external name are encountered, the merge run is aborted.
UPDATE-SDF-GLOBALS =
Specifies whether the global information of the input syntax file is to be overwritten (i.e. updated).
UPDATE-SDF-GLOBALS = YES
The global information of the input syntax file is overwritten with the global information of the syntax file specified here, but the version number of the input syntax file is retained.
UPDATE-SDF-GLOBALS = NO
The global information of the input syntax file is not overwritten.
Format 2: Merging user-generated syntax files
MERGE |
FILE = <filename 1..54> ,REMOVE-ID = <structured-name 1..15> ,REPLACE-PRODUCT = YES / NO |
FILE = <filename 1..54>
Specifies the syntax file to be merged with the input file. If MERGE statements were already executed subsequent to the OPEN, the syntax file is merged into the work file currently in use, which is the file containing the syntax files merged beforehand with MERGE (see "Handling work files ").
REMOVE-ID = <structured-name 1..15>
Short name of the syntax file (required for subsequent deletion).
REPLACE-PRODUCT =
Specifies whether any existing objects in the input syntax file are to be overwritten by objects with the same internal or external name from the syntax file specified here.
REPLACE-PRODUCT = YES
Objects in the input syntax file are overwritten by objects with the same internal or external name. This enables internal or external names to be renamed.
REPLACE-PRODUCT = NO
If objects with the same internal or external name are encountered, the merge run is aborted.
Notes
If an error occurs when handling a MERGE operation, processing resumes with the next MERGE statement. In this case SDF-I continues with the status of the last successful MERGE statement. The spin-off mechanism is initiated on program termination.If subsequent MERGE statements cannot be executed either, the output file reflects the status of the last successful MERGE. It will not contain all the desired products but will still be a valid syntax file.
If message SDI0035 appears after a MERGE statement for one of the syntax files supplied by Fujitsu, the supplied syntax file must be handled like a user-generated syntax file (see format 2), not an SUSF (see format 1).
If multiple syntax files for a number of products are to be merged, it is better to regenerate the system and group syntax files from the original syntax files by means of a batch task. The additional overhead in terms of memory is offset in this case by the increased integrity of the generated syntax files.