Transaction level resource accounting and chargeback for
                           CICS, DB2, IMS, CA-IDMS, NetView, VM, ...
Upcoming SlideShare
Loading in …5

Transaction level resource accounting and chargeback for CICS ...


Published on

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Transaction level resource accounting and chargeback for CICS ...

  1. 1. Transaction level resource accounting and chargeback for CICS, DB2, IMS, CA-IDMS, NetView, VM, and UNIX. To equitably charge for shared environments Up to three levels of shift accounting may be such as CICS, DB2, IMS, CA-IDMS or NetView, applied for standard workdays. Weekend and KOMAND has separate charging systems which holiday rate differentials are also supported. Shift charge at the transaction level rather than the global multipliers may be applied to the entire transaction, (region) level. In a VM environment, charging is or to specific resources within the transaction. The done at the batch-job or CMS level. UNIX environ- KOMAND Charging Systems accept as input the ments are tracked and charged at the individual standard SMF or Log records, plus records pro- process level and to the user level within Oracle duced by most major monitoring systems. and DB2/6000. For invoicing, the option exists to display As many transaction systems do not have a job- charges as a single line item showing the total card to identify account information, the methodol- transaction charges, or as multiple line items based ogy for determining ownership is based on field on individual resources. This option may be values (User ID, Terminal ID, Transaction ID, etc.) selected on a customer account basis, showing only found in the log records. Conversion of these field(s) the level of detail requested by each customer. into valid account numbers is performed by internal KOMAND Transaction Charging Systems and translation tables. A user exit point is provided if an input records supported: external translation table is desired. KOMAND CCS (CICS Charging System) The output from the transaction systems is in • IBM CMF 110 records summary form. If a customer produces one million • Landmark Systems Corp., “The Monitor for CICS transactions per day, these would be summa- CICS” TMON/CICS rized as a single account debit record. Should the • Candle Omegamon 110 records need arise, it is possible to produce a history file that • Boole & Babbage, Inc., MainView for CICS contains individual transaction detail records. A “Common” Rate Table allows the system KOMAND DBCS (DB2 Charging System) administrator to set resource rates for DASD space • IBM 101 or look-alike records (DAMS) and all of the Charging Systems (CCS, ICS, • BMC DB2 Activity Monitor DBCS, UNCS, IDCS, NCS and VMCS) from one • Boole & Babbage, Inc., MainView for DB2 location. KOMAND ICS (IMS Charging System) Transactions may be charged by resources • IBM IMS Type 7 Log Records used, a “flat rate” per transaction, or a combination • Boole & Babbage, Inc., MainView for IMS of the two. KOMAND IDCS (CA-IDMS Charging System) Selected transactions may have the following • KOMAND Generated Records (SMF format) “special” costing options applied: • CA-IDMS Performance Monitor Records • Free – track the resource consumption, but do not apply a charge KOMAND NCS (Host Network Charging System) • IBM NetView Type 39 SMF Records • Drop – do not charge or track this transaction KOMAND VMCS (VM Charging System) • Extra – apply a surcharge to basic resource • IBM VM Log Records charges • Sterling Software VMACCOUNT Records • Fixed – apply a flat rate charge rather than KOMAND UNCS (UNIX Charging System) charge by resource consumed • System “V” UNIX (HP, SUN, AIX) • Connect, processor, disk, print PACE Applied Technology, Inc. • 7900 Sudley Road • Suite 600 • Manassas, VA 20109 • 703.369.3200 • Fax 703.369.4595 •