saving/downloading controlers to Johnson NCM workstations
I added a DX controler to an NCM.I saved the file on the PC workstation,that holds all of the archive files.
What is the proper procedure for the following?
I want to save the file on a memory stick.
load that file on the other two Workstation PC's.
As of now the other two PC's see the controler in a seperate system file,at
the bottom of the directory tree,and not in the actual 9th Floor folder.
If I recall I have to use DOS to decompile the DDL. File to save it.and then recompile it to download it to the PC.
You should put some effort forth.
It is clearly detailed in the OWS User's Manual
To put a file on a memory stick, I use the drag drop method. You could use copy paste method to. The same will work go from memory stick.
If you perform modificatetions to the map all of the screens would look the same.
Actually it is in the DDL programming Manual
The dos Coommand to compile is
To un compile
Really? You must be a metasys ddl'ing genius now.
Originally Posted by cleancondenser
You're almost completely clueless on this matter.
Yes, your original nonsensical ramble could be done with ddl, but it would be much safer for someone that is trying to become a novice, to use the OWS method. But, by all means, proceed at will.
Here are some guesses on your future thread titles.
-What's the syntax for the unddl command?
-Hey, where did my unddl file go?
-I found my unddl file, now what?
-My ddl file won't compile, what does this error mean.
-My ddl compiled, but everything still looks the same, what up with that?
-What happened? All of my passwords and schedules are missing.
Ouch, that's gonna leave a mark !
Originally Posted by NINAX
cleancondenser, the method in the OWS Users manual is much safer. Doing it in "DDL" can cause some huge problems if you even make a very small mistake.
Simply adding a new system to each additional OWS would have only taken a couple of minutes and had very small risk involved in regrads to the N1 network. Be very careful using DDL on a system.
Last edited by Cagey57; 03-26-2010 at 03:55 PM.
If sense were so common everyone would have it !
All opinions expressed are my own. Any advice provided is based on personal experience, generally accepted fact or publicly available information. As such, it is worth exactly what you paid for it, not a penny more not a penny less !!
Not thru !! When you unddl then there is no sourcefile.... It gets created
Originally Posted by cleancondenser
If all you want to do is to move the DX system to a your 9th Floor Group on the other 2 computers. Then simply go to each computer highlite the DX system and under Setup, select "Modify Group Assignment"
As stated before: the OWS method is the safest way to accomplish these task for a novice Metasys operator.
You can go the ddl route, but be careful.... you won't be the first one to wipe out all passwords, calender entries, report/access groups, ip numbers and workstation settings with one mouseclick
I somewhat know what I am doing with PMI, and going the ddl path is still like handling wet dynamite to me. If you screw up...oh boy ..you could get screwed faster than a altar boy at the vatican.
Were you able to copy your files on the other drive with out any issues OK?
If you decide to pursue the DDL route, first read the first the Data Definition Language. Although I agree with freddy-b that it's really dangerous in experienced hands. Here's the steps
1) Upload the Global database at the archive OWS.
2) UNDDL the Global database at the archive OWS. If you have errors than you will have to correct them first.
3) Rename the Global file extension from GLOBAL.UND to GLOBAL.DDL
4) Copy it to a diskette.
5) Recompile the Global.DDL file
6) Download the Global database at the archive OWS.
7) Shut down Metasys and disconnect each of the non-archive OWSs from the LAN.
8) Compile the archives Global .DDL file on each non-archive OWS.
9) Start Metasys and download the Global database on each non-archive OWS.
10) Shut down Metasys, and delete the online Globrev.dbf (e.g., C:\Project\Contract\Netname\Globrev.dbf) file on each non-archive OWS.
11) Restart Metasys on each non-archive OWS.
12) Reconnect each non-archive OWS to the LAN.
Law Of The Thermostat: He who has the thermostat wins!!!!!
Assuming it was worth it (more than one System that needed a PC Group change), if you really understand PMI and it's data structure, one could accomplish the same in 5 steps. And you'd never ddl anything, disconnect PCs, or reboot software.
Originally Posted by simux
Thank you Simux
A former Johnson Tech demonstrated it your way.
He did tell me of his stories of where he lost passwords and other data.
This is not something I will be doing every day,but it is good to know.
Appreciate all the help.