|
|
|
Figure 4-25 is an Algorithm Qualification Worksheet.
+----------------------------------------------------------------------------------------------------------+ | | | Date: ____/____/____ Administrator: ____________________________________________ | +----------------------------------------------------------------------------------------------------------+ ALGORITHM QUALIFICATION WORKSHEET DATA BASE UNIT IDENTIFIER: __________ Journal File: _____________ Use groups for SYSID: Yes/No Subsysid: Yes/No Subtype: Yes/No COSTCTR1: Yes/No Workunit: Yes/No Alg Partial/Complete ID SYSID Subsysid Subtype COSTCTR1 S/E Workunit -------- ------------ --------------- ------------ ----------------------------- --- -------------------- ________ ____________ _______________ ____________ _____________________________ ___ ____________________ ________ ____________ _______________ ____________ _____________________________ ___ ____________________ ________ ____________ _______________ ____________ _____________________________ ___ ____________________ ________ ____________ _______________ ____________ _____________________________ ___ ____________________ ________ ____________ _______________ ____________ _____________________________ ___ ____________________ ________ ____________ _______________ ____________ _____________________________ ___ ____________________ ________ ____________ _______________ ____________ _____________________________ ___ ____________________ ________ ____________ _______________ ____________ _____________________________ ___ ____________________ ________ ____________ _______________ ____________ _____________________________ ___ ____________________ ________ ____________ _______________ ____________ _____________________________ ___ ____________________ ________ ____________ _______________ ____________ _____________________________ ___ ____________________ ________ ____________ _______________ ____________ _____________________________ ___ ____________________ ________ ____________ _______________ ____________ _____________________________ ___ ____________________ ___________________________________________________________________________________________________________________________
Figure 4-25. Algorithm Qualification Worksheet
Use the worksheet to define the following parameters:
1. DATABASE UNIT IDENTIFIER
Description: The one-character CA MICS database unit
identifier.
Default: From Algorithm Specification panel
Values: Character, length 1
2. JOURNAL FILE
Description: The name of the journal file whose
algorithms are being qualified.
Default: From Algorithm Specification panel
Values: Character, length 6. Selecting a journal file
for charging is discussed in Section 4.3.1.1.
3. USE GROUPS FOR: SYSID, SUBSYSID, SUBTYPE, COSTCTR1,
WORKUNIT
Description: Indicates whether the entries in the SYSID,
Subsysid, Subtype, COSTCTR1, or Workunit fields are
actual values or represent a group. To use a group, it
must be defined on the Qualification Groups panel
(MWF;4;2;3;9). See Section 4.3.2 for information on
defining qualification groups.
Default: NO
Values: Character, Y, N, YES, or NO
4. ALGORITHM IDENTIFIER
Description: The unique code used to refer to this list
of computation codes and their associated rates.
Default: From Algorithm Specification panel
Values: Character, length 3
NOTE: This must be a value specified on one of the
algorithm specification worksheets described in
Section 4.3.1.4.1. There must be a qualification
for each algorithm defined for this file.
5. SYSID
Description: The logical CA MICS system identifier (the
SYSID) that uniquely identifies the mainframe processor
to which this algorithm applies (if "Use groups for
SYSID" is NO) or the group name of CA MICS system
identifiers (if "Use groups for SYSID" is YES).
Default: *ALL
Values: Character, length 4. Valid values are *ALL,
*DEF, a valid SYSID value for this unit, or a valid SYSID
group name.
NOTE: If the algorithm applies to all SYSIDs, enter a
value of *ALL for SYSID. If the algorithm applies
to all SYSIDs that are not explicitly listed,
enter a value of *DEF for SYSID.
6. SUBSYSID
Description:
- For CICS, DB2, IDMS, or IMS Analyzer files, Subsysid
is the identifier of the CICS, DB2, IDMS, or IMS
system to which this algorithm applies.
- For SNT, Subsysid is the Primary Logical Unit (PLU).
- For the Batch and Operations Analyzer, the VM and CMS
Analyzer, the Space Analyzer, and the VAX/VMS
Analyzer, its contents vary depending on the file
being charged.
- For the Analyzer for MeasureWare OS Agents, Subsysid
is the application number (1 through 32) as defined in
the MeasureWare configuration parameters.
- For the Analyzer for MQSeries, Subsysid is the
MQSeries connection type.
If "Use groups for Subsysid" is YES, then a group name is
entered in the Subsysid field.
The value of the SUBSYSID variable is carried in the
Journal File WORKAREA Variable 2 field and can be
modified using the Journal File Eligibility feature
(MWF;4;2;S;2). Refer to the WORKAREA Variable 2 column
in Figure 7-3 in Section 7.1.1 for the standard SUBSYSID
variables.
The Subsysid comparison is generic for most Subsysid
variables. For example, if you specify a value of IMS,
it will match any data value that begins with IMS: IMS1,
IMS2, and so on.
However, if the Subsysid variable is application number,
the Subsysid comparison is exact. If you specify a value
of 1, it will match only application number 1.
Default: *ALL
Values: Character, length 8. Valid values are *ALL,
*DEF, a Subsysid value, or a Subsysid group name. Valid
values are determined by the Subsysid Validation Table
defined in Journal File Eligibility for journal files.
If there is no table, all values are valid. All values
are valid for complex-level external files.
NOTE: If the algorithm applies to all Subsysids, enter a
value of *ALL for Subsysid. If the algorithm
applies to all Subsysids that are not explicitly
listed, enter a value of *DEF for Subsysid.
Subsysid has a special meaning when specified in
conjunction with the batch program file (step
level accounting) or the batch job file (job level
accounting). In both of these cases, it is used
to distinguish between the batch, TSO, started
task, APPC, UNIX System Services and system
address space workloads. The values are @BAT,
@TSO, @STC, @TP, @OEM, and @SAS, respectively.
*ALL is also a valid specification in all cases.
When specified for the Batch Spool file, Subsysid
refers to the subsystem identifier (for example,
BNDL, JES2, JES3, PSF, or XWTR).
For the MULC Address Space Journal File (ACTJBM),
Subsysid is the first eight bytes of the Software
Product Name (MUPROD) so you can use different
charging algorithms by product name and version
(see Subtype below).
Subsysid also has a special meaning when specified
in conjunction with the CA MICS Space Analyzer
Option files. It denotes device type for the VSAM
and non-VSAM journal files, and the Systems
Managed Storage (SMS) storage class for the SMS
journal file. This allows you to charge your
non-SMS data sets by device type, and to charge
your SMS data sets by storage class. Subsysid
also denotes storage class for the Migrated Data
journal file and for the Backup Data journal file.
When specified in conjunction with the CA MICS
Network Analyzer Option, Subsysid distinguishes
between the PLU types (for example, IMS0, IMS1)
that are being used. The APPLID parameter in the
VTAM GEN establishes the value of the PLU. You
should read the Data Dictionary definition of PLU
and consult the VTAM system programmer prior to
using this parameter for the CA MICS Network
Analyzer Option. This allows you to charge at a
different rate for the application systems
utilized. *ALL is also a valid specification in
all cases.
When specified in conjunction with the IMS, CICS,
DB2, or IDMS Analyzers, you can use Subsysid for
files of these products to distinguish between the
different systems (for example, IMSID, CICSID,
DB2ID, or IDMSID). This allows you to charge
different rates for the various systems utilized.
Any Subsysid that is not explicitly indicated will
not be used in the chargeback system unless *DEF
has been used. *ALL is a valid specification to
indicate all systems and all activity.
Subsysid can be used with three files of the VM
and CMS Analyzer:
o For the VMCCMU file, Subsysid denotes the
Virtual Machine Execution Mode as specified
by the CMUXMODE variable. Its valid values
are BATCH, ONLINE, and GUEST.
o For the VMCDAC file, Subsysid denotes the
Device Class as specified by the DEVCLASS
variable. Its valid values are DASD/CKD,
DASD/FBA, and TAPE.
o For the VMCVRA file, Subsysid denotes the VRA
Accounting Subsysid, as specified by the
VRASBSYS variable. Its values are user-
defined, and you should review the Data
Dictionary entry for more information on its
contents.
Subsysid can be used with the VAX/VMS Analyzer's
DEAPRC and DEAIMG files to denote process type as
specified by the PRCTYPE and IMGTYPE variables,
respectively. Review the Data Dictionary entries
for these variables for more information on their
contents.
Subsysid can be used with the Analyzer for
MQSeries to charge differently for each MQSeries
connection type. The element, MQSATYP, has a value
which ranges between 1 and 6, with these integers
having the following meanings:
1 = CICS 4 = IMS,MPR,or BMP
2 = MVS/TSO 5 = Command server
3 = IMS Control region 6 = Channel initiator
7. SUBTYPE
Description:
- For IDMS, Subtype is the IDMS Task Type.
- For SNT, Subtype is the Logical Device Type.
- For DB2, a default variable is not shipped. The
suggested variable is DB2CONN, the connection
identifier. If you use DB2CONN, make sure it is a
sequence element in the DAYS level DB2DSU file.
Alternatively, you can assign Subtype to an account
code using the Journal File Eligibility - File
Specification panel.
- For the CA MICS Space Analyzer Option, Subtype can be
used with the SMS journal file to qualify algorithms by
the SMS management class values, or with the MIG
journal file to qualify algorithms by HSMLEVEL, which
contains the indicator of the DFHSM migration level.
- For APPC, Subtype is the TP type.
- For the Analyzer for MeasureWare OS Agents, Subtype is
AUMOPSYS, the operating system.
- For the Analyzer for MQSeries, Subtype is the MQSeries
subsystem name, MQMSSI.
The value of the Subtype variable is carried in the
Journal File WORKAREA Variable 1 field and can be
modified using the Journal File Eligibility feature
(MWF;4;2;S;2). Refer to the WORKAREA Variable 1 column
in Figure 7-3 in Section 7.1.1 for the standard Subtype
variables.
The Subtype comparison is generic. For example, if you
specify a value of IMS, it will match any data value that
begins with IMS: IMS1, IMS2, and so on.
Default: *ALL
Values: Character, length 8, valid values are *ALL,
*DEF, a valid Subtype value, or a valid Subtype group
name. The valid values are determined by the Subtype
Validation Table defined in Journal File Eligibility for
journal files. If there is no table, all values are
valid. All values are valid for complex-level external
files.
NOTE: If the algorithm applies to all Subtypes, enter a
value of *ALL for Subtype. If the algorithm
applies to all Subtypes that are not explicitly
listed, enter a value of *DEF for Subtype.
Subtype has a special meaning for IDMS. The
IDMTYPE value can be used with this parameter to
charge differently for the activity (noted by B
for Batch, C for CICS, or O for online).
Subtype can be used to qualify CA MICS Network
Analyzer Option charging by using a value of L for
Local, R for Remote, A for
Application-to-Application, and O for Other.
These values are in the PSULDEV, NSSLDEV, NACLDEV,
or NSCLDEV variables of the CA MICS Network
Analyzer Option.
When specified for the BATATP file, Subsysid
refers to the subsystem identifier (for example,
ASCH for APPC/MVS ASCH scheduled TPs).
For the MULC Address Space Journal File (ACTJBM),
Subtype is the Software Product Version (MUPROD)
so you can use different charging algorithms by
product name (see Subsysid above) and version.
Subtype has a special meaning for APPC. The
ATPTYPE value can used to charge differently for
standard and multitrans TPs. It can also
determine if a multitrans TP is a TP that can be
charged to a specific account or the multitrans
shell, which must be charged as an overhead.
8. COSTCTR1
Description: The Cost Center 1 value to which the
algorithm applies (if "Use groups for COSTCTR1" is NO) or
the Cost Center 1 group name (if "Use groups for
COSTCTR1" is YES).
Default: *ALL
Values: Character, length 30, valid values are *ALL,
*DEF, a valid COSTCTR1 value, or a valid Cost Center 1
group name.
NOTE: If the algorithm applies to all Cost Center 1
values, enter a value of *ALL for COSTCTR1. If
the algorithm applies to all Cost Center 1s that
are not explicitly listed, enter a value of *DEF
for COSTCTR1.
9. S/E
Description: Indicates whether the work unit specified
below is to be Selected For or Excluded From charging.
Default: (blank)
Values: Character, length 1, S, E, or blank
NOTE: Leave this field blank unless the algorithm has
specific work unit dependencies.
10. WORKUNIT
Description: Contains the value of the accounting
Workunit variable or Workunit group name that is to be
Selected For or Excluded From charging.
The Workunit comparison is generic. For example, if you
specify a Workunit value of IMS, it will match any data
value that begins with IMS: IMS1, IMS2, and so on.
Default: Blank
Values: Character, length 44. Use the scroll option to
enter a Workunit value of more than 12 characters.
NOTE: Leave this field blank unless the algorithm has
specific workunit dependencies. Either define a
workunit group, or use multiple lines to select or
exclude multiple workunits.
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |