ERP and the wasted transaction dilemma

Special Forums News, Links, Events and Announcements Complex Event Processing RSS News ERP and the wasted transaction dilemma

07-20-2010

Registered User

26,240, 27

Join Date: Sep 2000

Last Activity: 1 August 2008, 3:09 PM EDT

Posts: 26,240

Thanks Given: 0

Thanked 27 Times in 26 Posts

ERP and the wasted transaction dilemma

by Adrian Bridgwater, ZDNet UK Business transaction-related electronic information flow has spiraled to new heights. Companies operate on the aggregated results of millions of ‘events’ and the prevalence of web services has served to further swell the volumes of data that must be extrapolated, interpreted and processed at any one time. Who has [...]

More...

Linux Bot

View Public Profile for Linux Bot

Find all posts by Linux Bot

Previous Thread | Next Thread

8 More Discussions You Might Find Interesting

1. Programming

Difference between BEGIN TRANSACTION & START TRANSACTION?

What's the difference between BEGIN TRANSACTION vs START TRANSACTION? Also goes for COMMIT TRANSACTION vs COMMIT?

2. UNIX and Linux Applications

CK-ERP (Open Source Edu / ERP / CRM / MRP) v.0.30.1 released

Hi, folks, A new release, v.0.30.1, of CK-ERP, has been posted, at SourceForge.Net, sourceforge.net/projects/ck-erp . New features comprise seven new modules (ck-teacher, ck-counsellor, ck-student, ck-applicant, ck-family, ck-registrar, ck-eduadmin) for deployment within educational...

3. Shell Programming and Scripting

SQLPLUS error output....pls help...wasted all my day.

Code: print "$DB_CONNECT\n@$SQLDIR/SQLFILE.sql $INPUT" | sqlplus -s 2>> $LOGFILE | tee $IDW_HOME/data/supp/OUTPUTFILE1.dat | $PL_HOME/tabify_465.p > $IDW_HOME/data/supp/OUTPUTFILE2.txt 2>> $LOGFILE EXTRACT_RETURN_CODE=$? if then echo "EXTRACT or Tabify FALIED" >> $LOGFILE exit...

4. Shell Programming and Scripting

Append transaction header lines to same transaction's detail lines

Hi guys, I was wondering if someone can give me a hand in helping me append transaction header line in a file at the end of the transaction detail lines. Basically, I have a file that looks like this: FHEAD File1 THEAD TRANS1-blah TDETL HI1 TDETL HI2 TDETL HI3 TTAIL TRANS1-blah THEAD...

5. Red Hat

Patch management dilemma

I've inherited about 10 RHEL 3 boxes that are located in Europe behind a corporate firewall with no access to rhn.redhat.com I've been tasked with patching all of these systems but I ask, Does redhat issue patch bundles? In AIX, there are maintenance levels and Sun has patch clusters available...

6. Solaris

DiskSuite dilemma

Hello, We have this system a SunFire 280R running Solaris 8 Generic_117350-46. It has 2 36GB disks in it. They are mirrored with DiskSuite 4.2.1. When we execute a metastat all the devices report an Okay status, but when we go into metatool everything is in the Critical (maintenance)...

7. UNIX and Linux Applications

Linux based Open Source ERP System - CK-ERP

Hi, folks, I have developed CK-ERP, which is an open source accounting / MRP / ERP / CRM system that runs on top of multiple middlewares. It provides accounting and back office functionalities to SMEs and utilizes the underlying middleware to administer accounts/groups. Details about and...

8. UNIX for Dummies Questions & Answers

A Terminal Dilemma

Hi everyone, I hope this is the right place to ask this question... I have a contract to convert a mainframe/DB2 application to using AIX/Oracle. Everything went fine but we are now running into a terminal problem. With the Mainframe app, the clients had great response time from remote...

LEARN ABOUT DEBIAN

af_transaction

af_transact(3)						    Attribute Filesystem (AtFS) 					    af_transact(3)

NAME

       af_transaction, af_commit, af_abort - a simple transaction mechanism for AtFS

SYNOPSIS

       #include <atfs.h>

       int af_transaction (void)

       int af_commit (void)

       int af_abort (void)

DESCRIPTION

       These functions implement a simple transaction mechanism for AtFS.  A transaction starts with calling af_transaction. All changes to exist-
       ing ASOs performed hereafter have no immediate permanent effect.  They rather get into effect, when  the  transaction  is  ended.   Calling
       af_commit  ends	the  transactions  and causes all changes to be saved to disk. af_abort aborts the transaction without saving the changes.
       These will then be discarded.

       Only modification of the state of existing source ASOs will be deferred. Creation or deletion of ASOs have immediate effect, regardless	if
       a  transaction  is  in  effect  or  not.  Additionally, all operations on derived ASOs (all operations on the derived object cache) are not
       affected by the transaction.

       All archive files that are to be changed when the transaction is finished are locked until the end of the transaction.  The  lock  prevents
       all  other  applications  to perform any modifications on the archive file. You should make sure, that ending a transaction should never be
       dependent on the successful termination of another application (deadlock danger).

DIAGNOSTICS

       Upon error, -1 is returned and af_errno is set to the corresponding error number.

BUGS

       Changes to the contents of busy versions have immediate effect.

AtFS-1.71						     Fri Jun 25 14:33:21 1993						    af_transact(3)

Complex Event Processing RSS News