Further development of the SDM
Further development of the SDM
On 30 October 2017 a further revision of the Integrated Code of Conduct was issued. The roles of the main companies were described as follows:
LzLabs, based in Switzerland, was the main trading entity and the main hub of development activity. Most developers of the SDM were employed or engaged there, and those based at external contractors were ultimately managed from LzLabs;
LzLabs UK, based in the UK, was focused on QA and testing of SDM, as well as having technical sales, customer care and support functions;
Winsopia, based in the UK, was the mainframe test and development house, responsible for discovery work, testing of customer applications in the legacy mainframe environment and of the SDM’s interoperability with the legacy mainframe environment, due diligence on customer applications and data, and development of the z/OS-based tools which accompany the SDM, such as CPX and LMD.
The project roles for the SDM were described as (i) Developers – people working for LzLabs or its contractors who designed, developed and wrote the code for the SDM, including QA working within the development team; (ii) pre-sales, post-sales and support; (iii) QA – people working for LzLab or LzLab UK responsible for internal testing and quality assurance, other than QA personnel working within the development team; (iv) sales, management and other non-technical roles; and (v) Winsopia – responsible for discovery, testing on or interacting with the mainframe, processing of materials from customers’ mainframes, setting customer applications in a mainframe test environment, and development of z/OS-based tools.
Under this revised code, greater freedom was granted to LzLabs, Winsopia and LzLabs UK to communicate with each other, including visits to Winsopia’s premises.
Mr Rastall agreed in cross-examination that there was no supervision of LzLabs employees who visited Winsopia and for several years all passes and badges issued by Ms Wilmot at Winsopia automatically included access to the whole office, including access to the mainframe room. Such visitors included Mr Bleach, Mr Viebrock and Mr Vitale of LzLabs. Although this did not give them direct access to the mainframe, it enabled them to talk directly with those at Winsopia who did have direct access and allowed them to “look over their shoulders” as they used z/OS. There is no evidence that any notes of such discussions were taken, contrary to the requirements in the Codes of Conduct.
By March 2020, the development of the SDM was sufficiently advanced so that the clean room procedures were no longer required, as indicated in a message dated 24 March 2020 from Mr Moores to Mr Cresswell:
“I had a nice discussion with Thilo about managing our legal expenses - including merging companies, eliminating the review process, etc.
I will be surprised if Thilo hasn't had a long chat with Watson by now.
It seems to me that what we needed to do to build SDM is now securely in the can. And Lz has a very nice record to prove perfect reverse engineering & development.
I donno what role Clifford has going forward - but maybe a diminished role is feasible. Obviously you want to keep your terrific long standing relationship.”
Shortly afterwards, on 20 April 2020 a further revised version of the Integrated Code of Conduct was issued. The descriptions of the main companies changed. Winsopia was the mainframe test and z/OS-based tools development house, handling discovery work, testing of customer applications in the legacy mainframe environment and of the SDM’s interoperability with the legacy mainframe environment, due diligence on customer applications and data, and development of the z/OS-based tools which accompany the SDM, such as CPX and LMD. ‘LZ’ was stated to encompass all the other operations of LzLabs and its subsidiaries.
Under this final version of the Integrated Code of Conduct, there was further relaxation of communications between LzLabs and Winsopia, and the requirement for legal oversight was removed.
In mid-2020, the LzLabs UK office was closed and its employees were transferred to Winsopia.
- 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)