|
|
|
DIRECT ASSIGNMENT ALGORITHM WORKSHEET Use the Rate Table - Direct Assignment Algorithm Worksheet shown in Figure 4-21 for resource accounting algorithms only. If your algorithm is simple, with only one rate and one computation code for each charging element, this worksheet is sufficient for resource algorithms. If you need to use different computation codes and/or rates for one or more charging elements, use this worksheet and the Rate Table - Control Variable Algorithm Worksheet in Figure 4-22.
+----------------------------------------------------------------------------------------------------------+ | | | Date: ____/____/____ Administrator: ____________________________________________ | +----------------------------------------------------------------------------------------------------------+ RATE TABLE - DIRECT ASSIGNMENT ALGORITHM WORKSHEET DATA BASE UNIT IDENTIFIER: ____________ Journal Algorithm Description Comp Rate Effective Charging Element Description File ID Code Date ____________ ________ ____________________ _________ _________ ___________ ______________________________ _________ _________ ___________ ______________________________ _________ _________ ___________ _______________________________ _________ _________ ___________ _______________________________ _____________ ________ ___________________ ________ __________ ___________ _______________________________ ________ __________ ___________ _______________________________ ________ __________ ___________ _______________________________ ________ __________ ___________ _______________________________ _____________ ________ ___________________ ________ __________ ___________ _______________________________ ________ __________ ___________ _______________________________ ________ __________ ___________ _______________________________ ________ __________ ___________ _______________________________ _____________ ________ ___________________ ________ __________ ___________ _______________________________ ________ __________ ___________ _______________________________ ________ __________ ___________ _______________________________ ________ __________ ___________ _______________________________
Figure 4-21. Rate Table - Direct Assignment Algorithm Worksheet
1. DATABASE UNIT IDENTIFIER
Description: The one-character CA MICS database unit
identifier.
Default: None
Values: Character, length 1
2. JOURNAL FILE
Description: The name of the journal file to be charged
with this algorithm.
Default: None
Values: Character, length 6. The journal file must be
one selected for charging (see Section 4.3.1.1).
Note: You must code at least one algorithm for each
file selected. You can code more than one
algorithm for each file if you need to use
different computation codes and/or rates for
different mainframe processors (SYSIDs),
application subsystems (SUBSYSIDs), type of work
(SUBTYPE), or cost centers.
3. ALGORITHM IDENTIFIER
Description: A user-defined unique code that refers to
this list of computation codes and their associated
rates.
Default: None
Values: Character, length 3
Note: The identifier must be unique across all journal
files in the database unit.
4. DESCRIPTION
Description: A description of the use or application of
this specific algorithm.
Default: None
Values: Character, length 40
Note: This field is for your information only.
5. COMPUTATION CODE
Description: The computation code defining the charging
element to which the rate will be applied.
Default: None
Values: Character, length 4. Use a defined computation
code or one of the special computation codes JMIN and
SURC. Use JMIN to establish a minimum charge for each
work unit to be charged with this algorithm. Use SURC
to establish a work unit surcharge. You can associate
them with any journal file.
Note: Elements whose computation codes are specified
are kept in the accounting files but not
necessarily in the corresponding CA MICS file.
Check the component's GENIN member in
sharedprefix.MICS.GENLIB to see if the data
element will be kept.
6. RATE
Description: The rate at which the element identified
by the computation code will be charged.
Default: None
Values: Character, length 8, may contain up to six
decimal positions
7. EFFECTIVE DATE
Description: The date when the rate specified for the
computation code takes effect. You can specify two
effective dates for each charging element in an
algorithm. You can use different effective dates to
preassign a rate change for a future date. In
addition, you can begin charging for a new resource by
using a future date.
Default: Blank (interpreted as 01/01/60)
Values: Date, length 8, specified as MM/DD/YY; year
must be 80 or greater.
Note: When the journal file records are created during
the CA MICS daily job, this date is compared to
the date in the Effective Date Timestamp
Variable, BILLTS or ENDTS. If no effective rate
is found, a rate of missing is used, and the
computation code and rate will not appear in the
Ledger File. If all the rates in the journal
file record are missing, the record is not
written to the journal file. To cause the rate
to be carried in the journal file, use a rate of
zero (0) with an effective date of blank.
8. CHARGING ELEMENT DESCRIPTION
Description: The description of the charging element.
Default: None
Values: Character, length 40
Note: This field is for your information only.
CONTROL VARIABLE ALGORITHM WORKSHEET
Use the Rate Table - Control Variable Algorithm Worksheet in
Figure 4-22 for all transaction accounting algorithms and for
resource accounting algorithms that require different
computation codes and/or rates.
+----------------------------------------------------------------------------------------------------------+ | | | Date: ____/____/____ Administrator: ____________________________________________ | +----------------------------------------------------------------------------------------------------------+ RATE TABLE - CONTROL VARIABLE ALGORITHM WORKSHEET DATA BASE UNIT IDENTIFIER: __________ Journal Algor Effective Control Default Default Format Control Variable File ID Date Variable Comp Code Rate Value /Comp Code /Rate ______ ________ ___________ _______________ _________ __________ __________ ______________________________________ ______________________________________ ______________________________________ ______________________________________ ______ ________ ___________ _______________ _________ __________ __________ ______________________________________ ______________________________________ ______________________________________ ______________________________________ ______ ________ ___________ _______________ _________ __________ __________ ______________________________________ ______________________________________ ______________________________________ ______________________________________ ________________________________________________________________________________________________________________________________
Figure 4-22. Rate Table - Control Variable Algorithm Worksheet
1. DATABASE UNIT IDENTIFIER
Description: The one-character CA MICS database unit
identifier.
Default: None
Values: Character, length 1
2. JOURNAL FILE
Description: The name of the journal file to be charged
with this algorithm.
Default: None
Values: Character, length 6. The journal file must be
one selected for charging (see Section 4.3.1.1).
Note: You must code at least one algorithm for each
file selected. More than one algorithm can be
coded for each file if different computation
codes and/or rates need to be used for different
mainframe processors (SYSIDs), application
subsystems (SUBSYSIDs), type of work (SUBTYPE),
or cost centers.
3. ALGORITHM IDENTIFIER
Description: A user-defined unique code that refers to
this list of computation codes and their associated
rates.
Default: None
Values: Character, length 3
Note: The identifier must be unique across all journal
files in the database unit.
4. EFFECTIVE DATE
Description: The date on which the computation codes and
rates specified take effect.
Default: Blank (interpreted as 01/01/60)
Values: Date, length 8, specified as MM/DD/YY; year must
be 80 or greater.
Note: When the journal file records are being created
during the CA MICS daily job, this date is
compared to the date in the Effective Date
Timestamp Variable, BILLTS or ENDTS. If no
effective rate is found, a rate of missing is
used, and the computation code and rate will not
appear in the Ledger File. If all the rates in
the journal file record are missing, the record is
not written to the journal file. To cause the
rate to be carried in the journal file, use a rate
of zero (0) with an effective date of blank.
5. CONTROL VARIABLE NAME
Description: The data element upon which value the
computation code, and/or rate depends.
Default: CICAPU for the ACTJCA CICS Transaction Journal
File; IMSAPU for the ACTJIA IMS Transaction Journal File;
IDMAPU for the ACTJSA IDMS Transaction Journal File; and
TSOAPU for the ACTJTC and ACTJTI CA TSO/MON PM
Transaction Journal Files. No default for resource
journal files.
Values: Character, length 8
Note: This field is preset for transaction journal files
and normally should not be changed. The IMSAPU,
CICAPU, IDMAPU, and TSOAPU values are user-defined
using SAS coding in the cccAURT member for the
respective product.
6. DEFAULT COMPUTATION CODE
Description: The computation code that will be used for
values of the control variable not specified in item 9
below.
Default: 1500 for the ACTJCA CICS Transaction Journal
File; 1000 for the ACTJIA IMS Transaction Journal File,
1400 for the ACTJTC CA TSO/MON PM Command Transaction
Journal File, 1900 for the ACTJSA IDMS Transaction
Journal File, and 1480 for the ACTJTI CA TSO/MON PM
Interactive Transaction Journal File. No default for
resource journal files.
Values: Character, length 4. Use a computation code
defined in the Charging Element TAble.
Note: This field is preset for transaction journal files
and should not normally be changed.
7. DEFAULT RATE
Description: The rate that will be used for values of
the control variable specified in item 5. This rate is
used unless specific values and rates are entered in
items 9, 10, and 11.
Default: None
Values: Character, length 8, may contain up to six
decimal positions
Note: If you enter a value of zero, any control variable
values that are NOT specified below will have a
zero charge.
8. VARIABLE FORMAT
Description: The SAS format associated with the control
variable in the CA MICS product generation step.
Default: $12
Values: Character, length 12, any valid SAS format
Note: This field is used to "PUT" the control variable
value in order to look up its computation code and
rate at charging algorithm execution time during
CA MICS daily processing.
9. CONTROL VARIABLE VALUE
Description: A specific value of the control variable
with which a computation code and rate, discussed below
in items 10 and 11, will be associated. Omit this item
as well as items 10 and 11 for any control variable
values that you want to charge with the default
computation code and rate.
Default: None
Values: Character, length 12, any valid value of the
control variable (see Variable Format in item 7 above)
Note: The normal daily processing of the CA MICS product
will place values into all variables kept in its
files. If the control variable is not kept on the
product file from which this journal file is
derived, and if standard CA MICS processing does
not place values in it, you must write exit code
to assign values to it. This exit code should be
placed in the USRUfff macro in
sharedprefix.MICS.SOURCE(#cccEXIT), where fff is
the CA MICS product file ID and ccc is the CA MICS
product ID. Do not use the accounting journal
file exit for this purpose. Each value can be
charged with a different computation code and/or
rate.
10. COMPUTATION CODE
Description: The computation code that is to be used for
this specific value of the control variable.
Default: None
Values: Character, length 4
Note: This must be a valid computation code in the
Charging Element Table, and must be associated
with the CA MICS product file from which this
journal file is derived. It must be associated
with the same charging element as the default
computation code, and it must have the same
compute status as the default computation code.
If it references a derived (computed) element, it
must have the same computation routine (ACTF
member) as the default computation code. Only the
computation routine for the default computation
code will be included in the generated code.
11. RATE
Description: The rate that is to be used for this
specific value of the control variable.
Default: None
Values: Character, length 8, may contain up to six
decimal positions.
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |