The process of running STATS in the ghost mode to collect statistics is started by choosing a user id for the ghost user. This user id can be an existing user id or a special user id that is created for this purpose. In either case, the user id must be authorized with the appropriate resources, access modes, and permissions to run STATS.
In particular. the user id must be authorized for access in the ghost mode. must have sufficient fi Ie space to save the STATS fi les. must have sufficient memory to run STATS.
and must have the PM PRIV to run STATS. The following figure is an example of how a special user id would be created to run STATS in the ghost mode.
I SUPER
CP-6 SUPER cee
---CMD-CREATE :STATS.STATISTICS FRON DEFAULT OPT-ACCESS B-YES. o-YES. G-YES. TP=NO OPT-HSET - DP,SYS
OPT.FACCOUNT
SUB-GR-15eee. NOLIST-? DEFAULT BACKUP. NO ACUP sua-OPT -MEMORY MAX 8-256. 0-256. G-256
OPT-MEMORY DEF 8-128. 0-128. G-128 OPT-PASSWORD - PASSWORD
OPT-PRIV
sue.PM B-YES. o-YES. G-YES. TP-NO sua. END
OPT.SETUP G - IXEQ STATS_XEQ OPT. END
aI)-ENO
Figure 6. Sample STATS User 10 Creation
124 Creating a Ghost STATS User
Module ~2
CE6e-ee
In the example:
o The user id is authorized to run in batch, online, or ghost modes. The ghost mode can be used to collect the statistics; the batch and online modes can be used to do data reductions on the statistics.
o A file management account is created on DP#SYS to hold the STATS files. DP#SYS is chosen as the home packset because that packset is always mounted when the system is booted. The STATS ghost requires that the home packset be mounted when initiated because an XEO fi Ie is used and because STATS wi II create statistics files.
o The user id is given enough default memory to run the STATS processor.
o The user id is given the PM privi lege so that the STATS processor can be run.
o The user id is given a setup command for the ghost mode. This setup command executes the STATS_XEO.:STATS file when the ghost is started.
Creating an XEQ Command File
The ghost STATS user is usually set up to execute an XEO file. The XEO fi Ie controls how the ghost STATS user collects the system statistics. In the previous user
authorization, the XEO fi Ie was specified in the SETUP option. The XEO fi Ie name was STATS_XEO.:STATS. If the SETUP option is used as shown, the STATS_XEO. :STATS must be created. The fol lowing figure is an example of what that XEO fi Ie could be I ike. The comments in the XEO fi Ie describe how it functions.
In this example:
o The STATS commands to collect the system and FEP statistics are embedded in the STATS_XEO. :STATS XEO file. These STATS commands are put in a temporary star file (*STATS_COMMANDS). They are later used via an XEO statement with the appropriate substitutions.
o The XEO file submits one or two batch jobs to perform data reduction after collecting the statistics: data reduction of the statistics can be an automated part of statistics collection.
IDEFAULT PERIOO1_STOP$-0800, PERIOO1_INT$-60 IDEFAULT PERIOO2_STOP$-1800, PERIOO2_INT$=30 IDEFAULT PERIOD3_STOP$=2359. PERlOO3_INT$=60 IDEFAULT WEEKEND_STOP$=2359. WEEKEND_INT$=120 I"
I" This is an XEO file that controls the execution of the I" STATS ghost that collects system statistics. The STATS I" data is logged into a file whose name is of the form I" STATSDATA_yymmdd where yymmdd is the date as given by I" the IBEX $DATE function. This fi Ie is created in the l' current file directory (fi Ie management account).
I
I The DEFAULT substitution variables PERIODn_STOP$ and I PERlOOn_INT$ specify the stop time and interval size I for a period of every weekday. The start time for I PERIOD1 is 0000. The start time for al I other periods I is the stop time of the previous period. The stop I time. specified using a 24-hour clock. must be specified I as four decimal digits (with leading zeroes as necessary).
I
Figure 7. STATS_XEO: Sample STATS XEO Fi Ie (cont. next page)
CE60-00 Creating an XEO Command File
Module 6-2
125
The DEFAULT substitution variables WEEKEND_STOP$ and weekend by adding the appropriate DEFAULT substitution variables, command variables, and the appropriate IBEX commands to this XEQ fi Ie.
I LET PERlOO1_STOP
=
PERIOD1_STOP$, PERlOO1_INT=
PERIOD1_INT$ILET PERlOO2_STOP
=
PERIOD2_STOP$, PERIOD2_INT = PERlOO2_INT$I LET PERlOO3_STOP
=
PER I OD3_STOP$, PERlOO3_INT = PERIOD3_INT$I LET WEEKEND_STOP - WEEKEND_STOP$, WEEKEND_INT - WEEKEND_INT$
IDEFAULT DELETE supply the appropriate values.
$FID_EXIST ( '.STATS_COMMANDS' ) THEN DELETE .STATS_COMMANDS BUILD .STATS_COMMANDS
$STATS
MESSAGE STATS collecting statistics using INT$ minute intervals FI LE FI LE$
Beginning of iterative loop.
I" Get current dote, time, and day of the week. Also calculate
I"
IXEQ .STATS_COMMANDS FILE$ - 'XFILE',
I I NT$ .. X I NT, ;
I N-~
I"
I REDUCTION: Data reduction decision.
I"
ILET
statistics for system tuning and planning, all statistics are usually collected. Since al I statistics are collected, the system manager has the ability to generate any or all statistics displays to meet any unexpected requirements that might arise.
The collected statistics are either displayed as is, or a data reduction is performed. collection of the statistics.
128 STATS Data Reduction CE60-00
Module 6-2
Data reduction results need to be examined as they are produced. From these data reductions. the system manager can determine what is normal for the system. These data reductions wil I show the system manager if the CP-6 system is meeting its goals and objectives that are defined in terms of STATS items. As the workload and system
configuration change. the system manager will know from the data reductions when changes wil I have to be made in the system tuning parameters. In addition. the examination of
these data reductions may also reveal when the system configuration must be enlarged or upgraded to meet performance requirements.
An example of a batch data reduction job is shown in the fol lowing figure. This is the batch job that would be submitted by the STATS_XEQ.:STATS XEQ file.
IDEFAULT NAME$=STATS_REDUCTION
IDEFAULT WSN$=LOCAL. DEFER$=0:00. SCHED$=RERUN
!DEFAULT TIME$=30:00. M~128
IDEFAULT FPOOLS$=31
I JOB NAME=NAME$. WSN-WSN$. DEFER=DEFER$. SCHED$
!RES TIME=TIME$. MEM-MEM$
ILIMIT FPOOLS=FPOOLS$
!STATS
FILE FILE$
SPAN FROM$. MMDDYY$ - TO$. MMDDYY$
HISTOGRAM RESPONSE(SNAP). USER SIZE(SNAP). INTERACTION(SNAP) ALSO 01 CPU. RESOURCES. DEVICES. CHANNELS. PROCESSOR. FEP SUMMARY GLOM
STATISTICS ALL END
Figure 8. STATS_REDUCTION: Sample STATS Data Reduction Job
In this example. selected STATS data reductions are performed. These data reductions provide a starting point for system tuning and planning in less than 20 pages of output.
The sma I I amount of output can be quickly read by the system manager. If some of these data reductions are not useful. they can be removed from the data reduction commands.
If other data reductions are required. they can be added to the data reduction commands.
The reduction job example wil I function correctly under normal circumstances. If the system has an interruption (i.e .• ZAPI. DIEI. or SCREECH). the data reduction job wi I I not function correctly because the STATS processor GLOM command cannot perform
calculations for an interval during which a system interruption occurred. In this case.
the system manager wi I I have to manually perform the data reductions across the partial intervals. This procedure can be performed either at an onl ine terminal or by
submitting a batch job (i .e .• the STATS_REDUCTION job) with modified substitution parameters.
CE60-00 STATS Data Reduction 129
Module 6-2