CICS, DB2, IDMS, IMS, NetView and VM
Resources- and Subsystem-Accounting
To equitably charge for shared environments such as CICS, DB2, IMS, CA-IDMS or NetView, it is necessary to charge at the transaction level rather than the global (region) level. In a VM environment, charging should be at the batch-job or CMS level. To accommodate these charging philosophies, KOMAND has separate charging systems for all of the products shown above.
As these transaction systems do not have a job-card to identify account information, the methodology for determining ownership is based on any character field(s) (User I/D, Terminal I/D, Transaction I/D, etc.) found in the input records. Conversion of these field(s) into valid account numbers is performed by translation tables maintained in the charging system. A user exit point is provided if an external translation table is desired.
The output from the transaction systems is in summary form, i.e. if a customer produces one million CICS transactions per day, these would be summarized as a single account debit. Should the need arise, it is possible to produce a detailed history file that contains one fully costed record per transaction.
A COMMON Rate table allows the system administrator to set resource rates for DASD space (DAMS) and all of the Charging Systems (CCS, ICS, DBCS, UNCS, IDCS, NCS and VMCS) from one location.
Transactions may be charged by resources used, a “flat rate” per transaction, or a combination of the two.
Selected transactions may have the following “special” costing options applied:
- Free – track the resource consumption, but do not apply a charge
- Drop – do not charge or track this transaction
- Extra – apply a surcharge to basic resource charges
- Fixed – apply a flat rate charge rather than charge by resource consumed
Up to three levels of shift accounting may be applied for standard workdays. Weekend and holiday rate differentials are also supported. Shift multipliers may be applied to the entire transaction, or to specific resources within the transaction. The KOMAND Charging Systems accept as input the standard SMF or Log records, plus records produced by most major monitoring systems.
For invoicing, the option exists to display charges as a single line item showing the total transaction charges, or as multiple line items based on individual resources. This option may be selected on a customer account basis, showing only the level of detail requested by each customer.
KOMAND Transaction Charging Systems and input records supported:
- KOMAND/CCS (CICS Charging System)
- IBM CMF 110 records
- Landmark Systems Corp., “The Monitor for CICS” TMON/CICS
- Candle Omegamon 110 records
- BMC Software, MainView for CICS
- KOMAND/DBCS (DB2 Charging System)
- IBM 101 or look-alike records
- BMC DB2 Activity Monitor
- BMC Software, MainView for DB2
- KOMAND/ICS (IMS Charging System)
- IBM IMS Type 7 Log Records
- BMC Software, MainView for IMS
- KOMAND/IDCS (CA-IDMS Charging System)
- KOMAND Generated Records (SMF format)
- CA-IDMS Performance Monitor Records
- KOMAND/NCS (Network Charging System for mainframes)
- IBM NetView Type 39 SMF Record
- KOMAND/VMCS (VM Charging System)
- IBM VM Log Records
- Sterling Software VMACCOUNT Records
- KOMAND/UNCS (UNIX Charging System)
- System “V” UNIX (HP, SUN, AIX)
- Connect, processor, disk, print
This post is also available in German.