Previous Topic: 3.6 Avoiding IMS Duplicate ChargingNext Topic: 3.7.1 Avoiding Web Duplicate Charging


3.7 Avoiding SNT Duplicate Charging


CA MICS Accounting and Chargeback Option supports the
following CA MICS Network Analyzer Option files for
chargeback processing:

o NCP Network Accounting (SNTNAC) File
o NetSpy Terminal (SNTNSS) File
o NPM User Activity (SNTPSU) File
o NLDM Session Accounting (NVSNSA) File
o NLDM Session Connectivity (NVSNSC) File
o NLDM Response Time (NVSRTM) File

The NCP Network Accounting File is built from Network Session
Accounting (NSA) and Network Gateway Accounting (NGA) data,
from either CA NetSpy or IBM's NetView Performance Monitor
(NPM).  The NPM User Activity File is built from NPM Session
data.  The NLDM files are built using data from either IBM's
NetView Session Monitor/NLDM or NetMaster Network Management
for SNA.  The NetSpy Terminal File is built from NetSpy's
VTAM interface data.

Since there may be overlap between data from these sources,
CA MICS Accounting and Chargeback Option prevents the use of
both NPM and NetView Session Monitor/NLDM files concurrently
for billing.  Should you require the ability to implement
chargeback using both NPM and NetView Session Monitor/NLDM or
both NPM and CA NetMaster sources, we recommend that you call
CA Technical Support for assistance.


HOW TO AVOID DUPLICATE CHARGING

NetSpy and NPM may collect NSA data on both the secondary
(SLU) and primary (PLU) side of a session.  To prevent
collection of duplicate accounting data, collect NSA data on
the secondary side of a session only.  For information on how
to restrict NCP NSA accounting collection, refer to the
accounting parameters in the NCP BUILD Statement in the IBM
NCP Resource Definition Guide.  If your site collects NSA
data on both the primary and secondary sides of a session,
CA MICS data element NACCOLPT, NCP Collection Point (Primary
or Secondary), can help you detect and eliminate duplicate
NSA data.

Similarly, NetSpy and NPM may collect duplicate NGA data for
sessions that traverse multiple gateway NCPs.  To aid in the
detection and elimination of this duplicate data, collect all
NGA data at a single NetSpy or NPM collection host.  NetSpy
automatically discards duplicate NGA data.  It only accepts
NGA data for a given session from the first gateway NCP to
send data for that session.

NPM provides a user exit for detecting and discarding
duplicate NGA data.  See the NPM Installation and
Customization Guide.  CA MICS data elements NACANPLU
(Adjacent Network ID PLU Side), NACANSLU (Adjacent Network ID
SLU Side), and USESSIDC (Unique Session ID) may also be used
to detect and eliminate duplicate NGA data.