How to copy Rulesets from SOLVE:Operations Automation 11.9 to Netmaster Automation 12.1 or higher
search cancel

How to copy Rulesets from SOLVE:Operations Automation 11.9 to Netmaster Automation 12.1 or higher

book

Article ID: 69663

calendar_today

Updated On:

Products

SOLVE:Operations Automation NetMaster Network Management for TCP/IP NetMaster Network Automation

Issue/Introduction

How can I copy Rulesets from SOLVE:Operations Automation 11.9 to Netmaster Automation 12.1 or higher?

Environment

Release: SLOPEM00200-11.9-SOLVE:Operations-Automation
Component:

Resolution

The EXPORT facility can only be used to export Rulesets from one region to another within the same release.
To transfer Rulesets between releases, the /RAMUTIL facility can be used to migrate the desired rulesets from one product to another between differing releases.

Going from SOLVE:Operations 11.9 to Netmaster Automation 12.1 or 12.2 follow these steps:

1. shut down SOLVE:Operations

2. on Netmaster 12.1 or 12.2 go to /RAMUTIL.M

3. put in the DSN of the SOLVE:Operations RAMDB and specify YES in the Selective Migration field 

4. Select ‘Eventview Rulesets’.

5. F6 to action

6. Select the desired ruleset(s) - only the primary one is needed but if you add the sub rulesets it won't hurt - any duplicates will simply be noted as such.
7. F6 to action

8. You will see the number of components and what was copied or not.
    Example: 
RMMU1304 **** COPY COMPLETED - REFER TO LOG FOR DETAILS ****                  

     

        Components to be processed :      1                                      

 

        Components processed so far:      1                                      

 

                                                                           R=Review

        Components                           Total   Copied   Not Copied          

 

        Eventview Ruleset -> LTOVRRLE            6        6        0              

 

9. Use PF5 to take you to the log - it will show exactly what has been copied.

10. Go to /EADMIN and verify that what you have on SOLVE:Operations is now contained in Netmaster.
      If anything is missing, it will be ALL message rules or timer rules, or the entire ruleset, so will be pretty obvious.
      If it turns out that anything is missing, you can re-do the /RAMUTIL process - it will not replace duplicate records so will not break anything.

Additional Information

Example of messages you can expect to see in the log after step 9 when everything has been migrated from SOLVE:Operations region SLVOPS to a Netmaster region by user USER001

16.07.27 RMDBMS00 OBJID="LTOVRRLEZEVW9ALTSUB1" CREATED ON TUE 26-JUL-2016 AT 16.07.27 BY USER001 FROM SLV1 (REMOTE CREATE WAS DONE ON TUE 26-JUL-2016 AT 13.37.44)
16.07.27 RMDBMS00 OBJID="LTOVRRLEZEVW9ALTSUB2" CREATED ON TUE 26-JUL-2016 AT 16.07.27 BY User001 FROM SLV1 (REMOTE CREATE WAS DONE ON TUE 26-JUL-2016 AT 13.38.01)
16.07.27 RMDBMS00 OBJID="LTOVRRLEZEVW9ALTSUB3" CREATED ON TUE 26-JUL-2016 AT 16.07.27 BY USER001 FROM SLV1 (REMOTE CREATE WAS DONE ON TUE 26-JUL-2016 AT 13.38.14)
16.07.27 RMDBMS00 OBJID="LTOVRRLEZEVW93LTOVRRLE" CREATED ON TUE 26-JUL-2016 AT 16.07.27 BY USER001 FROM SLV1 (REMOTE CREATE WAS DON E ON TUE 26-JUL-2016 AT 12.50.30)
16.07.27 RMDBMS00 OBJID="LTOVRRLEZEVW94SLV17361704986717" CREATED ON TUE 26-JUL-2016 AT 16.07.27 BY USER001
16.07.27 RMDBMS00 OBJID="LTOVRRLEZEVW98STARTTIMER" CREATED ON TUE 26-JUL-2016 AT 16.07.27 BY USER001
16.07.27 RMDBMS00 OBJID="LTSUB1  ZEVW93LTSUB1" CREATED ON TUE 26-JUL-2016 AT 16.07.27 BY USER001 FROM SLV1 (REMOTE CREATE WAS DONE ON TUE 26-JUL-2016 AT 12.51.10)
16.07.27 RMDBMS00 OBJID="LTSUB1  ZEVW94SLV17361704995406" CREATED ON TUE 26-JUL-2016 AT 16.07.27 BY USER001
16.07.27 RMDBMS00 OBJID="LTSUB1  ZEVW98LTSUB1TM" CREATED ON TUE 26-JUL-2016 AT 16.07.27 BY USER001 FROM SLV1 (REMOTE CREATE WAS DON E ON TUE 26-JUL-2016 AT 13.32.41)
16.07.27 RMDBMS00 OBJID="LTSUB2  ZEVW93LTSUB2" CREATED ON TUE 26-JUL-2016 AT 16.07.27 BY USER001 FROM SLV1 (REMOTE CREATE WAS DONE ON TUE 26-JUL-2016 AT 12.51.21)
16.07.27 RMDBMS00 OBJID="LTSUB2  ZEVW94SLV17361705003832" CREATED ON TUE 26-JUL-2016 AT 16.07.27 BY USER001
16.07.27 RMDBMS00 OBJID="LTSUB2  ZEVW98LTSUB2TM" CREATED ON TUE 26-JUL-2016 AT 16.07.27 BY USER001 FROM SLV1 (REMOTE CREATE WAS DONE ON TUE 26-JUL-2016 AT 13.34.48)
16.07.27 RMDBMS00 OBJID="LTSUB3  ZEVW93LTSUB3" CREATED ON TUE 26-JUL-2016 AT 16.07.27 BY USER001 FROM SLV1 (REMOTE CREATE WAS DONE ON TUE 26-JUL-2016 AT 12.51.30)
16.07.27 RMDBMS00 OBJID="LTSUB3  ZEVW94SLV17361705010293" CREATED ON TUE 26-JUL-2016 AT 16.07.27 BY USER001
16.07.27 RMDBMS00 OBJID="LTSUB3  ZEVW98LTSUB3TM" CREATED ON TUE 26-JUL-2016 AT 16.07.27 BY USER001 FROM SLV1 (REMOTE CREATE WAS DON E ON TUE 26-JUL-2016 AT 13.35.51)


Example of messages you can expect to see if any duplicate records are encountered

16.50.44 RMMUAD05 Duplicate record - SN: LTOVRRLE V: ZEVW CL: 9A NM: LTSUB1
16.50.44 RMMUAD05 Duplicate record - SN: LTOVRRLE V: ZEVW CL: 9A NM: LTSUB2
16.50.44 RMMUAD05 Duplicate record - SN: LTOVRRLE V: ZEVW CL: 9A NM: LTSUB3
16.50.44 RMMUAD05 Duplicate record - SN: LTOVRRLE V: ZEVW CL: 93 NM: LTOVRRLE
16.50.44 RMMUAD05 Duplicate record - SN: LTOVRRLE V: ZEVW CL: 94 NM: SLV17361704986717
16.50.44 RMMUAD05 Duplicate record - SN: LTOVRRLE V: ZEVW CL: 98 NM: STARTTIMER