| Title: | Remote System Manager (RSM) Conference |
| Notice: | See 1184.1 for ptr to doc's, 1108 for product mgr info |
| Moderator: | ZENDIA::TBOYLE |
| Created: | Fri Apr 25 1986 |
| Last Modified: | Thu Jun 05 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 1687 |
| Total number of notes: | 6370 |
One of our biggest customer uses RSM V3.0 for distributing applications to some hundred clients. Lately he changed the name of the RSM server. He first changed the DECnet node name and then the RSM server name (by MANAGE REMOVE SERVER old-name and then RSM$CONFIGURE with the new-name). This went all well. But now he has two problems. 1. he get's 4 error messages for a SHOW SERVER MANAGE> show server .*/fu .PRDMG1 DECnet node: PRDMG1 %RSM-E-INVALID_CHARACT, object name contains an invalid character or nickname %RSM-E-OBJECT_INVALID, specified object name is not valid %RSM-E-INVALID_CHARACT, object name contains an invalid character or nickname %RSM-E-OBJECT_INVALID, specified object name is not valid %RSM-E-INVALID_CHARACT, object name contains an invalid character or nickname %RSM-E-OBJECT_INVALID, specified object name is not valid %RSM-E-INVALID_CHARACT, object name contains an invalid character or nickname %RSM-E-OBJECT_INVALID, specified object name is not valid MANAGE> 2. SDS installation of an application to the client fails. DISTRIBUTE> inst appl OMC_SYSMAN_V0320_AXP .zamxga/notif %RSM-I-SERVERNAME server name translation error %RSM-F-ERRINSTALL error in processing install command DISTRIBUTE> The second problem is caused due to the fact that the application still got the old server name in the "LIBRARY SERVER" field. Once again a command "DISTRIBUTE MODIF APPLICATION XY /LIBRARY" would be needed !!!! We can get around this by giving the server back the old RSM name (DECnet name remians the new). But problem 1.) remains. The SHOW SERVER still gives the error messages. Questions: for Problem 1.) Which RSM database went corrupt and how do we fix it ? for Problem 2.) How can we rename the RSM servername so that the SDS database also gets the new name in the "LIBRARY SERVER" fields ? There used to be a "RENAME" utility for V2.x. Is this utility also valid for V3.x and where do I find this tool on the Easynet ? Any help appreciated. Thanks, Peter
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1686.1 | Compress_rsm_db ... | UTRTSC::VELZEN | Pim van Velzen, CS/SSO Holland | Wed May 28 1997 16:41 | 83 |
Re: .0
> There used to be a "RENAME" utility for V2.x. Is this utility
> also valid for V3.x and where do I find this tool on the
> Easynet ?
I will append the description of the 'rename'-tool (the tool was later
renamed to compress_rsm_db. I doubt if it works on V3, as the format of
the/some datafiles has changed and DNS is not used anymore to store parts
of the information. Furthermore, the tool was meant to compress the data-
base and rename CLIENTs (and not the Server, as your customer wants).
I do have a copy of this tool available somewhere. Let me know, if you
would like to have it as well.
/\Pim.
COMPRESS_RSM_DB Utility
Abstract:
This utility allows a user to rename clients in the RSM database. It
is primarily needed when the DNS namespace is modified.
The utility also doubles as a database compression tool.
Details:
To use the utility, make sure that RSM is in a quiescent state (no
pending SDS requests in the queue, backup scanner process stopped).
Copy the following files into your current working directory. They are
contained in the RSM$BKP_DATA: and RSM$SDS_DATA: directories.
RSM$SDS_OS.DAT
RSM$SDS_LP.DAT
RSM$SDS_WS.DAT
RSM$BKP_HISTORY.DAT
RSM$BKP_SCHEDULE.DAT
If you would like to modify database names, add an additional file
called NAMES.DAT. The format of the file is <old_name> <whitespace>
<new_name>. Up to 200 names can be changed (both client and server
names are modified). The names must be FULL DNS names:
(e.g., .ENG.NAC.DSS.FOO), they must be entered in uppercase.
Invoke COMPRESS_RSM_DB.COM in your current working directory. The
executable COMPRESS_RSM_DB.EXE should also exist in your current
working directory.
If you would like to update the database files directly, execute the
command procedure from an account with write privileges to
RSM$SDS_DATA: and RSM$BKP_DATA:
Restrictions:
The utility does not update the DNS namespace. You must create any
new client and server entries by hand (MANAGE ADD CLIENT etc.). You
can do this before or after running the utility, but you won't be able
to access the converted data until the DNS database is updated.
Installation:
The kit contains the following files:
COMPRESS_RSM_DB(.COM,,.EXE,.TXT)
Support:
RSM Engineering does not officially support this code !
| |||||