Conference azur::mcc

Use MCC_DUMP_NS.COM (it's on MCC_COMMON) to produce an MCC command 
procedure from your current namespace. Then switch to DNS - don't forget 
to create the required directories for backtranslation and objects - and 
execute the procedure that MCC_DUMP_NS produced (you should check/edit 
it first to your needs).

*Robert

Greetings,

Getting the NS dump is only one aspect to consider. The procedure described in
.1 provides a registration script which would duplicate what you have 
registered today. Note however that if you want to use different DIRECTORIES in
dns the newly created script will require many edits.

Secondly, all your map files will not be found because the names are encoded
using your current naming option. When you change, it won't find it. You can
do some renaming of the map files to generic names after you've converted and
then save (it will then create new files with specific names). Do a directory
for my name in this conference with the word MAP in the title and someone
explains the detail in a reply.

Thirdly, you will also lose your alarms. I believe there is an exe which
can dump all the alarms for your current mir into a script for recreation after
the change. Look for this file:

USAMTS>set def sys$system
USAMTS>dir *alarm*.exe

Directory SYS$COMMON:[SYSEXE]

MCC_ALARMS_EXTRACT_RULES.EXE;5

Total of 1 file.


Fourthly, you will lose all historical set-ups. If you used procedures to
create the record/export commands you are all set. Just rerun them after the
change (but make edits if you changed directory locations for entities in dns).
If you didn't use scripts to create the environment consider it a lesson in 
life :(, use them next time.

cheers,
brad...

    Guys (.1 & .2),
    
    thanks for the replies.  I have a somewhat *virgin* setup, so I won't
    need to do massive reconstruction.  Thanks for all the details...
    
    /Mic