Resource Accounting for CICS, DB2,IDMS, IMS and VM
To equitably charge for shared environments such as CICS, DB2, IMS, or CA-IDMS, 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.
COMMON Rate Table – this table allows the system administrator to set resource rates for DASD space (DAMS) and all of the Charging Systems (CCS, ICS, DBCS, UNCS, IDCS, and VMCS) from one location.
Table maintenance may be performed using the KOMAND Information Manager running on a Windows 10, or higher system.
Transactions may be charged by resources used, a “flat rate” per transaction, or a combination of the two.
Any field on the input record may be used to apply “special” costing options to a transaction. These options are as follows:
- 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
Shift accounting is fully supported by the Transaction Charging Systems. Up to three levels of shift accounting may be applied to standard workdays. Weekend and holiday differentials are also supported. Shift/weekend/holiday multipliers may be applied to the entire transaction, or to specific resources within the transaction. The KOMAND Transaction Charging Systems accept as input the standard sub-system SMF or Log records plus records produced by most major monitoring systems.
For invoicing, the option exists to display the sub-system charges as a single line item showing the total transaction charge, 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 records supported:
- KOMAND/CCS (CICS Charging System)
- IBM CMF 110 records
- Allen Systems Group., “The Monitor for CICS” TMON/CICS
- KOMAND/DBCS (DB2 Charging System)
- IBM 101 or look-alike records
- KOMAND/ICS (IMS Charging System)
- IBM IMS Type 7 Log Records
- KOMAND/IDCS (CA-IDMS Charging System)
- CA-IDMS Performance Monitor Records
- Optional User Generated Records (SMF format)
- KOMAND/VMCS (VM Charging System)
- IBM VM Log Records
- VM ACCOUNT Records
Benefits
Lorem ipsum dolor, sit amet consectetur adipisicing elit.
Eum exercitationem pariatur iure nemo esse repellendus est
quo recusandae. Delectus, maxime.
Lorem ipsum dolor, sit amet consectetur adipisicing elit.
Eum exercitationem pariatur iure nemo esse repellendus est
quo recusandae. Delectus, maxime.
Lorem ipsum dolor, sit amet consectetur adipisicing elit.
Eum exercitationem pariatur iure nemo esse repellendus est
quo recusandae. Delectus, maxime.
Lorem ipsum dolor, sit amet consectetur adipisicing elit.
Eum exercitationem pariatur iure nemo esse repellendus est
quo recusandae. Delectus, maxime.