Renaming a system definition - assure_mimix

Renaming a system definition - assure_mimix - 10.0

Assure MIMIX Administrator Reference

Product type

Software

Portfolio

Integrate

Product family

Assure

Product

Assure MIMIX™ Software

Version

10.0

Language

English

Product name

Assure MIMIX

Title

Assure MIMIX Administrator Reference

2024

First publish date

1999

Last edition

2024-08-27

Last publish date

2024-08-27T12:04:03.662993

System definitions are typically renamed as a result of a change in hardware. When you rename a system definition, all other configuration information that references the system definition is automatically modified to include the updated system name. This includes journal definitions, transfer definitions, data group definitions, and associated data group entries.

Attention: Before you rename a system definition, ensure that MIMIX activity is ended, that remote journal links used by the MIMIX environment are ended, and that the Assure UI servers that run on or have instances which connect to the affected system are ended.

These instructions use MIMIX menus. See Accessing the MIMIX Main Menu for how to use them.

Do not attempt to start renaming multiple system definitons at the same time. If you have multiple system definitions to rename, these instructions identify when it is safe to begin renaming the next system definition.

Use these instructions to rename a single system definition. Variations in steps needed for a management system or a network system are identified. Do the following:

If you are using the Assure UI portal, you must end any Assure UI server that runs on the system whose system definition will be renamed, or any Assure UI server that connects to a product instance in which a system definition will be renamed. Use the appropriate command, as follows:
- If the Assure UI server runs on an IBM i platform, use the following command:
```
VSI001LIB/ENDVSISVR
```
- If the Assure UI server runs on a Windows platform, from the Windows Start menu, select:All Programs > Precisely Assure > Assure Unified Interface and click Stop Server.
From a management system, use the following command to perform a controlled end of the MIMIX installation:
```
ENDMMX
```
It may take some time for all processes to end.
From the MIMIX Intermediate Main Menu, select option 2 (Work with systems) and press Enter.

When all processes have ended you should see the value *INACTIVE in the System Manager, Journal Manager, Journal Inspection, and Collector Services columns.
From the Work with Systems display, select option 8 (Work with data groups) for the system whose definition you are renaming, and press Enter.
For each data group listed on the Work with Data Groups display, do the following to ensure that replication activity is quiesced and to record information you will need later for verifying the starting points in the journals.
1. Select option 8 (Display status) and press Enter.
2. Record the Last Read Receiver name and Sequence # for both database and object. You will need this information to verify the starting points in a later step.
  
  Note: We strongly recommend you also record the full three-part name of the data group and identify which system will be renamed. This will be useful when verifying that each data group has the correct journal starting points after the system definition has been renamed. This will be particularly useful if you will be attempting to rename more than one system definition (when directed) or when renaming within a multi-node environment.
3. Repeat Step 5 for each data group that includes the system definition to be renamed.
4. When you addressed all of the data groups, press F12 (Cancel) to return to the Work with Systems display.
To determine which transfer definitions need to be changed, do the following:
1. From the Work with Systems display, press F16 (System definitions).
2. From the Work With System Definitions display, locate the system to be renamed and select option 14 (Transfer defintion) for that system.
3. On the Work with Transfer Definitions display, check the following:
  - Each transfer definition in the list that has the system to be renamed identified in the System1 or System 2 columns must be changed using Step 7.
  - If there is a transfer definition with *ANY specified for the System 1 or System 2 columns, you will need to restart the system port jobs with the new host names when directed.
Perform this step for each transfer definition that includes the system to be renamed. To change a transfer definition, do the following:
1. Select option 2 (Change) and press Enter.
2. Press F10 to access additional parameters.
3. If the system to be renamed is System 1 and *SYS1 is shown for the System 1 host name or address prompt, specify the actual host name or IP address currently used for that system.
4. If the system to be renamed is System 2 and *SYS2 is shown for the System 2 host name or address prompt, specify the actual host name or IP address currently used for that system.
5. Press Enter.
  
  Note: Many installations will have an autostart entry for the STRSVR command. Autostart entries must be reviewed for possible updates of a new system name or IP address. For more information, see Identifying the current autostart job entry information and Changing an autostart job entry and its related job description.
From the system that will be renamed, do the following for each transfer defintion that was changed and for any transfer definition that specified *ANY for System 1 or System 2:
1. End the port job on the system, specifying the old value from the transfer defintion in the command:
```
              ENDSVR HOST(
              host-name-or-address
              ) PORT(
              port-number
              )
            
```
2. Re-start the port job on the system, specifying the new value from the transfer definition in the command:
```
STRSVR HOST(host-name-or-address) PORT(port-number)
```
  c.For every transfer derfinition that you changed in Step 7, verify that communication links start by using the command:
```
VFYCMNLNK PROTOCOL(*TFRDFN) TFRDFN(name system1 system2)
```
  IMPORTANT!Perform only one of the next two steps. Perform only the step that is for the type of system definition you are renaming (Step 9 to rename a network system or Step 10 to rename a management system.) Never attempt to perform both steps.
If the system to be renamed is a network system, the total number of nodes in the MIMIX instance affects where you need to perform the action to rename the system definition.
- If the instance has only one management system and one network system, skip to Step 9d.
- If the instance has three or more nodes, The network system to be renamed must be renamed from a management system with which it is allowed to communicate. (In an environment with three or more nodes, each network system may be configured to limit the number of management systems with which it is allowed to communicate.) Continue with Step 9a.
1. Use the command WRKSYSDFN to access the Work with System Definitions display.
2. Select option 5 (Display) for the network system definition that will be renamed.
3. On the Display System Definition display, press Page Down to locate the Communicate with mgt systems field.
  - If the value is *ALL, you can rename the network system defintion from any one of the management systems.
  - If one or more management systems are identified, you can rename the network system from one of the identified management systems.
