FairCom Corporation
 
FairCom Start PageFairCom ProductsDownloadsDeveloper SupportSales InformationFairCom CustomersFairCom Company InformationContact FairCom

Homebulletgrey.gifeNewsletterbulletgrey.gifVolume 24bulletgrey.gifTransaction Number Rollover

Transaction Number Rollover Continued ...

In Volume 23 of the FairCom eNewsletter, we discussed six byte transaction numbers and how to take advantage of this vast volume of available numbers to greatly increase the life span of your active c-tree data files.

We mentioned that some transaction-intensive applications using older versions of c-tree have experienced exhausting these numbers. With faster and faster hardware, and greater volumes than ever, there are good reasons to migrate to c-tree Plus and c-tree Server V8.14.

Consider a moderately high volume application with 1000 transactions per second:

Transaction Number Limits

  • V6 supports around 1 billion transactions: 1000 tps for ~11.6 days.
  • V8 supports 70 x 1012: 1000 tps for ~2000 years.

FairCom has created a comprehensive white paper describing this limitation of four byte transaction numbers, how to recover when you exhaust your supply of numbers, and how to convert and take advantage of six byte transaction number support. Download this valuable resource today! Six Byte Transaction Number Support

Contact FairCom and put V8 of c-tree Plus and c-tree Server in action today!

Migrate to 6-Byte Transaction #’s in 5 Easy Steps

  1. Relink all client applications with c-tree Plus V8 libraries.
  2. Install a new c-tree V8 Server or newer using recommended practices.
  3. Ensure ALL c-tree Server Transaction Logs (*.FCS) are removed.

    Warning: You will lose all User IDs and passwords when FAIRCOM.FCS is deleted. These can be recreated with the c-tree Server Administration utility, ctadmn.

  4. Ensure all data files have an extended header which allows huge file and six byte transaction numbers. V6 c-tree Plus data files may be converted using the c-tree Plus Conversion utility, ctcv67. Be sure to observe the note below concerning this standalone application.
  5. After starting the new c-tree Server, ensure ALL indices are rebuilt using the c-tree Server. Remember, existing indexes that have not had an appropriate extended header added will be rebuilt with the old four byte number support.

Note: You can use rebuild and other standalone programs linked with c-tree V8 as a single-user library, however be sure the 6 byte transaction number is activated with #define ctFeat6BT in your ctoptn.h file. It is off by default in this operational model.

Founded in 1988 and based in Naperville, IL, Context4 Healthcare, Inc. develops technology solutions for the coding, claims editing, and reimbursement challenges faced by today’s healthcare providers and payors. Their products are used to verify claim data on both sides of the healthcare transaction.

The Context solutions, together with a highly trained and experienced staff, empower healthcare providers and payors to reduce errors, claim denials, resubmissions, write-offs, run-away losses and claim handling costs. Their clients range from healthcare providers trying to ensure accurate claims submission to healthcare payor organizations trying to determine appropriate reimbursement. More than 2,500 physician practices, hospitals, insurance carriers, third party administrators and managed care organizations currently use their software and other products.

Context provides software and data products that help ensure compliant, fair and timely reimbursement. Their experienced and certified staff members build software solutions by analyzing payor reimbursement policies. Their data products are built using advanced statistical approaches and are tailored for ease of integration. The return on investment (ROI) of their products can be measured in weeks.

FairCom Start PageSite MapContact FairComThe FairCom Privacy Policy Your Location: USA | Europe | Brazil | Japan
Copyright 2012 FairCom Corporation. All rights reserved.