Item 32: Db2 Catalog table metadata
Item 32: Db2 Catalog table metadata
Db2 is a relational database software product that provides a database management system in which customers can store information. It is common ground that Db2 versions 10, 11 and 12 were ICA Programs supplied by IBM to Winsopia for use with z/OS.
The Db2 catalog tables are a collection of database tables that are created as part of the Db2 installation process and keep track of objects and resources available within a Db2 system. The Db2 materials include: (i) data provided with the Db2 product or created during installation of Db2 which is identified by the IBMREQD field; (ii) stored procedures in the form of Structured Query Language (“SQL”) statements, which allow programmers to write scripts and internal procedures that are stored in the Db2 catalog; (iii) default parameters and values in the table definitions; and (iv) IBM supplied packages and plans stored as records in the Db2 catalog tables. Mr Bray agreed in cross-examination that a Db2 catalog will always contain some material supplied by IBM.
CPX software copies information from the Db2 catalog when migrating Db2 data to the SDM. The evidence of Mr Palmer and Mr Bray was that Winsopia developed a set of filters so that, when migrating customer metadata and records stored in a Db2 relational database, CPX would exclude any information in the Db2 tables that might relate to IBM or other third-party products.
The experts agreed in their second joint statement that, at least from April 2016, CPX software included filters that were designed to exclude IBM provided objects, such as objects with the IBMREQD field set, when copying information from the Db2 catalog.
IBM’s case is that contemporaneous email exchanges show that, prior to April 2016, CPX filters were ineffective in excluding all ICA Programs and other IBM proprietary material when exporting data to the SDM.
On 27 April 2016 Mr Palmer of Winsopia sent an email to Mr Bray and Mr Rastall at Winsopia, and to Mr Garfield and Mr Wehrli at LzLabs, setting out discussion items for a DMA (CPX) meeting.
In response, Mr Bray sent an email to Mr Palmer, stating:
“To add to your list, there is a changed set of Winsopia DB2 Catalog Table Filters! Previously we were not excluding some IBM tables/programs.”
Mr Palmer updated the items for discussion at the meeting, including the following:
“… DB2 unload JCL catalog table filter syntax changes are required due to some IBM tables not being excluded from the migration payload. These changes will have to be identified and incorporated into the DMA.”
Mr Bray confirmed in cross-examination that before he identified the above issue and created the updated list of filters, the Db2 tables were not filtered and therefore they would be transferred from Winsopia to LzLabs whenever Db2 catalogs were exported.
The Db2 catalog tables contained data that was part of the Db2 supplied program and/or generated by the Db2 program on installation. Such categories of data were component parts of Db2 and constituted an ICA Program for the purpose of the ICA. Further, data stored in the Db2 catalog tables included IBM proprietary material.
It is clear that, when the CPX filter was first introduced, it was ineffective in excluding IBM data in the Db2 catalog tables from the materials intended to be exported to the SDM. However, as the defendants submit, there is no evidence that any such materials were actually transferred outside Winsopia. Mr Swanson confirmed in cross-examination that the experts searched for, but were unable to find, any evidence of any transfer of Db2 catalog resources from Winsopia prior to April 2016.
IBM relies on an email dated 30 March 2016, sent by Mr Palmer to Mr Rastall and Mr Bray at Winsopia and to LzLabs, referring to the migration of a package, including Db2 catalog data. However, the email expressly refers to such data being subject to legal approval to exclude all IBM proprietary rows. This suggests that, at least in this particular case, a manual review was used to remove IBM proprietary data, rather than any reliance on the CPX filter. It does not indicate that IBM Db2 material was sent by Winsopia to LzLabs.
It follows that IBM have not established any breach of the ICA in respect of this item.
- 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)