3. PERFORMANCE ANALYSIS TOOLS › 3.1 Batch Initiator Simulation › 3.1.6 Component Operation › 3.1.6.1 Batch Initiator Simulation Panel
3.1.6.1 Batch Initiator Simulation Panel
Batch Initiator Simulation is one of the Performance Manager
options available through the CA MICS Workstation Facility
(MWF). Chapter One of this guide explains how you use MWF to
get to the Performance Manager options.
/------------------------ Batch Initiator Simulation ---- Data Base Set To A \
|Command ===> |
| |
|Composing CA MICS Inquiry: BAT12 - Batch Initiator Study |
| |
|Time-span: DETAIL Cycle(s) ===> 01 - 02 |
|Data base ===> A (PRIMARY) _ _ _ _ |
| |
|Select SYSID ===> ____ ____ ____ ____ ____ ____ |
|Simulation date ===> _______ (ddmonyy) Select hours ===> __ -- __ (hh) |
|Simulate class ===> ________ Simulate time ===> _____ _____ (hh:mm)|
|Report class ===> ________ Report time ===> _____ _____ (hh:mm)|
|Aging (low/high/rate) ===> __ __ __ Report intvl. ===> 15 (1-60 min)|
| |
|Initiators ===> ________ ________ ________ ________ ________ ________ ________ |
| ________ ________ ________ ________ ________ ________ ________ |
| ________ ________ ________ ________ ________ ________ ________ |
| ________ ________ ________ ________ ________ ________ ________ |
| ________ ________ ________ ________ ________ ________ ________ |
| ________ ________ ________ ________ ________ ________ ________ |
| ________ ________ ________ ________ ________ ________ ________ |
| |
|Specify extended options ===> N (Y/N) |
| |
\---------------------------------------------------------------------------------/
Figure 3-11. Batch Initiator Simulation Inquiry Panel
Figure 3-11 illustrates a sample Batch Initiator Simulation
inquiry panel. The following is a discussion of the fields
that you need to code on the panel.
Timespan: DETAIL is the only valid value for this field.
You cannot change it.
Cycle(s): The one or more cycles from the CA MICS database
that you want to use for simulation, where nn is
the cycle number corresponding to the beginning
(and ending) cycles for which data is to be
selected.
This parameter is required. Valid values are
determined by the number of cycles of data kept
in your installation's CA MICS database for the
database unit specified in the database field
described below. The default value is the range
from cycle 1 to cycle 2.
Generally, if the SMF data at your installation
is dumped at midnight, you specify only a single
cycle value. If your SMF data is not dumped at
midnight, you may need to specify a cycle range
to include a full day of SMF data.
Database: The single-character CA MICS identifier for the
database to be accessed.
This field is required. Valid values are the
database unit identifiers available at your
installation. Contact your CA MICS System
Administrator if you do not know what database
units are available, or enter a question mark
(?) to view a list of your database units. The
default value is the database unit containing
the BATJOB and BAT-JS Files. You can select up
to five databases per inquiry.
Select The logical system identifier. This field is
SYSID: optional. Valid values are the system
identifiers denoted in the
sharedprefix.MICS.PARMS(SYSID) member of the
CA MICS complex. Contact your CA MICS System
Administrator if you do not know what system
identifiers are available at your installation.
You can simulate data from up to six SYSIDs at
once. The default is to report on all systems
found in the data. This field limits analysis
and reporting to specific systems.
Simulation The date of the data you want to use for
date: simulation, presented in ddmonyy format. This
field is required. There is no default value.
Selection The range of hours used to select data for
hours: simulation, presented in hh format. This field
is optional. Valid values are 00 through 23.
There is no default value.
Simulate The list of job classes to be simulated. This
class: field is optional. The default is to simulate
all classes contained in the BATJOB File. If
you code the Specify job input exit (one of the
Extended Options Menu choices) to create a new
class, do not specify a class list. The
default, simulate all classes, ensures that the
new class is included in the simulation. You
can specify a maximum of eight classes for one
simulation.
Simulate The earliest and latest times, respectively, to
time: be simulated, entered in hh:mm format. This
parameter is optional. Valid values are 00:00
through 23:59. The default value is 00:00
through 23:59. The time specification for the
latest time is exact. For example, if you
specify 10:00, the latest time included is
10:00, not 10:59:59.99, as is the case for some
CA MICS time specifications.
The period chosen for simulation should start
when there is little or no batch activity. The
ideal situation is to start with all initiators
drained and queues empty, since the model cannot
simulate any job that begins execution before
the simulation period.
Report The list of job classes to be reported. This
class: field is optional. There is no default value.
The classes you specify here must fall within
the classes specified on the Simulate class
field (that is, you cannot simulate classes A,
B, and C, then request a report on class X).
You cannot specify more than eight job classes.
Report The earliest and latest times, respectively, to
time: be reported on, entered in hh:mm format. This
field is optional. Valid values are 00:00
through 23:59. The default value is 00:00
through 23:59. The times you specify here must
fall within the times on the Simulate time
parameter (that is, you cannot simulate daytime
hours and then request a report of nighttime
hours).
Aging The specifications for increasing the priority
(low/high/ of a job (i.e., aging) after it has been in the
rate): input queue for a specified period of time.
Enter the JES2 priority aging parameters used at
your installation. (NOTE: JES3 workload
simulation is not supported by CA MICS.) This
field is optional. There is no default value
(that is, no aging is done). The data is
entered in aa bb cc format, where:
aa is the lowest priority a job can have and
still be considered for aging. Jobs of
lower priority will not be aged, no matter
how long they have been in the queue. Valid
values are numeric (0-15).
bb is the highest priority a job can reach by
being aged (a job must have a priority less
than this value in order to be considered
for aging). Valid values are numeric (0-15).
cc defines how long a job must be in the queue
at a particular priority before it is
eligible for aging. Valid values are
fractional parts of a day (a rate of 24
means that a job may be aged after 1/24th of
a day (one hour) in the queue).
Report The number of minutes used to keep data that is
intvl.: being reported on. This field is optional.
Valid values are integers from 1 to 60.
Initiators: The identifier for a series of strings, each of
which defines the classes served by one
initiator. These fields are required. You can
simulate data for up to 49 initiators for each
model. There is no default value.
If you are running the simulator to validate a
model, these fields should define the initiator
structure used on the system that you are
modeling. If you are using the simulator to try
a new initiator structure, these fields should
define the initiator structure that you are
considering. If you want to simulate more than
49 initiators, split the initiator structure
into groups of less than 50 initiators and
execute separately.
NOTE: The Batch Initiator Simulation inquiry
estimates the amount of job backlog depth to
support based on the maximum number of classes
defined for any single initiator. If your
system has more than five classes in any single
initiator, the "small" backlog model is
selected. This may cause you to receive message
PER00088 'JOBQ SIZE EXCEEDED.' Should this
happen, either reduce the number of classes
assigned to each initiator that has more than
five classes, or subdivide the simulation into
more than one run. For additional assistance,
contact your CA Technical Support
representative.
Specify The specification for further customizing the
extended outcome of the simulation. This field is
options: required. Valid values are N and Y. The
default value is N (No). If you select Y (Yes),
the Extended Options Menu appears. This menu is
described in detail in Section 3.1.6.2.
Copyright © 2014 CA.
All rights reserved.
|
|