There is no such thing as a 70 session gateway, it is a 70 AppleTalk client
limited gateway. It does not matter how many sessions are configured on
the SNA*ps 2.0 Gateway. The only limit is 70 attached Macintosh computers
over AppleTalk.
You can run a single Token Ring card with both 3270 and 5250 (APPC)
services at the same time. This is how our demonstration gateways and our
test gateways are configured. The session limit will be determined by the
RAM size on the Token Ring card. In this environment we strongly suggest
buying the 2MB upgrade memory chips.
This is done by configuring two separate SNA*ps Token Ring Lines and
Partners. The first pair of lines and partners would be for 3270 services.
It would be a Host type PU 5 connection for a PU2 gateway. The customer
then does an NCP and VTAM config for the PU 2.0 (3270, 3287) devices and
the SNA*ps gateway is matched with 3270 resources.
The second pair of lines and partners would be a PU 2.1 Peer-to-peer device
which supports APPC sessions to the AS/400. You would configure a
Controller, device, and mode description to support this attachment.
Obviously, there are two Token Ring addresses as destination addresses (one
for the source of the 3270 datastreams and one for the source of the AS/400
datastreams. The Macintosh Token Ring card will be given one Token Ring
address and it will be used as the destination for both the 3270 and AS/400
datastreams. When this is all said and done, there is one gateway with one
AppleTalk name projected on the LAN for both types of services. This can
be done all on one card.
As an example: you could have 50 3270 sessions and 55 APPC sessions to
support 5250 in the SNA*ps Config. Lets say a Macintosh AppleTalk client
attaches to the SNA*ps gateway and opens three 3270 sessions, two 5250
sessions, one SNA*ps Print 3287 session, and one DAL AS/400 session. This
SINGLE AppleTalk client has used 3 + 2 + 1 + 1 = 7 sessions.