|
|
|
|
|
|
This screen is used to submit a request to copy mappings. The copies produced are identical to the originals. Copies can be made between companies, within the same company, or between databases or systems.
You should already be familiar with the operation of the screen Mapping - Copy MQMO; only differences between MQM4 and MQMO are described here.
Your current company is the default destination or receiving company.
Copying single mappings within and between companies in the same system or database is performed in the same way as with MQMO, ignoring the From System and From Database fields. When copying a single mapping between companies, the From and To mapping names can be the same; if you are copying within the same company, then the To name must not be the same as the From name.
If a mapping already exists on the destination company which has the same name as the mapping you want to copy from the other company, then you can either delete the existing mapping manually or enter 'Y' in the To Overwrite field to have the existing mapping automatically deleted before the copy is performed.
To copy multiple mappings, you can use wildcards in the From Mapping field. Up to 1000 mappings can be copied in one operation. If multiple mappings are being copied, they all retain the same names on the destination company as on the source company. You will normally set the To Overwrite field rather than delete multiple mappings manually from the receiving company.
When copying multiple mappings, press Enter after filling in the From fields; the screen will then display the number of Matched Mappings - that is, the number of mappings on the source company whose names are matched by the wildcards in the From Mapping field. This is the number of mappings which will be copied when Update is used. (It is not possible at present to view the list of matched mappings directly from this screen; we recommend that you use the same mapping name wildcards on the screen Mapping - List, MQMA, to check which mappings will be copied.)
If any mapping on the receiving company has the same name as one of the mappings to be copied, and you have not set the To Overwrite field, then an error message will be displayed and the copy operation will not be allowed.
If any mapping on the receiving company has the same name as one of the mappings to be copied, and you have set in the To Overwrite field, then a warning message is displayed but the copy operation is allowed.
If there is no mapping in the source company (the one named in the From Company field) with a name which matches the one entered in the From Mapping field, a message is displayed and the copy is not performed.
When you copy mappings, you normally want to compile them too. To avoid having to compile the copied mappings individually, the screen provides an option to compile the mappings immediately after being copied. This is especially useful when large numbers of mappings are being copied.
Copying single or multiple mappings between databases or systems works in the same manner as already described, except that you need to specify the source system and/or database name, and a special compatibility check is performed before the copy operation is attempted.
Links between the databases or systems must have been established before you can copy mappings between systems.
(See Cross System Copying for information about the Compare Systems action and the automatic conversion which can be performed when copying between systems.)
The Update action initiates the copying process. The first step for cross-system or cross-database operations is always to perform the compatibility check; only if the system comparison does not detect any incompatibilities will the copy operation proceed.
Optional; if specified, must be name of an existing database to which links have already been established. (This field works in conjunction with From System; the entry here depends on the underlying database management system. See Cross System Copying for information about the Compare Systems action and the automatic conversion which can be performed when copying between systems.)
Optional; if specified, must be the name of an existing system to which links have already been established; this will normally be the Table Prefix. (This field works in conjunction with From Database; the entry here depends on the underlying database management system - see Cross System Copying)
Mandatory; must contain the identifier of a currently defined company on the source database/system.
If the mapping is to be copied within the same company, then the company identifier entered here should be the same as the one in the To Company field. The associated description is displayed alongside the company identifier.
Mandatory; must contain the name of a mapping to be copied. You can use wildcards to specify multiple mappings. When you press Enter, the number of mappings matching the entered name will be displayed to indicate how many will be copied if the operation succeeds.
At least one mapping with the specified name must already exist in the company named in the field From Company.
Display only; shows the number of mappings in the company named in the field From Company with names which match the entry in From Mapping.
Optional; if you do not enter the identifier of an existing company on the current system, then the current company is used as the destination for the copied mapping(s). The associated description for the company is displayed alongside.
Optional. If a single mapping is being copied within the same company, then you must enter a valid name which does not already exist in the current company. If a single mapping is being copied between companies, then you can enter a name if required; if not, then the copy mapping will have the same name as the original. If multiple mappings are being copied (that is, wildcards have been entered in From Mapping), then they will all retain the same names and this field is left blank.
Optional. Set this field if you want the mappings being copied to replace any with the same name which already exist in the current company; any existing mappings which do have the same name will be deleted before the new ones are copied. If you leave this blank and there is an existing mapping with the same name as one being copied, then an error message is displayed and no copy is performed.
Optional. Set this field if you want the mappings being copied to be compiled after they have been copied. If compiled versions of mappings with the same name already exist in the receiving company, the copied mappings will not be compiled unless To Overwite is set.
You can enter C to (re-)compile all mappings which match the entry in From Mapping without copying. In this case you cannot enter anything in any of the other To fields; any existing compiled versions will be overwritten.
Action |
Description |
Compare Systems |
This action is performed automatically when you use Update; it is also available via a function key for you to use as required. The action is used to check for incompatibilities between the source and destination databases; if differences are found which are not due to version changes, then the copy operation may not be allowed. (See the introduction to this chapter for details.) |
If not described in this topic, click on a field and press F1 to view help. See Common Fields for more information.
Fast prompt allows you to quickly view a list of options for certain fields.
See Using the Command Line on opening the screen without going through the menu.
See also
|
© Advanced, Jan 2021 |
|
