Embed Size (px)
Citation preview
Tivoli®
Decision
Support
for
OS/390®
Accounting
Feature
for
the
Host
Version
1.6,
December
2003
SH19-4495-05
���
Tivoli®
Decision
Support
for
OS/390®
Accounting
Feature
for
the
Host
Version
1.6,
December
2003
SH19-4495-05
���
Note
Before
using
this
information
and
the
product
it
supports,
read
the
information
in
“Notices”
on
page
93.
Sixth
Edition
(June
2003)
This
edition
applies
to
version
1,
release
6
of
Tivoli
Decision
Support
for
OS/390
(product
number
5695-101)
and
to
all
subsequent
releases
and
modifications
until
otherwise
indicated
in
new
editions.
This
edition
replaces
SH19-4495-04.
©
Copyright
International
Business
Machines
Corporation
1994,
2003.
All
rights
reserved.
Note
to
U.S.
Government
Users
Restricted
Rights—Use,
duplication
or
disclosure
restricted
by
GSA
ADP
Schedule
Contract
with
IBM
Corporation.
Contents
Figures
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. v
Preface
.
.
.
.
.
.
.
.
.
.
.
.
.
. vii
Who
should
read
this
book
.
.
.
.
.
.
.
.
. vii
What
this
book
contains
.
.
.
.
.
.
.
.
.
. vii
Publications
.
.
.
.
.
.
.
.
.
.
.
.
.
. viii
Tivoli
Decision
Support
for
OS/390
library
.
. viii
Using
LookAt
to
look
up
message
explanations
. ix
Accessing
publications
online
.
.
.
.
.
.
.
. x
Ordering
Publications
.
.
.
.
.
.
.
.
.
. x
Accessibility
.
.
.
.
.
.
.
.
.
.
.
.
. x
Contacting
software
support
.
.
.
.
.
.
.
.
. x
Conventions
used
in
this
book
.
.
.
.
.
.
.
. xi
Typeface
conventions
.
.
.
.
.
.
.
.
.
. xi
Part
1.
Accounting
feature
guide
.
.
. 1
Chapter
1.
Overview
of
the
Accounting
feature
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 3
Collecting
usage
data
.
.
.
.
.
.
.
.
.
.
. 3
Producing
billing
information
.
.
.
.
.
.
.
.
. 3
Setting
prices
.
.
.
.
.
.
.
.
.
.
.
.
. 4
Output
from
the
Accounting
feature
.
.
.
.
. 4
Working
with
the
Accounting
feature—an
example
4
Considerations
.
.
.
.
.
.
.
.
.
.
.
.
.
. 5
Customers
and
accounts
.
.
.
.
.
.
.
.
. 6
Billing
units
.
.
.
.
.
.
.
.
.
.
.
.
. 6
Prices
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 7
Chapter
2.
Preparing
the
Accounting
feature
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 9
How
the
Accounting
feature
works
.
.
.
.
.
.
. 9
Setting
up
security
.
.
.
.
.
.
.
.
.
.
.
. 10
Trimming
the
data
tables
.
.
.
.
.
.
.
.
.
. 10
Installing
the
Accounting
component
.
.
.
.
.
. 11
Maintaining
the
lookup
tables
.
.
.
.
.
.
.
. 11
Workload
period
and
special
day
tables
.
.
.
. 12
DCOLLECT
LAST_RUN
lookup
table
.
.
.
. 12
Network
resource
translation
table
.
.
.
.
. 13
Preparing
for
collect
.
.
.
.
.
.
.
.
.
.
. 13
Chapter
3.
Implementing
the
Accounting
feature
.
.
.
.
.
.
.
.
. 15
Understanding
Accounting
feature
tables
.
.
.
. 15
Table
types
.
.
.
.
.
.
.
.
.
.
.
.
.
. 15
Data
tables
.
.
.
.
.
.
.
.
.
.
.
.
. 16
Summary
tables
.
.
.
.
.
.
.
.
.
.
.
. 16
Lookup
tables
.
.
.
.
.
.
.
.
.
.
.
. 16
Views
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 16
Chapter
4.
Prorating
overhead
accounts
.
.
.
.
.
.
.
.
.
.
.
.
.
. 17
DRLJPROR
sample
job
.
.
.
.
.
.
.
.
.
. 18
Distributing
overhead
accounts
based
on
fixed
percentages
.
.
.
.
.
.
.
.
.
.
.
.
. 19
Distributing
overhead
accounts
based
on
relative
percentages
.
.
.
.
.
.
.
.
.
.
.
.
. 20
Part
2.
Accounting
feature
reference
.
.
.
.
.
.
.
.
.
.
.
.
. 21
Chapter
5.
Data
flow
.
.
.
.
.
.
.
.
. 23
Overview
of
data
flow
.
.
.
.
.
.
.
.
.
.
. 23
CICS
data
flow
.
.
.
.
.
.
.
.
.
.
.
.
. 24
Credit
debit
processing
data
flow
.
.
.
.
.
.
. 25
DB2
data
flow
.
.
.
.
.
.
.
.
.
.
.
.
. 26
DFSMS
data
flow
.
.
.
.
.
.
.
.
.
.
.
. 27
IMS
data
flow
.
.
.
.
.
.
.
.
.
.
.
.
. 28
NPM
and
NetView
data
flow
.
.
.
.
.
.
.
. 29
STC,
BATCH,
TSO
data
flow
.
.
.
.
.
.
.
. 30
Overhead
accounts
data
flow
.
.
.
.
.
.
.
. 31
Billing
process
data
flow
.
.
.
.
.
.
.
.
.
. 32
Chapter
6.
Data
tables
and
views
.
.
. 33
RAFBATCH
data
table
.
.
.
.
.
.
.
.
.
.
. 33
RAFJOBLOG
data
table
.
.
.
.
.
.
.
.
.
. 35
RAFCICS
data
table
.
.
.
.
.
.
.
.
.
.
. 37
RAFDASD
data
table
.
.
.
.
.
.
.
.
.
.
. 39
RAFDB2
data
table
.
.
.
.
.
.
.
.
.
.
.
. 40
RAFHSMBKUP
data
table
.
.
.
.
.
.
.
.
. 42
RAFHSMMIGR
data
table
.
.
.
.
.
.
.
.
. 43
RAFIMS
data
table
.
.
.
.
.
.
.
.
.
.
.
. 44
RAFNETSES20
data
table
.
.
.
.
.
.
.
.
.
. 45
RAFNETSES4X
data
table
.
.
.
.
.
.
.
.
. 47
RAFNETV
data
table
.
.
.
.
.
.
.
.
.
.
. 48
RAFSTC
data
table
.
.
.
.
.
.
.
.
.
.
.
. 49
RAFADDRLOG
data
table
.
.
.
.
.
.
.
.
. 50
RAFTSO
data
table
.
.
.
.
.
.
.
.
.
.
.
. 52
RAFSESLOG
data
table
.
.
.
.
.
.
.
.
.
. 53
USE_SUMMARY_D
data
table
.
.
.
.
.
.
.
. 54
USE_SUMMARY_D2
data
table
.
.
.
.
.
.
.
. 55
USE_SUMMARY_D3
data
table
.
.
.
.
.
.
.
. 56
USE_SUMMARY_D4
data
table
.
.
.
.
.
.
.
. 57
ACCT_PRORATEV1
view
.
.
.
.
.
.
.
.
. 58
ACCT_PRORATEV2
view
.
.
.
.
.
.
.
.
. 59
BILLED_DATA
data
table
.
.
.
.
.
.
.
.
.
. 60
Chapter
7.
Lookup
tables
.
.
.
.
.
.
. 63
ACCOUNT
.
.
.
.
.
.
.
.
.
.
.
.
.
. 63
ACCT_PRORATE
.
.
.
.
.
.
.
.
.
.
.
. 64
BILLING_PERIOD
.
.
.
.
.
.
.
.
.
.
.
. 65
CPU_NORMAL_DATA
.
.
.
.
.
.
.
.
.
. 66
CREDIT_DEBIT
.
.
.
.
.
.
.
.
.
.
.
.
. 67
CUSTOMER
.
.
.
.
.
.
.
.
.
.
.
.
.
. 68
PRICE_LIST
.
.
.
.
.
.
.
.
.
.
.
.
.
. 69
iii
Chapter
8.
Accounting
feature
translation
tables
.
.
.
.
.
.
.
.
.
. 71
RAFABATCH
.
.
.
.
.
.
.
.
.
.
.
.
.
. 71
RAFACICS
.
.
.
.
.
.
.
.
.
.
.
.
.
. 72
RAFADASD
.
.
.
.
.
.
.
.
.
.
.
.
.
. 73
RAFADB2
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 74
RAFAHSMBKUP
.
.
.
.
.
.
.
.
.
.
.
. 75
RAFAHSMMIGR
.
.
.
.
.
.
.
.
.
.
.
. 76
RAFAIMS
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 77
RAFANETSESM
.
.
.
.
.
.
.
.
.
.
.
.
. 78
RAFANETV
.
.
.
.
.
.
.
.
.
.
.
.
.
. 79
RAFASTC
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 80
RAFATSO
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 81
Chapter
9.
Accounting
feature
reports
83
Accounting
feature
report
definitions
.
.
.
.
.
. 83
Prorated
account
percentage
validation
report
.
. 83
Charges
by
billing
period
report
.
.
.
.
.
. 84
Charges
by
billing
period,
with
two
currencies
report
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 85
Billing
details
report
.
.
.
.
.
.
.
.
.
. 86
Charges
for
selected
billing
period
report
.
.
. 87
Chapter
10.
Considerations
for
dpAM
users
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 89
Part
3.
Appendixes
.
.
.
.
.
.
.
.
. 91
Notices
.
.
.
.
.
.
.
.
.
.
.
.
.
. 93
Trademarks
.
.
.
.
.
.
.
.
.
.
.
.
.
. 95
List
of
abbreviations
.
.
.
.
.
.
.
.
. 97
Glossary
.
.
.
.
.
.
.
.
.
.
.
.
.
. 99
Index
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 103
iv
Tivoli
Decision
Support
for
OS/390:
Accounting
Feature
for
the
Host
Figures
1.
Partial
view
of
an
RAFBATCH
summary
table
15
2.
General
overview
of
data
flow
.
.
.
.
.
. 23
3.
CICS
component
data
flow
.
.
.
.
.
.
. 24
4.
Credit
debit
processing
data
flow
.
.
.
.
. 25
5.
DB2
component
data
flow
.
.
.
.
.
.
. 26
6.
DFSMS
component
data
flow
.
.
.
.
.
. 27
7.
IMS
component
data
flow
.
.
.
.
.
.
.
. 28
8.
NPM
and
NETV
components
data
flow
29
9.
STC,
Batch,
TSO
component
data
flow
.
.
. 30
10.
Overhead
accounts
data
flow
.
.
.
.
.
. 31
11.
Billing
process
data
flow
.
.
.
.
.
.
.
. 32
12.
Prorated
account
percentage
validation
83
13.
Charges
by
charge
type
.
.
.
.
.
.
.
. 84
14.
Charges
by
billing
period,
with
two
currencies
85
15.
Billing
details,
partial
view
.
.
.
.
.
.
. 86
16.
Charges
by
charge
type
.
.
.
.
.
.
.
. 87
v
vi
Tivoli
Decision
Support
for
OS/390:
Accounting
Feature
for
the
Host
Preface
This
book
describes
how
to
use
IBM®
Tivoli®
Decision
Support
for
OS/390®
(hereafter
referred
to
as
Tivoli
Decision
Support
for
OS/390)
to
collect
and
report
performance
data
generated
by
the
Accounting
feature
of
Tivoli
Decision
Support
for
OS/390.
The
terms
MVS™,
OS/390,
and
z/OS™
are
used
interchangeably
throughout
this
book.
Who
should
read
this
book
The
Accounting
Feature
for
the
Host
is
for:
v
Anyone
who
is
going
to
install
or
use
the
Accounting
feature.
v
Data
processing
accounting
personnel
who
use
the
Accounting
feature
to
produce
reports
or
who
bill
the
customers
of
a
data
processing
center.
v
Administrators
who
wish
to
get
information
about
the
log
records
generated
by
the
producing
systems.
This
is
important
in
Tivoli
Decision
Support
for
OS/390
applications
for
deciding
which
services
can
be
charged
for
and
on
what
basis
the
charges
should
be
made.
v
Administrators,
primarily
as
a
guide
to
feature
installation
and
as
a
reference
to
table
and
report
definitions.
v
Users
who
are
interested
in
analyzing
the
Accounting
feature
data.
What
this
book
contains
This
book
contains
two
parts:
v
Use
Part
I,
“Accounting
feature
guide”,
for
an
overview
of
the
Tivoli
Decision
Support
for
OS/390
Accounting
feature
and
as
a
guide
to
using
it.
–
Chapter
1,
“Overview
of
the
Accounting
feature”
contains
an
overview
of
the
feature
and
gives
an
example
of
how
you
can
use
it.
–
Chapter
2,
“Preparing
the
Accounting
feature”
explains
how
the
Accounting
feature
and
Tivoli
Decision
Support
for
OS/390
work
together.
This
contains
installation
information
and
explains
how
to
work
with
the
Accounting
feature
tables.
–
Chapter
3,
“Implementing
the
Accounting
feature”
explains
the
Accounting
feature
tables.
–
Chapter
4,
“Prorating
overhead
accounts”
explains
how
to
allocate
overhead
costs
on
a
fixed
or
percentage
basis.v
Use
Part
II,
“Accounting
feature
reference”
as
a
reference
while
you
use
the
Accounting
feature.
–
Chapter
5,
“Data
flow”
explains
the
data
flow.
–
Chapter
6,
“Data
tables
and
views”
contains
examples
of
the
data
tables.
–
Chapter
7,
“Lookup
tables”
contains
examples
of
the
lookup
tables.
–
Chapter
8,
“Accounting
feature
translation
tables”
contains
examples
of
the
translation
tables.
–
Chapter
9,
“Accounting
feature
reports”
contains
examples
of
the
Accounting
feature
reports.
vii
–
Chapter
10,
“Considerations
for
dpAM
users”
compares
the
functions
provided
with
the
Tivoli
Decision
Support
for
OS/390
Accounting
feature
with
those
provided
with
dp
Accounting
Manager
(dpAM).
A
list
of
abbreviations,
glossary
and
index
follow
these
chapters.
Publications
This
section
lists
publications
in
the
Tivoli
Decision
Support
for
OS/390
library
and
any
other
related
documents.
It
also
describes
how
to
access
Tivoli
publications
online
and
how
to
order
Tivoli
publications.
Tivoli
Decision
Support
for
OS/390
library
The
following
documents
are
available
in
the
Tivoli
Decision
Support
for
OS/390
library:
v
Administration
Guide,
SH19-6816
Provides
information
about
initializing
the
Tivoli
Decision
Support
for
OS/390
database
and
customizing
and
administering
Tivoli
Decision
Support
for
OS/390.
v
Guide
to
the
Reporting
Dialog,
SH19-6842
Provides
information
for
users
who
display
existing
reports,
for
users
who
create
and
modify
reports,
and
for
administrators
who
control
reporting
dialog
default
functions
and
capabilities.
v
Language
Guide
and
Reference,
SH19-6817
Provides
information
for
adminstrators,
performance
analysts,
and
programmers
who
are
responsible
for
maintaining
system
log
data
and
reports.
v
User’s
Guide
for
the
Viewer,
SH19-4517
Provides
information
about
how
use
the
graphical
interface
for
Tivoli
Decision
Support
for
OS/390.
v
Messages
and
Problem
Determination,
SH19-6902
Provides
information
to
help
operators
and
system
programmers
understand,
interpret,
and
respond
to
Tivoli
Decision
Support
for
OS/390
messages
and
codes.
v
Accounting
Feature
for
the
Host,
SH19-4495
Provides
information
for
users
who
want
to
use
Tivoli
Decision
Support
for
OS/390
to
collect
and
report
performance
data
generated
by
the
Accounting
feature.
v
Accounting
Feature
for
the
Workstation,
SH19-4516
Provides
information
for
users
who
want
to
use
the
Accounting
Workstation
Option
to
manage,
process,
and
analyze
financial
data
on
a
workstation.
v
AS/400
System
Performance
Feature
Guide
and
Reference,
SH19-4019
Provides
information
for
administrators
and
users
about
collecting
and
reporting
performance
data
generated
by
AS/400®
systems.
v
CICS
Performance
Feature
Guide
and
Reference,
SH19-6820
Provides
information
for
administrators
and
users
about
collecting
and
reporting
performance
data
generated
by
Customer
Information
and
Control
System
(CICS®).
v
Distributed
Systems
Performance
Feature
Guide
and
Reference,
SH19-4018
viii
Tivoli
Decision
Support
for
OS/390:
Accounting
Feature
for
the
Host
Provides
information
for
administrators
and
users
about
collecting
and
reporting
performance
data
generated
byoperating
systems
and
applications
running
on
a
workstation.
v
IMS
Performance
Feature
Guide
and
Reference,
SH19-6825
Provides
information
for
administrators
and
users
about
collecting
and
reporting
performance
data
generated
by
Information
Management
System
(IMS™).
v
Network
Performance
Feature
Installation
and
Administration,
SH19-6901
Provides
information
for
network
analysts
or
programmers
who
are
responsible
for
setting
up
the
network
reporting
environment.
v
Network
Performance
Feature
Reference,
SH19-6822
Provides
information
for
network
analysts
or
programmers
who
are
responsible
for
setting
up
the
network
reporting
environment.
v
Network
Performance
Feature
Reports,
SH19-6821
Provides
information
for
network
analysts
or
programmers
who
use
the
Network
Performance
feature
reports.
v
System
Performance
Feature
Guide,
SH19-6818
Provides
information
for
performance
analysts
and
system
programmers
who
are
responsible
for
meeting
the
service-level
objectives
established
in
your
organization.
v
System
Performance
Feature
Reference
Vol.
I,
SH19-6819
Provides
information
for
administrators
and
users
with
a
variety
of
backgrounds
who
want
to
use
Tivoli
Decision
Support
for
OS/390
to
analyze
Multiple
Virtual
Storage
(MVS)
or
Virtual
Machine
(VM)
performance
data.
v
System
Performance
Feature
Reference
Vol.
II,
SH19-4494
Provides
information
for
administrators
and
users
with
a
variety
of
backgrounds
who
want
to
use
Tivoli
Decision
Support
for
OS/390
to
analyze
Multiple
Virtual
Storage
(MVS)
or
Virtual
Machine
(VM)
performance
data.
v
IBM
Online
Library
Omnibus
Edition
OS/390
Collection
Kit,
SK3T-4270
CD
containing
all
OS/390
documentation.
v
IBM
Online
Library
z/OS
Software
ProductsCollection
Kit,
SK2T-6012
CD
containing
all
z/OS
documentation.
Using
LookAt
to
look
up
message
explanations
LookAt
is
an
online
facility
that
lets
you
look
up
explanations
for
most
messages
you
encounter,
as
well
as
for
some
system
abends
and
codes.
Using
LookAt
to
find
information
is
faster
than
a
conventional
search
because
in
most
cases
LookAt
goes
directly
to
the
message
explanation.
You
can
access
LookAt
from
the
Internet
at:
http://www.ibm.com/eserver/zseries/zos/bkserv/lookat/
or
from
anywhere
in
z/OS
or
z/OS.e
where
you
can
access
a
TSO/E
command
line
(for
example,
TSO/E
prompt,
ISPF,
z/OSUNIX®
System
Services
running
OMVS).
The
LookAt
Web
site
also
features
a
mobile
edition
of
LookAt
for
devices
such
as
PCs,
Palm
OS,
or
Linux-based
handhelds.
So,
if
you
have
a
handheld
device
with
wireless
access
and
an
Internet
browser,
you
can
now
access
LookAt
message
information
from
almost
anywhere.
Preface
ix
Accessing
publications
online
IBM
posts
publications
for
this
and
all
other
Tivoli
products,
as
they
become
available
and
whenever
they
are
updated,
to
the
Tivoli
Software
Information
Center
Web
site.
The
Tivoli
Software
Information
Center
is
located
at
the
following
Web
address:
http://publib.boulder.ibm.com/tividd/td/tdprodlist.html
Click
the
Tivoli
Decision
Support
for
OS/390
link
to
access
the
product
library.
These
publications
are
available
in
or
HTML
format,
or
both.
Translated
documents
are
also
available
for
some
products.
Note:
If
you
documents
on
other
than
letter-sized
paper,
select
the
Fit
to
page
check
box
in
the
Adobe
Acrobat
dialog.
This
option
is
available
when
you
click
File
”
Print.
Fit
to
page
ensures
that
the
full
dimensions
of
a
letter-sized
page
on
the
paper
that
you
are
using.
Ordering
Publications
You
can
order
many
Tivoli
publications
online
at
the
following
Web
site:
http://www.elink.ibmlink.ibm.com/public/applications/publications/
cgibin/pbi.cgi
You
can
also
order
by
telephone
by
calling
one
of
these
numbers:
v
In
the
United
States:
800-879-2755
v
In
Canada:
800-426-4968
In
other
countries,
see
the
following
Web
site
for
a
list
of
telephone
numbers:
http://www.ibm.com/software/tivoli/order-lit/
Accessibility
Accessibility
features
help
users
with
a
physical
disability,
such
as
restricted
mobility
or
limited
vision,
to
use
software
products
successfully.
With
this
product,
you
can
use
assistive
technologies
to
hear
and
navigate
the
interface.You
can
also
use
the
keyboard
instead
of
the
mouse
to
operate
all
features
of
the
graphical
user
interface.
For
additional
information,
see
the
Accessibility
Appendix
in
the
Administration
Guide.
Contacting
software
support
If
you
have
a
problem
with
any
Tivoli
product,
refer
to
the
following
IBM
Software
Support
Web
site:
http://www.ibm.com/software/sysmgmt/products/support/
If
you
want
to
contact
software
support,
see
the
IBM
Software
Support
Guide
at
the
following
Web
site:
http://techsupport.services.ibm.com/guides/handbook.html
The
guide
provides
information
about
how
to
contact
IBM
Software
Support,
depending
on
the
severity
of
your
problem,
and
the
following
information:
x
Tivoli
Decision
Support
for
OS/390:
Accounting
Feature
for
the
Host
v
Registration
and
eligibility
v
Telephone
numbers
and
addresses,
depending
on
the
country
in
which
you
are
located
v
Information
you
must
have
before
contacting
IBM
Software
Support
Note:
For
Tivoli
NetView®
for
OS/390
customers
only,
additional
support
is
available
on
the
NETVIEW
CFORUM
(Customer
Forum)
through
the
IBM
Link
system.
This
forum
is
monitored
by
NetView
developers
who
answer
questions
and
provide
guidance.
When
a
problem
with
the
code
is
found,
you
are
asked
to
open
an
official
problem
management
record
(PMR)
to
obtain
resolution.
Conventions
used
in
this
book
This
guide
uses
several
conventions
for
special
terms
and
actions,
operating
system-dependent
commands
and
paths,
and
margin
graphics.
Typeface
conventions
This
guide
uses
the
following
typeface
conventions:
Bold
v
Lowercase
commands
and
mixed
case
commands
that
are
otherwise
difficult
to
distinguish
from
surrounding
text
v
Interface
controls
(check
boxes,
push
buttons,
radio
buttons,
spin
buttons,
fields,
folders,
icons,
list
boxes,
items
inside
list
boxes,
multicolumn
lists,
containers,
menu
choices,
menu
names,
tabs,
property
sheets),
labels
(such
as
Tip:,
and
Operating
system
considerations:)
v
Column
headings
in
a
table
v
Keywords
and
parameters
in
text
Italic
v
Citations
(titles
of
books,
diskettes,
and
CDs)
v
Words
defined
in
text
v
Emphasis
of
words
(words
as
words)
v
Letters
as
letters
v
New
terms
in
text
(except
in
a
definition
list)
v
Variables
and
values
you
must
provide
Monospace
v
Examples
and
code
examples
v
File
names,
programming
keywords,
and
other
elements
that
are
difficult
to
distinguish
from
surrounding
text
v
Message
text
and
prompts
addressed
to
the
user
v
Text
that
the
user
must
type
v
Values
for
arguments
or
command
options
Preface
xi
xii
Tivoli
Decision
Support
for
OS/390:
Accounting
Feature
for
the
Host
Part
1.
Accounting
feature
guide
Chapter
1.
Overview
of
the
Accounting
feature
.
. 3
Collecting
usage
data
.
.
.
.
.
.
.
.
.
.
. 3
Producing
billing
information
.
.
.
.
.
.
.
.
. 3
Setting
prices
.
.
.
.
.
.
.
.
.
.
.
.
. 4
Output
from
the
Accounting
feature
.
.
.
.
. 4
Working
with
the
Accounting
feature—an
example
4
Considerations
.
.
.
.
.
.
.
.
.
.
.
.
.
. 5
Customers
and
accounts
.
.
.
.
.
.
.
.
. 6
Billing
units
.
.
.
.
.
.
.
.
.
.
.
.
. 6
Prices
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 7
Chapter
2.
Preparing
the
Accounting
feature
.
.
. 9
How
the
Accounting
feature
works
.
.
.
.
.
.
. 9
Setting
up
security
.
.
.
.
.
.
.
.
.
.
.
. 10
Trimming
the
data
tables
.
.
.
.
.
.
.
.
.
. 10
Installing
the
Accounting
component
.
.
.
.
.
. 11
Maintaining
the
lookup
tables
.
.
.
.
.
.
.
. 11
Workload
period
and
special
day
tables
.
.
.
. 12
DCOLLECT
LAST_RUN
lookup
table
.
.
.
. 12
Network
resource
translation
table
.
.
.
.
. 13
Preparing
for
collect
.
.
.
.
.
.
.
.
.
.
. 13
Chapter
3.
Implementing
the
Accounting
feature
15
Understanding
Accounting
feature
tables
.
.
.
. 15
Table
types
.
.
.
.
.
.
.
.
.
.
.
.
.
. 15
Data
tables
.
.
.
.
.
.
.
.
.
.
.
.
. 16
Summary
tables
.
.
.
.
.
.
.
.
.
.
.
. 16
Lookup
tables
.
.
.
.
.
.
.
.
.
.
.
. 16
Views
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 16
Chapter
4.
Prorating
overhead
accounts
.
.
.
. 17
DRLJPROR
sample
job
.
.
.
.
.
.
.
.
.
. 18
Distributing
overhead
accounts
based
on
fixed
percentages
.
.
.
.
.
.
.
.
.
.
.
.
. 19
Distributing
overhead
accounts
based
on
relative
percentages
.
.
.
.
.
.
.
.
.
.
.
.
. 20
1
2
Tivoli
Decision
Support
for
OS/390:
Accounting
Feature
for
the
Host
Chapter
1.
Overview
of
the
Accounting
feature
The
Tivoli
Decision
Support
for
OS/390
Accounting
feature
is
designed
to
meet
the
requirements
of
both
the
independent
data
processing
center
that
offers
services
to
external
clients,
and
the
DP
department
that
is
part
of
a
large
organization
offering
services
to
internal
departments
in
the
same
organization.
The
Accounting
feature
helps
you
run
your
DP
center
either
as
a
cost
center,
distributing
the
budgeted
costs
equitably
among
the
defined
customers,
or
as
a
profit
center,
with
the
focus
on
prices,
revenue,
cost,
and
profit.
The
complex
process
of
distributing
data
processing
costs
often
confuses
the
users,
who
find
it
difficult
to
relate
the
billed
costs
to
the
services
provided.
You
can
use
the
flexible
pricing
and
billing
options
of
the
Tivoli
Decision
Support
for
OS/390
Accounting
feature
to
provide
the
customers
of
your
data
processing
center
with
a
better
understanding
of
their
data
processing
costs,
thus
enabling
them
to
manage
their
use
of
DP
services
more
efficiently.
The
billing
records
provided
by
the
Accounting
feature
can
be
forwarded
to
your
existing
invoicing
system,
thus
helping
you
to
integrate
the
financial
management
of
your
DP
center
with
your
corporate
financial
systems.
The
Accounting
feature
provides
you
with
the
means
to
successfully
manage
the
business
aspects
of
DP
across
the
entire
enterprise.
The
data
is
stored
in
a
DB2®
relational
database,
and
QMF™
or
an
equivalent
DB2
query
program
can
be
used
to
create
standard
reports.
In
addition,
you
can
use
QMF
or
another
report
writer
to
generate
your
own
reports,
using
the
SQL
statements
supplied
with
the
Accounting
feature
as
a
model.
Collecting
usage
data
With
the
Accounting
feature
you
can
collect
and
summarize
the
usage
data
from
each
of
your
subsystems.
For
all
usage
data,
the
Accounting
feature
determines:
v
The
workload
period
(for
example,
first
shift).
You
can
define
workload
periods
based
on
the
time
of
day,
the
day
of
the
week,
and
whether
a
day
is
a
holiday.
v
The
account
that
should
be
charged.
You
can
specify
which
values
in
the
usage
logs
correspond
to
each
account.
If
your
DP
center
has
more
than
one
processor,
you
can
specify
normalization
factors
to
account
for
different
processor
speeds.
The
Accounting
feature
then
records
both
the
number
of
CPU
seconds
used
and
the
number
of
normalized
CPU
seconds.
Producing
billing
information
You
first
define
the
billing
periods
for
which
customers
will
be
billed.
For
example,
the
billing
periods
could
be
January
1998,
February
1998,
and
so
on.
You
have
to
specify
a
start
date
and
an
end
date
for
each
billing
period.
For
each
billing
period,
customers
are
charged
according
to
their
level
of
system
usage.
You
specify
which
measurement
units
are
used.
For
example,
you
can
use
basic
resource
units
such
as
CPU
seconds,
for
resource
billing,
or
functional
units
such
as
CICS
transactions,
for
functional
billing.
You
can
use
the
default
measurement
units
or
define
your
own.
3
When
you
have
defined
your
measurement
units,
you
can
define
billing
units.
Your
billing
units
can
be
the
same
as
your
measurement
units,
or
more
complex.
For
example,
you
can
create
one
billing
unit
for
CPU
seconds
during
the
day
and
another
billing
unit
for
CPU
seconds
at
night.
You
can
also
base
your
billing
units
on
factors
like
job
class
and
priority.
You
can
use
the
default
billing
units
or
define
your
own.
Each
customer
is
billed
according
to
the
quantity
of
each
billing
unit
that
is
used,
and
the
prices
and
discounts
that
you
specify
for
that
billing
unit.
You
can
also
supplement
the
usage
logs
by
specifying
recurrent
charges
and
occasional
charges
and
refine
your
accounting
records
with
corrections,
credits,
and
reconciliation
amounts.
Setting
prices
You
specify
the
price
of
each
billing
unit
by
creating
price
lists.
In
each
price
list,
you
can
specify
the
price
for
each
billing
unit
in
two
different
currencies
(for
example,
dollars
and
euros).
You
can
create
a
single
price
list
to
use
for
all
customers
or
create
a
different
price
list
for
individual
customers
or
each
category
of
customers.
Output
from
the
Accounting
feature
You
can
get
both
detailed
reports
and
summaries
from
the
Accounting
feature.
You
can
use
the
predefined
report
definitions
that
are
included
with
the
Accounting
feature
to
produce
standard
reports
in
either
QMF
or
an
equivalent
DB2
query
program.
You
can
also
define
your
own
reports
from
the
information
in
the
Accounting
feature
DB2
database
by
writing
new
QMF
procedures
or
by
using
an
equivalent
product.
From
the
Accounting
feature
billing
data,
you
can
extract
billing
records
to
be
used
by
your
DP
center’s
invoicing
system.
A
billing
record
specifies
the
total
charge
for
a
customer’s
use
of
DP
services
during
a
specified
period.
Each
billing
record
has
a
related
billing
specification
that
contains
detailed
information
about
the
bill.
Working
with
the
Accounting
feature—an
example
Ace
Inc.
is
a
manufacturing
company.
As
a
result
of
rationalization
and
consolidation,
it
possesses
more
computer
resources
than
it
needs
for
its
manufacturing
process
and
company
administration.
The
data
processing
department
of
Ace
Inc.
has
for
some
time
provided
computer
services
to
external
customers.
The
financial
department
of
Ace
Inc.
is
concerned
that
the
computer
department
is
responsible
for
a
considerable
portion
of
the
internal
budget,
but
there
is
very
little
control
over
the
contribution
of
different
DP
services.
The
DP
manager
believes
that
the
external
customers
are
profitable,
and
that
investments
in
new
applications
would
be
worthwhile.
As
a
result
of
discussions
between
the
financial
department
and
the
DP
department,
Ace
Inc.
decides
to
implement
a
new
DP
accounting
policy
using
the
Accounting
feature.
The
DP
department
will
first
test
the
Accounting
feature
with
internal
customers
and
later
extend
the
test
to
include
external
customers.
The
producing
systems
used
by
Ace
Inc.
are
all
predefined
to
the
Accounting
feature.
The
program
administrator
decides
to
use
the
default
values
provided.
Overview
of
the
Accounting
feature
4
Tivoli
Decision
Support
for
OS/390:
Accounting
Feature
for
the
Host
Each
department
of
Ace
Inc.
is
defined
to
the
Accounting
feature
as
a
customer.
Some
departments
have
several
accounts;
other
departments
have
only
one.
The
terminal
ID
and
user
ID
for
each
log
record
determine
which
account
is
charged.
The
program
administrator
decides
to
use
some
of
the
default
measurement
units
defined
for
the
different
producing
systems.
The
DP
manager
wants
to
charge
different
prices
for
day
service
and
night
service.
Two
service
types
(DAY
and
NIGHT)
are
defined.
Each
billing
unit
consists
of
a
measurement
unit
and
one
of
the
two
service
types.
The
DP
manager
decides
to
try
three
different
price
lists:
v
If
Ace
Inc.
decides
to
practice
resource
billing,
CPU
seconds
can
be
defined
as
a
unit
for
billing
with
a
fixed
price
per
second.
v
Alternatively,
using
functional
billing,
a
price
can
be
set
for
each
transaction
ID
based
on
the
average
number
of
CPU
seconds
used
for
that
transaction.
v
By
using
service
billing,
prices
can
also
be
set
for
a
combination
of
billing
units
and
service
types.
The
different
price
lists
are
tested
on
this
log
data.
Considerations
The
purpose
of
the
Accounting
feature
is
to
help
you
bill
customers
for
computer
services.
To
do
this,
the
Accounting
feature
needs
to
know:
v
Whom
you
want
to
bill
(your
customers
and
accounts)
v
What
you
want
to
bill
for
(your
billing
units)
v
How
much
you
want
to
charge
for
each
billing
unit
(your
prices)
v
How
to
find
out
which
customer
used
which
service
and
when
Most
of
this
information
is
contained
in
logs
that
are
produced
by
the
various
computer
systems
that
a
customer
uses.
The
computer
systems
that
produce
these
logs
are
called
producing
systems.
With
this
information,
the
Accounting
feature
can
produce
billing
records
for
each
customer.
The
Accounting
feature
can
work
with
three
types
of
computer-usage
information:
v
Logs
produced
by
computer
systems
such
as
Customer
Information
Control
System
(CICS).
Each
time
the
system
is
used,
a
record
(containing
information
such
as
account
number,
time
stamp,
and
number
of
CPU
seconds
used)
is
added
to
the
log.
v
Snapshots
showing
resource
usage
at
a
particular
moment.
For
example,
you
could
take
a
weekly
snapshot
of
the
amount
of
DASD
used
by
each
account.
v
Information
that
is
not
contained
in
logs
or
snapshots.
For
example,
you
might
want
to
charge
customers
for
education.
You
can
enter
this
information
in
the
Accounting
feature
directly.
The
basic
function
of
the
Accounting
feature
can
thus
be
summarized
as
follows:
Input
Producing
system
summary
tables
Output
Billing
records
Processing
Using
the
information
that
you
provide
(such
as
customers,
billing
units,
and
prices),
transform
the
producing
system
summary
tables
into
billing
records
Overview
of
the
Accounting
feature
Chapter
1.
Overview
5
Customers
and
accounts
You
must
provide
the
following
information
to
the
Accounting
feature:
v
Which
customers
you
want
to
bill
v
Which
accounts
correspond
to
each
customer
v
Which
column
or
combination
of
columns
in
each
producing
system
log
identifies
the
account
You
can
also
define
certain
expenses
as
overheads
to
be
distributed
among
various
customers.
Billing
units
A
billing
unit
is
any
unit
that
you
use
to
bill
customers.
You
can
bill
customers
at
a
resource
level
or
a
functional
level.
Billing
customers
at
a
functional
level
is
called
functional
billing.
If
you
bill
customers
at
a
resource
level,
each
billing
unit
will
fall
into
one
of
these
categories:
v
A
column
in
a
producing
system
summary
table
(a
base
measurement
unit,
or
BMU).
For
example,
the
number
of
CPU
seconds.
v
A
BMU
combined
with
a
service
type.
For
example,
the
number
of
CPU
seconds
during
the
day
shift.
v
A
BMU
combined
with
more
than
one
service
type.
For
example,
the
number
of
CPU
seconds
during
the
day
shift
for
jobs
with
priority
1.
If
you
bill
customers
at
a
functional
level,
you
can
also
define
the
following
types
of
billing
units:
v
A
column
combined
with
a
specific
value
in
another
column
(a
derived
measurement
unit,
or
DMU).
For
example,
the
number
of
CICS
transactions
when
TRANS
is
TXN1.
A
billing
unit
that
uses
a
DMU
by
itself
is
similar
to
a
billing
unit
that
uses
a
BMU
combined
with
one
service
type.
You
should
use
the
DMU
construct
rather
than
the
service
type
when
you
want
to
avoid
double
charging
at
both
the
functional
and
resource
levels.
v
A
DMU
combined
with
one
or
more
service
types.
For
example,
the
number
of
CICS
transactions
when
TRANS
is
TXN1
during
the
day
shift.
If
you
decide
to
use
service
types
that
are
related
to
time,
you
specify
when
each
shift
begins
and
ends,
and
which
days
of
the
year
are
holidays
for
your
organization.
Overview
of
the
Accounting
feature
6
Tivoli
Decision
Support
for
OS/390:
Accounting
Feature
for
the
Host
Prices
You
must
specify
the
price
for
each
billing
unit
in
a
price
list.
In
the
price
list,
you
can
specify
the
price
for
each
billing
unit
in
two
different
currencies
(for
example,
dollars
and
euros).
You
can
specify
one
price
list
that
applies
to
all
customers,
or
specify
different
price
lists
for
different
customers.
You
can
also
specify
discounts
based
on
the
volume
of
service
that
a
customer
uses.
Overview
of
the
Accounting
feature
Chapter
1.
Overview
7
8
Tivoli
Decision
Support
for
OS/390:
Accounting
Feature
for
the
Host
Chapter
2.
Preparing
the
Accounting
feature
Tivoli
Decision
Support
for
OS/390
is
a
base
product
with
separate
add-on
features.
Each
feature
includes
a
number
of
components,
which
themselves
consist
of
the
object
definitions
required
to
collect
and
report
on
a
given
set
of
data.
How
the
Accounting
feature
works
The
Accounting
feature
of
Tivoli
Decision
Support
for
OS/390
consists
of
one
component
with
multiple
subcomponents.
Each
subcomponent
corresponds
to
a
single
subsystem
data
source.
Some
object
definitions
used
for
the
Accounting
feature
are
included
with
the
Tivoli
Decision
Support
for
OS/390
base
product,
while
the
remainder
are
shipped
when
the
feature
is
ordered.
The
Accounting
feature
has
as
a
prerequisite
that
you
have
installed
the
other
Tivoli
Decision
Support
for
OS/390
features
on
which
you
want
to
perform
accounting.
The
Accounting
feature
is
installed
in
the
same
manner
as
other
Tivoli
Decision
Support
for
OS/390
components
and
the
data
is
collected
during
normal
execution
of
a
Tivoli
Decision
Support
for
OS/390
collect
job.
Each
subcomponent
in
the
Accounting
component
is
made
up
of
the
following
set
of
object
definitions:
v
A
log
definition
(some
components
use
more
than
one
log
definition
to
accommodate
multiple
release
levels).
v
One
or
more
record
definitions.
Each
log
contains
one
or
more
record
types.
v
One
record
procedure
definition
in
component
parts
CICS
and
DASD
and
two
log
and
record
procedure
definitions
for
IMS.
v
A
lookup
table
for
account
translation.
The
NPM
and
NETV
component
parts
have
a
second
lookup
table
for
resource
name
translation.
The
DASD,
HSMBKUP,
and
HSMMIGR
component
parts
have
a
second
lookup
table
to
prevent
collect
being
done
twice
on
the
same
day
for
the
same
system
ID
and
DCOLLECT
record
type.
v
A
data
table.
The
BATCH,
STC,
and
TSO
component
parts
each
have
a
second
data
table
to
hold
intermediate
data
during
collect.
v
One
or
more
update
definitions.
The
update
definition
contains
the
instructions
for
summarizing
the
log
data
in
the
Tivoli
Decision
Support
for
OS/390
data
tables.
Log
definitions,
record
definitions,
log
procedures,
and
record
procedures
for
all
predefined
subsystems
are
shipped
with
Tivoli
Decision
Support
for
OS/390.
These
definitions
are
outlined
in
the
Administration
Guide
which
contains
references
to
the
detailed
descriptions
of
the
log
records
in
the
subsystem
manuals.
You
can
use
the
standard
Tivoli
Decision
Support
for
OS/390
workload
period
table,
PERIOD_PLAN,
for
the
Accounting
component,
as
described
in
“Workload
period
and
special
day
tables”
on
page
12.
All
subsystems
use
the
workload
period
table.
CPU
utilization
figures
are
not
normalized
in
data
tables
belonging
to
other
Tivoli
Decision
Support
for
OS/390
features.
The
same
is
true
for
the
collection
tables
used
for
individual
subsystems
in
the
Accounting
component.
9
CPU
normalization
is
performed
during
data
collection
in
the
Accounting
component
and
normalized
CPU
seconds
are
stored
in
the
USE_SUMMARY_D
and
BILLED_DATA
tables.
The
collect
process
uses
the
resource
accounting
CPU
normalization
lookup
table,
CPU_NORMAL_DATA,
which
you
update
through
the
Tivoli
Decision
Support
for
OS/390
dialog.
All
subsystems
that
support
CPU
normalization
use
this
normalization
table.
The
account
translation
lookup
tables
are
maintained
within
Tivoli
Decision
Support
for
OS/390.
Setting
up
security
Before
you
install
the
Accounting
feature
in
Tivoli
Decision
Support
for
OS/390,
you
must
have
the
requisite
authority
to
do
so.
The
system
tables
in
Tivoli
Decision
Support
for
OS/390
have
a
default
authorization
ID
of
DRLSYS
and
the
other
tables
a
default
authorization
ID
of
DRL.
The
system
tables
include
information
about
what
components
are
available
for
installation,
and
the
other
tables
include
all
data
and
lookup
tables.
Access
to
these
tables
is
controlled
through
the
RACF®
user
groups
DRL,
DRLSYS,
and
DRLUSER,
by
default.
To
install
the
Accounting
feature
in
Tivoli
Decision
Support
for
OS/390,
you
should
first
connect
the
installer’s
user
ID
to
the
RACF
groups
DRLSYS
and
DRL.
You
must
also
grant
DBADM
authority
at
the
database
level.
For
additional
information
on
the
SQL
GRANT
statement,
see
the
Administration
Guide.
If
you
want
to
grant
access
to
these
tables
to
other
user
groups,
or
to
individual
user
IDs,
you
must
type
their
values
in
the
appropriate
fields
of
the
Tivoli
Decision
Support
for
OS/390
dialog
parameters
screen.
Further
details
about
Tivoli
Decision
Support
for
OS/390
authorization
procedures
are
given
in
the
Administration
Guide.
Trimming
the
data
tables
If
you
do
not
plan
to
use
all
the
columns
in
a
resource
accounting
data
table
for
billing,
you
can
trim
the
corresponding
resource
accounting
data
tables
before
installing
the
Accounting
feature
in
Tivoli
Decision
Support
for
OS/390
by
removing
column
definitions.
This
should
improve
the
performance
of
the
collect
process
and
save
some
space
in
the
resource
accounting
data
tables.
If
you
decide
to
remove
column
definitions
from
the
resource
accounting
data
tables,
you
should
be
familiar
with
the
Tivoli
Decision
Support
for
OS/390
log
collector
language,
described
in
the
Language
Guide
and
Reference
To
trim
the
resource
accounting
data
tables,
edit
the
member
that
contains
the
resource
accounting
object
definition
for
the
subsystem
that
you
want
to
trim.
These
members
are
in
the
Tivoli
Decision
Support
for
OS/390
component
library,
called
DRL160.SDRLDEFS,
by
default.
The
members
for
each
component
and
their
location
are
shown
in
Table
1.
Table
1.
List
of
members
and
their
location
Component
Member
Name
Table
Translation
Batch
DRLTBAT
RAFJPOBLOG
RAFBATCH
RAFABATCH
CICS
DRLTCICS
RAFCICS
RAFACICS
DASD
DRLTDASD
RAFDASD
RAFADASD
Preparing
the
Accounting
feature
10
Tivoli
Decision
Support
for
OS/390:
Accounting
Feature
for
the
Host
Table
1.
List
of
members
and
their
location
(continued)
Component
Member
Name
Table
Translation
DB2
DRLTDB2
RAFDB2
RAFADB2
HSMBKUP
DRLTHSMB
RAFHSMBKUP
RAFAHSMBKUP
HSMMIGR
DRLTHSMM
RAFHSMMIGR
RAFAHSMMIGR
IMS
DRLTIMS
RAFIMS
RAFAIMS
NPM
DRLTNPM
RAFNETSES20
RAFNETSES4X
RAFANETSESM
NETV
DRTLTNETV
RAFNETV
RAFANETV
STC
DRLTSTC
RAFSTC
RAFADDRLOG
RAFASTC
TSO
DRLTTSO
RAFSESLOG
RAFTSO
RAFATSO
There
are
also
some
important
rules
that
you
should
be
aware
of:
v
You
must
ensure
that
columns
removed
from
the
tables
are
not
referenced
by
any
update
definitions.
v
In
the
case
of
normalized
CPU
seconds,
these
rules
apply:
–
If
a
resource
accounting
data
table
contains
a
CPU
usage
row
for
a
given
SMF
ID
and
a
matching
SMF
ID
exists
in
the
lookup
table
CPU_NORMAL_DATA,
then
the
CPU
usage
is
normalized
by
dividing
the
actual
CPU
seconds
used
by
the
normalization
value
in
CPU_NORMAL_DATA.
–
If
a
resource
accounting
data
table
contains
a
CPU
usage
row
for
a
given
SMF
ID
and
a
matching
SMF
ID
does
not
exist
in
the
lookup
table
CPU_NORMAL_DATA,
then
normalization
does
not
take
place
and
the
actual
CPU
seconds
are
carried
through
to
all
tables.
Installing
the
Accounting
component
Before
you
can
install
the
Accounting
component
in
Tivoli
Decision
Support
for
OS/390,
you
must
have
installed
the
Accounting
feature.
See
"Installing
a
Component"
in
the
Administration
Guide.
Maintaining
the
lookup
tables
After
you
have
installed
the
Accounting
component
in
Tivoli
Decision
Support
for
OS/390,
you
will
need
to
maintain
the
lookup
tables
used
by
the
component.
These
are:
v
The
period
and
special
day
tables
v
The
DFSMS_LAST_RUN
table
for
DASD,
HSMBKUP,
and
HSMMIGR
v
The
network
resource
translation
table
for
NPM
and
NETV
v
The
account
translation
lookup
tables
for
each
subsystem
v
The
billing
period
table
v
The
customer
table
v
The
account
table
v
The
account
proration
table
v
The
credit/debit
table
v
The
CPU
normalization
table
v
The
price
list
table
Preparing
the
Accounting
feature
Chapter
2.
Preparation
11
The
period
and
special
day
tables
are
shipped
as
part
of
the
Tivoli
Decision
Support
for
OS/390
base
code.
If
both
tables
were
customized
during
the
initial
product
installation,
then
the
Accounting
component
will
use
the
values
typed
in
at
that
time.
You
must
install
the
DFSMS
component
of
Tivoli
Decision
Support
for
OS/390
to
enable
the
Accounting
component
to
use
the
existing
DFSMS_LAST_RUN
table.
You
must
install
the
network
components
of
Tivoli
Decision
Support
for
OS/390
to
enable
the
Accounting
component
to
use
the
network
resource
translation
table.
Workload
period
and
special
day
tables
Tivoli
Decision
Support
for
OS/390
has
tables
that
define
workload
periods
(shifts).
They
are
called
PERIOD_PLAN
and
SPECIAL_DAY.
The
Tivoli
Decision
Support
for
OS/390
collect
process
will
reference
these
tables.
To
edit
the
Tivoli
Decision
Support
for
OS/390
tables:
1.
Select
Tables
from
the
Tivoli
Decision
Support
for
OS/390
Administration
window.
2.
Select
the
SPECIAL_DAY
table
(do
not
press
Enter).
3.
Select
Edit
from
the
menu
bar
and
update
the
table
with
data
for
these
columns:
DATE
DAY_TYPE
4.
Select
Tables
from
the
Tivoli
Decision
Support
for
OS/390
Administration
window.
5.
Select
the
PERIOD_PLAN
table
(do
not
press
Enter).
6.
Select
Edit
from
the
menu
bar
and
update
the
table
with
data
for
these
columns:
PERIOD_PLAN_ID
END_TIME
DAY_TYPE
PERIOD_NAME
START_TIME
The
PERIOD_PLAN_ID
must
be
%
or
a
more
specific
value
that
will
match
the
SMF
ID
of
the
data
collected
in
to
the
Accounting
component.
The
DAY_TYPE
must
be
’MON’,
’TUE’,
’WED’,
’THU’,
’FRI’,
’SAT’,
or
’SUN’
or
a
value
that
you
typed
in
the
SPECIAL_DAY
table.
If
you
want
your
workload
periods
to
be
continuous,
the
END_TIME
of
one
period
must
equal
the
START_TIME
of
another.
DCOLLECT
LAST_RUN
lookup
table
Because
DASD,
HSMBKUP,
and
HSMMIGR
are
snapshot
subsystems,
it
is
important
that
you
do
not
collect
data
for
the
same
resources
twice
on
the
same
day.
Tivoli
Decision
Support
for
OS/390
helps
you
control
this
through
the
use
of
a
lookup
table
called
DFSMS_LAST_RUN.
Each
time
the
Tivoli
Decision
Support
for
OS/390
collect
is
performed
for
these
component
parts,
this
table
will
be
updated
with
the
date
of
the
DCOLLECT
run
for
each
OS/390
system
ID
and
data
type.
This
control
mechanism
also
means
that
you
cannot
run
Tivoli
Decision
Support
for
OS/390
collects
for
these
component
parts
out
of
sequence.
That
is,
you
cannot
collect
for
June
21,
1997
after
you
collect
for
June
22,
1997.
Preparing
the
Accounting
feature
12
Tivoli
Decision
Support
for
OS/390:
Accounting
Feature
for
the
Host
Network
resource
translation
table
If
you
want
to
use
an
application
or
subsystem
ID
when
defining
billing
units
for
the
NPM
or
NETV
subsystem,
you
must
maintain
the
network
resource
translation
table.
This
table
translates
resource
names
used
by
the
subsystem
into
resource
synonyms
or
groups
for
accounting
purposes.
If
you
do
not
maintain
this
table,
the
synonym
and
group
columns
will
be
blank.
This
table
is
described
in
the
Network
Performance
feature
manuals.
You
must
have
the
Tivoli
Decision
Support
for
OS/390
Network
Performance
feature
installed
to
use
the
resource
translation
table
called
NW_RESOURCE.
You
maintain
this
through
the
Tivoli
Decision
Support
for
OS/390
network
administration
dialog,
as
described
in
the
Administration
Guide.
Preparing
for
collect
The
Accounting
component
collects
data
for
each
subsystem
from
the
Tivoli
Decision
Support
for
OS/390
logs
listed
in
Table
2.
Table
2.
Tivoli
Decision
Support
for
OS/390
logs
and
sample
collect
job
for
each
subsystem
Subsystem
Log
name
Sample
collect
job
BATCH
SMF
DRLJCOLL
CICS
SMF
DRLJCOLL
DASD
DCOLLECT
DRLJCOLL
DB2
SMF
DRLJCOLL
HSMBKUP
DCOLLECT
DRLJCOLL
HSMMIGR
DCOLLECT
DRLJCOLL
IMS
IMS_V510_COLLECT
IMS_V610_COLLECT
IMS_V710_COLLECT
DRLJCOIM
NPM
SMF
DRLJCOLL
NETV
SMF
DRLJCOLL
STC
SMF
DRLJCOLL
TSO
SMF
DRLJCOLL
Except
for
the
IMS
component,
to
collect
data
into
Tivoli
Decision
Support
for
OS/390,
you
normally
use
the
sample
batch
job
DRLJCOLL,
supplied
with
the
Tivoli
Decision
Support
for
OS/390
base
product
in
the
DRL160.SDRLCNTL
library
and
described
in
the
Administration
Guide.
As
supplied,
DRLJCOLL
is
set
up
to
collect
data
from
the
SMF
log.
If
you
are
collecting
for
a
subsystem
that
uses
a
different
log,
you
must
change
the
COLLECT
statement
to
read
from
the
correct
log.
You
may
also
need
to
make
some
other
changes,
which
are
described
in
this
section.
Normally,
Tivoli
Decision
Support
for
OS/390
will
collect
data
for
all
update
definitions
that
use
the
same
log
in
one
run.
If
you
want
to
restrict
the
collect
to
just
one
resource
accounting
subsystem,
and
to
exclude
other
subsystems
and
Tivoli
Decision
Support
for
OS/390
components
that
use
the
same
log,
change
the
COLLECT
statement
to
include
the
subsystem
table
only.
For
example,
to
collect
data
for
the
TSO
subsystem
only,
the
COLLECT
statement
could
INCLUDE
the
TSO
data
table
name,
as
follows:
Preparing
the
Accounting
feature
Chapter
2.
Preparation
13
COLLECT
SMF
INCLUDE
&PREFIX.RAFTSO;
For
full
details
of
the
syntax
of
the
Tivoli
Decision
Support
for
OS/390
COLLECT
statement,
refer
to
the
Language
Guide
and
Reference.
While
most
resource
accounting
subsystems
use
the
DRLJCOLL
job
to
collect
data,
the
IMS
subsystem
has
a
different
job,
called
DRLJCOIM.
This
is
supplied
with
the
Tivoli
Decision
Support
for
OS/390
base
product.
This
job
is
described
in
this
section,
along
with
other
information
that
you
must
consider
when
preparing
subsystems
for
collect.
Further
information
about
this
subject
is
provided
in
the
Tivoli
Decision
Support
for
OS/390
feature
manuals,
which
are
available
whether
or
not
you
have
installed
the
Tivoli
Decision
Support
for
OS/390
features
themselves.
Preparing
the
Accounting
feature
14
Tivoli
Decision
Support
for
OS/390:
Accounting
Feature
for
the
Host
Chapter
3.
Implementing
the
Accounting
feature
The
Accounting
feature
uses
computer-usage
information
from
logs
produced
by
computer
systems
such
as
CICS,
SMF
or
IMS.
These
systems
can
be
configured
so
that
each
time
the
system
is
used,
a
record
is
added
to
a
log.
A
log
usually
contains
information
such
as
an
account
number,
a
time
stamp,
and
the
number
of
CPU
seconds.
This
information
is
used
by
the
Accounting
feature
as
the
basis
for
calculating
charges
to
the
consumers
of
these
resources.
The
computer
systems
that
generate
these
logs
are
called
producing
systems.
The
Accounting
feature
collects
logs
from
a
number
of
producing
systems,
processes
the
information
and
stores
it
as
summary
tables
in
its
own
database.
Understanding
Accounting
feature
tables
Tables
in
the
Accounting
feature
database
contain
a
fixed
number
of
predefined
columns
and
a
variable
number
of
rows.
The
number
of
rows
in
each
table
varies
because
rows
are
added
during
data
collection
and
deleted
during
database
maintenance.
If
a
table
is
compared
to
a
sequential
file,
a
row
in
the
table
corresponds
to
a
record
in
the
file,
and
a
column
corresponds
to
a
field
in
the
record.
The
columns
that
contain
identification
data,
such
as
time
stamp
and
system
ID,
are
called
key
columns.
Key
columns
uniquely
identify
a
row
in
a
table.
The
columns
that
contain
measurement
data,
such
as
processor
time,
number
of
jobs,
and
response
times,
are
called
data
columns.
Some
tables
also
contain
computed
columns
(virtual
columns)
that
are
computed
from
the
values
in
other
columns
in
the
same
row.
Computed
columns
are
not
stored
in
the
database.
Figure
1
shows
the
arrangement
of
rows
and
columns
in
part
of
a
collect
feature
summary
table.
Table
types
The
Accounting
feature
database
consists
of
the
following
types
of
tables:
v
Data
tables
v
Summary
tables
v
Lookup
tables
v
System
tables
v
Views
+------------------------------------------------------------------------
Column
name
--
-
YEAR
-
MONTH
-
DAY
-
PERIOD
-
SYSID
-
ACCOUNT
-
...
-
NJOBS
-
CPUSEC
-
+------+-------+-----+--------+-------+---------+-----+-------+--------+-
Row
----------
-
00
-
JAN
-
15
-
P1
-
SYSA
-
ACCT1
-
-
1500
-
20
-
Row
----------
-
00
-
JAN
-
15
-
P1
-
SYSB
-
ACCT2
-
-
700
-
15
-
Row
----------
-
00
-
JAN
-
15
-
P1
-
SYSC
-
ACCT3
-
-
900
-
13
-
+------------------------------------------------------------------------
---------------------
Key
columns
-------------------
----
Data
columns
-
Figure
1.
Partial
view
of
an
RAFBATCH
summary
table
15
During
the
data
collection
process,
the
Accounting
feature
first
reads
the
log
data,
record
by
record,
into
Accounting
feature
data
tables.
The
Accounting
feature
adds
installation-dependent
data
from
lookup
tables,
which
you,
in
turn,
maintain
through
the
dialog.
The
data
collection
process
ends
with
a
summary
of
the
data,
for
example,
by
calculating
the
number
of
jobs
that
were
run
and
storing
the
result
in
summary
tables.
Data
tables
Data
tables
map
the
input
records
that
are
collected
by
the
Accounting
feature.
Data
tables
usually
contain
one
row
for
each
selected
record
from
the
input
log
data.
During
collection,
the
Accounting
feature
checks
to
see
whether
any
lookup
tables
apply
to
the
input
logs.
If
any
do,
it
merges
information
from
these
lookup
tables
with
the
log
data.
Some
collect
processing
uses
assembler
exits
to
process
input
fields
(user
column
computation
exit)
or
the
entire
input
record
(record
build
exit).
Summary
tables
Summary
tables
summarize
data
contained
in
data
tables.
Data
is
summarized
on
a
daily
basis,
and
can
also
be
summarized
by
groups,
such
as
account
ID,
period,
or
transaction
ID.
Lookup
tables
Lookup
tables
hold
user-entered
data
used
for
translating
specific
data
from
the
input
logs
before
it
is
summarized
into
the
summary
tables.
Views
Data
from
one
or
more
summary
tables
can
be
combined.
This
combination
of
data
is
called
a
view.
Use
a
view
when
you
need
to
combine
data
to
produce
a
comprehensive
report.
Views,
like
tables,
have
recorded
names
and
structures.
However,
unlike
tables,
views
cannot
hold
stored
data
and
are
referenced
only
at
reporting
time
when
the
data
from
the
tables
is
merged
in
the
report.
Implementing
the
Accounting
feature
16
Tivoli
Decision
Support
for
OS/390:
Accounting
Feature
for
the
Host
Chapter
4.
Prorating
overhead
accounts
Prorating
is
the
allocation
of
overhead
accounts
to
some
or
all
customers.
You
can
allocate
costs
based
on
fixed
percentages
or
as
variable
percentages
based
on
a
resource
such
as
CPU
usage.
For
example,
when
you
calculate
the
charge
rate
for
CPU
usage,
divide
the
total
cost
that
you
want
to
recover
by
the
amount
of
CPU
used
only
by
the
customers
that
will
be
charged.
By
excluding
the
overhead
use
of
CPU
in
this
rate
calculation,
you
distribute
the
overhead
CPU
usage
to
all
other
users
of
the
CPU.
17
DRLJPROR
sample
job
The
DRLJPROR
sample
job
prorates
overhead
accounts.
To
obtain
an
accurate
view
of
the
costs
by
customer
for
the
current
billing
date,
run
this
job
every
day
after
the
last
collect.
//DRLJPROR
JOB
(ACCT£),’ACC
PROR
JOB’
//***************************************************************
//*
*
//*
LICENSED
MATERIALS
-
PROPERTY
OF
IBM
*
//*
*
//*
5695-101
(C)
COPYRIGHT
IBM
CORPORATION
2003
*
//*
SEE
COPYRIGHT
INSTRUCTIONS.
*
//*
*
//***************************************************************
//*
*
//*
NAME:
DRLJPROR
*
//*
*
//*
STATUS:
TIVOLI
DECISION
SUPPORT
FOR
OS/390
1.6.0
*
//*
*
//*
FUNCTION:
*
//*
ACCOUNT
PRORATION
JOB.
*
//*
*
//*
*
//*
*
//*
*
//*
NOTES:
*
//*
BEFORE
YOU
SUBMIT
THE
JOB
MODIFY
WITH
CORRECT
VALUES:
*
//*
-
THE
TIVOLI
DECISION
SUPPORT
FOR
OS/390
*
//*
DS
NAMES
(DEFAULT=DRL160)
*
//*
-
THE
DB2
DATA
SET
NAMES
(DEFAULT=DSN610)
*
//*
-
THE
DB2
SUBSYSTEM
NAME
(DEFAULT
IS
DSN)
*
//*
AND
SYSTEM
TABLE
PREFIX
(DEFAULT
IS
DRLSYS).
*
//*
-
THE
DB2
PR
TABLE
PREFIX
(DEFAULT
IS
DRL)
*
//*
-
INSERT
THE
CORRECT
BILLING
PERIOD
VALUE
IN
THE
SET
*
//*
CLAUSE
(DEFAULT
IS
1999_12)
*
//*
*
//***************************************************************
//COLLECT
EXEC
PGM=DRLPLC,PARM=(’SYSTEM=DSN
SYSPREFIX=DRLSYS’)
//STEPLIB
DD
DISP=SHR,DSN=DRL160.SDRLLOAD
//
DD
DISP=SHR,DSN=DSN610.SDSNLOAD
//DRLIN
DD
*
SET
BILLING_PERIOD
=
’2000_12’;
RECALCULATE
DRL.USE_SUMMARY_D,
DRL.BILLED_DATA
FROM
DRL.ACCT_PRORATEV2;
//DRLLOG
DD
DUMMY
//DRLOUT
DD
SYSOUT=*,DCB=(RECFM=F,LRECL=80)
//DRLOUT
DD
SYSOUT=*,DCB=(RECFM=F,LRECL=80)
//DRLDUMP
DD
SYSOUT=*,DCB=(RECFM=VB,LRECL=32756)
DRLJPROR
sample
job
18
Tivoli
Decision
Support
for
OS/390:
Accounting
Feature
for
the
Host
Distributing
overhead
accounts
based
on
fixed
percentages
To
distribute
the
cost
of
overhead
accounts
based
on
fixed
percentages:
1.
In
the
ACCOUNT
lookup
table,
type
Y
in
the
OV_FLAG
column
for
each
account
that
is
an
overhead
account.
This
flag
prevents
the
overhead
accounts
from
flowing
to
the
BILLED_DATA
table
until
the
account
distribution
job
is
run.
2.
In
the
ACCT_PRORATE
lookup
table
for
each
customer:
a.
Type
FIXED
in
the
PRORATE_TYPE
column
of
ACCOUNT_ID1.
b.
Type
the
percentage
in
the
PERCENTAGE
column
of
ACCOUNT_ID1.
Percentages
should
total
100%
for
each
overhead
account
that
is
to
be
prorated.3.
If
you
want
to
confirm
that
the
percentages
for
each
account
total
100%,
run
the
RAFA001
resource
accounting
report.
For
more
information
about
the
report,
see
“Prorated
account
percentage
validation
report”
on
page
83.
4.
Customize
the
DRLJPROR
sample
job
for
your
organization:
a.
Change
the
Tivoli
Decision
Support
for
OS/390
data
set
names.
b.
Change
the
DB2
data
set
names.
c.
Change
the
DB2
subsystem
name
and
system
table
prefix.
d.
Change
the
DB2
Tivoli
Decision
Support
for
OS/390
table
prefix.
e.
Change
the
variable
BILLING_PERIOD
in
the
SET
statement
to
the
value
of
the
correct
billing
period.5.
Run
the
customized
DRLJPROR
job.
Distributing
overhead
accounts
based
on
fixed
percentages
Chapter
4.
Prorating
overheads
19
Distributing
overhead
accounts
based
on
relative
percentages
To
distribute
the
cost
of
overhead
accounts
based
on
relative
percentages:
1.
In
the
ACCOUNT
lookup
table,
type
Y
in
the
OV_FLAG
column
for
each
account
that
is
an
overhead
account.
This
flag
prevents
the
overhead
accounts
from
flowing
to
the
BILLED_DATA
table
until
the
account
distribution
job
is
run.
2.
In
the
ACCT_PRORATE
lookup
table,
define
the
distribution
rules.
To
distribute
the
overhead
based
on
the
relative
percentage
of
CPU
usage
for
each
CUSTOMER_ID
that
is
identified
in
the
table:
a.
In
the
PRORATE_TYPE
column
type
CPU.
b.
Leave
the
PERCENTAGE
column
blank.3.
Customize
the
DRLJPROR
sample
job
for
your
organization:
a.
Change
the
Tivoli
Decision
Support
for
OS/390
data
set
names.
b.
Change
the
DB2
data
set
names.
c.
Change
the
DB2
subsystem
name
and
system
table
prefix.
d.
Change
the
DB2
Tivoli
Decision
Support
for
OS/390
table
prefix.
e.
Change
the
variable
BILLING_PERIOD
in
the
SET
statement
to
the
value
of
the
correct
billing
period.4.
Run
the
customized
DRLJPROR
job.
Distributing
overhead
accounts
based
on
relative
percentages
20
Tivoli
Decision
Support
for
OS/390:
Accounting
Feature
for
the
Host
Part
2.
Accounting
feature
reference
Chapter
5.
Data
flow
.
.
.
.
.
.
.
.
.
.
. 23
Overview
of
data
flow
.
.
.
.
.
.
.
.
.
.
. 23
CICS
data
flow
.
.
.
.
.
.
.
.
.
.
.
.
. 24
Credit
debit
processing
data
flow
.
.
.
.
.
.
. 25
DB2
data
flow
.
.
.
.
.
.
.
.
.
.
.
.
. 26
DFSMS
data
flow
.
.
.
.
.
.
.
.
.
.
.
. 27
IMS
data
flow
.
.
.
.
.
.
.
.
.
.
.
.
. 28
NPM
and
NetView
data
flow
.
.
.
.
.
.
.
. 29
STC,
BATCH,
TSO
data
flow
.
.
.
.
.
.
.
. 30
Overhead
accounts
data
flow
.
.
.
.
.
.
.
. 31
Billing
process
data
flow
.
.
.
.
.
.
.
.
.
. 32
Chapter
6.
Data
tables
and
views
.
.
.
.
.
. 33
RAFBATCH
data
table
.
.
.
.
.
.
.
.
.
.
. 33
RAFJOBLOG
data
table
.
.
.
.
.
.
.
.
.
. 35
RAFCICS
data
table
.
.
.
.
.
.
.
.
.
.
. 37
RAFDASD
data
table
.
.
.
.
.
.
.
.
.
.
. 39
RAFDB2
data
table
.
.
.
.
.
.
.
.
.
.
.
. 40
RAFHSMBKUP
data
table
.
.
.
.
.
.
.
.
. 42
RAFHSMMIGR
data
table
.
.
.
.
.
.
.
.
. 43
RAFIMS
data
table
.
.
.
.
.
.
.
.
.
.
.
. 44
RAFNETSES20
data
table
.
.
.
.
.
.
.
.
.
. 45
RAFNETSES4X
data
table
.
.
.
.
.
.
.
.
. 47
RAFNETV
data
table
.
.
.
.
.
.
.
.
.
.
. 48
RAFSTC
data
table
.
.
.
.
.
.
.
.
.
.
.
. 49
RAFADDRLOG
data
table
.
.
.
.
.
.
.
.
. 50
RAFTSO
data
table
.
.
.
.
.
.
.
.
.
.
.
. 52
RAFSESLOG
data
table
.
.
.
.
.
.
.
.
.
. 53
USE_SUMMARY_D
data
table
.
.
.
.
.
.
.
. 54
USE_SUMMARY_D2
data
table
.
.
.
.
.
.
.
. 55
USE_SUMMARY_D3
data
table
.
.
.
.
.
.
.
. 56
USE_SUMMARY_D4
data
table
.
.
.
.
.
.
.
. 57
ACCT_PRORATEV1
view
.
.
.
.
.
.
.
.
. 58
ACCT_PRORATEV2
view
.
.
.
.
.
.
.
.
. 59
BILLED_DATA
data
table
.
.
.
.
.
.
.
.
.
. 60
Chapter
7.
Lookup
tables
.
.
.
.
.
.
.
.
. 63
ACCOUNT
.
.
.
.
.
.
.
.
.
.
.
.
.
. 63
ACCT_PRORATE
.
.
.
.
.
.
.
.
.
.
.
. 64
BILLING_PERIOD
.
.
.
.
.
.
.
.
.
.
.
. 65
CPU_NORMAL_DATA
.
.
.
.
.
.
.
.
.
. 66
CREDIT_DEBIT
.
.
.
.
.
.
.
.
.
.
.
.
. 67
CUSTOMER
.
.
.
.
.
.
.
.
.
.
.
.
.
. 68
PRICE_LIST
.
.
.
.
.
.
.
.
.
.
.
.
.
. 69
Chapter
8.
Accounting
feature
translation
tables
71
RAFABATCH
.
.
.
.
.
.
.
.
.
.
.
.
.
. 71
RAFACICS
.
.
.
.
.
.
.
.
.
.
.
.
.
. 72
RAFADASD
.
.
.
.
.
.
.
.
.
.
.
.
.
. 73
RAFADB2
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 74
RAFAHSMBKUP
.
.
.
.
.
.
.
.
.
.
.
. 75
RAFAHSMMIGR
.
.
.
.
.
.
.
.
.
.
.
. 76
RAFAIMS
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 77
RAFANETSESM
.
.
.
.
.
.
.
.
.
.
.
.
. 78
RAFANETV
.
.
.
.
.
.
.
.
.
.
.
.
.
. 79
RAFASTC
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 80
RAFATSO
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 81
Chapter
9.
Accounting
feature
reports
.
.
.
. 83
Accounting
feature
report
definitions
.
.
.
.
.
. 83
Prorated
account
percentage
validation
report
.
. 83
Charges
by
billing
period
report
.
.
.
.
.
. 84
Charges
by
billing
period,
with
two
currencies
report
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 85
Billing
details
report
.
.
.
.
.
.
.
.
.
. 86
Charges
for
selected
billing
period
report
.
.
. 87
Chapter
10.
Considerations
for
dpAM
users
.
. 89
21
22
Tivoli
Decision
Support
for
OS/390:
Accounting
Feature
for
the
Host
Chapter
5.
Data
flow
Overview
of
data
flow
This
chapter
shows
a
general
overview
of
the
data
flow
in
the
Tivoli
Decision
Support
for
OS/390
Accounting
feature
and
the
data
flow
in
the
various
components
of
the
Accounting
feature.
Figure
2
shows
a
general
overview
of
the
data
flow.
Log
Detail Subsystemtable
USE_SUMMARYtable
BILLED_DATAtable
Figure
2.
General
overview
of
data
flow
23
CICS
data
flow
The
CICS
component
of
the
Accounting
Feature
for
the
Host
collects
SMF
log
data
recorded
by
CICS
and
stores
the
data
in
the
Tivoli
Decision
Support
for
OS/390
database.
You
can
use
the
Reporting
Dialog
to
create
reports
based
on
this
data.
Figure
3
shows
an
overview
of
the
flow
of
data
from
the
CICS
licensed
program,
through
the
CICS
component
of
the
Tivoli
Decision
Support
for
OS/390
Accounting
feature,
and
finally
into
usable
reports.
Figure
3.
CICS
component
data
flow
CICS
data
flow
24
Tivoli
Decision
Support
for
OS/390:
Accounting
Feature
for
the
Host
Credit
debit
processing
data
flow
Figure
4
shows
the
credit
debit
processing
data
flow.
PRICE_LISTBILLING_PERIOD
BILLED_DATA
CREDIT_DEBIT
Figure
4.
Credit
debit
processing
data
flow
Credit
debit
processing
data
flow
Chapter
5.
Data
flow
25
DB2
data
flow
The
DB2
component
of
the
Accounting
feature
collects
SMF
log
data
recorded
by
DB2
and
stores
the
data
in
the
accounting
table.
You
can
use
the
Reporting
Dialog
to
create
reports
based
on
this
data.
Figure
5
shows
an
overview
of
the
flow
of
data
from
the
DB2
licensed
program,
through
the
DB2
component
of
the
Tivoli
Decision
Support
for
OS/390
Accounting
feature,
and
finally
into
usable
reports.
Figure
5.
DB2
component
data
flow
DB2
data
flow
26
Tivoli
Decision
Support
for
OS/390:
Accounting
Feature
for
the
Host
DFSMS
data
flow
The
DFSMS
component
of
the
Accounting
feature
collects
records
from
the
DCOLLECT
facility,
which
extracts
data
from
VTOCs
and
the
DFHSM
control
data
sets.
The
component
then
stores
the
information
in
tables
in
the
Tivoli
Decision
Support
for
OS/390
Accounting
feature
tables.
Figure
6
shows
an
overview
of
the
flow
of
data
within
the
DFSMS
component.
Figure
6.
DFSMS
component
data
flow
DFSMS
data
flow
Chapter
5.
Data
flow
27
IMS
data
flow
The
IMS
component
of
the
Accounting
feature
collects
records
for
the
composite
records
created
by
the
IMS
feature
of
Tivoli
Decision
Support
for
OS/390
and
stores
the
data
in
the
Tivoli
Decision
Support
for
OS/390
database.
Figure
7
shows
the
IMS
component
data
flow.
Notes:
1.
You
must
install
at
least
one
of
the
IMS
collect
components
before
you
install
the
IMS
subcomponent
of
the
Accounting
feature.
For
example,
if
you
have
installed
the
IMS
6.1
collect
component,
you
can
proceed
with
the
installation
of
the
IMS
subcomponent.
2.
You
may
receive
some
error
messages
during
the
installation
process
if
you
installed
the
IMS
collect
component
for
another
version
of
IMS.
You
can
ignore
these
error
messages
and
work
with
the
IMS
collect
component
that
you
have
installed.
IMS_VXXX_R2
RAFIMS Lookup Table
RAFAIMS
USE_SUMMARY_D CPU_NORMAL_DATABILLING_PERIODACCOUNT
Lookup TablesSummary Tables
Figure
7.
IMS
component
data
flow
IMS
data
flow
28
Tivoli
Decision
Support
for
OS/390:
Accounting
Feature
for
the
Host
NPM
and
NetView
data
flow
The
NPM
and
NetView
components
of
the
Accounting
feature
collect
records
from
the
SMF
data
set
and
store
extracted
and
summarized
data
in
the
Tivoli
Decision
Support
for
OS/390
database.
Figure
8
shows
the
flow
of
NPM
and
NETV
data.
Figure
8.
NPM
and
NETV
components
data
flow
NPM
and
NetView
data
flow
Chapter
5.
Data
flow
29
STC,
BATCH,
TSO
data
flow
The
STC,
Batch,
and
TSO
components
of
the
Accounting
feature
collect
records
from
the
SMF
data
set
and
store
extracted
and
summarized
data
in
the
Tivoli
Decision
Support
for
OS/390
database.
Figure
9
shows
the
flow
of
STC,
Batch,
and
TSO
data.
Figure
9.
STC,
Batch,
TSO
component
data
flow
STC,
BATCH,
TSO
data
flow
30
Tivoli
Decision
Support
for
OS/390:
Accounting
Feature
for
the
Host
Overhead
accounts
data
flow
The
flow
from
ACCT_PRORATEV2
to
USE_SUMMARY_D
is
performed
when
you
run
the
DRLJPROP
job,
which
contains
a
recalculate
statement.
Figure
10
shows
the
overhead
accounts
data
flow.
USE_SUMMARY_D2USE_SUMMARY_D3
USE_SUMMARY_D
PRICE_LISTBILLED_DATA
ACCT_PRORATE
USE_SUMMARY_D4
ACCT_PRORATEV1
ACCT_PRORATEV2
Figure
10.
Overhead
accounts
data
flow
Overhead
accounts
data
flow
Chapter
5.
Data
flow
31
Billing
process
data
flow
Figure
11
shows
the
billing
process
data
flow.
USE_SUMMARY_DxBILLED_DATA
ACCT_PRORATE
Figure
11.
Billing
process
data
flow
Billing
process
data
flow
32
Tivoli
Decision
Support
for
OS/390:
Accounting
Feature
for
the
Host
Chapter
6.
Data
tables
and
views
RAFBATCH
data
table
This
table
contains
summarized
data
for
the
BATCH
producing
system.
It
contains
records
created
by
jobs
run
under
JES2
or
JES3.
The
source
for
these
is
SMF
record
types
6,
25,
26,
and
30
(subtype
5).
Column
name
Data
type
Description
ACCOUNT
k
CHAR(8)
Account
ID,
obtained
using
the
mapping
rules
in
the
table
RAFBATCH.
DATE
k
DATE
Day
the
reader
recognized
the
JOB
cards,
obtained
from
SMF30RSD.
FUNCTION
k
CHAR(8)
By
default
the
first
character
of
the
job
name.
This
can
be
changed
by
the
user
to
give
any
other
value
desired.
JOBCLASS
k
CHAR(8)
Job
class,
obtained
from
SMF30CLS.
JOBNAME
k
CHAR(8)
Job
or
session
name,
obtained
from
SMF30JBN,
SMF26JBN,
SMF25JBN,
or
SMF6JBN.
PERIOD
k
CHAR(8)
Name
of
the
period,
obtained
from
the
values
’RAP’,
SMF30RSD,
SMF25RSD,
SMF26RSD,
or
SMF6RSD
and
SMF30RST,
SMF25RST,
SMF26RST,
or
SMF6RST
as
parameters
in
the
PERIOD
function.
PRINTER
k
CHAR(8)
Printer
name.
SYSID
k
CHAR(8)
System
ID,
obtained
from
SMF30SID.
CPUNMSEC
FLOAT
Normalized
CPU
time,
calculated
during
import
as
CPUSEC/CP_POWER,
where
CP_POWER
is
obtained
by
looking
up
SYSID
in
the
CPU
normalization
table.
CPUSEC
FLOAT
Total
time
taken
by
the
jobs
in
seconds,
calculated
as
SUM(SRBTIME
+
TCBTIME
+
IIPTIME
+
HCTTIME
+
RCTTIME),
obtained
from
SMF30CPT,
SMF30CPS,
SMF30IIP,
SMF30HCT,
and
SMF30RCT.
DISKBLKS
FLOAT
Number
of
blocks
issued
for
DASD
devices,
obtained
from
SMF30BLK,
where
SMF30DEV
=
hex’20’.
DISKMNTS
FLOAT
Number
of
DASD
mounts
for
the
job,
obtained
as
SUM(SMF30PDM
+
SMF30PRD
+
SMF25NDM).
EXCPS
FLOAT
Number
of
total
blocks
issued,
calculated
as
sum
of
DISKBLKS,
TAPEBLKS,
and
OTHERBLKS,
all
obtained
from
SMF30BLK.
GRAFBLKS
FLOAT
Number
of
blocks
issued
for
graphic
devices,
obtained
from
SMF30BLK,
where
SMF30DEV
=
hex’00’.
LAST_COLLECT_TIME
TIMESTAMP
Last
time
collect
was
done
for
this
table.
LAST_IMPORT_TIME
TIMESTAMP
Last
time
import
was
done
for
the
BATCH
producing
system.
MSSBLKS
FLOAT
Number
of
blocks
issued
for
MSS
devices,
obtained
from
SMF30BLK,
where
SMF30DEV
=
hex’42’.
NJOBS
FLOAT
Total
number
of
jobs,
calculated
as
COUNT(CPUTIME).
NPAGES
FLOAT
Approximate
physical
page
count,
including
duplicates
and
separators,
calculated
as
SUM(SMF6PGE).
OCRBLKS
FLOAT
Number
of
blocks
issued
for
OCR
devices,
obtained
from
SMF30BLK,
where
SMF30DEV
=
hex’04’.
33
Column
name
Data
type
Description
OTHRBLKS
FLOAT
Number
of
blocks
issued
for
devices
other
than
DASD
and
TAPE
devices,
obtained
from
SMF30BLK.
PRTLINES
FLOAT
Number
of
output
lines
generated
to
spool,
obtained
from
SMF26XLN.
SRBTIME
FLOAT
Time
under
service
request
block
(SRB)
in
seconds,
obtained
from
SMF30CPS.
TAPEBLKS
FLOAT
Number
of
blocks
issued
for
tape
devices,
obtained
from
SMF30BLK,
where
SMF30DEV
=
hex’80’.
TAPEMNTS
FLOAT
Number
of
tape
mounts
for
the
job,
obtained
as
SUM(SMF30PTM
+
SMF30TPR
+
SMF25NTM).
TCBTIME
FLOAT
Total
number
of
CPU
seconds
under
task
control
block
(TCB),
obtained
from
SMF30CPT.
WTRLINES
FLOAT
Number
of
logical
records
written
by
the
writer,
calculated
as
SUM(SMF6NLR)
RAFBATCH
data
table
34
Tivoli
Decision
Support
for
OS/390:
Accounting
Feature
for
the
Host
RAFJOBLOG
data
table
This
table
contains
intermediate
data
for
the
BATCH
producing
system
summarized
at
day
level.
It
is
created
by
jobs
run
under
JES2
or
JES3.
The
sources
for
this
table
are
SMF
record
types
6,
25,
26,
and
30
(subtype
5).
Column
name
Data
type
Description
J_TIMESTAMP
k
TIMESTAMP
Date
and
time
when
the
reader
recognized
the
job
cards,
obtained
from
SMF30RSD
and
SMF30RST.
J_JOBNAME
k
CHAR(8)
Name
of
the
job,
obtained
from
SMF30JBN.
J_ACCT1
CHAR(8)
Details
obtained
from
the
ACCT
parameter
of
the
job
card,
obtained
from
the
SMF30ACT
of
the
first
accounting
section.
J_ACCT2
CHAR(8)
Details
obtained
from
the
ACCT
parameter
of
the
job
card,
obtained
from
the
SMF30ACT
of
the
second
accounting
section.
J_ACCT3
CHAR(8)
Details
obtained
from
the
ACCT
parameter
of
the
job
card,
obtained
from
the
SMF30ACT
of
the
third
accounting
section.
J_ACCT4
CHAR(8)
Details
obtained
from
the
ACCT
parameter
of
the
job
card,
obtained
from
the
SMF30ACT
of
the
fourth
accounting
section.
J_ACCT5
CHAR(8)
Details
obtained
from
the
ACCT
parameter
of
the
job
card,
obtained
from
the
SMF30ACT
of
the
fifth
accounting
section.
J_FUNCTION
CHAR(8)
A
field
the
value
of
which
can
be
decided
by
the
user.
Default
value
of
this
column
is
the
first
character
of
JOBNAME.
J_HPTTIME
FLOAT
Time
consumed
to
support
requests
for
data
to
be
transferred
between
a
hiperspace
and
an
address
space,
calculated
as
SMF30HCT/100.
J_IIPTIME
FLOAT
Time
used
to
process
I/O
interrupts,
calculated
as
SMF30IIP/100.
J_JOBCLASS
CHAR(8)
Job
class,
obtained
from
SMF30CLS.
J_MDISKS
FLOAT
Number
of
disk
mounts
for
the
job,
calculated
as
SUM(SMF30PDM
+
SMF30PRD
+
SMF25NDM).
J_MTAPES
FLOAT
Number
of
tape
mounts
for
the
job
calculated
as
SUM(SMF30PTM
+
SMF30TPR
+
SMF25NTM).
J_NDISKBLKS
FLOAT
Number
of
blocks
issued
for
DASD
for
the
job,
obtained
from
SMF30BLK,
where
SMF30DEV
=
hex’20’.
J_NGRAFBLKS
FLOAT
Number
of
blocks
issued
for
graphic
devices
for
the
job,
obtained
from
SMF30BLK,
where
SMF30DEV
=
hex’00’.
J_NLINES
FLOAT
Number
of
lines
dumped
by
the
job,
obtained
from
SMF26XLN.
J_NMSSBLKS
FLOAT
Number
of
blocks
issued
for
MSS
devices
for
the
job,
obtained
from
SMF30BLK
where
SMF30DEV
=
hex’42’.
J_NOCRBLKS
FLOAT
Number
of
blocks
issued
for
OCR
devices
for
the
job,
obtained
from
SMF30BLK
where
SMF30DEV
=
hex’04’.
J_NOTHRBLKS
FLOAT
Number
of
blocks
issued
for
devices
other
than
disk
and
tape
devices,
obtained
from
SMF30BLK.
J_NPAGES
FLOAT
Approximate
physical
page
count,
including
duplicates
and
separators,
calculated
as
SUM(SMF6PGE).
J_NTAPEBLKS
FLOAT
Number
of
blocks
issued
for
tape
devices
for
the
job,
obtained
from
SMF30BLK
where
SMF30DEV
=
hex’80’.
J_PGMRNAME
CHAR(8)
Programmer
name,
obtained
from
SMF30USR.
J_PRINTER
CHAR(8)
Printer
name.
RAFJOBLOG
data
table
Chapter
6.
Data
tables
and
views
35
Column
name
Data
type
Description
J_RACFGRP
CHAR(9)
RACF
group,
obtained
from
SMF30GRP.
J_RCTTIME
FLOAT
Time
used
by
region
control
task
(RCT),
calculated
as
SMF30RCT/100.
J_SMFID
CHAR(4)
System
ID,
obtained
from
SMF30SID.
J_SRBTIME
FLOAT
Time
under
service
request
block
(SRB),
in
seconds
calculated
as
SMF30CPS/100.
J_TCBTIME
FLOAT
Total
number
of
CPU
seconds
under
time
control
block
(TCB),
calculated
as
SMF30CPT/100.
J_USERFLD
CHAR(8)
A
user
field,
obtained,
by
default,
from
the
first
character
of
SMF30JBN,
the
job
name.
J_USERID
CHAR(8)
RACF
user
ID,
obtained
from
SMF30RUD.
J_WTRLINES
FLOAT
Number
of
logical
records
written
by
the
writer,
calculated
as
SUM(SMF6NLR).
RAFJOBLOG
data
table
36
Tivoli
Decision
Support
for
OS/390:
Accounting
Feature
for
the
Host
RAFCICS
data
table
This
table
contains
summarized
data
for
the
CICS
producing
system.
Column
name
Data
type
Description
ACCOUNT
k
CHAR(8)
Account
ID,
obtained
using
the
mapping
rules
specified
in
the
table
RAFACICS.
APPLID
k
CHAR(8)
Generic
application
ID,
obtained
from
the
field
SMFMNPRN.
DATE
k
DATE
Day
on
which
the
CICS
transaction
was
started,
obtained
from
the
field
START.
PERIOD
k
CHAR(8)
Name
of
the
period,
obtained
from
the
values
’RAF’,
DATE(START),
and
TIME(START)
as
parameters
in
the
PERIOD
function.
SYSID
k
CHAR(8)
System
ID,
obtained
from
the
field
SMFMNSID.
TRANS
k
CHAR(8)
CICS
transaction
ID,
obtained
from
TRAN.
CPUNMSEC
FLOAT
Normalized
CPU
time,
calculated
during
import
as
CPUSEC/CP_POWER,
where
CP_POWER
is
obtained
by
looking
up
SYSID
in
the
CPU
normalization
table.
CPUSEC
FLOAT
CPU
time
taken
for
the
transaction
in
seconds,
calculated
as
SUM(USRCPUT_CLOCK
/
625E2).
DBCTLS
FLOAT
Number
of
DL/I
requests,
calculated
as
SUM(DBCTL_TOTC).
DLICALLS
FLOAT
Number
of
DL/I
calls,
calculated
as
SUM(DLI_CLK3_COUNT).
FCAMC
FLOAT
Number
of
file
access
method
calls,
calculated
as
SUM(FCAMCT).
FCIO
FLOAT
Number
of
file
control
I/O
waits,
calculated
as
SUM(FCIOWTT_COUNT).
JCIO
FLOAT
Number
of
journal
control
I/O
waits,
calculated
as
SUM(JCIOWTT_COUNT).
LAST_COLLECT_TIME
TIMESTAMP
Last
time
collect
was
done
for
this
table.
LAST_IMPORT_TIME
TIMESTAMP
Last
time
import
was
done
into
for
the
CICS
producing
system.
MAXSTOR
FLOAT
Peak
user
subpool
storage,
in
KB,
used
above
and
below
16MB,
calculated
as
SUM((SCUSRHWME
+
SCUSRHWM)/1024).
MAXSTORB
FLOAT
Peak
user
subpool
storage,
in
BYTES,
used
above
and
below
16MB,
calculated
as
SUM(SCUSRHWME
+
SCUSRHWM).
NPAGEIN
FLOAT
Number
of
virtual
storage
page-ins
calculated
as
SUM(PAGINCT).
This
value
is
valid
for
CICS
Version
2
only.
NTRANS
FLOAT
Number
of
transactions,
calculated
as
COUNT(START).
TCINPUT
FLOAT
Number
of
messages
received
from
the
primary
terminal,
calculated
as
SUM(TCMSGIN1).
TCIO
FLOAT
Number
of
terminal
control
I/O
waits,
calculated
as
SUM(TCIOWTT_COUNT).
TCOUTPUT
FLOAT
Number
of
messages
sent
to
the
primary
terminal,
calculated
as
SUM(TCMSGOU1).
TDSERV
FLOAT
Number
of
transient
data
requests,
calculated
as
SUM(TDTOTCT).
RAFCICS
data
table
Chapter
6.
Data
tables
and
views
37
Column
name
Data
type
Description
TSIO
FLOAT
Number
of
temporary
storage
I/O
waits,
calculated
as
SUM(TSIOWTT_COUNT).
RAFCICS
data
table
38
Tivoli
Decision
Support
for
OS/390:
Accounting
Feature
for
the
Host
RAFDASD
data
table
This
table
contains
summarized
data
for
the
DASD
producing
system.
The
data
is
obtained
from
the
record
DCOLLECT_DA
from
the
log
DCOLLECT.
Column
name
Data
type
Description
ACCOUNT
k
CHAR(8)
Account
ID
which
is
obtained
using
the
rules
specified
in
the
table
RAFADASD.
DATE
k
DATE
Day
on
which
the
DCOLLECT
was
performed,
obtained
from
the
field
DCUDATE.
MGTCLASS
k
CHAR(8)
First
eight
characters
of
the
management
class,
obtained
from
the
field
DCDMCLAS.
PERIOD
k
CHAR(8)
Name
of
the
period
obtained
by
using
the
date
and
time
from
the
PERIOD
function.
STCLASS
k
CHAR(8)
First
eight
characters
of
the
storage
class,
obtained
from
the
field
DCDSCLAS.
STGROUP
k
CHAR(8)
First
eight
characters
of
the
storage
group,
obtained
from
the
field
DCDSTOGP.
SYSID
k
CHAR(8)
System
ID,
obtained
from
the
field
DCUSYSID.
ALLOCSP
FLOAT
Total
allocated
space
in
MB,
calculated
as
SUM(DCDALLSP/1024).
For
VSAM
data
sets,
DCDALLSP=DCAHARBA/1024.
LAST_COLLECT_TIME
TIMESTAMP
Last
time
collect
was
done
for
this
table.
LAST_IMPORT_TIME
TIMESTAMP
Last
time
import
was
done
for
the
DASD
producing
system.
Ndata
set
FLOAT
Total
number
of
data
sets,
obtained
as
COUNT(DCAASSOC).
UNUSEDBL
FLOAT
Total
amount
of
unusable
storage
in
MB,
calculated
as
SUM(DCDNMBLK/1024).
UNUSEDSP
FLOAT
Total
unused
space
in
MB,
calculated
as
SUM((DCDALLSP-DCDUSESP)/1024).
USEDSP
FLOAT
Total
used
space
in
MB,
calculated
as
SUM(DCDUSESP/1024).
For
VSAM
data
sets,
DCDUSESP=DCAHURBA/1024.
RAFDASD
data
table
Chapter
6.
Data
tables
and
views
39
RAFDB2
data
table
This
table
contains
summarized
data
for
the
DB2
producing
system.
The
logs
are
collected
from
SMF
log
type
101.
Column
name
Data
type
Description
ACCOUNT
k
CHAR(8)
Account
ID,
obtained
using
the
mapping
rules
specified
in
the
table
RAFADB2.
AUTHORIZ
k
CHAR(8)
Authorization
ID,
obtained
from
QWHCAID.
CONNTYPE
k
CHAR(8)
Type
of
system
that
is
connected,
obtained
from
QWHCCN.
CORRELAT
k
CHAR(12)
Correlation
ID,
obtained
from
QWHCCV.
DATE
k
DATE
Day
on
which
the
DB2
task
was
initiated,
obtained
from
the
field
SM101DTE.
PERIOD
k
CHAR(8)
Name
of
the
period,
obtained
from
the
values
’RAF’,
SM101DTE,
and
SM101TME®
as
parameters
in
the
PERIOD
function.
PLANNAME
k
CHAR(8)
Plan
name,
obtained
from
QWHCPLAN.
SUBSYSID
k
CHAR(8)
DB2
subsystem
ID,
obtained
from
QWHSSSID.
SYSID
k
CHAR(8)
System
ID,
obtained
from
SM101SID.
ABEND
FLOAT
Total
number
of
application
programs
which
ended
abnormally,
calculated
as
SUM(ABEND)
where
ABEND=1
when
QWACRINV=20,
else
ABEND=0.
CPUNMSEC
FLOAT
Normalized
CPU
time,
calculated
during
import
as
CPUSEC/CP_POWER,
where
CP_POWER
is
obtained
by
looking
up
SYSID
in
the
CPU
normalization
table.
CPURATE
FLOAT
CPU
normalization
factor
for
the
given
system
ID.
CPUSEC
FLOAT
CPU
time,
calculated
as
SUM(TCBTIME
+
SRBTIME).
CRDBASE
FLOAT
Number
of
CREATE
DATABASEs
issued,
calculated
as
SUM(QXCRDAB).
CRINDEX
FLOAT
Number
of
CREATE
INDEXes
issued,
calculated
as
SUM(QXCRINX).
CRTABLE
FLOAT
Number
of
CREATE
TABLEs
issued,
calculated
as
SUM(QXCRTAB).
CRTABSP
FLOAT
Number
of
CREATE
TABLESPACEs,
issued
calculated
as
SUM(QXCTABS).
CRVIEW
FLOAT
Number
of
CREATE
VIEWs
issued,
calculated
as
SUM(QXDEFVU).
DEALLOC
FLOAT
Total
number
of
normal
deallocations,
calculated
as
SUM(DEALLOC)
where
DEALLOC=1
when
QWACRINV=12,
else
DEALLOC=0.
DELETECALLS
FLOAT
Number
of
DELETEs
issued,
calculated
as
SUM(QXDELET).
ELAPSTIM
FLOAT
Total
elapsed
time
of
the
application
in
seconds,
calculated
as
SUM(QWACESC-QWACBSC).
FETCHCALLS
FLOAT
Number
of
FETCHes
issued,
calculated
as
SUM(QXFETCH).
INSERTCALLS
FLOAT
Number
of
INSERTs
issued,
calculated
as
SUM(QXINSRT).
LAST_COLLECT_TIME
TIMESTAMP
Last
time
collect
was
done
for
this
table.
LAST_IMPORT_TIME
TIMESTAMP
Last
time
import
was
done
for
RAFDB2
data
table
40
Tivoli
Decision
Support
for
OS/390:
Accounting
Feature
for
the
Host
Column
name
Data
type
Description
PGMEND
FLOAT
Total
number
of
application
programs
terminated
with
work
unit
in
doubt,
calculated
as
SUM(PGMEND)
where
PGMEND=1
when
QWACRINV=40,
else
PGMEND=0.
the
DB2
producing
system.
SELECTCALLS
FLOAT
Number
of
SELECTs
issued,
calculated
as
SUM(QXSELECT).
SRBTIME
FLOAT
Total
time
under
service
block
request,
calculated
as
SUM(QWACESRB
-
QWACBSRB).
TCBTIME
FLOAT
Total
time
under
task
control
block,
calculated
as
SUM(QWACEJST
-
QWACBJST).
THREADS
FLOAT
Number
of
threads
processed,
calculated
as
COUNT(TIMESTAMP).
UPDATECALLS
FLOAT
Number
of
UPDATEs
issued,
calculated
as
SUM(QXUPDTE).
RAFDB2
data
table
Chapter
6.
Data
tables
and
views
41
RAFHSMBKUP
data
table
This
table
contains
summarized
data
for
the
HSMBKUP
producing
system.
The
details
are
obtained
through
the
record
DCOLLECT_B
from
the
log
DCOLLECT.
Column
name
Data
type
Description
ACCOUNT
k
CHAR(8)
Account
ID,
obtained
by
using
the
mapping
rules
specified
in
the
table
RAFAHSMBKUP.
DATE
k
DATE
Day
on
which
the
collect
was
performed,
obtained
from
the
field
DCUDATE.
MGTCLASS
k
CHAR(8)
First
eight
characters
of
the
management
class,
obtained
from
the
field
UBMCLAS.
PERIOD
k
CHAR(8)
Name
of
the
period
obtained
by
using
the
date
and
time
from
the
PERIOD
function.
STCLASS
k
CHAR(8)
First
eight
characters
of
the
storage
class,
obtained
from
the
field
UBSCLAS.
SYSID
k
CHAR(8)
System
ID,
obtained
from
the
field
DCUSYSID.
BCKSP
FLOAT
Total
amount
of
backup
space
in
MB,
calculated
as
SUM(UBDSIZE/1024).
DBCKSP
FLOAT
Total
amount
of
backup
space
in
MB
on
DASD,
calculated
as
SUM(UBDSIZE
*
DASD/1024),
where
DASD=1
when
UBDEVCL=’D’,
else
DASD=0.
LAST_COLLECT_TIME
TIMESTAMP
Last
time
collect
was
done
for
this
table.
LAST_IMPORT_TIME
TIMESTAMP
Last
time
import
was
done
for
the
HSMBKUP
producing
system.
NUMDBCK
FLOAT
Number
of
DASD
backup
copies,
obtained
as
SUM(DASD)
where
DASD=1
when
UBDEVCL=’D’,
else
DASD=0.
NUMTBCK
FLOAT
Number
of
tape
backup
copies,
obtained
as
SUM(TAPE)
where
TAPE=1
when
UBDEVCL=’T’,
else
TAPE=0.
TBCKSP
FLOAT
Total
amount
of
backup
space
in
MB
on
tape,
calculated
as
SUM(UBDSIZE
*
TAPE/1024),
where
TAPE=1
when
UBDEVCL=’T’,
else
TAPE=0.
RAFHSMBKUP
data
table
42
Tivoli
Decision
Support
for
OS/390:
Accounting
Feature
for
the
Host
RAFHSMMIGR
data
table
This
table
contains
summarized
data
for
the
HSMMIGR
producing
system.
The
data
is
obtained
through
the
record
DCOLLECT_M
from
the
log
DCOLLECT.
Column
name
Data
type
Description
ACCOUNT
k
CHAR(8)
Account
ID,
obtained
using
the
mapping
rules
specified
in
the
table
RAFAHSMMIGR.
DATE
k
DATE
Day
on
which
the
DCOLLECT
was
performed,
obtained
from
the
field
DCUDATE.
LEVEL
k
CHAR(8)
Level
of
migration,
obtained
based
on
the
value
in
the
field
UMFLAG1.
When
value
is
’01’
the
level
is
L1
and
if
value
is
’10’
then
the
level
is
L2.
MGTCLASS
k
CHAR(8)
First
eight
characters
of
the
management
class,
obtained
from
the
field
UMMCLAS.
PERIOD
k
CHAR(8)
Name
of
the
period,
obtained
by
using
the
date
and
time
from
the
PERIOD
function.
STCLASS
k
CHAR(8)
First
eight
characters
of
the
storage
class,
obtained
from
the
field
UMSCLAS.
SYSID
k
CHAR(8)
System
ID,
obtained
from
the
field
DCUSYSID.
DMIGRSP
FLOAT
Size
of
DASD
migration
copies
in
MB,
calculated
as
SUM(DASD
*
UMDSIZE/1024),
where
DASD=1
when
UMDEVCL=’D’,
else
DASD=0.
LAST_COLLECT_TIME
TIMESTAMP
Last
time
collect
was
done
for
this
table.
LAST_IMPORT_TIME
TIMESTAMP
Last
time
import
was
done
for
the
HSMMIGR
producing
system.
MIGRSP
FLOAT
Total
size
in
MB
of
migration
copies,
calculated
as
the
sum
of
space
migrated
onto
TAPE
and
space
migrated
onto
DASD.
NUMDMIGR
FLOAT
Number
of
migrated
data
sets
on
DASD,
calculated
as
SUM(DASD),
where
DASD=1
when
UMDEVCL=’D’,
else
DASD=0.
NUMTMIGR
FLOAT
Number
of
migrated
data
sets
on
tape,
calculated
as
SUM(TAPE),
where
TAPE=1
when
UMDEVCL=’T’,
else
TAPE=0.
TMIGRSP
FLOAT
Size
of
TAPE
migration
copies
in
MB,
calculated
as
SUM(TAPE
*
UMDSIZE/1024),
where
TAPE=1
when
UMDEVCL=’T’,
else
TAPE=0.
RAFHSMMIGR
data
table
Chapter
6.
Data
tables
and
views
43
RAFIMS
data
table
This
table
contains
summarized
data
for
the
IMS
producing
system.
The
data
for
this
table
is
collected
from
the
records
IMS_510_R2
and
IMS_610_R2,
in
the
logs
IMS_510_COLLECT,
and
IMS_610_COLLECT,
IMS_710_COLLECT,
respectively.
Column
name
Data
type
Description
ACCOUNT
k
CHAR(8)
Account
ID,
obtained
based
on
the
mapping
rules
specified
in
the
table
RAFAIMS.
DATE
k
DATE
First
date
found
for
the
transaction,
obtained
from
DRL_DATE.
PERIOD
k
CHAR(8)
Name
of
the
period,
obtained
from
the
values
’RAF’,
DRL_DATE,
and
DRL_TIME
as
parameters
in
the
PERIOD
function.
SYSID
k
CHAR(8)
System
ID,
obtained
from
the
collect
parameter
MVS_SYSTEM_ID.
TRANCLAS
k
CHAR(8)
Transaction
class,
obtained
from
DRL_TXCLS
or
DRL_TRANT1.
If
DRL_TRANT1
=
’T’
then
value
is
’$I’,
if
DRL_TRANT1
=
’S’
then
value
is
’$M’,
else
if
DRL_TXCLS
=
’6F’
or
’40’
then
value
is
’$U’,
else
value
is
the
value
of
DRL_TXCLS.
TRANS
k
CHAR(8)
Transaction
ID,
obtained
depending
on
the
value
of
the
first
character
in
the
fields
DRL_TRANT
and
DRL_SMBNM.
TRANTYPE
k
CHAR(8)
Transaction
type,
obtained
from
DRL_TRANT.
CPUNMSEC
FLOAT
Normalized
CPU
time,
calculated
during
import
as
CPUSEC/CP_POWER,
where
CP_POWER
is
obtained
by
looking
up
SYSID
in
the
CPU
normalization
table.
CPUSEC
FLOAT
DBCALLS
FLOAT
Total
number
of
database
calls
for
the
transaction,
calculated
as
SUM(DRLCLCNT).
DCCALLS
FLOAT
Total
number
of
calls
to
message
queue,
calculated
as
SUM(DRLGNMES
+
DRLGUMES
+
DRLISMES
+
DRLPUMES).
LAST_COLLECT_TIME
TIMESTAMP
Last
time
collect
was
done
for
this
table.
LAST_IMPORT_TIME
TIMESTAMP
Last
time
import
was
done
for
the
IMS
producing
system.
NMSGS
FLOAT
Total
number
of
output
messages
issued
to
the
output
queue,
calculated
as
SUM(DRL_OUTMSG).
NOUTCHAR
FLOAT
Total
number
of
bytes
of
text
data
inserted
into
the
message
queue,
calculated
as
SUM(DRL_LMSGB
+
DRL_SMSGB).
NTRANS
FLOAT
Total
number
of
transactions
processed
in
the
system.
NTRANSD
FLOAT
Same
as
NTRANS
for
compatibility
with
SLR.
RAFIMS
data
table
44
Tivoli
Decision
Support
for
OS/390:
Accounting
Feature
for
the
Host
RAFNETSES20
data
table
This
table
contains
summarized
data
for
the
NETSESM
producing
system.
The
logs
are
collected
from
SMF
record
type
28
(subtype
X’20’).
Column
name
Data
type
Description
ACCOUNT
k
CHAR(8)
Account
ID,
obtained
by
using
the
mapping
rules
specified
in
the
table
RAFANETSESM.
ANUM
k
CHAR(8)
Account
number
supplied
by
the
session
manager,
obtained
from
LSCDANUM.
APPL
k
CHAR(8)
Synonym
of
the
resource,
obtained
from
LOOKUP
table
NW_RESOURCE.
user.
APPLGRUP
k
CHAR(8)
Group
name
of
the
resource,
obtained
from
LOOKUP
table
DPAMNW_RESOURCE
or
NW_RESOURCE
if
the
Network
Performance
component
is
installed
in
Tivoli
Decision
Support
for
OS/390
and
the
update
definition
is
modified
by
the
user.
DATE
k
DATE
Date
on
which
the
log
record
was
recorded,
obtained
from
the
field
LSAACBSK.
GROUPID
k
CHAR(8)
Group
ID
supplied
by
the
session
manager,
obtained
from
the
field
LSCDGRUP.
PCID
k
CHAR(8)
Unique
session
ID,
obtained
from
LSCDPCID.
PERIOD
k
CHAR(8)
Name
of
the
period,
obtained
from
values
’RAF’,
SMF28DTE,
and
SMF28TME
as
parameters
in
the
PERIOD
function.
Date
and
time
when
the
record
was
moved
to
the
external
log
buffer.
PRIORITY
k
INTEGER
Transmission
priority,
obtained
from
LSCDTPF.
RESOURCE
k
CHAR(8)
Application
name.
The
primary
logical
unit
(PLU)
name
from
ACDEB.
Obtained
from
LSCDPNAM.
SMFID
k
CHAR(4)
SMF
identifier.
SMID
k
CHAR(8)
Name
that
the
session
manager
passed
to
NPM
in
the
session
manager
identifier
MS
subvector,
obtained
from
LSCDSMID.
USERID
k
CHAR(8)
Operator
ID
supplied
by
the
session
manager,
obtained
from
the
field
LSCDUSER.
XNET
k
CHAR(1)
Cross-domain
session
indicator,
Y/N,
obtained
from
LSCDXNET.
CTLSESS
INTEGER
Control
session
indicator,
0/1,
obtained
from
LSCDFLAG.
EXTSESS
INTEGER
Extended
session
indicator,
0/1,
obtained
from
LSCDFLAG.
LAST_COLLECT_TIME
TIMESTAMP
Last
time
collect
was
done
for
this
table.
LAST_IMPORT_TIME
TIMESTAMP
Last
time
import
was
done
for
the
NETSESM
producing
system.
SCTLKBR
FLOAT
Sum
of
control
KB,
secondary
to
primary
(inbound
control
data).
Obtained
from
LSAASCCC.
SCTLKBS
FLOAT
Sum
of
control
KB,
primary
to
secondary
(outbound
control
data).
Obtained
from
LSAAPCCC.
SCTLPIUR
FLOAT
Sum
of
control
PIUs,
secondary
to
primary
(inbound
control
data).
Obtained
from
LSAASCBC.
SCTLPIUS
FLOAT
Sum
of
control
PIUs,
primary
to
secondary
(outbound
control
data).
Obtained
from
LSAAPCBC.
SMSGKBR
FLOAT
Sum
of
message
KB,
secondary
to
primary
(inbound
operator
messages).
Obtained
from
LSAASMCC.
RAFNETSES20
data
table
Chapter
6.
Data
tables
and
views
45
Column
name
Data
type
Description
SMSGKBS
FLOAT
Sum
of
message
KB,
primary
to
secondary
(outbound
operator
messages).
Obtained
from
LSAAPMCC.
SMSGR
FLOAT
Sum
of
messages,
secondary
to
primary
(inbound
operator
messages).
Obtained
from
LSAASMBC.
SMSGS
FLOAT
Sum
of
messages,
primary
to
secondary
(outbound
operator
messages).
Obtained
from
LSAAPMBC.
STXTKBR
FLOAT
Sum
of
text
KB,
secondary
to
primary
(inbound
operator
data).
Obtained
from
LSAASTCC.
STXTKBS
FLOAT
Sum
of
text
KB,
primary
to
secondary
(outbound
operator
data).
Obtained
from
LSAAPTCC.
STXTPIUR
FLOAT
Sum
of
text
PIUs,
secondary
to
primary
(inbound
operator
data).
Obtained
from
LSAASTBC.
STXTPIUS
FLOAT
Sum
of
text
PIUs,
primary
to
secondary
(outbound
operator
data).
Obtained
from
LSAAPTBC.
RAFNETSES20
data
table
46
Tivoli
Decision
Support
for
OS/390:
Accounting
Feature
for
the
Host
RAFNETSES4X
data
table
This
table
contains
session
time
data
for
the
NETSESM
producing
system.
The
logs
are
collected
from
SMF
record
type
28
(subtypes
X’48’
and
X’49’).
Column
name
Data
type
Description
DATE
k
DATE
Date
on
which
the
log
record
was
recorded,
obtained
from
the
field
SMF28DTE.
PCID
k
CHAR(8)
Unique
session
ID,
obtained
from
SMAPCID.
SESSCNTE
INTEGER
Number
of
session
ends.
Obtained
by
counting
records
subtype
X’49’.
SESSCNTS
INTEGER
Number
of
session
starts.
Obtained
by
counting
records
subtype
X’48’.
SESSTSE
TIMESTAMP
Time
stamp
for
session
end.
Obtained
from
SMATIME
in
record
subtype
X’49’.
SESSTSS
TIMESTAMP
Time
stamp
for
session
start.
Obtained
from
SMATIME
in
record
subtype
X’48’.
RAFNETSES4X
data
table
Chapter
6.
Data
tables
and
views
47
RAFNETV
data
table
This
table
contains
summarized
data
for
the
NETV
producing
system.
It
is
obtained
from
record
SMF_039_1_TO_7
in
the
SMF
log.
Column
name
Data
type
Description
ACCOUNT
k
CHAR(8)
Account
ID,
obtained
based
on
the
mapping
rules
specified
in
RAFANETV.
APPLID
k
CHAR(8)
Synonym
of
the
VTAM®
resource,
obtained
from
the
mapping
specified
in
the
table
NW_RESOURCE.
DATE
k
DATE
Day
when
the
record
was
moved
to
external
log
buffer,
obtained
from
LOGRDATE.
PERIOD
k
CHAR(8)
Name
of
the
period,
obtained
from
the
values
’RAF’,
LOGRDATE,
and
LOGRTIME
as
parameters
in
the
PERIOD
function.
Date
and
time
when
the
record
was
moved
to
the
external
log
buffer.
SYSID
k
CHAR(8)
System
ID,
obtained
from
LOGRSYID.
CTLBUFFX
FLOAT
Total
number
of
control
PIUs
sent
between
primary
and
secondary,
calculated
as
SUM(LACCPCBC
+
LACCSCBC).
CTLCHARX
FLOAT
Total
number
of
control
bytes
sent
between
primary
and
secondary,
calculated
as
SUM(LACCPCCC
+
LACCSCCC).
ELAPSTIM
FLOAT
Session
elapsed
time
in
hours,
calculated
as
SUM((LACCENDT2
-
LACCBEGT2)/3600)
where
LACCENDT2
is
the
collection
end
time
and
LACCBEGT2
is
the
collection
begin
time.
LAST_COLLECT_TIME
TIMESTAMP
Last
time
collect
was
done
for
this
table.
LAST_IMPORT_TIME
TIMESTAMP
Last
time
import
was
done
for
the
NETV
producing
system.
NSESS
FLOAT
Number
of
sessions
calculated
as
SUM(NSESS)
where
NSESS=1
when
LOGRSUBT=2
or
5,
else
NSESS=0.
TXTBUFFX
FLOAT
Total
number
of
text
PIUs
sent
between
primary
and
secondary,
calculated
as
SUM(LACCPTBC
+
LACCSTBC).
TXTCHARX
FLOAT
Total
number
of
text
bytes
sent
between
primary
and
secondary,
calculated
as
SUM(LACCPTCC
+
LACCSTCC).
RAFNETV
data
table
48
Tivoli
Decision
Support
for
OS/390:
Accounting
Feature
for
the
Host
RAFSTC
data
table
This
table
contains
summarized
data
for
the
STC
producing
system.
The
logs
are
collected
from
SMF
log
type
30
(subtype
4).
Column
name
Data
type
Description
ACCOUNT
k
CHAR(8)
Account
ID,
obtained
by
using
the
mapping
rules
specified
in
the
table
RAFASTC.
DATE
k
DATE
Date
on
which
the
log
was
recorded,
obtained
from
the
field
SMF30RSD.
PERIOD
k
CHAR(8)
Name
of
the
period,
obtained
from
the
values
’RAF’,
SMF30RSD,
and
SMF30RST
as
parameters
in
the
PERIOD
function.
STCNAME
k
CHAR(8)
Started
task
name
obtained
from
the
field
SMF30JBN.
SYSID
k
CHAR(8)
System
ID,
obtained
from
the
field
SMF30SID.
CPUNMSEC
FLOAT
Normalized
CPU
time,
calculated
during
import
as
CPUSEC/CP_POWER,
where
CP_POWER
is
obtained
by
looking
up
SYSID
in
the
CPU
normalization
table.
CPUSEC
FLOAT
Total
time
taken
by
the
task,
calculated
as
TCBTIME
+
SRBTIME
+
RCTTIME
+
HPTTIME
+
IIPTIME.
DISKBLKS
FLOAT
Number
of
blocks
allocated
for
DASD
devices,
calculated
as
SUM(SMF30BLKS)
where
SMF30DEV
=
hex’20’.
EXCPS
FLOAT
Number
of
executed
channel
programs,
calculated
as
SUM(SMF30TEP).
GRAFBLKS
FLOAT
Number
of
blocks
allocated
for
graphic
devices,
calculated
as
SUM(SMF30BLKS)
where
SMF30DEV
=
hex’00’.
LAST_COLLECT_TIME
TIMESTAMP
Last
time
collect
was
done
for
this
table.
LAST_IMPORT_TIME
TIMESTAMP
Last
time
import
was
done
for
the
STC
producing
system.
MSSBLKS
FLOAT
Number
of
blocks
allocated
for
MSS
devices,
calculated
as
SUM(SMF30BLKS)
where
SMF30DEV
=
hex’42’.
NSTCS
FLOAT
Number
of
started
task
steps
obtained
as
COUNT(CPUTIME).
OCRBLKS
FLOAT
Number
of
blocks
allocated
for
OCR
devices,
calculated
as
SUM(SMF30BLKS)
where
SMF30DEV
=
hex’04’.
OTHRBLKS
FLOAT
Number
of
blocks
allocated
for
devices
other
than
DASD
and
tape
devices,
calculated
as
SUM(SMF30BLKS)
where
SMF30DEV
<>
hex’20’
or
hex’80’.
SRBTIME
FLOAT
Total
time
under
service
request
block,
calculated
as
SUM(SMF30CPS).
TAPEBLKS
FLOAT
Number
of
blocks
allocated
for
tape
devices,
calculated
as
SUM(SMF30BLKS)
where
SMF30DEV
=
hex’80’.
TCBTIME
FLOAT
Total
time
under
task
control
block,
calculated
as
SUM(SMF30CPT).
RAFSTC
data
table
Chapter
6.
Data
tables
and
views
49
RAFADDRLOG
data
table
This
table
contains
intermediate
data
for
the
STC
producing
system
summarized
at
day
level.
The
source
for
this
table
is
SMF
record
type
30
(subtype
4).
Column
name
Data
type
Description
A_TIMESTAMP
k
TIMESTAMP
Date
and
time
when
the
reader
recognized
the
job
cards,
obtained
from
SMF30RSD
and
SMF30RST.
A_STCNAME
k
CHAR(8)
Name
of
the
job
specified,
obtained
from
SMF30JBN.
A_STEPNO
k
INTEGER
Number
of
the
step
that
created
this
record,
obtained
from
SMF30STN.
A_ACCT1
CHAR(8)
Obtained
from
the
first
eight
characters
of
SMF30ACT,
obtained
from
the
first
accounting
section.
A_ACCT2
CHAR(8)
Obtained
from
the
first
eight
characters
of
SMF30ACT,
obtained
from
the
second
accounting
section.
A_ACCT3
CHAR(8)
Obtained
from
the
first
eight
characters
of
SMF30ACT,
obtained
from
the
third
accounting
section.
A_ACCT4
CHAR(8)
Obtained
from
the
first
eight
characters
of
SMF30ACT,
obtained
from
the
fourth
accounting
section.
A_ACCT5
CHAR(8)
Obtained
from
the
first
eight
characters
of
SMF30ACT,
obtained
from
the
fifth
accounting
section.
A_HPTTIME
FLOAT
Time
consumed
to
support
requests
for
data
to
be
transferred
between
a
hiperspace
and
an
address
space,
obtained
as
SMF30HCT/100.
A_IIPTIME
FLOAT
Time
used
to
process
I/O
interrupts,
calculated
as
SMF30IIP/100.
A_NDISKBLKS
FLOAT
Number
of
blocks
issued
for
DASD
for
the
job,
obtained
from
SMF30BLK
where
SMF30DEV
=
hex’20’.
A_NEXCPS
FLOAT
Number
of
executed
channel
programs
calculated
as
SUM(SMF30TEP).
A_NGRAFBLKS
FLOAT
Number
of
blocks
issued
for
graphic
devices
for
the
job,
obtained
from
SMF30BLK
where
SMF30DEV
=
hex’00’.
A_NMSSBLKS
FLOAT
Number
of
blocks
issued
for
MSS
devices
for
the
job,
obtained
from
SMF30BLK
where
SMF30DEV
=
hex’42’.
A_NOCRBLKS
FLOAT
Number
of
blocks
issued
for
OCR
devices
for
the
job,
obtained
from
SMF30BLK
where
SMFDEV
=
hex’04’.
A_NOTHRBLKS
FLOAT
Number
of
blocks
issued
for
devices
other
than
disk
and
tape
devices,
obtained
from
SMF30BLK.
A_NTAPEBLKS
FLOAT
Number
of
blocks
issued
for
tape
devices
for
the
job,
obtained
from
SMF30BLK
where
SMF30DEV
=
hex’80’.
A_PGMNAME
CHAR(8)
Program
name,
obtained
from
SMF30PGM.
A_RACFGRP
CHAR(9)
RACFGRP,
obtained
from
SMF30GRP.
A_RCTTIME
FLOAT
Time
used
by
region
control
task
(RCT),
calculated
as
SMF30RCT/100.
A_SMFID
CHAR(4)
System
ID,
obtained
from
SMF30SID.
A_SRBTIME
FLOAT
Time
under
service
request
block
(SRB),
calculated
as
SMF30CPS/100
.
A_TCBTIME
FLOAT
Total
number
of
CPU
second
under
time
control
block
(TCB),
calculated
as
SMF30CPT/100.
RAFADDRLOG
data
table
50
Tivoli
Decision
Support
for
OS/390:
Accounting
Feature
for
the
Host
Column
name
Data
type
Description
A_USERFLD
CHAR(8)
A
user
field,
obtained,
by
default,
from
the
first
character
of
SMF30JBN,
the
job
name.
A_USERID
CHAR(8)
RACF
user
ID,
obtained
from
SMF30RUD.
RAFADDRLOG
data
table
Chapter
6.
Data
tables
and
views
51
RAFTSO
data
table
This
table
contains
summarized
data
for
the
TSO
producing
system.
The
logs
are
collected
from
SMF
log
type
30
(subtype
5).
Column
name
Data
type
Description
ACCOUNT
k
CHAR(8)
Account,
obtained
using
the
mapping
specified
in
the
RAFATSO
table.
DATE
k
DATE
Date
on
which
the
TSO
session
was
started,
obtained
from
SMF30RSD.
PERIOD
k
CHAR(8)
Name
of
the
period,
obtained
from
the
values
’RAF’,
SMF30RSD,
and
SMF30RST
as
parameters
in
the
PERIOD
function.
SYSID
k
CHAR(8)
System
ID,
obtained
from
SMF30SID.
CPUNMSEC
FLOAT
Normalized
CPU
time,
calculated
during
import
as
CPUSEC/CP_POWER,
where
CP_POWER
is
obtained
by
looking
up
SYSID
in
the
CPU
normalization
table.
CPUSEC
FLOAT
Total
CPU
time,
calculated
as
SUM(SMF30IIP
+
SMF30RCT
+
SMF30HCT
+
SMF30TCB
+
SMF30SRB).
EXCPS
FLOAT
Total
number
of
executed
channel
programs
during
the
session,
calculated
as
SUM(SMF30TEP).
LAST_COLLECT_TIME
TIMESTAMP
Last
time
the
collect
was
done
for
this
table.
LAST_IMPORT_TIME
TIMESTAMP
Last
time
import
was
done
for
the
TSO
producing
system.
NSESS
FLOAT
Number
of
TSO
logon
sessions,
calculated
as
the
count
of
accounting
records.
RAFTSO
data
table
52
Tivoli
Decision
Support
for
OS/390:
Accounting
Feature
for
the
Host
RAFSESLOG
data
table
This
table
contains
intermediate
data
for
the
TSO
producing
system
summarized
at
day
level.
Column
name
Data
type
Description
S_JOBNAME
k
CHAR(8)
Name
of
the
job,
obtained
from
SMF30JBN.
S_TIMESTAMP
k
TIMESTAMP
Date
and
time
when
the
reader
recognized
the
JOB
cards
and
is
obtained
from
SMF30RSD
and
SMF30RST.
S_ACCT1
CHAR(8)
Details
obtained
from
the
ACCT
parameter
of
the
job
card,
obtained
from
the
SMF30ACT
of
the
first
accounting
section.
S_ACCT2
CHAR(8)
Details
obtained
from
the
ACCT
parameter
of
the
job
card,
obtained
from
the
SMF30ACT
of
the
second
accounting
section.
S_ACCT3
CHAR(8)
Details
obtained
from
the
ACCT
parameter
of
the
job
card,
obtained
from
the
SMF30ACT
of
the
third
accounting
section.
S_ACCT4
CHAR(8)
Details
obtained
from
the
ACCT
parameter
of
the
job
card,
obtained
from
the
SMF30ACT
of
the
fourth
accounting
section.
S_ACCT5
CHAR(8)
Details
obtained
from
the
ACCT
parameter
of
the
job
card,
obtained
from
the
SMF30ACT
of
the
fifth
accounting
section.
S_HPTTIME
FLOAT
Time
consumed
to
support
requests
for
data
to
be
transferred
between
a
hiperspace
and
an
address
space,
calculated
as
SMF30HPT/100.
S_IIPTIME
FLOAT
Time
used
to
process
I/O
interrupts,
calculated
as
SMF30IIP/100.
S_NEXCPS
FLOAT
Number
of
executed
channel
programs,
calculated
as
SUM(SMF30TEP).
S_RACFGRP
CHAR(9)
RACF
group,
obtained
from
SMF30GRP.
S_RCTTIME
FLOAT
Time
used
by
region
control
task
(RCT),
calculated
as
SMF30RCT/100.
S_SMFID
CHAR(8)
System
ID,
obtained
from
SMF30SID.
S_SRBTIME
FLOAT
Time
under
service
request
block
(SRB),
calculated
as
SMF30CPS/100.
S_TCBTIME
FLOAT
Total
number
of
CPU
time
under
time
control
block
(TCB),
calculated
as
SMF30CPT/100.
S_TERMID
CHAR(8)
RACF
terminal
ID,
obtained
from
SMF30TID.
S_USERFLD
CHAR(8)
User
field,
obtained,
by
default,
from
the
first
character
of
SMF30RUD,
the
RACF
user
ID.
S_USERID
CHAR(8)
RACF
user
ID
obtained
from
SMF30RUD.
RAFSESLOG
data
table
Chapter
6.
Data
tables
and
views
53
USE_SUMMARY_D
data
table
This
table
provides
daily
usage
data
for
all
producing
systems.
Column
name
Data
type
Description
ACCOUNT_ID1
k
CHAR(12)
Account
name
from
usage
record
and/or
LOOKUP.
ACCOUNT_ID2
k
CHAR(12)
Account
name
from
usage
record
and/or
LOOKUP.
ACCOUNT_ID3
k
CHAR(12)
Account
name
from
usage
record
and/or
LOOKUP.
ACCOUNT_ID4
k
CHAR(12)
Account
name
from
usage
record
and/or
LOOKUP.
ACCOUNT_ID5
k
CHAR(12)
Account
name
from
usage
record
and/or
LOOKUP.
BILLING_PERIOD
k
CHAR(8)
Billing
period
from
LOOKUP.
CUSTOMER_ID
k
CHAR(15)
Customer
name
from
LOOKUP.
DATE
k
DATE
Date
when
the
usage
was
recorded.
OV_FLAG
k
CHAR(1)
Flag
for
overhead
accounts.
PERIOD_NAME
k
CHAR(8)
Time
period.
The
name
that
you
define
in
the
PERIOD_PLAN
table.
Use
it
to
group
time
intervals
according
to
operator
shifts
or
to
separate
peak
and
other
periods.
SMF_ID
k
CHAR(4)
MVS
system
ID.
The
SMF
system
ID.
From
SMFMVSID.
SUBSYSTEM_ID
k
CHAR(8)
Subsystem
name.
CPU_SECONDS
FLOAT
Number
of
CPU
seconds.
DASD_MBYTES
FLOAT
Number
of
DASD
MB.
DISK_EXCPS
FLOAT
Number
of
disk
exceptions.
PAGES_PRINTED
FLOAT
Number
of
pages
printed.
PRINT_LINES
FLOAT
Number
of
lines
printed.
SESSION_KBYTES
FLOAT
Number
of
session
KB.
TAPE_MOUNTS
FLOAT
Number
of
tape
mounts.
TAPE_EXCPS
FLOAT
Number
of
tape
exceptions.
USE_SUMMARY_D
data
table
54
Tivoli
Decision
Support
for
OS/390:
Accounting
Feature
for
the
Host
USE_SUMMARY_D2
data
table
This
table
provides
alternate
grouping
for
USE_SUMMARY
table.
Column
name
Data
type
Description
BILLING_PERIOD
k
CHAR(8)
Billing
period
ID
from
LOOKUP.
CPU_SECONDS
FLOAT
Number
of
CPU
seconds.
DASD_MBYTES
FLOAT
Number
of
DASD
MB.
DISK_EXCPS
FLOAT
Number
of
disk
exceptions.
PAGES_PRINTED
FLOAT
Number
of
pages
printed.
PRINT_LINES
FLOAT
Number
of
lines
printed.
SESSION_KBYTES
FLOAT
Number
of
session
KB.
TAPE_MOUNTS
FLOAT
Number
of
tape
mounts.
TAPE_EXCPS
FLOAT
Number
of
tape
exceptions.
USE_SUMMARY_D2
data
table
Chapter
6.
Data
tables
and
views
55
USE_SUMMARY_D3
data
table
This
table
provides
alternate
grouping
for
USE_SUMMARY_table.
Column
name
Data
type
Description
BILLING_PERIOD
k
CHAR(8)
Billing
period
ID
from
lookup.
CUSTOMER_ID
k
CHAR(15)
Customer
ID
CPU_SECONDS
FLOAT
Number
of
CPU
seconds.
DASD_MBYTES
FLOAT
Number
of
DASD
MB.
DISK_EXCPS
FLOAT
Number
of
disk
exceptions.
PAGES_PRINTED
FLOAT
Number
of
pages
printed.
PRINT_LINES
FLOAT
Number
of
lines
printed.
SESSION_KBYTES
FLOAT
Number
of
session
KB.
TAPE_MOUNTS
FLOAT
Number
of
tape
mounts.
TAPE_EXCPS
FLOAT
Number
of
tape
exceptions.
USE_SUMMARY_D3
data
table
56
Tivoli
Decision
Support
for
OS/390:
Accounting
Feature
for
the
Host
USE_SUMMARY_D4
data
table
This
table
provides
daily
usage
data
for
all
producing
systems.
Column
name
Data
type
Description
ACCOUNT_ID1
k
CHAR(12)
Account
name
from
usage
record
and/or
LOOKUP.
ACCOUNT_ID2
k
CHAR(12)
Account
name
from
usage
record
and/or
LOOKUP.
ACCOUNT_ID3
k
CHAR(12)
Account
name
from
usage
record
and/or
LOOKUP.
ACCOUNT_ID4
k
CHAR(12)
Account
name
from
usage
record
and/or
LOOKUP.
ACCOUNT_ID5
k
CHAR(12)
Account
name
from
usage
record
and/or
LOOKUP.
BILLING_PERIOD
k
CHAR(8)
Billing
period
from
LOOKUP.
CPU_SECONDS
FLOAT
Number
of
CPU
seconds.
DASD_MBYTES
FLOAT
Number
of
DASD
MB.
DISK_EXCPS
FLOAT
Number
of
disk
exceptions.
PAGES_PRINTED
FLOAT
Number
of
pages
printed.
PERIOD_NAME
k
CHAR(8)
Time
period.
The
name
that
you
define
in
the
PERIOD_PLAN
table.
Use
it
to
group
time
intervals
according
to
operator
shifts
or
to
separate
peak
and
other
periods.
PRINT_LINES
FLOAT
Number
of
lines
printed.
SESSION_KBYTES
FLOAT
Number
of
session
KB.
SMF_ID
k
CHAR(4)
MVS
system
ID.
The
SMF
system
ID.
From
SMFMVSID.
SUBSYSTEM_ID
k
CHAR(8)
Subsystem
name.
TAPE_EXCPS
FLOAT
Number
of
tape
exceptions.
TAPE_MOUNTS
FLOAT
Number
of
tape
mounts.
USE_SUMMARY_D4
data
table
Chapter
6.
Data
tables
and
views
57
ACCT_PRORATEV1
view
This
view
contains
prorating
data
based
on
the
USE_SUMMARY_D4
data
table.
Column
name
Data
type
Description
ACCOUNT_ID1
k
CHAR(12)
Account
name
from
usage
record
and/or
LOOKUP.
ACCOUNT_ID2
k
CHAR(12)
Account
name
from
usage
record
and/or
LOOKUP.
ACCOUNT_ID3
k
CHAR(12)
Account
name
from
usage
record
and/or
LOOKUP.
ACCOUNT_ID4
k
CHAR(12)
Account
name
from
usage
record
and/or
LOOKUP.
ACCOUNT_ID5
k
CHAR(12)
Account
name
from
usage
record
and/or
LOOKUP.
PERIOD_NAME
k
CHAR(8)
Time
period.
The
name
that
you
define
in
the
PERIOD_PLAN
table.
Use
it
to
group
time
intervals
according
to
operator
shifts
or
to
separate
peak
and
other
periods.
SMF_ID
k
CHAR(4)
MVS
system
ID.
The
SMF
system
ID.
From
SMFMVSID.
SUBSYSTEM_ID
k
CHAR(8)
Subsystem
name.
ACCT_PRORATEV1
view
58
Tivoli
Decision
Support
for
OS/390:
Accounting
Feature
for
the
Host
ACCT_PRORATEV2
view
This
view
contains
prorating
data
based
on
the
ACCT_PRORATE
lookup
table
and
the
ACCT_PRORATEV1
view.
Column
name
Data
type
Description
ACCOUNT_ID1
k
CHAR(12)
Account
name
from
usage
record
and/or
LOOKUP.
ACCOUNT_ID2
k
CHAR(12)
Account
name
from
usage
record
and/or
LOOKUP.
ACCOUNT_ID3
k
CHAR(12)
Account
name
from
usage
record
and/or
LOOKUP.
ACCOUNT_ID4
k
CHAR(12)
Account
name
from
usage
record
and/or
LOOKUP.
ACCOUNT_ID5
k
CHAR(12)
Account
name
from
usage
record
and/or
LOOKUP.
CUSTOMER_ID
k
CHAR(15)
Customer
name
to
allocate
a
percentage.
PERCENTAGE
FLOAT
Fixed
percentage.
Must
add
100%
for
account.
PERIOD_NAME
k
CHAR(8)
Time
period.
The
name
that
you
define
in
the
PERIOD_PLAN
table.
Use
it
to
group
time
intervals
according
to
operator
shifts
or
to
separate
peak
and
other
periods.
PRORATE_TYPE
CHAR(8)
Character
fixed
or
the
variable
to
be
used.
SMF_ID
k
CHAR(4)
MVS
system
ID.
The
SMF
system
ID.
From
SMFMVSID.
SUBSYSTEM_ID
k
CHAR(8)
Subsystem
name.
ACCT_PRORATEV2
view
Chapter
6.
Data
tables
and
views
59
BILLED_DATA
data
table
This
table
provides
the
usage
data
for
all
producing
systems,
the
corresponding
unit
price
and
total
amount
for
the
various
types
of
data.
It
can
store
two
different
unit
prices
and
total
amounts,
depending
on
the
currencies
used
(for
example,
dollars
and
euros).
Column
name
Data
type
Description
SMF_ID
k
CHAR(4)
CRDB
BP_ID
k
CHAR(8)
Billing
period.
CU_ID
k
CHAR(15)
Customer
ID.
AC1
k
CHAR(12)
Account
ID1.
AC2
k
CHAR(12)
Account
ID1.
AC3
k
CHAR(12)
Account
ID1.
AC4
k
CHAR(12)
Account
ID1.
AC5
k
CHAR(12)
Account
ID1.
DATE
k
DATE
Date.
PERIOD_NAME
k
CHAR(8)
Shift
associated.
CHARGE_TYPE
k
CHAR(1)
Type
of
charge.
The
char
R
indicates
a
one-time
charge.
SUBSYSTEM_ID
k
CHAR(8)
Subsystem
associated.
CPU_SECONDS_V
FLOAT
Sum
of
CPU
seconds.
CPU_SECONDS_P
FLOAT
Price
of
CPU
seconds
(primary
currency).
CPU_SECONDS_A
FLOAT
Total
amount
for
CPU
seconds
(primary
currency).
TAPE_EXCPS_V
FLOAT
Sum
of
tape
exceptions.
TAPE_EXCPS_P
FLOAT
Price
of
tape
exceptions
(primary
currency).
TAPE_EXCPS_A
FLOAT
Total
amount
of
tape
exceptions
(primary
currency).
DISK_EXCPS_V
FLOAT
Sum
of
disk
exceptions.
DISK_EXCPS_P
FLOAT
Sum
of
disk
exceptions
(primary
currency)
DISK_EXCPS_A
FLOAT
Total
amount
of
disk
exceptions
(primary
currency).
PRINT_LINES_V
FLOAT
Sum
of
lines.
PRINT_LINES_P
FLOAT
Price
of
lines
(primary
currency).
PRINT_LINES_A
FLOAT
Total
amount
of
lines
(primary
currency).
TAPE_MOUNTS_V
FLOAT
Sum
of
tape
mounts.
TAPE_MOUNTS_P
FLOAT
Price
of
tape
mounts
(primary
currency).
TAPE_MOUNTS_A
FLOAT
Total
amount
of
tape
mounts
(primary
currency).
PAGES_PRINTED_V
FLOAT
Sum
of
pages
printed.
PAGES_PRINTED_P
FLOAT
Price
of
pages
printed
(primary
currency).
PAGES_PRINTED_A
FLOAT
Total
amount
of
pages
printed
(primary
currency).
DASD_MBYTES_V
FLOAT
Sum
of
DASD
MB.
DASD_MBYTES_P
FLOAT
Price
of
DASD
MB
(primary
currency).
DASD_MBYTES_A
FLOAT
Total
amount
of
DASD
MB
(primary
currency).
SESSION_KBYTES_V
FLOAT
Sum
of
session
KB.
SESSION_KBYTES_P
FLOAT
Price
of
session
KB
(primary
currency).
SESSION_KBYTES_A
FLOAT
Total
amount
of
session
KB
(primary
currency).
BILLED_DATA
data
table
60
Tivoli
Decision
Support
for
OS/390:
Accounting
Feature
for
the
Host
Column
name
Data
type
Description
MISC_A
FLOAT
Total
amount
(primary
currency).
CPU_SECONDS_P2
FLOAT
Price
of
CPU
seconds
(additional
currency).
CPU_SECONDS_A2
FLOAT
Total
amount
for
CPU
seconds
(additional
currency).
TAPE_EXCPS_P2
FLOAT
Price
of
tape
exceptions
(additional
currency).
TAPE_EXCPS_A2
FLOAT
Total
amount
of
tape
exceptions
(additional
currency).
DISK_EXCPS_P2
FLOAT
Sum
of
disk
exceptions
(additional
currency).
DISK_EXCPS_A2
FLOAT
Total
amount
of
disk
exceptions
(additional
currency).
PRINT_LINES_P2
FLOAT
Price
of
lines
(additional
currency).
PRINT_LINES_A2
FLOAT
Total
amount
of
lines
(additional
currency).
TAPE_MOUNTS_P2
FLOAT
Price
of
tape
mounts
(additional
currency).
TAPE_MOUNTS_A2
FLOAT
Total
amount
of
tape
mounts
(additional
currency).
PAGES_PRINTED_P2
FLOAT
Price
of
pages
printed
(additional
currency).
PAGES_PRINTED_A2
FLOAT
Total
amount
of
pages
printed
(additional
currency).
DASD_MBYTES_P2
FLOAT
Price
of
DASD
MB
(additional
currency).
DASD_MBYTES_A2
FLOAT
Total
amount
of
DASD
MB
(additional
currency).
SESSION_KBYTES_P2
FLOAT
Price
of
session
KB
(additional
currency).
SESSION_KBYTES_A2
FLOAT
Total
amount
of
session
KB
(additional
currency).
MISC_A2
FLOAT
Total
amount
(additional
currency).
BILLED_DATA
data
table
Chapter
6.
Data
tables
and
views
61
BILLED_DATA
data
table
62
Tivoli
Decision
Support
for
OS/390:
Accounting
Feature
for
the
Host
Chapter
7.
Lookup
tables
This
chapter
describes
the
lookup
tables
that
are
part
of
the
Tivoli
Decision
Support
for
OS/390
Accounting
feature.
ACCOUNT
This
table
provides
account
details
including
the
customer
ID
that
owns
the
table
or
a
flag
to
indicate
an
overhead
account
to
be
prorated.
Column
name
Data
type
Description
AC_AC1
k
CHAR(12)
First
account
qualifier.
AC_AC2
k
CHAR(12)
Second
account
qualifier.
AC_AC3
k
CHAR(12)
Third
account
qualifier.
AC_AC4
k
CHAR(12)
Fourth
account
qualifier.
AC_AC5
k
CHAR(12)
Fifth
account
qualifier.
AC_CUST_ID
CHAR(15)
Customer
ID
that
owns
this
account
AC_NAME
CHAR(30)
Descriptive
name
to
on
invoices
63
ACCT_PRORATE
This
Accounting
feature
table
defines
what
account
proration
logic
will
be
used,
if
any,
for
this
environment.
This
table
is
called
ACCT_PRORATE
and
is
referenced
by
the
RECALCULATE
function
when
account
proration
is
in
use.
The
Accounting
component
provides
for
fixed
percentage
proration
and
variable
proration.
Both
forms
of
proration
are
controlled
through
the
use
of
the
proration
lookup
table.
The
lookup
table
provides
either
the
fixed
percentage
amount
of
the
account
to
be
allocated
to
a
particular
customer
or
it
provides
the
variable
that
will
be
used
to
prorate
the
charges
to
the
customer
on
a
relative
usage
basis.
The
default
for
variable
proration
is
CPU
usage.
The
actual
account
usage
will
be
prorated
to
each
customer
based
on
that
customer’s
percentage
of
overall
CPU
usage
during
the
billing
period.
The
update
definition,
RAF_ACCT_PRORATE
in
member
DRLUACCP
of
data
set
DRL160.SDRLDEFS,
can
be
modified
to
prorate
account
usage
on
any
other
usage
variable
that
is
collected
and
stored
in
the
USE_SUMMARY_D
table.
Note:
If
fixed
percentage
proration
is
used,
the
total
of
all
percentages
entered
should
equal
100.
Column
name
Data
type
Description
CUSTOMER_ID
k
CHAR(15)
Customer
name
to
allocate
a
percentage.
ACCOUNT_ID1
k
CHAR(12)
Account
name
to
be
prorated.
ACCOUNT_ID2
k
CHAR(12)
Account
name
to
be
prorated.
ACCOUNT_ID3
k
CHAR(12)
Account
name
to
be
prorated.
ACCOUNT_ID4
k
CHAR(12)
Account
name
to
be
prorated.
ACCOUNT_ID5
k
CHAR(12)
Account
name
to
be
prorated.
PERCENTAGE
FLOAT
Fixed
percentage.
Must
add
100%
for
account.
PRORATE_TYPE
CHAR(8)
Character
fixed
or
the
variable
to
be
used.
ACCT_PRORATE
lookup
table
64
Tivoli
Decision
Support
for
OS/390:
Accounting
Feature
for
the
Host
BILLING_PERIOD
This
table
defines
billing
periods.
It
stores
billing
periods
for
all
producing
systems
and
is
referenced
during
the
collect
process.
Column
name
Data
type
Description
BP_ID
k
CHAR(8)
Billing
Period
Name
BP_EFF_DT
k
DATE
Billing
Period
Start
Date.
BP_END_DT
k
DATE
Billing
Period
End
Date.
BP_EOY_FLAG
k
CHAR(1)
Billing
Period
End
of
the
Accounting
Year.
BILLING_PERIOD
lookup
table
Chapter
7.
Lookup
tables
65
CPU_NORMAL_DATA
This
table
controls
normalization
of
CPU
seconds.
Column
name
Data
type
Description
CP_SMF_ID
k
CHAR(4)
SMF
ID
the
normalization
factor
applies
to.
CP_START_DATE
k
DATE
Start
date
for
the
SMF
ID.
CP_POWER
FLOAT
Native
CPU
seconds
are
divided
by
this
value
to
calculate
the
normalized
equivalent.
CP_END_DATE
DATE
End
date
for
the
SMF
ID.
CP_DESC
VARCHAR(30)
Description
of
the
SMF
ID
normalized.
CPU_NORMAL_DATA
lookup
table
66
Tivoli
Decision
Support
for
OS/390:
Accounting
Feature
for
the
Host
CREDIT_DEBIT
This
table
is
called
CREDIT_DEBIT
and
is
referenced
by
the
RECALCULATE
function
when
credits
and
debits
are
processed
for
accounts.
The
table
defines
what
credits
and
debits
will
be
used,
if
any,
for
this
environment.
Debits
and
credits
can
be
one
time
or
recurring.
One
time
debits
and
credits
will
be
removed
from
the
credit/table
lookup
table
after
processing.
A
negative
amount
indicates
a
credit
and
a
positive
amount
indicates
a
debit.
Credits
and
debits
may
be
entered
in
two
different
currency
amounts
(for
example,
dollars
and
euros)
or
in
resource
usage
amounts.
Column
name
Data
type
Description
CUSTOMER_ID
k
CHAR(15)
Customer
name
to
receive
credit
or
debit.
ACCOUNT_ID1
k
CHAR(12)
Account
ID1
to
be
associated
with
credit
or
debit.
ACCOUNT_ID2
k
CHAR(12)
Account
ID2
to
be
associated
with
credit
or
debit.
ACCOUNT_ID3
k
CHAR(12)
Account
ID3
to
be
associated
with
credit
or
debit.
ACCOUNT_ID4
k
CHAR(12)
Account
ID4
to
be
associated
with
credit
or
debit.
ACCOUNT_ID5
k
CHAR(12)
Account
ID5
to
be
associated
with
credit
or
debit.
DATE
k
DATE
Date
for
debit
or
credit.
PERIOD_NAME
k
CHAR(8)
Shift
associated
with
the
credit
or
debit.
SUBSYSTEM_ID
k
CHAR(8)
Subsystem
associated
with
the
credit
or
debit.
TYPE
k
CHAR(1)
Type
of
charge.
The
character
R
indicates
a
one
time
charge
other
values
will
be
purged
monthly.
DESCRIPTION
CHAR(30)
Description
to
be
printed
on
the
invoice.
AMOUNT
FLOAT
Amount
of
credit
or
debit
(primary
currency).
AMOUNT2
FLOAT
Amount
of
credit
or
debit
(additional
currency).
CPU_SECONDS
FLOAT
CPU
seconds
for
credit
or
debit.
TAPE_EXCPS
FLOAT
Number
of
tapes
exceptions
for
credit
or
debit.
DISK_EXCPS
FLOAT
Number
of
disks
exceptions
for
credit
or
debit.
PRINT_LINES
FLOAT
lines
for
credit
or
debit.
TAPE_MOUNTS
FLOAT
Tape
mounts
for
credit
or
debit.
PAGES_PRINTED
FLOAT
Pages
printed
for
credit
or
debit.
DASD_MBYTES
FLOAT
DASD
MB
for
credit
or
debit.
SESSION_KBYTES
FLOAT
DASD
KB
for
credit
or
debit.
CREDIT_DEBIT
lookup
table
Chapter
7.
Lookup
tables
67
CUSTOMER
This
table
provides
customer
information
for
invoice
printing.
The
Accounting
component
has
a
table
that
defines
customers,
which
is
called
CUSTOMER
and
is
referenced
during
the
collect
process.
Column
name
Data
type
Description
CU_ID
k
CHAR(15)
Customer
ID.
This
must
be
unique.
CU_NAME
CHAR(30)
Customer
name.
CU_EFF_DT
DATE
Effective
start
date
of
customer
CU_END_DT
DATE
End
date
after
which
no
charges
should
accrue.
CU_LEDGER_AC_ID
CHAR(30)
Ledger
Account
Field.
CU_TYPE
CHAR(1)
Type
of
customer.
I
for
Internal
E
for
External.
CU_CHARGEABLE_IND
CHAR(1)
Y
or
N
if
the
customer
is
chargeable.
CU_CONTACT_NAME
VARCHAR(30)
Name
of
contact
person.
CU_CONTACT_NUMBER
CHAR(16)
Phone
number
of
contact
person.
CU_ADDR1
VARCHAR(40)
Line
one
of
the
address
for
the
customer.
CU_ADDR2
VARCHAR(40)
Line
two
of
the
address
for
the
customer.
CU_ADDR3
VARCHAR(40)
Line
three
of
the
address
for
the
customer.
CUSTOMER
lookup
table
68
Tivoli
Decision
Support
for
OS/390:
Accounting
Feature
for
the
Host
PRICE_LIST
This
table
stores
pricing
data
for
all
producing
systems.
It
enables
you
to
store
pricing
data
with
a
primary
currency
(for
example,
dollars)
and
an
additional
currency
(for
example,
euros).
A
sample
job
(DRLJSAC)
is
available
in
the
CNTL
library
to
simplify
the
conversion
from
the
primary
to
the
additional
currency
and
the
update
of
this
table.
Column
name
Data
type
Description
CUS
k
CHAR(15)
Customer
ID.
AC1
k
CHAR(12)
Account
ID1.
AC2
k
CHAR(12)
Account
ID2.
AC3
k
CHAR(12)
Account
ID3.
AC4
k
CHAR(12)
Account
ID4.
AC5
k
CHAR(12)
Account
ID5.
SSID
k
CHAR(8)
Subsystem
ID.
PER
k
CHAR(8)
Time
Period.
EFF_DT
k
DATE
Effective
Date.
END_DT
k
DATE
End
Date.
CPU_SEC_P
FLOAT
Price
of
CPU
seconds
(primary
currency).
TAPE_E_P
FLOAT
Price
of
tape
exceptions
(primary
currency).
DISK_E_P
FLOAT
Price
of
disk
exceptions
(primary
currency).
PRINT_P
FLOAT
Price
of
lines
(primary
currency).
TAPE_M_P
FLOAT
Price
of
tape
mounts
(primary
currency).
PAGES_P
FLOAT
Price
of
pages
printed
(primary
currency).
DASD_M_P
FLOAT
Price
of
DASD
MB
(primary
currency).
SES_K_P
FLOAT
Price
of
session
KB
(primary
currency).
CPU_SEC_P2
FLOAT
Price
of
CPU
seconds
(additional
currency).
TAPE_E_P2
FLOAT
Price
of
tape
exceptions
(additional
currency).
DISK_E_P2
FLOAT
Price
of
disk
exceptions
(additional
currency).
PRINT_P2
FLOAT
Price
of
lines
(additional
currency).
TAPE_M_P2
FLOAT
Price
of
tape
mounts
(additional
currency).
PAGES_P2
FLOAT
Price
of
pages
printed
(additional
currency).
DASD_M_P2
FLOAT
Price
of
DASD
MB
(additional
currency).
SES_K_P2
FLOAT
Price
of
session
KB
(additional
currency).
PRICE_LIST
lookup
table
Chapter
7.
Lookup
tables
69
PRICE_LIST
lookup
table
70
Tivoli
Decision
Support
for
OS/390:
Accounting
Feature
for
the
Host
Chapter
8.
Accounting
feature
translation
tables
RAFABATCH
This
table
contains
the
rules
for
translating
account
translation
elements
in
SMF
log
records
to
account
IDs
in
the
RAFBATCH
table.
Column
name
Data
type
Description
ACCT1
k
CHAR(8)
Value
to
be
matched
with
the
first
eight
characters,
obtained
from
SMF30ACT
of
the
first
accounting
section.
ACCT2
k
CHAR(8)
Value
to
be
matched
with
the
first
eight
characters,
obtained
from
SMF30ACT
of
the
second
accounting
section.
ACCT3
k
CHAR(8)
Value
to
be
matched
with
the
first
eight
characters,
obtained
from
SMF30ACT
of
the
third
accounting
section.
ACCT4
k
CHAR(8)
Value
to
be
matched
with
the
first
eight
characters,
obtained
from
SMF30ACT
of
the
fourth
accounting
section.
ACCT5
k
CHAR(8)
Value
to
be
matched
with
the
first
eight
characters,
obtained
from
SMF30ACT
of
the
fifth
accounting
section.
RACFGRP
k
CHAR(9)
Value
to
be
matched
with
the
RACF
group
of
the
job,
obtained
from
SMF30GRP.
USERID
k
CHAR(8)
Value
to
be
matched
with
the
RACF
user
ID
of
the
job,
obtained
from
SMF30RUD.
JOBNAME
k
CHAR(8)
Value
to
be
matched
with
the
job
name
of
the
job
obtained
from
SMF30JBN,
SMF26JBN,
or
SMF25JBN.
SYSID
k
CHAR(8)
Value
to
be
compared
with
the
system
identification
obtained
from
SMF30SID.
PGMRNAME
k
CHAR(8)
Value
to
be
compared
with
the
programmer
name
obtained
from
SMF30USR.
JOBCLASS
k
CHAR(8)
Value
to
be
compared
with
the
jobclass
of
the
job
obtained
from
SMF30CLS.
USERFLD
k
CHAR(8)
Value
to
be
compared
with
J_USERFLD
in
RAFJOBLOG,
whose
default
value
is
the
first
character
of
the
job
name.
The
user
can
modify
this
default
calculation.
ACCTID
CHAR(8)
Account
ID,
obtained
when
the
key
columns
match
the
corresponding
log
fields.
71
RAFACICS
This
table
contains
the
rules
for
translating
account
translation
elements
in
CICS
log
records
to
account
IDs
in
the
RAFACICS
table.
Column
name
Data
type
Description
TERMID
k
CHAR(4)
Value
to
be
compared
with
the
terminal
ID,
obtained
from
the
field
TERM.
USERID
k
CHAR(8)
Value
to
be
compared
with
the
user
ID,
obtained
from
the
field
USER.
OPERID
k
CHAR(3)
Value
to
be
compared
with
the
operator
ID,
obtained
from
the
field
OPER.
APPLID
k
CHAR(8)
Value
to
be
compared
with
the
generic
application
ID,
obtained
from
the
field
SMFMNPRN.
SYSID
k
CHAR(8)
Value
to
be
compared
with
the
system
ID,
obtained
from
the
field
SMFMNSID.
TRANTYPE
k
CHAR(8)
Value
to
be
compared
with
the
transaction
type,
obtained
from
field
PGMNAME.
If
PGMNAME=DFHMIR
or
DFHMIRS
then
the
obtained
value
is
’FS’,
if
PGMNAME=DFHCRP
or
DFHRTE
then
the
obtained
value
is
’TERM’,
else
the
obtained
value
is
’APPL’.
TRANSID
k
CHAR(4)
Value
to
be
compared
with
the
transaction
ID,
obtained
from
the
field
TRAN.
USERFLD
k
CHAR(8)
Value
to
be
compared
with
the
value
calculated
for
USERFLD.
By
default
the
first
character
of
the
field
USERID.
Can
be
altered
by
the
user.
ACCTID
CHAR(8)
Account
ID,
obtained
when
the
key
columns
match
the
corresponding
log
fields.
RAFACICS
translation
table
72
Tivoli
Decision
Support
for
OS/390:
Accounting
Feature
for
the
Host
RAFADASD
This
table
contains
the
rules
for
translating
account
translation
elements
in
DCOLLECT
log
records
to
account
IDs
in
the
RAFADASD
table.
Column
name
Data
type
Description
DSNQUAL1
k
CHAR(8)
Value
to
be
compared
with
the
first
qualifier
of
the
data
set
in
the
field
DCAASSOC.
DSNQUAL2
k
CHAR(8)
Value
to
be
compared
with
the
second
qualifier
of
the
data
set
in
the
field
DCAASSOC.
DSNQUAL3
k
CHAR(8)
Value
to
be
compared
with
the
third
qualifier
of
the
data
set
in
the
field
DCAASSOC.
DSNQUALL
k
CHAR(8)
Value
to
be
compared
with
the
last
qualifier
of
the
data
set
in
the
field
DCAASSOC.
SYSID
k
CHAR(8)
Value
to
be
compared
with
the
system
identification
in
the
field
DCUSYSID.
ACCTID
CHAR(8)
Account
ID,
obtained
when
the
key
columns
match
the
corresponding
log
fields.
RAFADASD
translation
table
Chapter
8.
Accounting
feature
translation
tables
73
RAFADB2
This
table
contains
the
rules
for
translating
account
translation
elements
in
DB2
log
records
to
account
IDs
in
the
RAFADB2
table.
Column
name
Data
type
Description
CORRELAT
k
CHAR(12)
Value
to
be
compared
with
the
correlation
ID,
obtained
from
field
QWHCCV.
CONNTYPE
k
CHAR(8)
Value
to
be
compared
with
the
type
of
system
that
is
connected,
obtained
from
QWHCCN.
AUTHORIZ
k
CHAR(8)
Value
to
be
compared
with
the
authorization
ID,
obtained
from
QWHCAID.
SUBSYSID
k
CHAR(8)
Value
to
be
compared
with
the
subsystem
ID,
obtained
from
QWHSSSID.
SYSID
k
CHAR(8)
Value
to
be
compared
with
the
system
ID,
obtained
from
SM101SID.
ACCTID
CHAR(8)
Account
ID,
obtained
when
the
key
columns
match
the
corresponding
log
fields.
RAFADB2
translation
table
74
Tivoli
Decision
Support
for
OS/390:
Accounting
Feature
for
the
Host
RAFAHSMBKUP
This
table
contains
the
rules
for
translating
account
translation
elements
in
the
DCOLLECT
log
to
account
IDs
in
the
RAFHSMBKUP
table.
Column
name
Data
type
Description
DSNQUAL1
k
CHAR(8)
Value
to
be
compared
with
the
first
qualifier
of
the
data
set
in
the
field
UBDSNAM.
DSNQUAL2
k
CHAR(8)
Value
to
be
compared
with
the
second
qualifier
of
the
data
set
in
the
field
UBDSNAM.
DSNQUAL3
k
CHAR(8)
Value
to
be
compared
with
the
third
qualifier
of
the
data
set
in
the
field
UBDSNAM.
DSNQUALL
k
CHAR(8)
Value
to
be
compared
with
the
last
qualifier
of
the
data
set
in
the
field
UBDSNAM.
SYSID
k
CHAR(8)
Value
to
be
compared
with
the
system
ID
in
the
field
DCUSYSID.
ACCTID
CHAR(8)
Account
ID,
obtained
when
the
key
columns
match
the
corresponding
log
fields.
RAFAHSMBKUP
translation
table
Chapter
8.
Accounting
feature
translation
tables
75
RAFAHSMMIGR
This
table
contains
the
rules
for
translating
account
translation
elements
in
the
DCOLLECT
log
to
account
IDs
in
the
RAFHSMMIGR
table.
Column
name
Data
type
Description
DSNQUAL1
k
CHAR(8)
Value
to
be
compared
with
the
first
qualifier
of
the
data
set
in
the
field
UMDSNAM.
DSNQUAL2
k
CHAR(8)
Value
to
be
compared
with
the
second
qualifier
of
the
data
set
in
the
field
UMDSNAM.
DSNQUAL3
k
CHAR(8)
Value
to
be
compared
with
the
third
qualifier
of
the
data
set
in
the
field
UMDSNAM.
DSNQUALL
k
CHAR(8)
Value
to
be
compared
with
the
last
qualifier
of
the
data
set
in
the
field
UMDSNAM.
SYSID
k
CHAR(8)
Value
to
be
compared
with
the
system
ID
in
the
field
DCUSYSID.
ACCTID
CHAR(8)
Account
ID,
obtained
when
the
key
columns
match
the
corresponding
log
fields.
RAFAHSMMIGR
translation
table
76
Tivoli
Decision
Support
for
OS/390:
Accounting
Feature
for
the
Host
RAFAIMS
This
table
contains
the
rules
for
translating
account
translation
elements
in
IMS
log
records
to
account
IDs
in
the
RAFIMS
table.
Column
name
Data
type
Description
TERMID
k
CHAR(8)
Values
of
logical
terminal
IDs
which
will
be
compared
with
the
value
in
the
field
DRL_OLTERM.
USERID
k
CHAR(8)
Values
of
USERIDs
which
will
be
compared
with
the
value
in
the
field
DRL_OUSER.
SYSID
k
CHAR(8)
Values
of
the
system
identifications
which
will
be
compared
with
the
value
in
the
collect
parameter
MVS_SYSTEM_ID.
TRANTYPE
k
CHAR(8)
Values
of
transaction
types
which
will
be
compared
with
the
value
in
the
field
DRL_TRANT.
TRANSID
k
CHAR(8)
Value
of
transaction
ID
which
will
be
compared
with
the
value
depending
on
the
first
character
of
the
fields
DRL_TRANT
and
DRL_SMBNM.
ACCTID
CHAR(8)
Account
ID,
obtained
when
the
key
columns
match
the
corresponding
log
fields.
RAFAIMS
translation
table
Chapter
8.
Accounting
feature
translation
tables
77
RAFANETSESM
This
table
contains
the
rules
for
translating
account
translation
elements
in
SMF
log
records
to
account
IDs
in
the
RAFNETSES20
table.
Column
name
Data
type
Description
ANUM
k
CHAR(8)
To
be
matched
with
the
account
number
of
the
session
obtained
from
LSCDANUM.
USERID
k
CHAR(8)
To
be
matched
with
the
operator
ID
of
the
session
obtained
from
LSCDUSER.
GROUPID
k
CHAR(8)
To
be
matched
with
the
group
ID
of
the
session
obtained
from
LSCDGRUP.
ACCTID
CHAR(8)
Account
ID,
obtained
when
the
key
columns
match
the
corresponding
log
fields.
RAFANETSESM
translation
table
78
Tivoli
Decision
Support
for
OS/390:
Accounting
Feature
for
the
Host
RAFANETV
This
table
contains
the
rules
for
translating
account
translation
elements
in
SMF
log
records
to
account
IDs
in
the
RAFNETV
table.
Column
name
Data
type
Description
SLUGROUP
k
CHAR(8)
Value
to
be
compared
with
the
first
four
characters
of
SLUNAME
plus
blanks,
obtained
from
LSESSNAM.
SLUNAME
k
CHAR(8)
Value
to
be
compared
with
the
Secondary
Logical
Unit
(SLU)
name,
obtained
from
LSESSNAM.
PLUGROUP
k
CHAR(8)
Value
to
be
compared
with
the
first
four
characters
of
PLUNAME
plus
blanks,
obtained
from
LSESPNAM.
PLUNAME
k
CHAR(8)
Value
to
be
compared
with
the
Primary
Logical
Unit
(PLU)
name,
obtained
from
LSESPNAM.
SUBSYSID
k
CHAR(8)
Value
to
be
compared
with
the
subsystem
ID,
obtained
from
LOGRSUBS.
SYSID
k
CHAR(8)
Value
to
be
compared
with
the
system
ID.
ACCTID
CHAR(8)
Account
ID,
obtained
when
the
key
columns
match
the
corresponding
log
fields.
RAFANETV
translation
table
Chapter
8.
Accounting
feature
translation
tables
79
RAFASTC
This
table
contains
the
rules
for
translating
account
translation
elements
in
SMF
log
records
to
account
IDs
in
the
RAFSTC
table.
Column
name
Data
type
Description
ACCT1
k
CHAR(8)
To
be
matched
with
the
first
eight
characters
of
SMF30ACT,
obtained
from
the
first
accounting
section.
ACCT2
k
CHAR(8)
To
be
matched
with
the
first
eight
characters
of
SMF30ACT,
obtained
from
the
second
accounting
section.
ACCT3
k
CHAR(8)
To
be
matched
with
the
first
eight
characters
of
SMF30ACT,
obtained
from
the
third
accounting
section.
ACCT4
k
CHAR(8)
To
be
matched
with
the
first
eight
characters
of
SMF30ACT,
obtained
from
the
fourth
accounting
section.
ACCT5
k
CHAR(8)
To
be
matched
with
the
first
eight
characters
of
SMF30ACT,
obtained
from
the
fifth
accounting
section.
RACFGRP
k
CHAR(9)
To
be
matched
with
the
RACF
group
of
the
JOB
obtained
from
SMF30GRP.
USERID
k
CHAR(8)
To
be
matched
with
the
RACF
user
ID
of
the
job
obtained
from
SMF30RUD.
JOBNAME
k
CHAR(8)
To
be
matched
with
the
JOBNAME
of
the
job
obtained
from
SMF30JBN,
SMF26JBN,
or
SMF25JBN.
SYSID
k
CHAR(8)
To
be
compared
with
the
system
ID,
obtained
from
SMF30SID.
PGMNAME
k
CHAR(8)
To
be
compared
with
the
program
name,
obtained
from
SMF30PGM.
USERFLD
k
CHAR(8)
To
be
compared
with
A_USERFLD
in
RAFADDRLOG,
whose
default
value
is
the
first
character
of
the
job
name.
The
user
can
modify
this
default
calculation.
ACCTID
CHAR(8)
Account
ID,
obtained
when
the
key
columns
match
the
corresponding
log
fields.
RAFASTC
translation
table
80
Tivoli
Decision
Support
for
OS/390:
Accounting
Feature
for
the
Host
RAFATSO
This
table
contains
the
rules
for
translating
account
translation
elements
in
SMF
log
records
to
account
IDs
in
the
RAFTSO
table.
Column
name
Data
type
Description
ACCT1
k
CHAR(8)
To
be
matched
with
the
first
eight
characters,
obtained
from
SMF30ACT
of
the
first
accounting
section.
ACCT2
k
CHAR(8)
To
be
matched
with
the
first
eight
characters,
obtained
from
SMF30ACT
of
the
second
accounting
section.
ACCT3
k
CHAR(8)
To
be
matched
with
the
first
eight
characters,
obtained
from
SMF30ACT
of
the
third
accounting
section.
ACCT4
k
CHAR(8)
To
be
matched
with
the
first
eight
characters,
obtained
from
SMF30ACT
of
the
fourth
accounting
section.
ACCT5
k
CHAR(8)
To
be
matched
with
the
first
eight
characters,
obtained
from
SMF30ACT
of
the
fifth
accounting
section.
RACFGRP
k
CHAR(9)
To
be
matched
with
the
RACF
group
of
the
job,
obtained
from
SMF30GRP.
USERID
k
CHAR(8)
To
be
matched
with
the
RACF
user
ID
of
the
job,
obtained
from
SMF30RUD.
TERMID
k
CHAR(8)
To
be
compared
with
the
terminal
ID,
obtained
from
SMF30TID.
SYSID
k
CHAR(8)
To
be
compared
with
the
system
ID,
obtained
from
SMF30SID.
USERFLD
k
CHAR(8)
To
be
compared
with
S_USERFLD
in
RAFSESLOG,
whose
default
value
is
the
first
character
of
the
RACF
user
ID.
The
user
can
modify
this
default
calculation.
ACCTID
CHAR(8)
Account
ID,
obtained
when
the
key
columns
match
the
corresponding
log
fields.
RAFATSO
translation
table
Chapter
8.
Accounting
feature
translation
tables
81
RAFATSO
translation
table
82
Tivoli
Decision
Support
for
OS/390:
Accounting
Feature
for
the
Host
Chapter
9.
Accounting
feature
reports
This
chapter
describes
the
reports
that
are
provided
with
the
Tivoli
Decision
Support
for
OS/390
Accounting
feature.
Accounting
feature
report
definitions
This
section
describes
the
report
definitions.
Prorated
account
percentage
validation
report
The
following
information
identifies
the
report:
Report
ID
RAFA001
Report
Group
Resource
Accounting
Reports
Source
ACCT_PRORATE
Attributes
ACCOUNT,
PRORATION,
PERCENTAGE,
VALIDATION
Figure
12
shows
an
example
of
this
report:
The
report
contains
the
following
information:
ACCOUNT_ID1
Account
name
1.
ACCOUNT_ID2
Account
name
2.
ACCOUNT_ID3
Account
name
3.
ACCOUNT_ID4
Account
name
4.
ACCOUNT_ID5
Account
name
5.
CUSTOMER_ID
Customer
name.
PERCENTAGE
Percent
used.
Prorated
Account
Percentages
Validation
FIX
ANY
ACCOUNT
WITH
PERCENTAGE
OTHER
THAN
%100
ACCOUNT
ACCOUNT
ACCOUNT
ACCOUNT
ACCOUNT
CUSTOMER
ID1
ID2
ID3
ID4
ID5
ID
PERCENTAGE
------------
------------
------------
------------
------------
-----------
----------
ACCN01
MARELLA-1
9.700E+01
Figure
12.
Prorated
account
percentage
validation
83
Charges
by
billing
period
report
The
following
information
identifies
the
report:
Report
ID
RAFA004
Report
Group
Resource
Accounting
Reports
Source
BILLED_DATA_CREDIT_DEBIT
Attributes
BILLING,
SUMMARY
Figure
13
shows
an
example
of
this
report:
The
report
contains
the
following
information:
BP_ID
Billing
period.
CPU_SECONDS
Number
of
CPU
seconds
used.
TAPE_EXCPS
Number
of
tape
exceptions.
DISK_EXCPS
Number
of
disk
exceptions.
PRINT_LINES
Number
of
lines
printed.
TAPE_MOUNTS
Number
of
tape
mounts.
PAGES_PRINTED
Number
of
pages
printed.
DASD_MBYTES
Number
of
DASD
MB.
SESSION_KBYTES
Number
of
session
KB.
MISC
Miscellaneous.
CHARGES
BY
CHARGE
TYPE
BP
CPU
TAPE
DISK
TAPE
PAGES
DASD
SESSION
ID
SECONDS
EXCPS
EXCPS
LINES
MOUNTS
PRINTED
MBYTES
KBYTES
MISC
--------
----------
---------
---------
----------
----------
----------
----------
----------
----------
NULLBP
0.000E+00
-
-
-
-
-
-
-
0.000E+00
PUTV
4.943E+01
-
-
-
-
-
-
-
0.000E+00
Figure
13.
Charges
by
charge
type
Charges
by
billing
period
report
84
Tivoli
Decision
Support
for
OS/390:
Accounting
Feature
for
the
Host
Charges
by
billing
period,
with
two
currencies
report
The
following
information
identifies
the
report:
Report
ID
RAFA005
Report
Group
Resource
Accounting
Reports
Source
BILLED_DATA
Attributes
BILLING,
SUMMARY
Figure
14
shows
an
example
of
this
report:
The
report
contains
the
following
information:
BILLING_PERIOD
Billing
period.
CUSTOMER_ID
Customer
name.
CPU_SEC_QUANTITY
Sum
of
CPU
seconds.
CPU_SEC_PRICE_C1
Price
of
CPU
seconds
with
first
currency
(for
example,
dollars).
CPU_SEC_AMOUNT_C1
Total
amount
for
CPU
seconds
with
first
currency
(for
example,
dollars).
CPU_SEC_PRICE_C2
Price
of
CPU
seconds
with
second
currency
(for
example,
euros).
CPU_SEC_AMOUNT_C2
Total
amount
for
CPU
seconds
with
second
currency
(for
example,
euros).
Charges
by
Billing
Period,
with
Two
Currencies
CPU
CPU
CPU
CPU
CPU
SEC
SEC
SEC
SEC
BILLING
CUSTOMER
SEC
PRICE
AMOUNT
PRICE
AMOUNT
PERIOD
ID
QUANTITY
C1
C1
C2
C2
--------
----------
---------
---------
---------
---------
---------
NULLBP
CUST1
4.36
10.00
43.60
100.00
436.00
Figure
14.
Charges
by
billing
period,
with
two
currencies
Charges
by
billing
period,
with
two
currencies
report
Chapter
9.
Accounting
feature
reports
85
Billing
details
report
The
following
information
identifies
the
report:
Report
ID
RAFA002
Report
Group
Resource
Accounting
Reports
Source
BILLED_DATA
Attributes
BILLING,
DETAILS,
BILLED_DATA
Figure
15
shows
an
example
of
this
report:
The
report
contains
the
following
information:
BILLING_PERIOD
Billing
period.
CUSTOMER
Customer
name.
CHARGE_TYPE
ACCOUNT
AC2
AC3
AC4
AC5
PERIOD_NAME
DESCRIPTION
QUANTITY
PRICE
AMOUNT
BILLING
DETAILS
REPORT
BILLING
CHARGE
PERIOD
PERIOD
CUSTOMER
TYPE
ACCOUNT
AC2
AC3
AC4
AC5
NAME
DESCRIPTION
QUANTITY
PRICE
AMOUNT
--------
---------------
------
----------
-----
-----
-----
-----
-------
------------
---------
----------
---------
PUTV
MARELLA-1
N
ACCN01
NIGHT
CPU
SECONDS
3.316E+01
1.000E+00
8.289E+00
PUTV
MARELLA-2
N
ACCN02
NIGHT
CPU
SECONDS
3.311E+01
1.000E+00
8.277E+00
PUTV
MARELLA-3
N
ACCN03
NIGHT
CPU
SECONDS
3.305E+01
1.000E+00
8.262E+00
PUTV
MARELLA-4
N
ACCN04
NIGHT
CPU
SECONDS
3.264E+01
1.000E+00
8.159E+00
PUTV
MARELLA-5
N
ACCN05
NIGHT
CPU
SECONDS
3.301E+01
1.000E+00
8.253E+00
PUTV
MARELLA-6
N
ACCN06
NIGHT
CPU
SECONDS
3.278E+01
1.000E+00
8.195E+00
Figure
15.
Billing
details,
partial
view
Billing
details
report
86
Tivoli
Decision
Support
for
OS/390:
Accounting
Feature
for
the
Host
Charges
for
selected
billing
period
report
The
following
information
identifies
the
report:
Report
ID
RAFA003
Report
Group
Resource
Accounting
Reports
Source
BILLED_DATA
Attributes
BILLING,
SUMMARY
Variables
BP_ID
Figure
16
shows
an
example
of
this
report:
The
report
contains
the
following
information:
BP_ID
Billing
period.
CPU_SECONDS
Number
of
CPU
seconds
used.
TAPE_EXCPS
Number
of
tape
exceptions.
DISK_EXCPS
Number
of
disk
exceptions.
PRINT_LINES
Number
of
lines
printed.
TAPE_MOUNTS
Number
of
tape
mounts.
PAGES_PRINTED
Number
of
pages
printed.
DASD_MBYTES
Number
of
DASD
MB.
SESSION_KBYTES
Number
of
session
KB.
MISC
Miscellaneous.
CHARGES
BY
CHARGE
TYPE
BP
CPU
TAPE
DISK
TAPE
PAGES
DASD
SESSION
ID
SECONDS
EXCPS
EXCPS
LINES
MOUNTS
PRINTED
MBYTES
KBYTES
MISC
--------
----------
---------
---------
----------
----------
----------
----------
----------
----------
PUTV
4.943E+01
-
-
-
-
-
-
-
0.000E+00
Figure
16.
Charges
by
charge
type
Charges
for
selected
billing
period
report
Chapter
9.
Accounting
feature
reports
87
Charges
for
selected
billing
period
report
88
Tivoli
Decision
Support
for
OS/390:
Accounting
Feature
for
the
Host
Chapter
10.
Considerations
for
dpAM
users
This
chapter
compares
the
functions
of
the
Tivoli
Decision
Support
for
OS/390
Accounting
feature
with
those
of
the
dp
Accounting
Manager
(dpAM).
The
Tivoli
Decision
Support
for
OS/390
Accounting
feature
provides
basic
accounting
and
chargeback
features.
If
you
are
moving
from
the
dp
Accounting
Manager
to
the
Accounting
feature,
see
the
following
table
about
the
functional
equivalents
of
the
two
products.
In
the
case
of
functionality
that
is
in
the
dp
Accounting
Manager
but
not
included
in
the
base
support
in
the
Accounting
feature,
suggestions
are
provided
to
help
you
achieve
similar
functionality.
Table
3.
dpAM
and
Accounting
feature
comparison
Function
dpAM
Tivoli
Decision
Support
for
OS/390
Accounting
feature
User
Interface
yes
yes
(Tivoli
Decision
Support
for
OS/390
user
interface.)
Overhead
accounts
yes
yes
(Fixed
and
variable
proration.)
Batch
accounting
yes
yes
CICS
accounting
yes
yes
IMS
accounting
yes
yes
DB2
accounting
yes
yes
DASD
accounting
yes
yes
Network
accounting
yes
yes
Credit/Debits
yes
yes
(Enhanced
to
allow
two
different
currency
values
in
addition
to
quantity.)
Flexible
pricing
yes
yes
Price
list
versions
yes
no
(Price
list
is
a
lookup
table.
Prior
versions
can
be
copied
to
a
file
for
historical
reference.)
Cost
lists
yes
no
(Product
can
be
customized
to
include
a
cost-list
table.
Additional
customization
could
enable
this
cost-list
table
to
be
used
in
creating
updates
to
the
price
list
lookup
table.)
Forecasting
yes
no
(Data
could
be
exported
to
spreadsheet
or
other
third-party
product
that
provides
forecasting
capabilities.)
Budgeting
yes
no
(Accounting
feature
can
be
customized
to
include
budget
tables
and
queries.)
89
90
Tivoli
Decision
Support
for
OS/390:
Accounting
Feature
for
the
Host
Part
3.
Appendixes
91
92
Tivoli
Decision
Support
for
OS/390:
Accounting
Feature
for
the
Host
Notices
This
information
was
developed
for
products
and
services
offered
in
the
U.S.A.
IBM
may
not
offer
the
products,
services,
or
features
discussed
in
this
document
in
other
countries.
Consult
your
local
IBM
representative
for
information
on
the
products
and
services
currently
available
in
your
area.
Any
reference
to
an
IBM
product,
program,
or
service
is
not
intended
to
state
or
imply
that
only
that
IBM
product,
program,
or
service
may
be
used.
Any
functionally
equivalent
product,
program,
or
service
that
does
not
infringe
any
IBM
intellectual
property
right
may
be
used
instead.
However,
it
is
the
user’s
responsibility
to
evaluate
and
verify
the
operation
of
any
non-IBM
product,
program,
or
service.
IBM
may
have
patents
or
pending
patent
applications
covering
subject
matter
described
in
this
document.
The
furnishing
of
this
document
does
not
give
you
any
license
to
these
patents.You
can
send
license
inquiries,
in
writing,
to:
IBM
Director
of
Licensing
IBM
Corporation
500
Columbus
Avenue
Thornwood,
NY
10594
U.S.A.
For
license
inquiries
regarding
double-byte
(DBCS)
information,
contact
the
IBM
Intellectual
Property
Department
in
your
country
or
send
inquiries,
in
writing,
to:
IBM
World
Trade
Asia
Corporation
Licensing
2-31
Roppongi
3-chome,
Minato-ku
Tokyo
106,
Japan
The
following
paragraph
does
not
apply
to
the
United
Kingdom
or
any
other
country
where
such
provisions
are
inconsistent
with
local
law:
INTERNATIONAL
BUSINESS
MACHINES
CORPORATION
PROVIDES
THIS
PUBLICATION
″AS
IS″
WITHOUT
WARRANTY
OF
ANY
KIND,
EITHER
EXPRESS
OR
IMPLIED,
INCLUDING,
BUT
NOT
LIMITED
TO,
THE
IMPLIED
WARRANTIES
OF
NON-INFRINGEMENT,
MERCHANTABILITY
OR
FITNESS
FOR
A
PARTICULAR
PURPOSE.
Some
states
do
not
allow
disclaimer
of
express
or
implied
warranties
in
certain
transactions,
therefore,
this
statement
might
not
apply
to
you.
This
information
could
include
technical
inaccuracies
or
typographical
errors.
Changes
are
periodically
made
to
the
information
herein;
these
changes
will
be
incorporated
in
new
editions
of
the
publication.
IBM
may
make
improvements
and/or
changes
in
the
product(s)
and/or
the
program(s)
described
in
this
publication
at
any
time
without
notice.
Any
references
in
this
information
to
non-IBM
Web
sites
are
provided
for
convenience
only
and
do
not
in
any
manner
serve
as
an
endorsement
of
those
Web
sites.
The
materials
at
those
Web
sites
are
not
part
of
the
materials
for
this
IBM
product
and
use
of
those
Web
sites
is
at
your
own
risk.
93
IBM
may
use
or
distribute
any
of
the
information
you
supply
in
any
way
it
believes
appropriate
without
incurring
any
obligation
to
you.
Licensees
of
this
program
who
wish
to
have
information
about
it
for
the
purpose
of
enabling:
(i)
the
exchange
of
information
between
independently
created
programs
and
other
programs
(including
this
one)
and
(ii)
the
mutual
use
of
the
information
which
has
been
exchanged,
should
contact:
IBM
Corporation
2Z4A/101
11400
Burnet
Road
Austin,
TX
78758
U.S.A.
Such
information
may
be
available,
subject
to
appropriate
terms
and
conditions,
including
in
some
cases
payment
of
a
fee.
The
licensed
program
described
in
this
document
and
all
licensed
material
available
for
it
are
provided
by
IBM
under
terms
of
the
IBM
Customer
Agreement,
IBM
International
Program
License
Agreement
or
any
equivalent
agreement
between
us.
This
information
contains
examples
of
data
and
reports
used
in
daily
business
operations.
To
illustrate
them
as
completely
as
possible,
the
examples
include
the
names
of
individuals,
companies,
brands,
and
products.
All
of
these
names
are
fictitious
and
any
similarity
to
the
names
and
addresses
used
by
an
actual
business
enterprise
is
entirely
coincidental.
COPYRIGHT
LICENSE:
This
information
contains
sample
application
programs
in
source
language,
which
illustrate
programming
techniques
on
various
operating
platforms.
You
may
copy,
modify,
and
distribute
these
sample
programs
in
any
form
without
payment
to
IBM,
for
the
purposes
of
developing,
using,
marketing
or
distributing
application
programs
conforming
to
the
application
programming
interface
for
the
operating
platform
for
which
the
sample
programs
are
written.
These
examples
have
not
been
thoroughly
tested
under
all
conditions.
IBM,
therefore,
cannot
guarantee
or
imply
reliability,
serviceability,
or
function
of
these
programs.
You
may
copy,
modify,
and
distribute
these
sample
programs
in
any
form
without
payment
to
IBM
for
the
purposes
of
developing,
using,
marketing,
or
distributing
application
programs
conforming
to
IBM’s
application
programming
interfaces.
Each
copy
or
any
portion
of
these
sample
programs
or
any
derivative
work,
must
include
a
copyright
notice
as
follows:
©
(your
company
name)
(year).
Portions
of
this
code
derived
from
IBM
Corp.
Sample
Programs.
©
Copyright
IBM
Corp.
_enter
the
year
or
years_.
All
rights
reserved.
If
you
are
viewing
this
information
in
softcopy
form,
the
photographs
and
color
illustrations
might
not
appear.
94
Tivoli
Decision
Support
for
OS/390:
Accounting
Feature
for
the
Host
Trademarks
DB2,
DB2
Universal
Database,
IBM,
the
IBM
logo,
Tivoli,
Tivoli
Enterprise,
Tivoli
Enterprise
Console,
AS/400,
CICS,
IMS,
MVS,
Netview,
OS/390,
QMF,
RACF,
TME,
VTAM,
WebSphere
and
z/OS
are
trademarks
or
registered
trademarks
of
International
Business
Machines
Corporation
in
the
United
States,
other
countries,
or
both.
Microsoft,
Windows,
Windows
NT,
and
the
Windows
logo
are
trademarks
of
Microsoft
Corporation
in
the
United
States,
other
countries,
or
both.
UNIX
is
a
registered
trademark
of
The
Open
Group
in
the
United
States
and
other
countries.
Java
and
all
Java-based
trademarks
are
trademarks
of
Sun
Microsystems,
Inc.
in
the
United
States,
other
countries,
or
both.
Other
company,
product,
and
service
names
may
be
trademarks
or
service
marks
of
others.
Notices
95
96
Tivoli
Decision
Support
for
OS/390:
Accounting
Feature
for
the
Host
List
of
abbreviations
These
abbreviations
appear
in
this
book:
BMU
base
measurement
unit
CICS
Customer
Information
and
Control
System
CPU
central
processing
unit
DL/I
Data
Language/I
DMU
derived
measurement
unit
DP
data
processing
IMS
Information
Management
System
I/O
input/output
NPM
NetView
Performance
Monitor
SMF
system
management
facilities
SQL
Structured
Query
Language
TSO
time-sharing
option
97
98
Tivoli
Decision
Support
for
OS/390:
Accounting
Feature
for
the
Host
Glossary
A
account.
Based
on
the
information
in
usage
logs,
all
usage
is
allocated
to
an
account.
For
example,
you
can
use
fields
such
as
user
ID
and
terminal
ID
to
determine
the
account.
Each
account
belongs
to
a
customer,
who
will
be
charged
for
its
system
usage.
ad
hoc
billing.
Ordinarily,
billing
is
performed
after
the
end
of
a
billing
period.
If
you
need
to
bill
certain
customers
for
some
charges
before
the
end
of
the
billing
period,
you
can
produce
an
ad
hoc
bill.
administration.
A
Tivoli
Decision
Support
for
OS/390
task
that
includes
maintaining
the
database,
updating
environment
information,
and
ensuring
the
accuracy
of
data
collected.
administration
dialog.
The
set
of
host
windows
used
to
administer
Tivoli
Decision
Support
for
OS/390.
agent.
In
UNIX
Performance
feature,
a
set
of
programs
running
on
a
network
node
that
gather
data
about
the
node
and
write
the
data
to
log
files.
Agents
can
gather
data
by
issuing
UNIX
commands,
and
by
reading
files
such
as
UNIX
accounting
files.
B
billing
period.
The
Accounting
feature
can
generate
billing
periods
every
week,
every
two
weeks,
twice
per
month,
once
per
month,
or
once
per
quarter.
You
can
also
specify
the
start
date
and
end
date
of
each
billing
period
manually.
billing
unit.
Customers
are
charged
according
to
the
number
of
billing
units
that
they
consume.
A
billing
unit
can
consist
of
only
a
measurement
unit
(such
as
CPU
seconds)
or
a
measurement
unit
and
one
or
more
service
types
(such
as
CPU
seconds,
during
first
shift,
with
jobclass
A).
BMU.
Base
measurement
unit.
C
collect.
A
process
used
by
Tivoli
Decision
Support
for
OS/390
to
read
data
from
input
log
data
sets,
interpret
records
in
the
data
set,
and
store
the
data
in
DB2
tables
in
the
Tivoli
Decision
Support
for
OS/390
database.
component.
An
optionally
installable
part
of
an
Tivoli
Decision
Support
for
OS/390
feature.
control
table.
A
predefined
Tivoli
Decision
Support
for
OS/390
table
that
controls
results
returned
by
some
log
collector
functions.
credit.
If
you
discover
an
error
in
a
previous
bill,
you
can
specify
a
positive
or
negative
credit.
The
credit
can
be
either
a
number
of
billing
units
or
an
amount
of
money.
customer.
A
customer
is
a
person
or
organization
that
uses
the
services
provided
by
your
DP
center.
Each
customer
has
one
or
more
accounts.
D
Data
Language/I
(DL/I).
An
IBM
database-management
facility.
data
table.
A
Tivoli
Decision
Support
for
OS/390
table
that
contains
performance
data
used
to
create
reports.
DMU.
Derived
measurement
unit.
discounts.
You
can
give
customers
discounts
based
on
their
level
of
system
usage.
You
can
define
one
set
of
discounts
for
all
customers,
or
different
discounts
for
different
customers.
99
distributed
transaction
processing.
The
distribution
of
processing
among
transactions
that
communicate
synchronously
with
each
other
over
intersystem
or
interregion
links.
E
environment
information.
All
of
the
information
that
is
added
to
the
log
data
to
create
reports.
This
information
can
include
data
such
as
performance
groups,
shift
periods,
installation
definitions,
and
so
on.
F
final
billing.
At
the
end
of
a
billing
period,
you
can
produce
a
preliminary
bill,
check
the
preliminary
bill,
and
then
produce
a
final
bill.
You
then
export
the
billing
information
to
your
invoicing
system.
functional
billing.
In
functional
billing,
customers
are
charged
in
terms
of
billing
units
that
are
meaningful
to
them,
such
as
CICS
transactions,
rather
than
in
terms
of
the
basic
resources
of
the
computing
system.
(Contrast
with
Resource
billing.)
G
gather.
A
process
performed
by
agents
in
which
performance
data
is
entered
into
log
files.
The
log
files
are
located
on
the
same
nodes
as
the
agents.
H
help
topics.
An
online
table
of
contents
for
the
Tivoli
Decision
Support
for
OS/390
online
help
information.
K
key
columns.
The
columns
of
a
DB2
table
that
together
constitute
the
key.
key
value.
The
value
used
to
sort
records
into
groups.
L
log.
Any
sequential
data
set
used
as
input
to
Tivoli
Decision
Support
for
OS/390.
log
collector.
A
Tivoli
Decision
Support
for
OS/390
program
that
processes
log
data
sets
and
provides
other
services.
log
collector
language.
Tivoli
Decision
Support
for
OS/390
statements
used
to
supply
definitions
to
and
invoke
services
of
the
log
collector.
log
data
set.
Any
sequential
data
set
used
as
input
to
Tivoli
Decision
Support
for
OS/390.
log
definition.
The
description
of
a
log
data
set
processed
by
the
log
collector.
log
procedure.
A
program
module
that
is
used
to
process
all
record
types
in
certain
log
data
sets.
logical
unit
(LU).
A
port
through
which
a
user
gains
access
to
the
services
of
a
network.
lookup
expression.
An
expression
that
specifies
how
a
value
is
obtained
from
a
lookup
table.
lookup
table.
A
Tivoli
Decision
Support
for
OS/390
DB2
table
that
contains
grouping,
translation,
or
substitution
information.
M
measurement
units.
You
can
measure
system
usage
at
a
basic
resource
level
(such
as
CPU
seconds)
or
at
a
functional
level
(such
as
CICS
transactions).
Measurement
units
serve
as
the
basis
for
billing
units.
100
Tivoli
Decision
Support
for
OS/390:
Accounting
Feature
for
the
Host
O
object.
An
integral
part
of
a
feature
component
needed
for
data
collection
(for
example,
record
definitions,
record
procedures,
and
update
definitions).
occasional
charges.
You
can
specify
charges
for
occasional
services
such
as
consultancy,
education,
or
programming
effort.
These
charges
can
be
recorded
either
as
a
volume
of
billing
units
or
as
an
amount
of
money.
P
Tivoli
Decision
Support
for
OS/390
database.
A
set
of
DB2
tables
that
includes
data
tables,
lookup
tables,
system
tables,
and
control
tables.
preliminary
billing.
Before
you
produce
your
final
bill,
you
can
produce
a
preliminary
bill.
You
can
check
the
preliminary
bill
and
make
any
necessary
changes
before
producing
the
final
bill.
You
can
also
produce
preliminary
bills
before
the
end
of
a
billing
period,
if
you
want
up-to-date
usage
information.
producing
system.
Any
product
or
service
whose
usage
is
recorded
is
called
a
producing
system
in
Accounting
Feature.
The
most
common
producing
systems,
such
as
TSO
and
CICS,
are
predefined
in
the
Accounting
feature.
purge
condition.
Instruction
for
purging
unneeded
data
from
the
Tivoli
Decision
Support
for
OS/390
database.
R
record
definition.
The
description
of
a
record
type
contained
in
the
log
data
sets
used
by
Tivoli
Decision
Support
for
OS/390,
including
detailed
record
layout
and
data
formats.
record
procedure.
A
program
module
that
is
called
to
process
some
types
of
log
records.
record
type.
The
classification
of
records
in
a
log
data
set.
recurrent
charges.
You
can
charge
customers
for
items
that
occur
regularly
but
do
not
appear
in
any
usage
log.
For
example,
you
might
define
a
recurrent
charge
for
terminal
rental.
region.
A
section
of
the
dynamic
area
that
is
allocated
to
a
job
step
or
system
task.
report
definition
language.
Tivoli
Decision
Support
for
OS/390
statements
used
to
define
reports
and
report
groups.
report
group.
A
collection
of
Tivoli
Decision
Support
for
OS/390
reports
that
can
be
referred
to
by
a
single
name.
reporting
dialog.
A
set
of
host
or
workstation
windows
used
to
request
reports.
reports.
Various
QMF
procedures
are
supplied
with
Accounting
Feature
for
producing
reports.
You
can
modify
these
reports
or
define
your
own
reports
using
QMF
or
equivalent
product.
resource.
Any
facility
of
the
computing
system
or
operating
system
required
by
a
job
or
task,
including
central
storage,
input/output
devices,
the
processing
unit,
data
sets,
and
control
or
processing
programs.
resource
billing.
In
resource
billing,
customers
are
charged
in
terms
of
billing
units
that
relate
directly
to
the
basic
resources
of
the
computing
system,
such
as
CPU
seconds.
(Contrast
with
Functional
billing.)
resource
group.
A
collection
of
resources
identified
as
belonging
to
a
particular
department
or
division.
Resources
are
organized
into
groups
to
reflect
the
structure
of
an
organization.
resource
information.
Environment
information
that
describes
the
elements
in
a
system
(for
example,
a
network).
S
section.
A
structure
within
a
record
that
contains
one
or
more
fields
and
may
contain
other
sections.
Glossary
101
service
billing.
A
method
of
charging
that
reflects
the
different
costs
of
running
a
DP
center
under
different
conditions.
source.
In
an
update
definition,
the
record
or
DB2
table
that
contains
the
data
used
to
update
an
Tivoli
Decision
Support
for
OS/390
DB2
table.
subcomponent.
An
optionally
installable
part
of
an
Tivoli
Decision
Support
for
OS/390
feature
component.
system
table.
A
DB2
table
that
stores
information
for
controlling
log
collector
processing,
Tivoli
Decision
Support
for
OS/390
dialogs,
and
reporting.
T
target.
In
an
update
definition,
the
DB2
table
in
which
Tivoli
Decision
Support
for
OS/390
stores
data
from
the
source
record
or
table.
threshold.
The
maximum
or
minimum
acceptable
level
of
usage.
Usage
measurements
are
compared
with
threshold
levels.
Transmission
Control
Protocol/Internet
Protocol
(TCP/IP).
A
non-proprietary
communications
protocol
for
linking
workstations
to
host
computers
and
to
other
hardware.
U
update
definition.
Instructions
for
entering
data
into
DB2
tables
from
records
of
different
types
or
from
other
DB2
tables.
updates.
Instructions
in
Tivoli
Decision
Support
for
OS/390
on
how
to
process
data
from
log
data
sets
to
DB2
tables.
usage
data.
Producing
systems
generate
logs
that
contain
usage
information.
The
Accounting
feature
collects
this
usage
data.
V
view.
An
alternative
representation
of
data
from
one
or
more
tables.
A
view
can
include
all
or
some
of
the
columns
contained
in
the
table
on
which
it
is
defined.
W
workload
periods.
You
can
define
workload
periods,
in
order
to
charge
different
prices
for
system
usage
at
different
times.
For
example,
by
charging
more
for
system
work
during
the
day
on
workdays,
you
encourage
customers
to
run
low-priority
work
at
night,
or
on
weekdays
or
holidays.
102
Tivoli
Decision
Support
for
OS/390:
Accounting
Feature
for
the
Host
Index
Aabbreviations
used
in
this
book,
list
of
97
accessibility
x
ACCOUNT
lookup
table
63
account
proration
tablehow
to
use
with
Tivoli
Decision
Support
for
OS/390
64
Accounting
featurecollecting
usage
data
3
comparison
with
dpAM
functions
89
customizing
for
the
Accounting
feature
9
data
flow
23
implementing
15
installing
11
output
4
overview
3
preparing
9
preparing
for
collect
13
producing
billing
information
3
reports
83
setting
up
security
10
tables
33
trimming
data
tables
10
working
with,
an
example
4
ACCT_PRORATE
lookup
table
64
ACCT_PRORATEV1view
58
ACCT_PRORATEV2view
59
audience
for
this
book,
intended
vii
BBATCH
producing
systemRAFABATCH
translation
table
71
RAFBATCH
data
table
33
RAFJOBLOG
data
table
35
BILLED_DATA
data
table
60
billing
period
tablehow
to
use
with
Tivoli
Decision
Support
for
OS/390
65
billing
units
6,
7
BILLING_PERIOD
lookup
table
65
booksfeedback
viii
online
viii
ordering
viii
CCICS
producing
systemRAFACICS
translation
table
72
RAFCICS
data
table
37
collecting
usage
data
3
CPU
normalizationwith
trimmed
collector
tables
11
CPU_NORMAL_DATA
lookup
table
66
CREDIT_DEBIT
lookup
table
67
credit/debit
tablehow
to
use
with
Tivoli
Decision
Support
for
OS/390
67
CUSTOMER
lookup
table
68
customer
support
x
customer
tablehow
to
use
with
Tivoli
Decision
Support
for
OS/390
68
customers
and
accounts
6
DDASD
producing
systemRAFADASD
translation
table
73
RAFDASD
data
table
39
DASD
subsystemDCOLLECT
LAST_RUN
lookup
table
12
data
flowbilling
process
32
CICS
24
credit
debit
processing
25
DB2
26
DFSMS
27
general
flow
23
IMS
28
NPM
and
NetView
29
overhead
account
31
STC,
BATCH,
TSO
30
data
table
in
resource
accountingtrimming
10
data
table
in
Tivoli
Decision
Support
for
OS/390introduction
9
data
tablesBILLED_DATA
60
RAFADDRLOG
50
RAFBATCH
33
RAFCICS
37
RAFDASD
39
RAFDB2
40
RAFHSMBKUP
42
RAFHSMMIGR
43
RAFIMS.
44
RAFJOBLOG
35
RAFNETSES20
45
RAFNETSES4x
47
RAFNETV
48
RAFSESLOG
53
RAFSTC
49
RAFTSO
52
USE_SUMMARY_D
54
USE_SUMMARY_D2
55
USE_SUMMARY_D3
56
USE_SUMMARY_D4
57
DB2
producing
systemRAFADB2
translation
table
74
RAFDB2
data
table
40
DFSMS_LAST_RUN
lookup
table
12
dpAM,
comparison
with
Accounting
feature
functions
89
DRLJCOLL
batch
job
13
dummyintroduction
9
Gglossary
99
Hhow
to
use
this
book
vii
HSMBKUP
producing
systemRAFAHSMBKUP
translation
table
75
RAFHSMBKUP
data
table
42
HSMBKUP
subsystemDCOLLECT
LAST_RUN
lookup
table
12
HSMMIGR
producing
systemRAFHSMMIGR
translation
table
76
RAFHSSSIGR
data
table
43
HSMMIGR
subsystemDCOLLECT
LAST_RUN
lookup
table
12
Iimplementing
the
Accounting
feature
15
IMS
producing
systemRAFIMS
data
table
44
RAFIMS
translation
table
77
installing
the
Accounting
feature
11
intended
audience
for
this
book
vii
Llist
of
abbreviations
used
in
this
book
97
list
of
terms
used
in
this
book
99
log
in
Tivoli
Decision
Support
for
OS/390introduction
9
LookAt
message
retrieval
tool
ix
lookup
table
in
Tivoli
Decision
Support
for
OS/390introduction
9
maintaining
11
lookup
tablesACCOUNT
63
ACCT_PRORATE
64
BILLING_PERIOD
65
CPU_NORMAL_DATA
66
CREDIT_DEBIT
67
CUSTOMER
68
PRICE_LIST
69
Mmaintaining
lookup
tables
11
manualsfeedback
viii
103
manuals
(continued)online
viii
ordering
viii
message
retrieval
tool,
LookAt
ix
NNETSESM
producing
systemRAFANETSESM
translation
table
78
RAFNETSES20
data
table
45
RAFNETSES4X
data
table
47
NETV
producing
systemRAFNETV
data
table
48
NETV
subsystemTivoli
Decision
Support
for
OS/390
resource
translation
table
13
NLDM
producing
systemRAFANETV
translation
table
79
NPM
subsystemTivoli
Decision
Support
for
OS/390
resource
translation
table
13
NW_RESOURCE
lookup
table
13
Oonline
publications
x
ordering
publications
x
output
from
the
Accounting
feature
4
overview
of
the
Accounting
feature
3
PPreparing
for
collect
13
Preparing
the
Accounting
feature
9
PRICE_LIST
lookup
table
69
pricing
4
producing
billing
information
3
publicationsfeedback
viii
online
viii
ordering
viii
RRAFADDRLOG
data
table
50
RAFJOBLOG
data
table
35
RAFMSESLOG
data
table
53
record
definition
in
Tivoli
Decision
Support
for
OS/390introduction
9
reportsbilling
period
details
86
charges
by
billing
period
84
charges
by
billing
period
report,
with
two
currencies
85
charges
for
selected
billing
period
87
prorated
account
percentage
validation
83
resource
accountingtrimming
the
data
tables
10
Ssecurity
10
setting
prices
4
software
support
x
special
day
tablehow
to
use
with
Tivoli
Decision
Support
for
OS/390
12
STC
producing
systemRAFADDRLOG
data
table
50
RAFASTC
translation
table
80
RAFSTC
data
table
49
Ttables
dataBILLED_DATA
60
RAFADDRLOG
50
RAFBATCH
33
RAFCICS
37
RAFDASD
39
RAFDB2
40
RAFHSMBKUP
42
RAFHSMMIGR
43
RAFIMS.
44
RAFJOBLOG
35
RAFNETSES20
45
RAFNETSES4x
47
RAFNETV
48
RAFSESLOG
53
RAFSTC
49
RAFTSO
52
USE_SUMMARY_D
54
USE_SUMMARY_D2
55
USE_SUMMARY_D3
56
USE_SUMMARY_D4
57
lookupACCOUNT
63
ACCT_PRORATE
64
BILLING_PERIOD
65
CPU_NORMAL_DATA
66
CREDIT_DEBIT
67
CUSTOMER
68
PRICE_LIST
69
translationRAFABATCH
71
RAFACICS
72
RAFADASD
73
RAFADB2
74
RAFAHSMBKUP
75
RAFAHSMMIGR
76
RAFAIMS.
77
RAFANETSESM
78
RAFANETV
79
RAFASTC
80
RAFATSO
81
tables,
described
11,
16
terms
used
in
this
book
99
Tivoli
Decision
Support
for
OS/390distribution
of
objects
9
preparing
for
collect
13
setting
up
security
10
user
groups
10
translation
tablesRAFABATCH
71
RAFACICS
72
RAFADASD
73
RAFADB2
74
RAFAHSMBKUP
75
RAFAHSMMIGR
76
translation
tables
(continued)RAFAIMS.
77
RAFANETSESM
78
RAFANETV
79
RAFASTC
80
RAFATSO
81
trimming
data
tables
10
TSO
producing
systemRAFATSO
translation
table
81
RAFSESLOG
data
table
53
RAFTSO
data
table
52
Uupdate
definition
in
Tivoli
Decision
Support
for
OS/390introduction
9
use
of
this
book,
intended
vii
user
groupsin
Tivoli
Decision
Support
for
OS/390
10
Vviews
ACCT_PRORATEV1
58
ACCT_PRORATEV2
59
views,
described
16
Wwho
should
use
this
book
vii
working
with
the
Accounting
feature,
an
example
4
workload
period
tablehow
to
use
with
Tivoli
Decision
Support
for
OS/390
12
104
Tivoli
Decision
Support
for
OS/390:
Accounting
Feature
for
the
Host
����
Program
Number:
5695-101
Printed
in
USA
SH19-4495-05