4. Go to the management system of a two-node environment, or to a management system that you identified in Step 9c, and enter the command:
```
WRKSYSDFN
```
5. From the Work with System Definitions display, select option 7 (Rename) for the network system definition to be renamed and press Enter.
6. On the Rename System Definitions (RNMSYSDFN) display, specify the new name of the network system at the To system definition prompt. Then press Enter.
7. Processing may take some time. Once the rename operation is complete, press F12.
8. Go to Step 11 and continue.
If the system to be renamed is a management system, go to that system and do the following:
1. Enter the command:
```
WRKSYSDFN
```
2. From the Work with System Definitions display, select option 7 (Rename) for the management system definition to be renamed and press Enter.
3. On the Rename System Definitions (RNMSYSDFN) display, specify the new name of the management system at the To system definition prompt. Then press Enter.
4. Processing may take some time. Once the rename operation is complete, press F12.
From the system where you performed the rename operation, enter the following command:
```
WRKSYS
```
The Work with Systems display appears. Type a 9 (Start) next to the system that is identified as the local system and press Enter.
The Start MIMIX Managers (STRMMXMGR) display appears. Do the following:
1. At the Manager prompt, specify *SYS.
2. Press Enter.
From the Work with Systems display (WRKSYS command), type 7 (System manager status) next to the system that is the local system and press Enter.
On the resulting Work with System Pairs display, all of the system manager processes associated with the selected system definition are shown. Each row identifies a pair of systems between which a system manager process exists and the direction (source to target) in which it transfers data. Do the following:
1. Check each applicable system manager process to ensure there is no backlog.
2. After the system pair status shows an unprocessed count of zero, continue with the following steps.
End MIMIX using the command:
```
ENDMMX
```
Wait for all processes to end before continuing.
From a command line on a management system, enter the following command to start the system managers:
```
STRMMXMGR SYSDFN(*ALL) MGR(*SYS)
```
Perform Step 18 through Step 21 from the system that was renamed.
From the system that was renamed, enter the following command:
```
WRKSYS
```
On the Work with Systems display, select option 8 (Work with data groups) for the system that was renamed and press Enter.

In the resulting list of data groups, one of the systems in each data group has been renamed. For the following step, you will need to know the original names of both systems in each data group and the new name of the renamed system. The information you recorded in Step 5 to verify the starting point shows the old system name. In multi-node environments, the verify step can become confusing if you are not diligent about keeping track of what name has changed.

For each data group listed, do the following:

From the Work with Data Groups display, select option 9 (Start DG) and press Enter.
The Start Data Group (STRDG) display appears. Press F10 to display additional parameters.
At the Show confirmation screen prompt, specify *YES.
If the data group being started is controlled by an application group, press PageDown. Then specify *YES for the Override if in data rsc. group prompt.
Press Enter.

The Confirmation display appears. Use the information you recorded in Step 5b to verify the information displayed has the correct starting point for the journal receivers.

Field on Confirmation display	Expected Value
Database journal receiver	Database receiver name recorded in Step 5b.
Database sequence number	Equal to 1 + the last read sequence number recorded for Database in Step 5b. Note: A value that is more than 1 larger than the previously recorded value is not correct.
Object journal receiver	Object receiver name recorded in Step 5b.
Object sequence number	Equal to 1 + the last read sequence number recorded for Object in Step 5b. Note: A value that is more than 1 larger than the previously recorded value is not correct.

Do one of the following:

To confirm the starting point and start the data group, press Enter.
If the receiver name or sequence number for either database or object does not match the expected value shown in the table above, press F12 (Cancel). Determine whether the information you are using to verify the starting point is for the data group you are attempting to start. Then try Step 20 again. For Step 20b, specify the recorded values for the Database large sequence number and Object large sequence number prompts, then press F10 and continue with the instructions.

Repeat Step 20 for each data group listed on the Work with Data Groups display.

Verify that all of the data groups on the Work with Data Groups display are active before continuing with the next step. Refer to the Assure MIMIX Operations book for more information.
If you are renaming only one system definition, continue with the next step. If you have more system definitions to be renamed, you can now safely return to Step 2 to begin renaming the next system definition.

Data groups not affected by the renamed system definition must be restarted using Step 23 through Step 26 from a management system.
From a management system, enter the command:
```
WRKSYS
```
From the Work with Systems display, select option 8 (Work with data groups) on the management system and press Enter.
From the Work with Data Groups display, for each data group that is not active, do the following:
1. Select option 9 (Start DG) for a data group (highlighted red) that is not active and press Enter.
2. The Start Data Group (STRDG) display appears. Press Enter. Additional parameters are displayed.
3. If the data group being started is controlled by an application group, press F10, then press PageDown. At the Override if in data rsc. group prompt, Then specify *YES.
4. Press Enter to start the data group.
The Work with data groups display reappears. Ensure all data groups are active. Press F5 to refresh data. Refer to the Assure MIMIX Operations book for more information.
Start the Assure UI server using the appropriate command:

For an Assure UI server on an IBM i platform, use the following command:
```
VSI001LIB/STRVSISVR
```

For an Assure UI server that runs on a Windows platform, from the Windows Start menu, select:All Programs > Precisely Assure > Assure Unified Interface > Start.