Designing for reuse is a common cost-saving technique used in the software industry that can be applied to IRI SortCL (Sort Control Language)-compatible job design. Designing for reuse can result in a smaller inventory of scripts; and reduce script development, maintenance and execution costs.
In part 4 of this five-part series regarding newly added ASN.1 support in the SortCL program central to the IRI Voracity data management platform and its component structured data processing products — IRI CoSort, NextForm, FieldShield, and RowGen — we take a look specifically at their common graphical user interface (GUI) for job design, IRI Workbench.
In the previous article, new support for SortCL-compatible jobs in the IRI Voracity data processing ecosystem for ASN.1-encoded data files was introduced. This article takes a more in-depth look through sample jobs demonstrating various use cases, ASN.1 encoding rules, schema files, and the Protocol Data Units (PDUs) involved with data defined in ASN.1 schemas.
This article is the third of four articles discussing newly added support for Excel files in the core IRI program for structured data definition and manipulation, SortCL.
The names of IRI software products and how they run have at times been a source of mystery, or even confusion, to the uninitiated. This article spells out the pieces and clarifies their interplay, providing a quick primer for prospective users, partners, and new industry analysts.
Production or test data targets, as well as the operational log data, created by SortCL-compatible data manipulation or generation jobs in the IRI Voracity data management platform and its included products (IRI CoSort, NextForm, RowGen, FieldShield and DarkShield) are all machine-readable.
Editors Note, Q2’19: In addition to the method described below, there is now also available to IRI FieldShield (data masking product) or IRI Voracity (data management platform) users a Data Class Database Masking wizard, which can be used if you have pre-classified your data.