Article ID: 246685
Article Last Modified on 12/4/2007
APPLIES TO
- Microsoft SNA Server 4.0 Service Pack 4
- Microsoft Host Integration Server 2000 Standard Edition
- Microsoft Host Integration Server 2000 Service Pack 1
- Microsoft Host Integration Server 2000 Standard Edition
- Microsoft Host Integration Server 2004 Standard Edition
- Microsoft Host Integration Server 2006
This article was previously published under Q246685
INTRODUCTION
This article lists the maximum number of supported objects for Microsoft SNA Server and for Microsoft Host Integration Server.
MORE INFORMATION
You must consider the following:
- Com.cfg, the configuration file for SNA Server 4.0 and earlier versions, has a limit of 65,536 objects, or records. You can view the type and number of objects by using the Snacfg.exe file. For example, you can use the following command: '
snacfg #com.cfg /count
- The configuration file for Host Integration Server and later versions does not have an object limit.
- A "node" is one instance of the SNA Server service. SNA Server and Host Integration Server support up to four nodes per server.
- SNA Server 4.0 and Host Integration Server 2000 support a maximum of 30,000 LUs per server. Host Integration Server 2004 supports 60,000 dependent LUs. However, we have only tested as many as 30,000 dependent LUs in a Host Integration Server 2004 installation.
Note SNA Server 4.0 and Host Integration Server 2000 and later versions do not prevent you from specifying more than the supported limit of LUs.
If you exceed an object in SNA Server, you may receive the following error message:
For example, if an administrator assigns more than 4,000 LUs to a particular user or group, this error occurs. By design, SNA Server has set limits on the number of objects that can be added to SNA Manager. These limits depend on the type of object. Host Integration Server 2000 and later versions do not have these limits.
| Area | Object | Maximum |
|---|---|---|
| Server | Servers per SNA subdomain | 15 |
| Server | Nodes per server | 4 |
| Server | Nodes per SNA subdomain | 60 |
| Server | Connections per node | 250 |
| Server | Active client sponsor connections per server | 8000 |
| Link Service | Link services per server | 64 |
| Link Service | Links (adapters) per server | 1,024 |
| Link Service | Connections per adapter | 250 |
| LUs | LUs per node | 15,000 |
| LUs | LUs per user/group | 4,000 |
| LUs | Dependent LUs per connection | 255 |
| LUs | LUs per passthrough connection | 255 |
| Pools | LUs assigned per pool | 30,000 |
| Pools | 3270 pools | 10,000 |
| Pools | LUA pools | 10,000 |
| Pools | Downstream LU pools | 10,000 |
| Users | Users per pool | 10,000 |
| Users | Users per LU | 10,000 |
| APPC | Modes per LU | 64 |
| APPC | Partners per LU | 250 |
| APPC | LUs per mode | 10,000 |
| APPC | APPC LUs per node | 3,000 |
| APPC | APPC Remote LUs per connection | 10,000 |
| APPC | Maximum negotiated sessions per Local APPC LU | 15,000 |
| CPIC | CPIC symbolic destination names | 454 |
REFERENCES
For more information, click the following article numbers to view the articles in the Microsoft Knowledge Base:
228924 "SNA OLE the number of objects has reached their limit" error message
225261 Error line number returned by Snacfg.exe may be incorrect, other enhancements
107192 Multiple connections to the same host over 802.2
317805 Sponsor connection changes in Host Integration Server
Keywords: kbtshoot kbprb KB246685
