Section VII - Unlawful means conspiracy
Section VII - Unlawful means conspiracy
IBM’s case is that the defendants combined with each other to achieve the common end of developing the SDM using unlawful means, namely, breaches of the ICA by Winsopia and procurement of such breaches by the other defendants. It is said that the combination was entered into with the intention to injure the claimant, by developing a competitor product which would damage the claimant’s mainframe business, the defendants undertook concerted action consequent upon the combination, knowing that the breaches and procurement of such breaches were unlawful, and the claimant suffered damage as a result of the conspiracy.
The defendants’ position is that none of the necessary elements of the tort have been established and IBM’s case fails on both the evidence and the law. The case is entirely dependent on the breach and procurement allegations but fails with those allegations. There was no combination or agreement to develop the SDM using material and information extracted from the IBM mainframe software in breach of the ICA. IBM has failed to establish the requisite mental element to found its conspiracy claim based on the procurement case. IBM has failed to establish any causal link between the alleged unlawful acts and the loss alleged to have been caused. There was no intention to injure IBM.
Given my findings on breach of the ICA and unlawful procurement above, this additional claim is of limited relevance to the outcome of the case. However, as it has been addressed by the parties, I consider it briefly below.
The pleaded case is as follows:
44A. Further, the Defendants entered into an unlawful means conspiracy to commit breaches of the ICA and/or procure breaches of the ICA. In particular:
44A.1 The Defendants (and each of them) combined with the other Defendants (and each of them) to achieve the common end of developing the SDM using unlawful means. In summary (and as further particularised above):
44A.1.1 The First Defendant developed and marketed the SDM, using information and material that had been passed to it by the Second Defendant in breach of the ICA, and procured breaches of the ICA.
44A.1.2. The Second Defendant breached the ICA in order to assist the First Defendant in the development of the SDM.
44A.1.3 The Third Defendant developed and marketed, and/or assisted the First Defendant in the development and marketing of, the SDM to third parties, knowing it had been and/or would be developed as a result of the Second Defendant’s breaches of the ICA, and procured breaches of the ICA.
44A.1.4 The Fourth and Fifth Defendants were responsible for the operations of each of the corporate Defendants as set out above, and procured the breaches of the ICA.
44A.1.5 As the (ultimate) beneficial owner and controller of each of the Defendants, it is inferred that the Sixth Defendant took the initial decision to develop the SDM via an unlawful scheme requiring breaches of the ICA by the Second Defendant, and was principally responsible for the development of the scheme to achieve these ends. In any event, he was principally responsible for the execution of this scheme, as the ultimate decision-maker throughout the process of developing the SDM. The Sixth Defendant also procured the breaches of the ICA as set out above.
44A.2 The said unlawful means therefore comprised:
44A.2A Breaches of clauses 4.1.2(b), 4.1.3(a) and 4.13(b) of the ICA by the Second Defendant, as set out at paragraphs 23-28 above; and
44A.2B Procurement of the said breaches by the First and Third to Sixth Defendants, which was itself tortious, as set out at paragraphs 29-34F above. Without the said breaches the SDM could not have been developed, for the reasons set out above at paragraph 27.
44A.3 The said combination was entered into with the intent to injure the Claimant, by developing a competitor product which would damage the Claimant’s mainframe business.
44A.4. The Defendants undertook concerted action consequent upon the combination, as set out above.
44A.5 The Claimant suffered damage as a result of the conspiracy, as further set out below at paragraph 46.2.
44B. To the extent relevant, it is averred that the Defendants knew that the breaches and/or procurement of breaches set out above were unlawful.
44C. In the premises the Defendants (and each of them) is liable for the tort of unlawful means conspiracy for such damage as was caused by the Second Defendant’s breaches of the ICA.”
- Heading
- Mrs Justice O’Farrell
- Section II - Background to the dispute
- The SDM
- Hercules
- Neon litigation
- Formation of LzLabs and Winsopia
- The ICA
- SDM development and the clean room procedures
- Launch of the SDM
- Project Eiger
- Further development of the SDM
- Audit request and termination
- Section III - The proceedings
- The Issues
- The factual witnesses
- Section IV - Construction of the ICA
- Approach to construction of the ICA
- Scope of licence
- The ICA Programs
- Customer applications
- Licensed Program Specifications
- Independent software vendors (ISVs)
- Debugging tools
- Restrictions on use of ICA Programs
- Legislative framework
- Berne Convention
- TRIPS
- WIPO
- Software Directive
- Copyright, Designs and Patents Act 1988 (CDPA)
- Applicable legal principles
- Conclusions on ICA
- Section V - Alleged breaches of the ICA
- Disassembly, decompilation and translation
- Item 2: Load Module Decompiler (“the LMD”) (Paragraph 11.2 of the Technical Particulars)
- Item 3: CICS Control Blocks Document (Paragraph 11.3 of the Technical Particulars)
- Item 4: EXEC DLI (Paragraphs 27.18 & 28.19 of RRRAPOC)
- Item 5: IBM Binder Software (Paragraph 11.4 of the Technical Particulars)
- Compiler listings – summary of the dispute
- Item 6: IGZCIVL COBOL runtime module (Paragraph 11.6 of the Technical Particulars)
- Item 7: CICS Translators (Paragraph 20.1-2 of the Technical Particulars)
- Item 8: Floating point rounding rules (Paragraph 20.3 of the Technical Particulars)
- Item 9: IBM PL/1 compiler (Paragraph 20.4 of the Technical Particulars & Paragraph 27 of the POC)
- Item 10: XML Parse statements (Paragraphs 33-38 of the Technical Particulars)
- Item 11: COBOL initialisation, branching and I/O declaratives (Paragraphs 27.4&27.5 RRRAPOC)
- Item 12: PL/I Condition handling (Paragraphs 27.10-27.12 of RRRAPOC)
- Reverse engineering through the systematic use of traces, dumps, slip traps, packet sniffing and other debugging tools techniques – summary of the dispute
- Item 13: CICS-to-CICS communications (Paragraph 28.1 of the Technical Particulars)
- Item 14: AMBLIST analysis of CICS Stubs (Paragraph 28.2 of the Technical Particulars)
- Item 15: Colesoft z/XDC and COBOL initialisation (Paragraph 28.3 of the Technical Particulars)
- Item 16: XDC and IMS (Paragraph 28.4 of the Technical Particulars)
- Additional examples
- Item 17: SLIP Traps and CICS (Paragraph 28.5 of the Technical Particulars)
- Item 18: SLIP Traps and COBOL (Paragraph 28.6 of the Technical Particulars)
- Macros and Copybooks - introduction
- Macros (Paragraphs 32.1-32.9 of the Technical Particulars) – summary of the dispute
- Item 19: DR-3246 (Paragraph 32.1 of the Technical Particulars)
- Item 20: DR-10237 (Paragraph 32.2 of the Technical Particulars)
- Item 21: DR-2753 (Paragraph 32.3 of the Technical Particulars)
- Item 22: DR-2771 (Paragraph 32.4 of the Technical Particulars)
- Item 23: DR-2796 (Paragraph 32.5 of the Technical Particulars)
- Item 24: DR-3280 (Paragraph 32.6 of the Technical Particulars)
- Item 25: DR-4281 (Paragraph 32.7 of the Technical Particulars)
- Item 26: DR-4322 (Paragraph 32.8 of the Technical Particulars)
- Item 27: DR-0847 (Paragraph 32.9 of the Technical Particulars)
- Macros - discussion
- Copybooks (Paragraphs 2.1.1.3 and 32.10-32.12 of the Technical Particulars) – nature of the dispute
- Item 28: DR-715 (Paragraph 32.10 of the Technical Particulars)
- Item 29: DR-753 (Paragraph 32.11 of the Technical Particulars)
- Item 30: DR-756 (Paragraph 2.1.1.3 of the Technical Particulars)
- Copybooks - discussion
- Transferring “unscrubbed” materials
- Item 31:Epiphany
- Item 32: Db2 Catalog table metadata
- Item 33: DSS dump
- Item 34: Kednos
- Item 35: CSECTs deliberately omitted from scrubbing
- Items 36 and 42: Unscrubbed CSECTs
- Items 37 and 40: IMS PROCLIB & DLIBATCH
- Item 38: DFHEI1 module
- Item 39: IGZXANE
- Item 41: IGZXNE3N
- Item 43: CEEBETBL, CEEBLLST, IBMPINPL & CEESG*
- Item 44: DR-4617
- Item 45: DR-171
- Item 46: Scrubbing failures
- Item 47: @@TRGLOC CSECT
- Item 48: PARMLIB & PROCLIB
- Use outside Enterprise and beyond Designated Machine
- Item 49: Brad Taylor (Paragraph 44.2 of the Technical Particulars)
- Item 50: Winsopia Pizzabox (Paragraph 44.5 of the Technical Particulars)
- Item 51: Justin Bendich (Paragraph 44.6 of the Technical Particulars)
- Conclusions on technical breaches
- Section VI - Wrongful procurement of breach
- Applicable legal principles
- LzLabs
- LzLabs UK
- Claims against the directors
- Mr Moores
- Summary on unlawful procurement
- Section VII - Unlawful means conspiracy
- Applicable legal principles
- Knowledge of unlawfulness
- Summary on unlawful means conspiracy
- Section VIII – Audit and Termination
- Validity of audit request
- Validity of termination
- Section IX - Limitation
- Contractual limitation
- Statutory Limitation
- Deliberate concealment
- Finding - section 32(1)(b)
- Finding - Section 32(2)
- Actual or constructive knowledge – legal principles
- Date of knowledge issues
- ICA 2013
- Mr Knight - 2017
- Mr Anzani - 2018
- Conclusions
![HT-2021-000363 - [2025] EWHC 532 (TCC)](https://backend.juristeca.com/files/emisores/logo_yJUntHA.png)