How to link and sync SOLVE or Netmaster regions
search cancel

How to link and sync SOLVE or Netmaster regions

book

Article ID: 123061

calendar_today

Updated On:

Products

NetMaster Network Automation NetMaster Network Management for SNA NetMaster Network Management for TCP/IP NetMaster File Transfer Management SOLVE:Operations Automation SOLVE:Access Session Management SOLVE:FTS SOLVE

Issue/Introduction

This document describes the steps to take to prevent data loss when preparing to link and sync regions as well as how to unlink regions as needed.
 

When working to create a multi-system environment with linked regions that are focal or subordinate, it can be confusing as to exactly what steps to take in which order.
The Multisystem shortcut /MADMIN option SD displays a warning message that states 'all data will be deleted and replaced by with data from remote region'.
This is not desirable.  

Environment

Netmaster Suite all releases

Resolution

This document is for creating two focal regions.

Step one: ensure that the MULTISYS parameter group is configured to allow for traffic to flow between regions. It is necessary for the subsequent steps.
 
 
Step two: Data preservation
When doing a link and sync, the RAMDB of the region on which you are doing the link and sync is overwritten by the RAMDB of the system to which you are linking.
 
In the Administration Guide under Administering a Multisystem Environment, it states

Multisystem Implementation Considerations


When you implement your multisystem environment, consider the following information:

  • Ensure that the link requirements are satisfied for the planned multisystem environment.
  • When you link two regions, the knowledge base in one region overwrites the knowledge base in the other region. Transmit all system images that the local region uses to the target focal point region before synchronization.
  • You can only link a region to a focal point region. The focal point region can be a stand-alone region or part of a multisystem environment.
  • You can only link a stand-alone region into a multisystem environment.


 
Here’s the link: https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-mainframe-software/intelligent-operations/ca-solve-operations-automation/11-9/administering/administering-a-multisystem-environment.html#AdministeringaMultisystemEnvironment-LinkandSynchronizeRegions 
 
 
So here’s an example of what this means:
 
SYSTEM A                                  SYSTEM B                    
 
1.Issue command
   To sync to system B                2.RAMDB content overwrites sytem A
                               ß------------------------
 
So before doing the link and sync, you need to ensure that the RAMDB content from SYSTEM A has been copied to SYSTEM B.
 
To do so on SYSTEM A, go to /MADMIN - Multi-System Support Administration (or A.M from the main menu)
From this screen select option TI 
 
 SYSA -------- Automation Services : Multi-System Support Menu ---------/MADMIN
Select Option ===>                                                           
                                                                               
   TI - Transmit System Image                             TRANSYS           
   TS - Transmit Services                                 TRANSER           
   TC - Transmit Common Components                        TRANCC            
   TR - Transmit Ruleset                                  TRANRUL           
   LR - List Linked Regions                               LISTREG           
   SD - Link Region and Synchronize Database              -                  
   MM - Link Region in Migration Mode                     -                 
   U  - Unlink Region SLVSYSA                              -                 
   L  - View Task Log                                     -                 
   X  - Exit                                                                 
 
Fill out the screen with the Region you intend to link to (the remote region), your desired local system image that you want to transmit to the other system and other details as requested.
You are MERGING the system images; you do not want to overwrite or replace anything on SYSB, just add the information from SYSA.
The last section is populated with the available transmission methods as defined in your local MULTISYS parameter group.
The stack definition is pointing to the remote TCP/IP stack but is populated ONLY if TCP/IP  is a valid transmission option.
 
If anything is unclear, PF1 provides help screens with additional explanation.
 
SYSA------- Automation Services : Remote System Identification --------------
Command ===>                                                Function=TRANSMIT
               
Identify the Remote Region:                                                   
   Primary Name ........... SLVSYSB  (Identifies the target region)          
                                                                              
Specify the System Image to be transmitted:                                   
   System Name ...........+ SYSA                                              
   Version ...............+ 0002                                             
   Transmission Mode ...... MERGE    (REPLACE, OVERLAY or MERGE)              
                                                                              
Specify the Communication Access Methods to be used by this system: [defined in MULTISYS parameter group]          
   Use VTAM? .............. YES                                              
   Use EPS? ............... YES                                              
   TCP/IP Host Name/Addr ..
      Port Number .........                                           
 
 
Step three: Link and Sync
After transmitting the System Image, you can issue the SD option (Link Region and Synchronize Database)from the same /MADMIN menu.
What it will do during synchronization is to copy your SYSA and SYSB RAMDB content to SYSA.
 
Please remember that it is always the region where you are issuing the SD command where the RAMDB is being overwritten, so it must always be copied over to the region to which you are doing the link and sync in order to prevent loss of data.
 
 

NOTE:   The links persist across restarts. 

 

You will receive an alert on SYSA when SYSB goes down which will clear when it comes back up, and vice versa.





Step four (as needed) : Unlinking regions

Unlinking a region is done from the same menu as the RAMDB transmit and link and sync.

 
Go to /MADMIN - Multi-System Support Administration (or A.M from the main menu)
This time select option U 

SLVSYSA-------- Automation Services : Multi-System Support Menu ---------/MADMIN


Select Option ===>                                                           
                                                                               
   TI - Transmit System Image                             TRANSYS           
   TS - Transmit Services                                 TRANSER           
   TC - Transmit Common Components                        TRANCC            
   TR - Transmit Ruleset                                  TRANRUL           
   LR - List Linked Regions                               LISTREG           
   SD - Link Region and Synchronize Database              -                  
   MM - Link Region in Migration Mode                     -                 
   U  - Unlink Region SLVSYSA                              -                 
   L  - View Task Log                                     -                 

   X  - Exit     
 
 
You will get a warning screen :

WARNING: The unlinking of <RegionName> will result in its

         ISOLATION from all other regions.

 
Once unlinked you will not be able to monitor or control
another region's resources from this region and you will
not be able to monitor or control this region's resources
from any other region.
 
To reconnect this region to another Automation Services region
after unlinking you will need to once again perform
database synchronization.



Hit PF6 to complete the unlink or PF12 to cancel out of the screen.

This step is needed in the following situations:
- before permanently removing an LPAR from the system
- before upgrading to a new release
- may occasionally be needed before upgrading maintenance

Additional Information

Powered by Wolken Software