Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!ames!ucbcad!ucbvax!TAMCHEM.BITNET!BMW6957 From: BMW6957@TAMCHEM.BITNET.UUCP Newsgroups: mod.computers.vax Subject: Changing network areas in RSX Message-ID: <8703241936.AA09678@ucbvax.Berkeley.EDU> Date: Tue, 24-Mar-87 11:20:00 EST Article-I.D.: ucbvax.8703241936.AA09678 Posted: Tue Mar 24 11:20:00 1987 Date-Received: Thu, 26-Mar-87 02:00:40 EST Sender: daemon@ucbvax.BERKELEY.EDU Distribution: world Organization: The ARPA Internet Lines: 100 Approved: info-vax@sri-kl.arpa Regarding the recent question about changing the area address under RSX. I can't seem to get through to the interested party, so I'll post my response to the net. Maybe the VMS types on INFO-VAX will appreciate how easy they have it after reading this. First, I'll assume that the operating system is RSX-11M, rather than RSX-11S or RSX-11M-PLUS (why? Because that's what I have :-) ). PLUS should be similar enough that this info will still be useful. Unless you intend to make more drastic changes than simply re-addressing the area, you will not need to do another SYSGEN nor NETGEN. You shouldn't need to do another SYSGEN in any event, but a NETGEN would be necessary if you changed from a non-routing to a routing node or vice-versa (for example). There are 3 utilities which are used to modify the network under RSX: CFE - Configuration File Editor, updates the premanent database VNP - Virtual Network Program, updates the system's boot image NCP - Network Control Program, updates the running (Volatile) network I will assume that you are using the default filenames of CETAB.MAC for the permanent database and RSX11M.SYS for the boot image. CETAB.MAC is in UFD [net,54], where 'net' is the network group (usually 5). RSX11M.SYS should be in the system UFD, [1,54]. First, you will need to find out a little about how the network is currently configured. Log onto the running system as a privileged user and set your CLI to MCR (if you're currently using DCL, the command SET TERM MCR should do it). Then type the command NCP SHOW EXEC (If NCP is not installed, first install it with INS [5,54]NCP -- assuming the network group is 5). If the address of the executor does NOT include the area number, then you are running a phase III node and you shouldn't have to change anything. A phase III node is always in the same area as the phase IV node to which it is attached. If the executor address includes the area number, then you will have to make some changes. Now, set your UFD to that of the boot image (SET /UIC=[1,54], if your system is standard) and RUN [5,54]VNP. When VNP prompts for a filename, give it the filename of the boot image -- RSX11M is the norm. At the VNP> prompt issue the command SHOW EXEC. If you get the message: VNP - Communications Executive Not Loaded Then your network has not been loaded into the boot image. Exit VNP with a control-Z. Next, if your network HAS been loaded into the boot image, it will probably be easier to remove it with VNP and then use VNP to reinstall the network after making the changes. There is a problem with this, since VNP can be used to make minor changes to the network so that the permanent database (CETAB.MAC) may not be an accurate reflection of the current network. You may want to use VNP as above to get a list of known circuits, known processes, known lines, known nodes, system, and executor parameters to compare them with those in the permanent database. I don't use VNP, but I believe the commands are (in VNP, of course) SHOW KNOWN CIRCUITS, SHOW KNOWN PROCESS, SHOW KNOWN LINES, SHOW KNOWN NODES, SHOW SYSTEM, and SHOW EXEC CHAR. You should be able to remove the network from the boot image with the VNP command CLEAR SYS (you may have to set various items to STATE OFF, first). Now, you should use CFE to update the permanent database (NEVER USE AN EDITOR OTHER THAN CFE ON CETAB.MAC! NEVER, NEVER, NEVER!). Changing the area of the executor WILL NOT "carry along" the other nodes. Each node address will need to be changed separately. If you have an extensive node database, it might be wise have NCP show the known nodes to a file so that it can be editted into the appropriate CFE commands (Use, at MCR level with the net up, the command NCP SHOW KNOWN NODES TO file). To use CFE, change your UFD to [5,54] (assuming the network group is 5). and then RUN CFE. When CFE prompts for a filename, give it the name of the permanent database (CETAB.MAC) or simply hit a return to take the default. At the CFE prompt, the node area can be changed with CFE> SET EXEC ADDRESS area.node HOST area.node For each remote node that needs to be changed, use CFE> CLEAR NODE xxx ALL CFE> SET NODE area.node NAME xxx If you have all these commands in a text file, then simply enter @filename at the CFE> prompt. Exit CFE with a control-Z and the database will be updated. To cancel the changes, exit CFE with the KILL command. Finally, if your network was NOT loaded into the boot image, you should be finished. The changes will take effect at the next boot (actually at the next network load, which is usually done at boot time). If your network WAS loaded into the boot image, use VNP to load the new network parameters (Assuming that you have already removed the old network, the VNP command SET SYSTEM should load the new one). BEWARE that VNP (like the system utility VMR) will corrupt your system's boot image if a crash occurs during processing. This may leave your system in an unbootable state, so ALWAYS be sure you have a current backup of the system disk before attempting any of this! Hope this helps. Brad Wilson Chemistry Department Texas A&M University BMW6957@TAMCHEM.BITNET (409) 845-2529