As a guideline for installations new to TSO/E, assume that an
installation doing program development on 3270 terminals will have
two ready users for every ten users logged on. This average will vary,
depending on the type of terminal and on the type of TSO/E session
(data entry, problem solving, program development).
What is the required response time and expected transaction
rate for different categories of TSO/E transactions at different times,
such as peak hours?
What is the expected response time for short transactions?
How will this response time be measured?
Should response time be different for select groups of TSO/E
users?
How should semi-trivial and non-trivial transactions be treated?
How are they defined?
An installation can use RMF™ workload
reports or SMF data in type 34 and 35 records available to help define
trivial and non-trivial TSO/E work. Based on service definition coefficients
of CPU=10.0,IOC=5.0,MSO=3.0,SRB=10.0; the following approximations
can be made:
Short TSO/E commands use 200 service units or less.
Medium length commands use between 200 and 1000 service units.
Long TSO/E commands use 1000 service units or more.
What is the required service rate for TSO/E users?
If 2-second response time (as reported by RMF) is required for very short TSO/E commands
(100 service units), the required service rate for such a transaction
is 100/2 or 50 service units per second. Service rates for other types
of transactions should be computed also.