RISC SYSTEM/6000 TO BE USED IN A SNA SDLC
ITEM: RTA000029411
QUESTION:
MY CUSTOMER IS LOOKING FOR A RISC SYSTEM/6000 MODEL 980 TO FILL HIS
NETWORKING REQUIREMENT. THE CUSTOMER WANTS TO DOWN SIZE FROM HIS
CURRENT IBM 4381-92E PROCESSOR WITH A 3745 AND A MVS SESSION MANAGER
TO A MODEL 980. THE NETWORK CONSISTS OF VARIOUS LEASED LINES, ABOUT 30
THAT VARY IN SPEED FROM 56KB TO 9600 BPS. EACH USER (SALES REP) WOULD
HAVE MULTIPLE SESSIONS FROM 10 TO 15 FOR A TOTAL OF ABOUT 800.
WE WILL BE USING MPCA ADAPTERS, SNA SERVICES AND HCON TO MEET THE
REQUIREMENTS.
-- DON'T FORGET THAT THE SYSTEM WILL BE RUNNING THE REGULAR BATCH AND
ONLINE TRANSACTIONS.
---------JUST SOME OF THE QUESTIONS I HAVE------------------------------
1. CAN A 980 HANDLE THIS TYPE OF NETWORKING REQUIREMENT?
2. COULD YOU SUGGEST ANOTHER CONNECTIVITY SOLUTION OTHER THAN
MPCA CARDS? WOULD A 6611 FIT INTO THIS TYPE OF NETWORK?
3. HOW MANY MPCA CARDS CAN THE 980 HANDLE, 56KB AND 9600.
4. DO YOU KNOW OF A WAY TO HELP US DESIGN A NETWORK OF THIS TYPE?
5. WHAT ABOUT A SESSION MANAGER, DOES ONE EXIST FOR RISC SYSTEM
6000'S IBM OR OEM?
6. ANYTHING YOU CAN SUGGEST TO HELP.
---------- ---------- ---------- --------- ---------- ----------
A: I will enumerate my responses to correspond to your questions.
1. The RS/6000 model 980 will support up to 7 Multiprotocol (mpqp)
adapters. Each mpqp adapter supports up to 4 SDLC links transmitting
with speeds up to 64 Kbps. So the hardware itself will support the
environment you are describing. We are not able to respond to
performance questions through HONE. However, the following are some
general rules of thumb you may find useful. Each port on the mpqp
adapter represents 1 PU to the host. Each PU (mpqp port) can
support a maximum of 254 LUs. Each user session to the host will
use an LU. I am not sure if the 800 sessions will be enabled
concurrently, but if not, LU pooling would allow you to conserve
resources by reducing the LU requirements from 800. Each LU will
represent 2 sessions to the host (1600 minimum sessions). SNA
supports a maximum of 5000 sessions. From prior experience, we
generally see a PU requiring an additional 7 MB memory. Also,
each HCON session requires a e789x process to communicate with the
LU session. Each e789x process requires 400K of paging space.
2. SNA Services is also supported over Token Ring, Ethernet, and
X.25 adapters. Considering the number of LUs you require, the
other adapters may present a different problem. Although the mpqp
may represent up to 4 PUs per adapter, the token ring and ethernet
adapters currently only support 1 PU per adapter. Since the 980
supports a maximum of 4 token ring or ethernet adapters, this
would bring you alittle closer to the maximum LUs allowed
(i.e. 254*4 with TR or ENET vs 254*4*7 with mpqp). Of course
the token ring and ethernet links would provide higher
throughput so that is also a consideration.
I do not see any problems that would be solved by the 6611 for
this configuration. I am not sure exactly what you had in mind
for this question.
3. See answer to question 1.
4. As far as I know, there are no tools for designing this type
of network.
5. There is not a separate session manager on the RS/6000.
SNA Services includes a session manager for LU6.2 (this is part
of the architecture). SNA Services allows dependent LUs (such
as LU2s used for emulation sessions) to establish SSCP-LU and LU-LU
sessions with the host (this is also according to architecture).
For dependent LUs session management is done by VTAM (the SSCP).
HCON provides for LU (session) pooling so that when a session is
started, the first available one is used (this allows you to
require only the number of LUs for concurrent sessions).
---------- ---------- ---------- --------- ---------- ----------
This item was created from library item Q620603 CBKVL
Additional search words:
CARDS CBKVL FEB93 HARDWARE IX MPCA NETWORK NETWORKING OZNEW OZNOTPID
RISC RISCOHW RISCSYSTEM SDLC SESSIONS SNA S6000 TP 800
WWQA: ITEM: RTA000029411 ITEM: RTA000029411
Dated: 04/1996 Category: RISCOC
This HTML file was generated 99/06/24~12:43:11
Comments or suggestions?
Contact us