DB2 record locking only protects against simultaneous access to a record (row) during a single CICS transaction (and similarly in IMS/DC and other environments).  Since information is normally displayed in one transaction and updated in another, the application programmer is responsible for extending the lock between transactions.  Various techniques are available, all of which involve timestamp processing which Telon will not generate without CASE Integrators techniques.  Quite apart from this, the techniques are fairly complicated, and it is extremely important that every program use exactly the same technique.  Different programs, each using a different valid technique, will not protect each other.

Anything which is an application standard, whether security, PFKey processing, record locking, screen layout standards, or whatever, can be built into Telon rather than taught and enforced on all your programmers.

CASE Integrators has great experience in building these features into Telon in release-independent ways.

Home Page
Back to Consulting
Office Locations and Contact information