Item 51: Justin Bendich (Paragraph 44.6 of the Technical Particulars)
Item 51: Justin Bendich (Paragraph 44.6 of the Technical Particulars)
The allegation is that during a visit to Winsopia in March 2019, Mr Bendich, a developer at LzLabs, was permitted by Winsopia to use its mainframe, in breach of the ICA.
Mr Bendich did not provide a witness statement or give oral evidence. His email of 24 March 2019 describes his visit to Winsopia, during which he described how GTF traces were run on the Winsopia mainframe and compared with similar traces on the SDM:
“GTF (the Generalized Trace Facility) will simply stop after a while, even if you give it plenty of disk space…
Each load module is created from COBOL source code. COBOL's implementation requires each produced load module to include IBM-copyrighted run-time code (CSECTs). By our Code of Conduct, this code is not allowed to enter LzLabs. Therefore, if we want to analyze these traces at LzLabs, we must reliably remove these instructions from the trace. Because the hardware allows only one range, this removal must be performed after the trace is obtained.
The instruction traces also contain IBM-copyrighted DB2 code, some of which resides in the home address space, and some of which resides in the DBM1 address space. I believe the code in the DBM1 address space can be pre-filtered by a suitable SLIP option. We didn't try to do this. With the post-processing software i developed while at Winsopia (see below), it's easy to remove these instructions.”
Professor Weissman concludes from Mr Bendich’s email that he ran GTF traces using the Winsopia mainframe. Mr Stephens agrees with Professor Weissman that Mr Bendich was shown the GTF trace output, and appears to have written a C program to help ‘scrub’ it, but that neither of these would necessarily require access to a mainframe. Neither Professor Weissman nor Mr Stephens were able to find any datasets or user credentials disclosed on the zPDT server that indicated that Mr Bendich had access to the IBM Mainframe.
Mr Bendich sent an email dated 3 May 2019 to Mr Hedley in which he gave an account of his visit to Winsopia, suggesting that the GTF traces might have been run on the mainframe by Mr Maddison of Winsopia, rather than Mr Bendich:
“Bob Maddison, a Winsopia employee, took GTF traces from the mainframe, put them on the thumb drive, and handed it to me so that i could transfer them onto the NUC. I wrote a lot of code which stayed on the Winsopia NUC. I used this code to process the traces, mostly to eliminate extraneous information, including all IBM-written code (see included e-mail, below). None of this code ever left Winsopia. None of the traces, processed or otherwise, ever left Winsopia.”
In cross-examination Professor Weissman fairly accepted that, having regard to the above email, it is possible that Mr Maddison, rather than Mr Bendich, ran the GTF trace on the mainframe.
The evidence is not clear on this issue. It is unfortunate that Mr Bendich did not provide any witness evidence, which prevented IBM from having an opportunity to challenge it. On balance, I am not satisfied that this allegation is established.
- 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)