-.
PCLASS Statement
The PC LASS statement controls the measurement parameters used by the response time monitor. These measurement parameters include:
• The time boundaries between the response time counters
• The response time definition used for a session
• The response time objective used for a session
• Whether you can display the response time of the last transaction for their session.
If you do not code any of the statements discussed in this section, the following defaults are used for all sessions:
• The boundaries between the counters are at 1, 2, 5, and 10 seconds.
• Response time is defined as "time to first character."
• You cannot display your own response time.
• No response time objective is defined.
If the defaults are acceptable, you can omit this statement, but you must not code the INITMOD AAUINLDM PERFMEM = membername statement.
Two statements control the response time monitor. The first, PCLASS, is used to define performance classes; the second, MAPSESS, is used to map each session into one of the defined performance classes. A performance class determines the response time measurement parameters for the sessions mapped into that per-formance class_
If you code PC LASS and MAPSESS statements, create a member in DSIPARM and put them in that member. The name of this new member must match the name coded on the INITMOD AAUINLDM PERFMEM=membername statement.
You must code one PC LASS definition statement for each performance class you define. These PC LASS statements must be the first statements that appear in the member of DSIPARM named on the INITMOD AAUINLDM PERFMEM=membername definition statement.
W' ~··.>:·v:':.t::: ":~~'::::"'":'~}'0::: :/'
C#~fn.<: ;<f"f:;p~tid/ '
, ;,' ..•. ;\.:.:;\/; .. :;.\
cname
is the name of the performance class you define. This name is used on one or more MAPSESS statements as the value of cname in the PCLASS parameter. The name starts in column one of the statement and is required.
BOUNDS == (a,b,c,d)IC1 .2.5.10)
lists the upper time limit on each of the first four response time counters.
These times can be specified in minutes, seconds, and tenths of seconds (mm:ss.s), in seconds only (ss or ss.s), in tenths of seconds only (.s): or in minutes only (mm:). The maximum time you can specify is 1S00 seconds; any value of 60 seconds or more is converted to minutes for display.
The first counter is incremented when response time is less than or equal to a;
the second counter is incremented when response time is greater than a but less than or equal to b; and so on. The fifth response time counter is incre-mented when response time is greater than d.
If a BOUNDS parameter is specified with less than four boundaries coded, the maximum time allowed is used for the omitted boundaries. If the BOUNDS
parameter is omitted, the default is BOUNDS=(1,2.5.10).
RTDEF == FIRSTICDEBIKEYBDILAST
defines how response time is measured. It is measured as the time from the activation of a transaction, such as when the ENTER key is pressed, until a response is received. This parameter allows you to define "received" in one of the following ways.
CDEB
KEYBD LAST
means the first character of the reply from the host has arrived at the user's terminal. If RTDEF is omitted, FIRST is the default.
means an "SNA Change Direction" or an "SNA End Bracket" has been received at the user's terminal.
means the user's terminal keyboard is unlocked.
means the last character of the reply from the host has been received at the user's terminal.
Nole: If a response time monitor is monitoring an LU to LU session and the
PCLASS statement defining the session uses an RTDEF value not supported by the response time monitor, then the PCLASS statement is ignored and the session is mapped to another class. If no other classes are defined or match, the default performance class is used.
DSPL YLOC == YESINO
controls the display of response time.
YES allows the terminal user to display the response time of the last transaction at the terminal.
NO no response is displayed.
Nole: The default is set by the RTMDISP initialization statement. If
RTMDISP is not specified, the default for DSPL YLOC is NO.
OBJTIME == mm:ss.sIOO:OO.O
is the time threshold of the performance objective. It can be entered as minutes, seconds, and tenths of seconds (mm:ss.s), in seconds only (ss or ss.s), in tenths of seconds only (.s), or in minutes only (mm:). The maximum time is 1800 seconds; any value of 60 seconds or more is converted to minutes for display.
Nole: If OBJTIME is 0, no response time objective data is displayed for sessions mapped to this PCLASS statement. Refer to the MAPSESS statement to determine how sessions are mapped to a PCLASS statement.
If OBJTIME is not equal to one of the values of the BOUNDS parameter, it is rounded off to the nearest BOUNDS value.
PC LASS
Note: A response time objective includes both a time threshold and a per-centage. For example, for a particular terminal you might want response times to be less than 5 seconds (the threshold) for 80% (the percentage) of the activity.
OBJPCT = pppl~
is the percentage portion of the performance objective.
ppp is the percentage of transactions that should take less time than the time specified by OBJTIME.
~ is the default value.
Note: If OBJPCT is 0, no response time objective data is displayed for sessions mapped to this PC LASS statement. Refer to the MAPSESS statement to determine how sessions are mapped to a PCLASS statement.
Related Statements: INITMOO, MAPSESS
P~S Statement
The p~s statement defines the terminals that can log on directly to this NetView.
You can code either the P~S or the POSPOOL definition statement, -or code both. This statement is coded in the DSIDMN member of DSIPARM.
termina/name [, ... ]
is the name of a terminal.
Use the p~s statement as often as necessary to define all operator terminals.
Related Statements: POSPOOL