Microsoft KB Archive/222087

= How to combine multiple SNA subdomains into one subdomain by using Snacfg in Host Integration Server =

Article ID: 222087

Article Last Modified on 12/4/2007

-

APPLIES TO


 * Microsoft Host Integration Server 2006
 * Microsoft Host Integration Server 2004 Standard Edition
 * Microsoft Host Integration Server 2000 Standard Edition

-



This article was previously published under Q222087



SUMMARY
In some cases, it may be helpful to combine multiple SNA subdomains into one subdomain. Although the recommended method for doing this is to demote one primary Host Integration Server server to a backup, have it join the desired subdomain, and then re-create its previous configuration (such as connections, users, LUs, and so on), you can combine the Com.cfg files from the two primary servers so that the new backup server's configuration is retained. You can combine Com.cfg files by using Snacfg.exe, the Host Integration Server command line utility.



MORE INFORMATION
When combining the Com.cfg files from multiple SNA subdomains, there cannot be duplicate names of any of the following items:
 * Host Integration Server server names
 * Connection names
 * LU names
 * Shared folder share names
 * Print session names
 * Pool names
 * User names
 * Workstation names
 * Host security domain names

NOTE: If the Everyone group is configured under the Configured Users folder in SNA Manager, remove that group and re-add it in SNA Manager after the Com.cfg files have been combined.

In the following scenario, server A is the primary Host Integration Server server in subdomain A. server B is the primary Host Integration Server server in subdomain B, and it will be joining subdomain A as a backup server.  On servers A and B, export each Com.cfg file to a text file by using the following command:

snacfg #[ ] /print >filename.txt

 Save the text files, and name them so that you can tell which Host Integration Server server each corresponds to (for example, ServerA.txt and ServerB.txt). Open ServerB.txt in Notepad. On the Edit menu, click Select All, and then click Copy. In another Notepad window, open ServerA.txt. Move the pointer to the bottom of ServerA.txt, leave one blank line, and paste the text that was copied from ServerB.txt. On the File menu, click Save As, and then name the combined text file (for example, Combined.txt). Copy the blank Com.cfg file from the Host Integration Serverinstallation media onto the hard disk drive. The file is located in the I386\System\Config directory on the CD. After you copy the blank Com.cfg, go into the properties of the file and clear the Read Only check box.</li> Compile the text file that contains the configurations of both Host Integration Server servers back into the blank Com.cfg file that you copied from the Host Integration Server installation media. To do this, run the following command at a command prompt:

snacfg #[ ] @combined.txt /v

Note The, in the previous step, is the path of the blank Com.cfg. The /v option represents "verbose," and it is optional. If there are any errors in compiling the text file into the blank Com.cfg, /v will determine the line where the error is in the text file.</li> The new Com.cfg now contains the configurations of both servers. The file may be viewed offline in SNA Manager. Verify that the configuration information looks correct. There are several items that you should check at this point: <ul> If there are APPC print sessions configured, go into the properties of each of these print sessions, and reenter the AS/400 User ID and Password on the Security tab.</li> If there are 3270 print sessions configured to use PDT files, go into the properties of each print session, select the Overrides tab, and then click the PDT File button to browse and locate the PDT file. Select the PDT file, and then click OK.</li> If Host Security is configured, you may have to re-assign connections to the Host Security Domains. Also, you may have to re-add the user information in Host Account Manager.</li> If you removed the Everyone group from Configured Users, re-add it. For each other useror group, run the following command atthe command prompt:

snacfg #[ ] user /validate

Note If this command is not run for each user, the users may receive a "User is not configured" error message when they try to connect sessions to the Host Integration Server server, even though the users appear in SNA Manager and have LUs assigned to them.</li></ul> </li> After you have verified that the new Com.cfg is ready to use: <ol style="list-style-type: lower-alpha;"> Stop the SnaBase service on server A and server B.</li> Make backup copies of the existing Com.cfg files on each server, in case the files must be restored for any reason.</li> Copy the new Com.cfg to the Sna\System\Config directory on server A.</li></ol> </li> Delete the Snaexp.snav file from the Sna\System directory on server A and server B.

This file will be recreated when SNA Manager is restarted.

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

175110 How to change the subdomain name in SNA Server

</li> HIS server A (the primary) is ready to operate with the new Com.cfg at this point: <ol style="list-style-type: lower-alpha;"> On server B, atthe command prompt, run svconfig.exe. This opens the Server Configuration dialog box.</li> Demote server B to a backup server, enter the name of the primary server (server A), and enter the name of the subdomain that this server will be joining (subdomain A).</li></ol> </li> Restart server B. It should now be functional as a backup server in subdomain A.</li></ol>

Additional query words: HIS 2000 HIS2004 HIS2006

Keywords: kbhowto KB222087

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.